Playbook · Solo-consultant time tracking
How a Solo Consultant Automates Time Tracking Without Losing the Billable Hours Doing the Work
Auto-capture billable hours from call notes, generate weekly client invoices from tracked time, and reconcile payments without a manual ledger — for the hours a solo consultant actually bills.
Most solo consultants lose two to three hours a week to the part of the job nobody invoices for: jotting down call times at the end of the day, hand-keying hours into a weekly invoice, then reconciling a payment against a personal spreadsheet that quietly drifts out of sync by week three. The work that actually pays is already on the calendar; the hours go to the work around it. The fix is a three-step pipeline from captured-meeting to weekly invoice to reconciled payment — every step one tool you already pay for, chained in Make or Zapier. Wire it up once on a Saturday and the timesheet stops being a second inbox, and the payment-reconciliation step stops being a Sunday-night panic.
Last updated:
Why time-tracking is where the hours actually leak
Delivery is the visible cost — a strategy call, a deliverable written, a Friday afternoon sync to walk through the next-steps doc. Time-tracking is the invisible cost you absorb around it: the ten-minute reconstruction of the morning call at 6pm, the Times New Roman invoice drafted in Notion at 11pm, the half-hour figuring out which Stripe charge maps to which retainer the morning payment hits. Multiply that by twelve client engagements a month and time-tracking is genuinely a week of unbilled time. Unlike delivery, it is also nearly identical every engagement — same retrieval, same row, same reimbursement — which is exactly why it runs on autopilot cleanly.
The 3-step pipeline: auto-capture billable hours from call notes → generate weekly client invoices from tracked time → reconcile payments without a manual ledger
Each step is one tool you already pay for. Auto-capture is a Fireflies or Otter transcript pulled into Notion via Zapier — every call notes the duration, attendees, and the keyword "billable" or "internal" detected from the title. Weekly invoice is a Friday-morning Make routine that reads the past seven days of tagged meetings, groups by client, and emits a Stripe Invoice per client pre-filled with hours and rate. Reconciliation is the same Stripe webhook pinging a Notion ledger row with paid date and method — no spreadsheet, no hand-update, no Sunday-night reconciliation. One trigger per step, all chained in Make or Zapier.
Pick the tools that already pay for themselves
You do not need new software. Notion for the billable-time database, Stripe for invoicing and payment capture, Gmail for the weekly client email, Otter or Fireflies for transcript capture, and the banking login you already use. The orchestrator is the only new line item: a single Make or Zapier seat running the three-step chain, ~$20 a month. Reusing paid-for tools means the pipeline pays back in hours saved the second it goes live, even before you price in faster collection on invoices issued the same day.
Where to keep it personal (the three human touches)
Automation handles the timesheet and reconciliation; humans handle the trust. Keep three touches off-pipeline: the five-minute weekly client summary you write yourself on a Friday afternoon, the mid-engagement check-in unscheduled when a project hits a wall, and the inline note on every invoice that says something a client has not heard before. Those three are what a client mentions three months later when they re-up. The pipeline handles everything that surrounds them — the same Friday-morning invoice, the same Stripe-tax row, the same polite-resend two days after the invoice goes out.
The 90-minute wire-up (no-code recipe)
Block one Saturday morning. Twenty-five minutes: build the billable_time Notion database with two columns — date and billable-or-internal — and prompt the Fireflies or Otter Zap to write to it. Thirty minutes: build the weekly-invoice Make routine, group by client, and template a Stripe Invoice per client pre-filled with hours and rate. Twenty minutes: add the Stripe payment_intent.succeeded webhook back into Notion so the row flips to "paid" without a hand-update. Test once end-to-end on a fake client. By lunch you have replaced two unbillable hours per week of time-tracking and reconciliation with a 30-second background process.
How to know it stuck (a one-metric check-in)
Pick one metric: percent of weekly invoices that reconcile without a hand-update to the ledger. Measure it for your last four weeks by hand; the median is your baseline. After thirty days on the pipeline, re-measure. If the median has not risen by at least twenty points, one step in your chain is leaking — almost always the Fireflies-to-Notion hand-off (missing the billable keyword on titles that say "catchup") or the Stripe-to-Notion webhook (firing on a payment_intent.canceled event that should have been filtered upstream). Fix that single bottleneck and run the pipeline for another month before you tune the rest.
More playbooks
Keep reading
Prefer the playbook in another format? Email us at flux-ai-7@polsia.app.
Share: email a friend.