The seven places a service business leaks margin
Most operations don't lose money in one place. They lose it in the joints — and every one of these seven can be spotted from your own chair.
A service business rarely loses money in one dramatic place. It loses it quietly, in the minutes between one system and the next, one person and the next. Those minutes feel free. Added up across a year, they equal salaries.
We audit operations of 10 to 200 people, and the same seven leaks appear in almost every one. Here they are — each with the fastest way to spot it without commissioning anything.
The handoff
Work that is finished by one person and waiting for the next. A confirmed booking sits in an inbox until ops opens it; a signed quote waits for someone to raise the invoice. Nothing is happening to it — it's just waiting. Spot it: follow one job end to end and note every time it changes hands. The waiting usually outweighs the working.
The re-key
The same customer name typed into three systems by three people — each typo a future support ticket. Spot it: ask your team which fields they copy-paste every day. They'll answer instantly, because it's the part of the job they hate.
The after-hours queue
Enquiries that arrive at 11 p.m. and get answered at 9 a.m. — by which time a third have gone elsewhere. Spot it: pull timestamps on last month's lost enquiries and count how many arrived outside office hours.
The follow-up gap
Every lead gets a first reply; almost none get a fifth. The deal doesn't die — it just stops being anyone's job. Spot it: count open conversations in your CRM with no next action scheduled. That number is your quiet pipeline write-off.
The reconciliation
Month-end: invoices matched to contracts by hand, disputes resolved by memory. Two senior people lose a week to it, twelve times a year. Spot it: ask finance what the last three disputed invoices cost to resolve, in hours.
The single memory
What was agreed with a client lives in one person's head and inbox. When they're on leave, the business is too. Spot it: ask "what did we agree with X?" and time how long the answer takes — and how many people it interrupts.
The status chase
Hours spent asking "where is this?" — in stand-ups, in group chats, in walking to someone's desk. It produces nothing; it only locates work. Spot it: search your chat tool for "any update" and count last week's hits.
None of these need heroics to fix. They need arithmetic: price each leak in hours, rank by payback, fix the top one properly, measure it monthly. That's the whole method — and it's why our engagements start with an audit rather than a demo.
Two weeks inside your operation, every leak priced by payback.