How a Pest Control Company Designed Pay That Rewards Quality, Not Just Speed

Paying technicians a flat hourly rate is simple, and it is also blind. It pays the technician who treats six homes a day the same as the one who treats four, and it pays the technician whose customers cancel service within a month the same as the one whose customers stay for years. A pest control company had been running its field team almost entirely on flat hourly pay, informally grouped into three rough bands, under $25 an hour, $25 to $30, and above $30, with no real connection between what a technician earned and what they actually produced.

The obvious fix looks simple from the outside: pay technicians a percentage of what they produce instead of a flat rate, and let the incentive do the work. Leadership had a real concern about that fix, though, and it was the right one to have. A pure production-based plan, paid on revenue per hour with no other guardrails, creates an obvious incentive to move fast. A technician trying to maximize revenue per hour has every reason to shorten each stop, skip the parts of the job a homeowner will not notice missing, and move to the next address. Existing quality signals, like callback rate and online reviews, were not reliable enough on their own to catch that kind of quiet corner-cutting before it did real damage to the business.

The Real Design Problem Was Not The Commission Rate

Most pay plan redesigns spend their energy arguing over a single number: what percentage should a technician earn. That was not actually the hard part here. The hard part was designing a plan where the percentage could not be gamed by rushing, because a percentage on its own does not know the difference between a technician who earned their revenue with a thorough job and one who earned it by cutting the service short.

That meant the plan needed guardrails built directly into the pay structure, not policies layered on top of it after the fact that a manager would have to remember to enforce. A guardrail that lives inside the compensation formula gets enforced automatically, every single pay period, without anyone having to catch a problem after it has already cost the company a customer. A guardrail that lives in an employee handbook gets enforced only when someone notices, which in a growing pest control business with technicians running independent routes all day is not often enough.

The company's existing callback-rate data made the risk concrete rather than theoretical. Callback rates across the existing team already ranged from roughly 2% on the low end to 11% on the high end, real technicians on real routes with a meaningful spread in how often a customer needed a second visit. That spread is exactly what a production-only plan risks making worse if speed becomes the only thing pay rewards.

A Three-Level Structure Built On Production, Fenced In By Quality

ShareWillow built the plan around three technician levels, each earning a different share of the revenue they personally produce: 16% for Level 1, 18% for Level 2, and 20% for Level 3 technicians, with every technician guaranteed the higher of that performance pay or their hourly base rate, so nobody's pay could fall below where it started. On top of the base tiers, the plan added revenue-per-day qualifier thresholds at $1,200 and $1,500 a day, with the commission rate stepping up for technicians who consistently clear those daily numbers.

The guardrails sit directly inside that same structure rather than off to the side. A job has to run at least 25 minutes of actual time on service to count toward a technician's production pay at all, which removes the incentive to log a job as complete after a token visit. A technician's cancellation rate has to stay under 1.5% to remain fully qualified for the production tiers, and callbacks carry a direct pay deduction, with a target under 3% and a stretch goal between 0.5% and 1%. Every lever a technician might otherwise pull to inflate revenue per hour at the expense of the actual job has a countervailing cost built into the same formula that pays them.

Testing The Formula Against Real Paychecks Before Anyone Trusted It

A pay formula on a whiteboard is not the same thing as a pay formula that holds up against real payroll. Before rolling the plan out, the company ran its own recent payroll data through the new structure to see what technicians would actually have earned under it, compared to what they earned under the old flat hourly system.

One technician's numbers make the comparison concrete. Across a recent two-week period, that technician worked 87 hours at an hourly rate of $28.50, for a total of $2,479.50 under the old flat-rate system, tied entirely to hours logged, with no connection to what was actually sold and installed on those routes. Over that same period, the technician generated $14,002.60 in production. Run through the new Level 2 tier, at 18% of production, that same period pays out $2,520.47, a modest but real increase for the exact same work, this time calculated from what the technician actually produced rather than simply the hours they clocked.

A second technician's baseline told a similar story: 86 hours worked against $10,734 in production over a comparable stretch. Numbers like these, pulled from actual payroll rather than a hypothetical example, are what let leadership sign off on a production-based plan with confidence instead of a leap of faith. The formula was not just theoretically fair. It was tested against the company's own technicians and its own real numbers before a single paycheck changed under the new system.

Why Testing Against Real Data Matters More Than It Sounds Like It Should

It would have been faster to design the tiers, announce the new plan, and see how the first few pay periods landed. Most companies redesigning pay do exactly that, and most of the time it works out fine. The risk is the times it does not: a formula that looked reasonable on paper turns out to shortchange a specific type of technician, a residential specialist versus a commercial one, say, or someone who works a slower but higher-value route, and the company only finds out after that technician's first disappointing paycheck.

Running real historical data through the proposed formula before launch turns that risk into a design conversation instead of a live incident. If the Level 2 tier had come back paying meaningfully less than the technician's old hourly rate for the same real period, that would have been a signal to adjust the percentage or the tier thresholds before anyone's actual paycheck was affected. Because the test came back showing a comparable or better payout for real, already-worked hours, the company could roll the plan out knowing the math held up against its own team's actual production, not just a hypothetical average technician.

Rewarding More Than Just The Sale

Production tiers and quality guardrails cover the core of the plan, but the full structure reaches further into the behaviors that actually build a recurring pest control business. A conversion-rate bonus rewards technicians for turning inspections into signed service: $25 for a 70% to 85% inspection-to-close rate, $50 above 85%. A $5 spiff for every five-star review gives technicians a small, immediate reason to ask for one on the doorstep instead of hoping it happens on its own. Recurring membership sales pay a 10% commission, while one-time services pay 15%, a deliberate gap that steers technician behavior toward the recurring revenue that actually compounds for a pest control company over time, rather than treating every sale as equally valuable to the business.

What The Guardrails Actually Protect

It is worth being direct about what this story is and is not. The plan above was designed and tested against real payroll data before launch, not measured after months of live results. That distinction matters, and it is exactly why the guardrails were built into the compensation formula itself rather than treated as a policy to enforce separately. A company moving field technicians onto production-based pay for the first time cannot fully know how behavior will shift until the plan is live. What it can control, before day one, is whether the formula itself makes cutting corners a losing move rather than a hidden shortcut.

That is the real value of building the 25-minute minimum service time, the 1.5% cancellation cap, and the callback deduction directly into the pay tiers instead of leaving them as separate rules. A technician chasing a higher revenue-per-day tier cannot get there by rushing jobs, because a rushed job either falls below the minimum service time and does not count, or shows up later as a cancellation or callback that costs money out of the same paycheck the fast work was supposed to pad. The incentive to do the job right and the incentive to earn more stop competing with each other and start pointing in the same direction.

What Other Companies Weighing Production Pay Should Take From This

If your team is still on flat hourly pay because leadership is worried a production-based plan would just teach technicians to rush, that worry is reasonable, and it is solvable without giving up on production pay altogether. The fix is not to avoid paying for production. It is to make sure the formula paying for production also penalizes the exact behaviors that would undermine the work, minimum time on site, cancellation limits, callback deductions, built into the same calculation rather than bolted on afterward.

The story of the HVAC company that discovered its own payout math had quietly drifted from what technicians actually earned makes a related point from a different angle: a pay plan is only as trustworthy as the data and the guardrails underneath it. Testing a new formula against a technician's own real hours and real production before it goes live, the way this pest control company did with $2,479.50 in old pay against $2,520.47 projected under the new tier, is what turns a pay redesign from a leap of faith into a plan a technician can actually trust the day it launches.