Do the arithmetic on your own shop for a second. Take the amount a technician typically knocks off when a customer winces — call it forty dollars. Multiply by how often it happens across all your techs in a month. Multiply by twelve.
For most small service businesses that number lands somewhere between a decent used truck and a technician's annual pay, and it appears nowhere in any report. It is not theft, not incompetence, not a pricing problem. It is the accumulated cost of dozens of small, well-intentioned decisions made by people standing in front of a customer with no tool other than the price. Losses of that shape are why attrition stays stubborn — per BLS Business Employment Dynamics data, roughly 20% of new establishments fail within their first year and about half within five, and the cause is almost always money rather than demand.
As of September 2026, most shops under twenty technicians still have no written answer to two basic questions: who is allowed to reduce a price, and by how much. The price book gets rewritten, the price increase gets agonized over for months — and then the new number gets quietly negotiated down in a driveway by a tech nobody ever told they could not do that. A technician discount policy is the control that makes the price book real.
Why techs discount
None of the real reasons are greed, which is why punishing the behavior does not fix it.
The first and biggest is conflict avoidance. A customer goes quiet, sucks their teeth, says "that's more than I thought." The tech is one person in someone's garage with no manager to hide behind, and the cheapest way to end that discomfort costs the company forty dollars and costs them nothing. Most people take that trade every time, and never think of it as spending the company's money.
The second is a genuine close attempt. The tech reads real hesitation, believes the job is about to walk, and reaches for the only lever they have. This one deserves respect — the instinct is correct, the tool is wrong. A tech discounting to save a job needs a better option to offer, not a lecture.
Third is sympathy. The customer is elderly, or a single parent, or clearly having a bad week. This is the hardest to argue with and the easiest to abuse, because "the guy seemed nice" is not a category anybody wants to write a policy against.
Fourth is guilt over the estimate. The job ran long, or the tech had to come back, or a part was wrong. Rather than raise it with the owner, the tech quietly discounts to compensate — converting a fixable operational problem into an invisible revenue loss. That is why callback and rework rate is worth tracking on its own: the callback costs you twice, once in labor and once in the apology discount nobody logged.
Notice that three of the four are conversations, not prices. A discount is what a technician reaches for when they have run out of things to say.
Give techs a real tool, not a blank cheque
The correct response to "my techs discount too much" is rarely "my techs need to stop discounting." It is "my techs need something to offer that is not money."
Tiered options. The most effective substitute is a good-better-best structure, where the tech genuinely moves down a tier rather than shaving the price of the one they quoted. A lower tier does less work for less money — a repair instead of a replacement, a standard part instead of a premium one, a shorter warranty term. The customer keeps agency, the shop keeps margin, and the tech has an answer that is not a concession. Building those tiers is covered in good-better-best option pricing.
A review or referral waiver. Trading a modest, fixed amount for a review the shop actually values is a real transaction, not a giveaway, and it converts the awkward moment into future work — the argument in our guide to getting five-star reviews. Keep it fixed and small; the moment it becomes negotiable it is just a discount with a story attached.
A return-visit price. When the objection is scope rather than cost, splitting the work — do the urgent portion now at full rate, book the rest at a stated price for a later date — keeps today's margin intact and puts a second job on the calendar.
A payment option. Often the objection is not "too expensive" but "not this week." That is a cash-timing problem, and discounting is the wrong medicine for it. A payment plan or financing on a big-ticket job solves the real constraint without touching the price — and beats the usual alternative of discounting and letting the balance ride, given that late and unpaid invoices are among the most commonly reported cash-flow problems for small business owners per Intuit's cash-flow research.
Give a tech those four moves and the reflexive forty dollars stops being the only exit from an uncomfortable silence.
The ceiling and the approval path
Now the control itself, which has exactly two parts: a number a tech can approve alone, and a path for anything above it.
Set the ceiling against real gross margin rather than by feel. If a job carries roughly 45% margin, a 10% discount takes about a fifth of the profit — tolerable now and then, corrosive as a routine. Most small shops settle between 5% and 10%, or a flat dollar cap of comparable size, and the specific number matters far less than the fact that it is written down and applies to everyone identically. A ceiling that exists only in the owner's head is not a ceiling; it is a mood.
Above the ceiling, someone else has to say yes, and the path has to be fast enough that it does not cost the job. A text to the owner answered in two minutes is a functioning approval path. A form emailed to an office that opens tomorrow is not.
| No discount policy | Fixed tech ceiling | Approval required above ceiling | |
|---|---|---|---|
| Margin | Leaks continuously and invisibly | Bounded and predictable per job | Best protected; large concessions are deliberate |
| Close rate | High on price-sensitive jobs, at unknown cost | Holds — techs keep a real move | Slight risk if approval is slow; unaffected if it is fast |
| Tech autonomy | Total, and unsupported | Clear authority within known limits | Autonomy for small calls, backup for big ones |
| Owner visibility | None until margin is already gone | Discount dollars visible per job and per tech | Full — every exception has a name and a reason |
The middle column is where most shops should live day to day, with the third reserved for genuinely large jobs. A ceiling alone, with nothing above it, quietly turns into a floor — techs learn the maximum and start using it as the default, which is a real failure mode worth watching in the monthly numbers.
Record the discount; never just lower the price
This is the part shops skip, and skipping it makes everything above unenforceable.
When a tech types $340 over a $380 book price, the sale record says $340. No discount, no reason, no pattern, no exception — just a smaller number that looks exactly like a correctly-priced cheaper job. You cannot review what was never recorded, and you cannot coach a behavior you cannot see.
There is a bookkeeping argument here as well as a management one. The IRS guidance on recordkeeping expects records that support the income reported on a return, and treats electronic records as satisfying the same requirement as paper. A sale recorded at $340 with no trace of the $380 it started at is a thinner record than one showing both numbers and why they differ.
A discount has to be a line: full book price on top, the concession below it as its own amount, with a reason from a short fixed list. Price objection. Review waiver. Goodwill after a callback. Repeat customer. Four or five options chosen from a list rather than typed as free text, because free text produces strings you cannot sum at quarter end.
The customer benefits too. An invoice showing $380 with a $40 concession says something entirely different from one showing $340 — the first says here is what this is worth and here is what we did for you, the second permanently resets their expectation of your price. Every silent discount trains a customer to expect the lower number next time, which is exactly how a shop ends up unable to make a price increase stick.
Parts discipline matters the same way. Techs who would never cut labor will sometimes drop a part to cost to close a job, which is worse — it eliminates the margin funding sourcing, carrying and warranty replacement, as covered in parts markup and margin. Discounts come off the total as a stated line, never out of a part's price.
Read the report once a month
Once discounts are recorded lines, the review is a five-minute exercise, and it is the whole reason for the recording. The SBA's guidance on managing business finances makes the unglamorous point that income and expenses have to be tracked continuously rather than reconstructed later — and discounts are the expense most small shops never track at all, because they never file themselves as one.
Pull two numbers: total discount dollars for the month, and discount dollars by technician against each tech's revenue. The total tells you the size of the leak. The per-tech split tells you where it is, and it is almost never evenly distributed — most shops find one or two people accounting for the large majority of concessions.
Resist the reflex to treat that as a discipline issue. A tech discounting heavily is usually reporting something true. They may be getting the price-sensitive end of the schedule. They may be quoting a service where your book price genuinely is above market. They may be the one sent to every callback, apologizing with money for someone else's rework. Or they may hate the conversation and never have been given an alternative. Four causes, four different responses — and only one is about the technician.
The comparison worth making is discount rate against close rate. A tech discounting well above average while closing at the same rate as everyone else is giving away money that was not buying anything. A tech discounting more and closing meaningfully more may be worth exactly what they spend. That distinction only exists if you can see both numbers, which is why discount review belongs alongside your operating reports rather than in a one-off spreadsheet built after a bad quarter — and because a discounted job still carries full costs, the honest measure of whether it was worth taking is true profit per job, not revenue.
What your commission plan is quietly telling them
Pay structure sets the default behavior long before any policy does, and most owners have never looked at it from this angle.
A technician on a percentage of revenue spends their own money every time they discount. They will negotiate, hold the price and reach for a tiered option first — not because they read the policy but because the arithmetic is in their pocket. A tech on a flat rate per job loses nothing; the job pays the same either way, and shaving forty dollars is a free way to end an unpleasant moment. Neither structure is wrong, and flat rate has real advantages in predictability. But if you pay flat rate, you have to supply the discipline the pay structure does not.
The failure case to avoid is commission calculated on revenue before discounts, which pays the tech in full on money the business never collected. Calculate on the net collected amount, so a concession costs the person granting it something — the mechanics per technician are covered in technician commission tracking.
Watch the interaction with the ceiling too. If commission is calculated after discounts, a tech giving the full 10% on every job is taking a real pay cut to avoid awkward conversations. That usually turns out to be a training problem rather than a pricing one.
Rolling it out without insulting your best tech
The rollout fails when it lands as an accusation. Techs hear "we are capping discounts" as "we think you have been stealing," and the person most offended is usually your best closer.
Frame it as authority granted rather than removed, because for most shops that is literally true — there was never a stated limit, so nobody had explicit permission for anything. Publish the ceiling, the approval path and the reason list together, and give the alternatives first: build the tiers, agree the waiver amount, set up the payment option, then introduce the cap. A ceiling introduced before the alternatives exist removes the tech's only tool and hands the loss to your close rate instead of your margin.
Then hold the line on consistency. The fastest way to kill a discount policy is for the owner to override it casually for a friend of the family while a tech is being asked to justify twenty dollars. Every technician hears about that within a week.
The bottom line
Margin in a service business rarely disappears in one dramatic event. It leaves in forty-dollar increments, granted by good people handed a price and no other way to survive an awkward pause.
Fix it in four moves. Give techs real alternatives to money off — tiers, a fixed waiver, a return visit, a payment option. Set a written ceiling anyone can approve alone, and a fast path above it. Record every concession as its own line with a reason, so the book price stays intact and the exception stays visible. Then read the per-tech numbers monthly and be genuinely curious about what they say.
Do that and discounting stops being a leak and becomes what it should have been: a deliberate, bounded tool your technicians use on purpose, with the price book behind them instead of against them.
Related reading: Raising prices in a service business · Good-better-best option pricing · Technician commission tracking. For a complete machine-readable feature and pricing reference, see our LLM reference page.