Walk the office of a mid-market service company on a Tuesday and count the systems. A CRM for sales. A field app for the crews. Accounting software for the books. Each one paid for, each one working roughly as advertised. Then watch what the people are doing. The office manager is retyping a closed job from the field app into an invoice. Someone is copying estimate numbers from a spreadsheet into the CRM. The owner is on the phone relaying a schedule change the software already knows about. The software is fine. The people are the wiring.
That wiring has a name in every other industry: integration. When a manufacturer connects two machines, the connection is engineered, tested, and owned. When a service company connects sales to field to finance, the connection is usually a person with a phone and a good memory. It works, right up until Tuesday gets busy. Then it drops things, and every dropped thing is money.
The leak chain
The money does not leak in one place. It leaks in seven.
In the home-services operations we review, these seven handoffs are useful places to look. They follow a job from first ring to paid invoice.
01
The missed call
A call rings out during a job and goes to voicemail. Whether anyone calls back depends on how the afternoon goes.
02
The slow estimate
A crew measures Tuesday morning. The bid goes out Thursday, because the measurements sat in a phone. The competitor's went out Tuesday.
03
The dead follow-up
The estimate is out, the customer goes quiet, and the chase belongs to whoever remembers.
04
The paper handoff
A finished job travels back to the office as photos in a group text and a ticket riding in a truck until Friday.
05
The Sunday re-entry
The week's numbers get re-keyed into the accounting software by the one person who cannot quit.
06
The aging receivable
An invoice hits day 31 unpaid, and nothing in particular happens that week.
07
The owner as the integration
Stop answering your phone for a week and see how much of the operation stalls. Whatever stalls is running through you.
Six of those are process leaks. The seventh is the one this note is about, because it is the sum of the other six. Every handoff that has no owner and no system defaults to the same fallback: you. The missed call escalates to your phone. The stalled estimate waits for your numbers. The day-31 invoice waits until you feel the cash get tight.
Nobody decided the owner should be the integration. It is just where every unowned handoff lands.
What it costs
Each leak looks too small to fix. Together they set your ceiling.
Put honest numbers on just the first link. These are the published figures we trust enough to cite, sources named:
27% of calls to home-services businesses go unanswered. · Invoca, 2024
Typical shops book about 42% of the calls they answer. · ServiceTitan data, 3,000+ trade businesses, 2022
Published estimates run as high as $1,200 per missed call. · Housecall Pro, 2024
In our own work we assume $200 to $500 per missed call, deliberately under the published estimates, and we still will not let that figure drive a calculation. The missed-call calculator on this site uses your call volume and your average ticket instead, because your number is the only one that matters. The point survives any assumption: the first link alone leaks real money, and there are six more links behind it.
The other six do not come with published studies, and we will not invent statistics for them. You do not need any. You know what a bid that goes out two days late does to your close rate. You know what the Sunday re-entry costs, because you know who does it and what their Monday looks like.
The fix order
Fix what bleeds most among what closes fastest.
The instinct is to attack the seventh leak head on: hire an operations manager, or buy a bigger software suite, and stop being the bottleneck by decree. It does not work, because leak seven is not a link you can grab. It is the shape the other six make. The owner stops being the integration when the handoffs stop routing through the owner, one handoff at a time.
So the order matters. A missed-call text-back rule can often be tested quickly. A written follow-up cadence can begin once one owner and one approval rule are named. The paper handoff is usually the deeper rebuild, because every crew, every form, and every habit touches it; you get to it after the fast leaks stop bleeding. Attack what bleeds most among what can be closed fastest, and let the seventh leak drain as the six upstream of it close.
Score your own chain before you change anything. The 7-leak self-audit asks seven questions, scores them in your browser, and ranks your fix order. No email, and your answers never leave your machine.
The conclusion
The system you are missing is not another app.
None of this argues for more software. Most of the operations we walk already own more software than they use. It argues for one system of record where a job lives from first call to paid invoice, and for handoffs owned by a system instead of remembered by a person. That is what we build, and it is also what a stubborn owner can build without us.
Your software was never the system. The handoffs are the system. Right now, the handoffs are you.
Fair questions
The pushback, answered straight.
Is the software we already bought the problem?
Usually not. Most operations we walk own capable software. The leak is in the handoffs between the tools, where a person re-keys, relays, or remembers. In our blueprints, the verdict for most existing tools is keep or connect, not replace.
Can we close the leaks ourselves?
Some of them, starting this week. A text-back rule for missed calls and a written follow-up cadence with one named owner take discipline more than software. The deep rebuilds, like one job record from call to paid, take more. Score your chain first and work in order.
Written by
Rodrigo Yeo
Founder of Arkode. Builds operating systems for service companies in the US and Mexico.