How to Build a Technician Bonus Plan for a Home Service Business
A badly designed bonus plan creates misaligned incentives that cost more than the bonus paid out. Here is the framework for tying tech compensation to the metrics that predict both revenue and quality.
Key takeaways
- Bonusing on revenue alone incentivizes upselling every customer whether appropriate or not
- The right structure combines revenue per day, customer review score, and callback rate rather than any single metric
- A service agreement conversion bonus of $25 per plan signed is specific, measurable, and tied to high-LTV behavior
- The tech should be able to calculate their own bonus without a spreadsheet
A badly designed bonus plan costs more than the bonus itself. The misaligned behavior it creates: unnecessary upsells, rushed callbacks, inflated ticket totals. These erode customer trust and generate downstream costs that rarely show up in the same line item as the bonus paid out.
The goal is a plan that rewards the output you actually want: higher revenue, satisfied customers, clean work, and growing recurring contracts. Here is the framework.
The 3 Misaligned Bonus Designs to Avoid
Bonusing on revenue only. Revenue per job goes up when techs push work that does not need doing. Most customers cannot evaluate whether a recommendation is legitimate. Techs who learn that more revenue equals more money will find revenue. Some of that revenue will be real. Some will be callbacks, inflated repairs, and replaced parts that had useful life left. The 1-star reviews and refund requests eventually follow.
Bonusing on jobs per day. Job volume bonuses create speed pressure. A tech who can fit 8 jobs in a day by cutting diagnostic time short will fit 8 jobs. Callback rates go up. Quality complaints go up. The bonus cost is small; the callback cost is large.
Bonusing only on customer reviews. Review scores alone produce friendly, low-conflict techs who avoid difficult conversations with customers. A tech who avoids telling a customer their unit needs replacement because it might sour the review is not doing their job. Reviews should be in the formula, not the whole formula.
The pattern in all three: a single metric that maps to one part of the desired behavior, while leaving the rest unmanaged.
Text Clint: "what is each tech's revenue per day, callback rate, and review score this month?"
The Right Metrics to Bonus On
The combination that predicts both revenue quality and work quality:
Revenue per day. Not revenue per job. Revenue per day accounts for job mix and prevents the perverse incentive to stretch jobs unnecessarily. Calculate it as total billable revenue divided by days in the field.
Customer review score. Average rating across reviews where the tech was named or assigned. This catches quality signals that do not show up in callbacks (a customer who would not call back but would leave a 3-star review is still a signal).
Callback rate. Percentage of completed jobs that generate a callback within 30 days. This is the clearest proxy for work quality. High revenue with high callback rate means you are paying for volume that generates rework cost. See how to reduce callbacks in field service for the operational levers behind that number.
Use all three. A tech should not be able to hit the bonus by excelling on one metric while the others deteriorate. The bonus pays at or above threshold on all three.
Text Clint: "which techs have callback rates above 8% this quarter?"
Structure Examples by Trade
These are illustrative structures, not universal benchmarks. The thresholds need to be calibrated to your specific operation and market.
HVAC. Weekly bonus of $50 if revenue per day exceeds $1,100 AND callback rate is below 7%. Review score of 4.5 or above is required to be eligible. This structure rewards productive days without creating a quality sacrifice.
Plumbing. $0.50 per verified Google review received in the week (customer named the tech or the CRM job record links to the review). Cap at $30/week. This directly incentivizes the customer interaction quality that produces reviews rather than just asking for reviews.
Residential cleaning. $100/month bonus for zero re-clean callbacks in the month AND an average customer satisfaction score of 4.7 or above. Re-cleans are expensive for cleaning operations; the monthly bonus with a clean record creates a strong incentive to do the job right the first time.
The common structure: a threshold the tech must clear on quality metrics (callback rate, review score) to be eligible, and a revenue threshold that determines the payout level. Revenue gates the upside. Quality metrics gate eligibility. The underlying scoreboard is in technician performance metrics.
Text Clint: "list techs who are eligible for the bonus this week based on revenue and callback rate"
The Service Agreement Bonus
Service agreements deserve a separate, specific bonus because the LTV impact of a signed agreement is disproportionately large.
The right structure: $25 per new service agreement signed at the job, paid monthly. No cap. No eligibility requirement beyond the signed agreement.
Why this works: the benefit is direct and proportional. Each agreement has a defined annual value. The $25 payout is a small fraction of the first-year revenue of a typical agreement. The tech's incentive is aligned with the company's interest. There is no ambiguity about what the metric means. For the upstream program design, see how to start a service agreement program (HVAC).
What to avoid: tiered service agreement bonuses that require a minimum number per month before any payout. Techs who do not hit the minimum feel penalized rather than rewarded. Pay from the first agreement.
Track signed agreements per tech monthly. A tech consistently signing 0 agreements is either not asking or encountering customers with consistently low-maintenance systems. Either way, it is worth investigating.
Text Clint: "how many service agreements did each tech sign this month?"
How to Communicate the Plan so It Works
A bonus plan that the tech cannot calculate on their own does not change behavior. If a tech needs to wait for a paycheck to find out whether they hit the bonus, the plan is not shaping daily decisions the way it should.
The test: can a tech standing in a customer's driveway at 4 PM calculate whether they are on track for the bonus this week? If yes, the plan is simple enough to work. If no, simplify it.
Practical communication steps:
Post the plan in writing with a worked example. Walk through a scenario where a tech hits all three thresholds and show the bonus calculation. Walk through one where the callback rate disqualifies them. Clarity on the disqualifier matters as much as clarity on the upside.
Review the metrics in your weekly dispatch or team standup. If techs never see their own callback rate or revenue-per-day numbers, the bonus is disconnected from behavior. Visibility is what creates the feedback loop. See how to set up employee performance reviews for the parallel formal cadence.
When you change the plan, explain why. Techs who understand that the callback threshold was tightened because rework cost exceeded bonus cost will accept it. Techs who experience a silent change to their compensation will not.
Text Clint: "show me a weekly summary of each tech's bonus metrics in a format I can share with the team"
How Clint Surfaces Bonus Calculation Data
Clint reads your CRM job data to surface the metrics that feed your bonus plan. Revenue per day per tech, callback rates, review mentions by tech name: these are a text away rather than a weekly spreadsheet export. You can check any tech's bonus eligibility at any point in the pay period, not just at month-end when it is too late to coach.
Sources
Frequently Asked Questions
4 questions home service owners actually ask about this.
01Should the bonus be weekly, bi-weekly, or monthly?
Weekly bonuses produce stronger behavioral feedback because the feedback loop is tighter. Monthly bonuses are administratively simpler. For quality metrics like callback rate, monthly is typically more stable because sample sizes are larger. For revenue metrics, weekly works. Many shops run a weekly revenue bonus and a monthly quality-eligibility check.
02What percentage of total compensation should the bonus be?
The base should cover reasonable expected output. The bonus should represent meaningful upside without being so large that a bad month creates financial distress. For field techs, a well-designed bonus typically adds 10-20% to total compensation in good months. If the bonus is more than 25% of total comp, the base is probably too low.
03How do I handle techs who complain the targets are unfair?
Set thresholds from your own data, not industry benchmarks. Pull your median revenue per day and median callback rate for the last 6 months. Set the bonus threshold at or slightly above median. Techs arguing against median performance as an unfair target are arguing against average expectations, which is a performance conversation, not a compensation conversation.
04What if two techs share a job? Who gets the service agreement credit?
Assign the agreement credit to the tech who presented and closed it. If that is unclear, split it evenly. Decide the rule in advance and write it into the plan documentation.
See Clint in action
Clint is the pre-built AI for home service shops. Connect your CRM, email, and phone system in minutes and the agents run on your real data.