Pay structure is not a payroll detail. It is the set of instructions you give a technician about what you want them to do when nobody is watching, and most schemes in this trade accidentally ask for the wrong thing.
Here is how the common structures behave, what they really cost, and how to design one that does not quietly manufacture callbacks.
Start with the loaded cost, not the wage
The wage is not the cost. Before comparing any structure, work out what an hour of technician time actually costs you.
On top of the base wage you are paying payroll taxes, workers' compensation, general liability exposure, vehicle cost and commercial auto insurance, fuel, equipment, phone, uniforms, training time and continuing education.
A reasonable planning assumption is that wage plus taxes and insurance lands somewhere around 1.3 to 1.5 times the base rate, before the vehicle. Add the truck and the number moves again. [VERIFY — workers' compensation rates in particular vary significantly by state and classification.]
Then there is utilisation. A technician paid for 40 hours does not bill 40. Subtract drive, admin, callbacks and dead time and you may be at 26 to 30 productive hours — which is why how to route pest control technicians is a pay question as much as a scheduling one. Every 30 minutes of drive you remove is 30 minutes you are already paying for that becomes billable.
Work the real number out before designing anything. It is the floor under every structure below.
Hourly: predictable, and it does not reward rushing
Straight hourly is the simplest and, for a first hire, usually the right answer.
What it does well. Predictable cost per week. Easy for the technician to understand. Critically, it does not reward speed — so there is no financial incentive to skip the interior inspection, thin an application or leave the record until later.
Where it falls down. It does not reward anything either. A technician doing twelve careful stops a day earns the same as one doing seven. Over time that is demoralising for the good one.
Who it fits. Trainees, new hires in their first year, and any route where quality and compliance matter more than throughput — which is most residential pest work.
Per-stop or commission: productive, and it needs guard rails
Paying a fixed amount per completed stop, or a percentage of revenue, aligns the technician's income with output.
What it does well. A motivated technician on a dense route can earn genuinely well, and your cost per stop becomes predictable regardless of how the day goes.
Where it falls down, and this is the important part. Pure piece rate pays for completion, not quality. The behaviours it rewards are: shorter visits, skipped interior checks, thin or late records, and no appetite for the difficult account. All of those produce callbacks, and callbacks are unpaid work — the economics of that are in how to handle callbacks and re-services.
It also creates a compliance risk that is specific to this trade. The application record is the one part of the job with no customer visible waiting for it, so it is the first thing a rushed technician lets slide.
If you use it, pay for the stop only when the record is complete. That single rule removes most of the downside.
Note also that commission and piece-rate structures still have to satisfy minimum wage and overtime law for non-exempt employees, which generally means tracking hours regardless of how pay is calculated. [VERIFY — confirm with a payroll professional for your state.]
The structure most small companies land on
Base hourly at a defensible rate, plus a performance element that is a modest share of total pay rather than the bulk of it.
A worked example for a residential technician:
| Component | Amount |
|---|---|
| Base hourly, 40 hours | Market rate for your area |
| Revenue share above a weekly threshold | 5% of revenue over $4,000 |
| Retention bonus, quarterly | Paid if cancellations on their route stay under a set rate |
| Upsell commission | 10% of first-year value on plans they sell in the field |
Why this shape works. The base makes the week predictable, which matters to somebody with rent. The revenue share rewards a full day without making a thin day frightening. The retention bonus is the clever part: it pays for work that does not generate a callback, which is the exact opposite incentive to piece rate. And field upsells are genuinely incremental revenue the technician is uniquely placed to find — a rodent exclusion spotted in a crawlspace.
Tie the bonus to things the technician controls
This is where most schemes fail. A bonus on total company revenue is meaningless to one technician on one route; a bonus on something they personally determine changes behaviour.
Good candidates:
- Callback rate on their own route
- Retention of accounts on their route — and the levers for that are in how to reduce cancellations on recurring accounts
- Reviews naming them, which is also your cheapest marketing channel
- Record completeness, measured as jobs completed with a full application record on the day
- Upsells sold in the field
Bad candidates: company profit, which they cannot see or influence; and stops per day on its own, which is piece rate wearing a different hat.
Make it calculable by the person being paid
Whatever you choose, the technician must be able to work out their own pay without asking you.
If only the owner can compute it, two things happen. The technician assumes it is being shaved, and the scheme stops motivating anything because the link between effort and money is invisible.
That means the underlying numbers have to be visible: how many stops they completed, what revenue those stops produced, how many callbacks came back to them. PestShift records jobs against the technician who performed them, keeps the price on each job, and reports revenue by period, so "what did my route produce this week" is a question with an answer rather than an argument.
Budget for the full first year
A new technician is not profitable in month one. Training time is your time, their stop count starts low and climbs over months, and early callbacks are a cost you absorb.
Plan for a ramp: materially below target in the first month, approaching it by the third, at it somewhere in months four to six for a trainee. Judge the hire at ninety days on record completeness, callback rate and customer response — not on stops per day in week two. The hiring process itself is covered in how to hire your first pest control technician.
Review pay annually, before somebody asks
Wages move. If yours do not, you train a technician for two years and lose them to a company offering a dollar more.
Set a review month, look at local rates, and raise deliberately rather than reactively. A raise you offer is worth far more than the same raise granted after a resignation letter, and replacing a trained technician costs months of productivity plus the acquisition cost of the accounts that leave with them.
If you are still working out whether you can afford the hire at all, how much to charge for pest control is where the hourly floor comes from, and our own pricing is published — office and admin seats do not count toward the technician limit, so a dispatcher costs nothing extra.