The handoffs, not the work
Owners describe the problem as "we're drowning in admin." When we map the week, the admin itself is rarely the issue. Entering a job into the system takes four minutes. The problem is the hour it sat in an inbox before anyone noticed it, the follow-up that never went out because the person who would have sent it was on site, the invoice that waited for a timesheet that waited for a note.
A handoff is any point where work has to move from one person, tool or stage to the next and a human has to notice it. Service businesses have five big ones between a new inquiry and a paid invoice. Each one leaks hours and, worse, leaks revenue, because the customer feels the delay before you do.
Handoff one: inquiry to intake
What breaks: the form submission that sits until morning, the voicemail nobody transcribes, the email inquiry that goes to the one person who is out. The customer who called three companies hires the one that answered.
What a system does: every inquiry, from every channel, lands in one place with the fields filled, the source recorded and a confirmation sent in under a minute, around the clock. After-hours calls get an answer, not voicemail. The owner sees a list of named, qualified inquiries in the morning instead of three hang-ups.
Measure: time from inquiry to first response, by channel. Most companies find it is hours during the day and a full night after it.
Handoff two: intake to scheduling
What breaks: the back-and-forth. "Does Tuesday work?" "No, Thursday." Four emails and a day to book something that should take one click. Meanwhile the estimate that needed a site visit is aging.
What a system does: booking tied to real availability, confirmations and reminders by text, reschedules handled without a person, and the appointment written to the calendar and the CRM at the same time. For quotes and proposals, the follow-up sequence starts the moment the document goes out and runs until it is accepted, declined or dead, so nothing depends on someone remembering.
Measure: quotes with no follow-up after seven days. In the companies we audit it is usually a third of them.
Handoff three: delivery to documentation
What breaks: the work gets done and the record doesn't. Notes live in a technician's head, a lawyer's legal pad, an account manager's email. The timesheet is filled in on Friday from memory. Nobody can say what was delivered without asking the person who delivered it.
What a system does: the record is written as a by-product of the work. Meeting summaries and action items generated from the call and logged. Job completion captured on the phone in the truck, photos attached, status updated. Time captured from the calendar and the tools rather than reconstructed.
Measure: days between work completed and work documented. Every day in that gap is a day the invoice can't go out.
Handoff four: documentation to invoice
What breaks: billing happens in batches, when someone has time, from records that are incomplete, so invoices go out late and wrong and get disputed. Cash sits in the gap.
What a system does: invoices generated from the completed record on a rule (on completion, on milestone, on the first of the month), reviewed by a person for the exceptions, sent the same day. The dispute rate drops because the invoice matches the documentation, because it came from it.
Measure: days from work completed to invoice sent. The number owners quote and the number the system shows are rarely the same.
Handoff five: invoice to collection
What breaks: the reminder that is awkward to send, so it doesn't get sent, and the receivable that ages into a problem. The person who would chase it is the person who also sells, delivers and manages, so chasing loses.
What a system does: a reminder sequence that is polite, on time and automatic, escalating to a person only when it needs to. A list, every Monday, of what is outstanding and what was promised. The awkwardness is gone because nobody had to decide to send it.
Measure: days sales outstanding, and the share of invoices that needed a human touch to get paid.
The order to fix them in
Not the one that annoys the owner most. The one with the most volume and the clearest rules, which is almost always handoff one (inquiry to intake), then handoff two (the follow-up), then four (billing). Three and five follow once the records exist to drive them.
Build one, run it for four weeks without the owner touching it, measure the before and after, then build the next. That cadence is how the 20 hours a week come back in a way that stays back. It is also how a company finds out which of the hires it was planning it no longer needs, which is the number we actually track.
If you'd rather have it mapped for you: the free Revenue-per-Employee Audit takes the hires you're planning, shows what a system absorbs from each, and prices the 90-day build. Written, within three business days.