By Greg Allan, tradesman and creator of Data First Coaching
Why is my mechanic workshop busy but not making money?
Because a full booking sheet measures labour efficiency, not operational efficiency, and those are two different things. Every hoist can be occupied, every technician flat out on diagnostics or a logbook service, and the workshop can still be losing money once every paid hour, not just the billed ones, is counted against it.
Most mechanic workshop owners track whether a job got done and charged. Fewer track what that job actually returned once wages, overhead and every non-billable hour in the place are weighed against it. The job still gets finished, the invoice still goes out, so it feels like the business is doing okay. The bank balance tells a different story.
What is the difference between labour efficiency and operational efficiency in a workshop?
Labour efficiency asks whether a technician's billed hours match the time booked against a job. Operational efficiency asks whether the whole workshop's paid hours, including the apprentice sweeping up, the tech waiting on approval, and the time spent redoing a comeback, are covered by what comes in.
A workshop can hit a strong labour efficiency number on paper, hours billed look close to hours rostered, while operational efficiency is quietly underwater. That gap is invisible on a docket. It only shows up once every paid hour in the workshop, billable or not, gets properly attributed to the work.
Why do comebacks, approvals and apprentices quietly eat the margin?
Because each of these is paid time that produces no billed labour, and in most mechanic workshops that time never gets separated out from the time that does. A comeback means a technician is back on a car they already charged for, redoing work for nothing. A customer sitting on an approval for extra work on a roadworthy or a brake job means a hoist and a tech standing idle mid-booking. An apprentice learning the job on the clock is paid wages against very little billable output while they build skill.
None of that is wrong to carry. A workshop needs apprentices, warranty work happens, approvals take time. The problem is not having those costs sitting on their own, so they get spread silently across every other job instead, making profitable work look thin and genuinely unprofitable work invisible.
Picture a workshop owner who sat down to work out what a job really cost once labour rate, parts margin and overhead were all accounted for. The overhead alone was loading something close to eighty dollars an hour onto every job, which made the whole business look like it was losing money on every car that came through. Strip the non-billable hours straight back out and the number dropped to something that was clearly too low to be true either way. The real figure was sitting somewhere between those two, and he could not find it by eye.
What number actually shows the truth in a mechanic workshop?
The number that matters is the true cost of operations, built from every paid wage hour in the workshop, technicians and apprentices both, set against billable hours actually invoiced, not rostered or booked. That figure, tracked job by job and month by month, is what tells a mechanic workshop owner whether being busy is the same as being profitable.
Memory cannot hold this. An owner remembers the big jobs, the fleet account that paid well, the tyres and brakes work that moved fast. What gets forgotten is the comeback, the half day waiting on a customer's yes for extra work, the apprentice hours against a scan tool diagnosis that took three times as long as it should have. The data does not forget any of it.
How can AI agents fix this without adding more admin?
AI agents can pull wages, overhead and job data straight from the systems a workshop already runs and keep the true cost of operations current, so the owner sees it without anyone in the workshop doing extra paperwork. An AI agent is software that does a job the way the owner would, with their prices, wording and rules, so it works the way this workshop already prices and invoices, not a generic template.
This matters because a mechanic workshop owner's time is already spent between the hoist, the front counter and chasing approvals. Adding another spreadsheet is not the answer. An agent that sits quietly in the background, keeping overhead and non-billable cost in its own bucket rather than spread across every job, means the number stays accurate without becoming another job on the owner's list.
Should I just book in more work to fix it?
No, not on its own. More bookings on top of a workshop that is already leaking paid hours to comebacks, approvals and apprentice time usually just means more of the same leak, at a bigger scale. A data first look at the workshop's own numbers shows whether the fix is more bookings, fewer comebacks, tighter approval turnaround, or better use of apprentice time on the hoist.
Chasing volume as the first move treats the symptom. The booking sheet looks fuller, the stress goes up, and the margin problem is still sitting underneath it, just with more jobs running through the same leak.
How does Data First Coaching approach this?
Data First Coaching starts from the workshop's own job and wages data through the Trade Business Intelligence, not from a conversation about how busy things feel. It looks at true cost of operations against billable hours, job by job, to find exactly where paid time stops turning into margin, whether that is comebacks, approvals, or apprentice hours on the hoist.
Greg Allan built this from his own experience running a trade business where, as he puts it, “the job still gets done, you still charge the money, so you think you're doing okay.” He has also said plainly, “I wasn't tracking profitability on jobs. I was just going, yeah, I made some money there.” The how, working out that number and putting the right agent in the right place, is worked through inside the Academy, with members, because the Trade Business Intelligence is powered by every member, for every member.
