The problem with paying a great tech the same as a mediocre one
Straight hourly pay has one honest virtue: it's simple, and nobody argues about the math. But it also quietly pays your best technician exactly what it pays your worst. The tech who diagnoses cleanly, sells the repair the customer actually needs, finishes without a callback, and leaves the homeowner writing a five-star review takes home the same check as the one who misses the real problem, leaves early, and generates a return trip next week. When effort and outcome earn the same as coasting, coasting is the rational choice — and over a couple of years the ambitious techs figure that out and leave for a shop that pays them for being good.
Performance pay is how you fix that misalignment: you tie some portion of what a tech earns to what they actually produce — revenue sold, jobs closed clean, customers kept happy. Done right, it's the closest thing to a magic lever a service business has, because it turns "work harder because I said so" into "work harder because it's your money too." Done wrong, it turns your trades into commissioned salespeople who oversell scared homeowners, and it poisons the customer trust that took you years to build. The difference is entirely in what you choose to pay for — and that choice is the whole game.
Pay for the outcomes you actually want
The iron rule of any incentive plan is that you get what you pay for — literally, and often in ways you didn't intend. Pay for revenue alone and you'll get overselling. Pay for speed alone and you'll get callbacks. The art is choosing metrics that only go up when the customer and the business both win:
- Sold revenue, but net of callbacks and refunds. Paying a spiff on what a tech sells is fine — as long as a job that comes back as a warranty callback claws the spiff back. That single adjustment is what keeps commission from becoming a license to oversell, because a repair the customer didn't need tends to come back, and now it costs the tech instead of paying them.
- First-time fix rate. Paying a bonus tied to fixing it on the first visit rewards the exact behavior that makes customers loyal and keeps your windshield time down. It's a metric that's almost impossible to game dishonestly — you can't fake a job that doesn't come back.
- Clean closeouts. A small reward for jobs that close with the photos, notes, and completion checklist all done is how you get the paperwork discipline that flat hourly pay never buys you. The tech who documents well is protecting the company; pay them for it.
- Customer-rated satisfaction. Tying a piece of pay to the reviews and ratings a tech generates is the counterweight that keeps a revenue incentive honest — because a pushy upsell tanks the rating, and now the tech feels it.
The pattern is to pay for the bundle of things a genuinely good visit produces — the right repair, sold cleanly, fixed the first time, documented, and appreciated — never for any single number in isolation. A one-metric plan always gets gamed; a balanced one is hard to game because gaming one number wrecks another.
You cannot pay on performance you cannot measure
Here is the practical wall most shops hit: a performance pay plan is only as trustworthy as the data underneath it, and if the numbers come from a shoebox of paper tickets and the tech's own memory, every payday becomes an argument. The tech swears they sold more than the sheet says; the office can't prove otherwise; trust erodes on both sides. A pay plan built on numbers nobody trusts is worse than no plan at all.
This is where the same operational discipline that runs the day also has to feed payroll. In Hosting Field the sold amount, the labor hours logged, and the job's cost and margin all come off the actual job record — the same record the tech worked from and the office invoiced against — so the number the spiff is calculated on is the number everyone already agreed to when the job closed. The performance scorecard that shows callback rate, first-time-fix, and utilization isn't a separate spreadsheet the office maintains to settle pay disputes; it's a read on the same job data. When the pay math traces back to records the tech can see, the plan feels fair — and a plan that feels fair is one techs will actually chase. The software's job here is to make the scoreboard trustworthy; deciding what's on the scoreboard is still yours.
Design it so nobody feels tricked
The fastest way to blow up a pay plan is to make it feel like a trap — a number that moves when nobody's looking, a cap that appears the month someone finally earns big, a formula only the owner understands. A few rules keep it clean:
- Make it simple enough to explain in one sentence. If a tech can't calculate roughly what a job earns them while they're standing on the doorstep, the plan won't change behavior — it'll just confuse people. "You keep X% of the sold repair, minus anything that comes back" beats a nine-variable formula every time.
- Never cap it, and never move the goalposts. The moment a tech earns a big month and you quietly lower the rate or add a ceiling, you've taught everyone that performing well gets punished. That single move undoes years of trust. If the plan pays out more than you expected, that's the plan working — the tech sold more, and you made money on it too.
- Protect the floor. A pure-commission tech has a terrifying week when the schedule is thin or they're stuck on a huge multi-visit job that hasn't closed yet. A base wage under the incentive keeps good people from leaving over one slow stretch, and it keeps the commission from creating pressure to oversell just to make rent.
- Pay the team things too. Not everything good is individual. A shop-wide bonus on hitting a low callback rate or a high utilization ratio keeps techs helping each other instead of hoarding the gravy jobs — because if the plan is purely individual, the incentive to help a struggling teammate is exactly zero.
The goal is a plan a tech would design for themselves if they were being fair — one that pays them well for doing the job right and never punishes them for a slow week or a big month. That's the plan that keeps your best people and pulls your middle ones up.
What to watch
- Callback rate on high-commission techs. The single most important number to watch after you turn on revenue-based pay. If your top sellers also have the highest callback rate, the incentive is driving overselling and the clawback isn't biting hard enough — fix that before it costs you customers.
- Average ticket versus satisfaction. Track sold-per-job against customer ratings together. Rising tickets with steady ratings is the plan working. Rising tickets with falling ratings is the plan quietly turning your techs into people the customer won't call back.
- Pay spread across the team. How far apart the top and bottom earners land. A healthy spread means the plan is rewarding real differences in performance; no spread means it isn't actually incentivizing anything and you're just adding complexity to a flat wage.
Paying technicians on performance is the difference between a shop where the good ones drift away and one where they stay and get better, because for the first time their paycheck moves with their skill. But every incentive is a wish you're making about behavior, and the plan grants it literally — so pay for the whole bundle of a good visit, not one seductive number; build it on job data everyone trusts so payday is never an argument; and design it so a fair tech would sign up for it happily. Get that right and performance pay stops being a gimmick that risks your reputation and becomes the quiet engine that makes your best people want to stay — and your customers glad they did.