By Greg Allan, tradesman and creator of Data First Coaching
What really happens when a mechanic workshop wins a fleet account?
A fleet account looks like the workshop has arrived. A logbook contract, a run of cars and utes rotating through the hoist, bookings filling the diary weeks ahead. But the account itself is not the prize. The real contest is what happens on every single vehicle that comes in under that contract, because that is where the margin is actually won or lost.
Fleet rates are negotiated before the workshop ever sees a car. The labour rate is usually lower than retail, the parts margin often capped, and the fleet manager expects quick turnaround so their drivers are not waiting on their ute or car. That is the deal a mechanic signs up to. What is not agreed anywhere is what happens the moment a service turns up something extra: a worn brake component, a failed roadworthy item, a diagnostics flag the scan tool picks up that was not part of the original job.
Why can a full workshop still come up short on fleet work?
Because busy and profitable are two different things, and fleet work hides the gap better than retail work does. A technician under pressure to keep a fleet vehicle moving will often just do the extra brake job or the extra hour of diagnostics inside the time already quoted, rather than stop and raise it.
On one job that costs a mechanic workshop very little. On a fleet contract it happens car after car, service after service, because the pressure to keep the account's vehicles turning over is constant. The hoist looks fully booked, the apprentice is flat out handing tools to the technician, the diary says the workshop is going well. The bank account tells a different story, because the same small leak has repeated across every vehicle in that fleet for the whole month.
What number actually tells you whether a fleet account is paying off?
Not the number of cars booked in, and not the total invoiced to the fleet account at the end of the month. The number that tells the truth is the gross profit margin on that fleet's work specifically, checked job by job rather than lumped into the workshop's overall revenue.
A workshop owner going on memory will usually say the fleet account is going fine, because the hoist has been busy and the invoices have gone out. That feeling is almost always based on an old picture. Data first is the only way to see whether the labour rate and parts margin on that account are still covering what it actually costs to service those vehicles, once every comeback, every bit of warranty work and every bit of unflagged extra time is counted in.
How do you price a fleet account before you agree to the rate?
Pricing a fleet account has to be worked out before the rate is agreed, not adjusted after the account is already filling the diary. The labour rate and parts margin offered need to be checked against what it genuinely costs your workshop to service that fleet's mix of vehicles, not just what wins the contract against another workshop.
The same discipline applies once the account is running. When a technician finds extra work on a fleet vehicle, a failed roadworthy item, a part close to its limit, that should go back to the fleet contact as a proper variation with options, not a single number slipped onto the invoice. A good, better, best approach, presented clearly and tied to an approval and a booked date for the extra work, protects the margin and keeps the fleet manager informed instead of surprised at invoice time.
How do you stop extra brake and roadworthy work disappearing into the quoted time?
You put something in place right at the point the technician would otherwise keep working without raising it. An AI agent, which is software that does a job the way you would, using your prices, your wording and your approval rules, can sit exactly there: at the moment a job is about to run past the time or parts it was quoted for.
Instead of the technician making a judgement call under pressure to keep a fleet car moving, the agent flags the extra work, builds the good, better, best options in your own pricing, and sends them to the fleet contact for approval before the job continues. Nothing moves forward until the approval and a booked date for the extra work are in. Another AI agent can do the same thing with warranty work and comebacks, matching each one against the original job so the pattern shows up instead of disappearing into next month's accounts.
Is a full booking diary the same as a profitable fleet account?
No, and a full diary can hide a fleet account that is barely paying for itself. Picture a mechanic workshop owner who came off the hoist to run the business and watched profitability take a real hit, then spent a stretch working out where the gap had actually come from.
The fix was not more fleet cars. It was lifting prices across most of the work the workshop did, adding a proper diagnostic time charge and a couple of other line items that used to be absorbed for nothing, and handing the operations manager ownership of gross profit margin as a monthly KPI, reviewed against a revenue target for each technician. The diary did not need to get fuller. It needed to stop leaking on every car that was already in it.
How does Data First Coaching approach this?
Data First Coaching starts with the fleet account's own numbers through the Trade Business Intelligence, not with how busy the hoist looks. It checks gross profit margin on that fleet's work specifically, finds where the gap between quoted time and actual time first opens up, and works out whether the problem is the rate, the approval process, or both. As Greg puts it, “If you haven't allowed for enough time, there's a problem with your pricing.” The how, building the checks and the agents that catch it, is worked through inside the Academy, among members who are open minded, innovative and willing to share what they find, because the Trade Business Intelligence is powered by every member.

