How Do I Get My Pest Techs to Sell Mosquito and Termite Add-Ons in 2026?

The two paths: incentive-first versus scorecard-first

Almost every pest operator who wants technicians selling mosquito and termite add-ons ends up choosing between two approaches, and the choice determines what you build first, what you pay for, and how long it takes to see attach rates move.

Path one is incentive-first. You announce a spiff — a flat dollar amount per mosquito program sold, a larger one per termite inspection that converts to a treatment or bait installation — and you let the money do the teaching. The appeal is speed. You can launch an incentive-first program in a single Monday morning meeting. No software, no dashboards, no rollout plan. By Friday you will have data on which techs respond to money and which do not. The weakness is that money alone does not create skill. A technician who has spent six years doing quarterly general pest service has never once had to ask a homeowner for an additional four hundred dollars. Offering that tech thirty dollars per mosquito sale does not teach them the sentence to say when the homeowner says "let me talk to my husband." Incentive-first programs almost always produce a barbell result: two or three natural salespeople triple their income, everyone else stays flat, and within ninety days the owner concludes "my techs just aren't salespeople."

Path two is scorecard-first. You define the full set of behaviors a complete technician produces — route completion and service quality, mosquito program attach, termite inspection offers, rodent exclusion referrals, review requests, callback rate — weight each one, and score every tech on every line. The composite becomes the number that drives coaching conversations, promotion, and eventually pay. The appeal is durability. A scorecard makes the gap visible and specific: this tech runs a clean route but has offered zero termite inspections in six weeks, and everyone including the tech can see it. The weakness is time-to-signal. You need four to six weeks of data before the scorecard means anything, and you need a manager willing to run weekly one-on-ones against it. Scorecard-first without coaching is just a report nobody reads.

The honest answer for most pest operations under thirty technicians is that you run both, sequenced. Scorecard-first alone is too slow to build belief. Incentive-first alone is too shallow to build skill. The sequence that works is: define the scorecard, launch a simple spiff at the same time so techs feel the upside immediately, then let the scorecard drive the coaching that turns the spiff into a repeatable habit. What you should not do is run a third path — the one most shops actually default to — which is "mention it at the morning meeting and hope." That is neither incentive nor scorecard. It is a wish.

There is a fourth consideration that sits underneath both paths: the offer itself has to be sayable. Neither a spiff nor a scorecard fixes an offer that requires the tech to give a five-minute lecture on the biology of subterranean termites. If your mosquito pitch takes ninety seconds and ends with an open-ended question, techs will skip it under time pressure. The tightest programs give the technician one sentence of observation, one sentence of offer, and a closed question. That is a training artifact, not a pay artifact, and it belongs in the rollout regardless of which path you weight more heavily.

How to decide between them

The decision comes down to four inputs: how many technicians you run, how much route density you have, whether your field service software can already report attach rate per tech, and whether you have a service manager with time to coach.

Headcount. Under six technicians, a formal weighted scorecard is often overhead you cannot afford to maintain. You know every tech's habits personally. A simple spiff plus a weekly fifteen-minute huddle where you read the attach numbers aloud does most of the work. Between six and twenty-five technicians, the scorecard becomes essential — you have crossed the threshold where you can no longer hold every tech's performance in your head, and the barbell problem gets expensive. Above twenty-five, you need the scorecard plus real software to compute it, because manual maintenance in a spreadsheet fails within two quarters.

Route density. This is the input most owners underweight. A tech running fourteen stops a day in a dense suburban route has almost no slack. Adding a ninety-second mosquito conversation to every stop costs them twenty minutes, which is a stop and a half. If you have not built time into the route, the incentive fights the dispatch board and the dispatch board wins. Operators who succeed here either trim two stops from the day during peak mosquito season, or they restrict the offer to properties that meet a pre-flagged criterion — standing water visible, dense landscaping, a prior mosquito complaint in the notes — so the tech makes the offer at four stops a day instead of fourteen. Targeting beats volume on a tight route.

Reporting capability. If your field service platform can already tag a work order line item by service type and roll it up per technician, you can build a scorecard this month. If it cannot — if mosquito sales get recorded as a note in a text field — you have a data problem before you have a sales problem, and no incentive will survive the argument about whose sale it was. Fix the tagging first. This is the RevOps half of the job and it is genuinely the part most pest shops skip.

Coaching bandwidth. A scorecard with no weekly conversation attached decays into wallpaper in about five weeks. If your service manager is also dispatching, also handling callbacks, and also running two routes when someone calls out, they do not have coaching time, and you should start with the incentive plus a very small scorecard — three lines, not nine — until you can free up an hour a week.

The concrete numbers behind each option

Numbers here are the ones you should build your own model around, using your actual pricing. The point is the structure of the math, not borrowed benchmarks — your market sets your prices.

The spiff math. Start from your own gross margin on a mosquito program. Take the seasonal contract value, subtract product cost, subtract the labor minutes per treatment across the season, and you have the contribution. A spiff that pays somewhere in the range of five to fifteen percent of first-season contribution is typically large enough to change behavior without eating the reason you sold it. What matters more than the exact percentage is that the number is flat, immediate, and memorable. A technician can hold "twenty-five dollars per mosquito program" in their head at a customer's back gate. They cannot hold "eight percent of adjusted first-year gross contribution net of chemical." Complexity in a field spiff is the same as no spiff.

Termite behaves differently and needs its own structure. A termite inspection is not a sale — it is a lead. The technician who spots mud tubes, a swarm, or damaged trim is generating an inspection appointment that a licensed termite specialist will convert days later. If you pay only on closed termite work, the general pest tech gets paid weeks after the effort, for an outcome they do not control, and they stop looking. The structure that actually works is a two-part payment: a small amount paid immediately for a qualified referral that results in an inspection being scheduled and kept, plus a larger amount paid when the job sells. The first payment is the behavioral driver. The second is the upside. Define "qualified" tightly and in writing — photo evidence of conducive conditions or activity, homeowner agreed to a date — or you will pay for junk referrals within three weeks.

Attach rate is the metric, not revenue. Revenue per tech is contaminated by route mix. A tech assigned to a high-value commercial route will out-earn a residential tech no matter what either of them does. Attach rate — offers made divided by qualifying stops, and sales divided by offers made — isolates behavior from territory. Track both halves. A tech with a low sales-per-offer number needs a coaching conversation about objection handling. A tech with a low offers-per-stop number needs a conversation about time management or belief in the product. Those are entirely different problems and one number hides both.

Set the baseline before you launch. Pull the last full season of add-on sales per technician. That is your control. Whatever program you run, the only honest measure is the change against that baseline in the same season the following year, adjusted for headcount and stop volume. Operators who skip the baseline argue about whether the program worked forever, because there is nothing to argue against.

The weighted scorecard math is simple arithmetic. Composite equals the sum of weight times level across every KPI. List eight or nine lines — route completion, service quality and callback rate, mosquito program attach, termite referral rate, rodent exclusion offers, review requests, customer retention on their book, and safety or documentation compliance. Assign each a weight reflecting current priority. Score each tech one to five per line. Sum the products. A tech at level five on route completion but level one on mosquito attach and level one on termite referrals lands a mediocre composite even though they look great on the dispatch board — which is exactly the visibility you were missing.

Seasonality should move the weights, not the KPIs. In your mosquito window, mosquito attach might carry a weight of five while termite carries two. During swarm season, you flip them overnight. The KPI list stays stable so techs are not relearning the system every quarter; only the weights move, and you announce the move in one sentence at a Monday meeting. This is the single biggest advantage of a weighted matrix over a flat commission table: you re-aim the entire crew in a day without rewriting a comp plan.

Budget for the training, not just the pay. The realistic cost of standing this up is a half-day initial session, then fifteen minutes of role-play at the start of each week for the first six to eight weeks. Multiply that by loaded labor cost and route hours lost, and you have a real number. It is almost always smaller than the cost of a year of flat attach rates, but it belongs in the plan so it does not get skipped when the schedule gets tight.

What the offer actually sounds like on the property

This is the part that separates programs that work from programs that get announced. A pest tech's credibility comes from being the person who found the problem, not the person selling something. Build the offer around that.

The mosquito offer has a natural trigger: standing water and harborage. The technician is already walking the perimeter. The script is an observation, a consequence, and a closed question. Something in the shape of: "While I was checking the back, I noticed the water sitting in the planter bases and the ivy along the fence line — that's where mosquitoes breed and rest during the day. We run a treatment every three weeks through the season that knocks that down. Want me to put you on the schedule starting with next visit?" Three sentences. Ends with a yes-or-no question, not "would you be interested in learning more." The technician does not need to explain active ingredients unless asked.

The termite offer has a different emotional register. Nobody is annoyed by termites the way they are annoyed by mosquitoes — they are frightened by the repair bill. The tech's job is to report the finding factually and hand off. "I saw some mud tubing on the block near the crawl access. That's a sign of subterranean activity and it's worth a proper inspection — I'm not licensed to make that call. Our termite tech can come out Thursday or Friday and do a full inspection. Which works better?" The alternative-choice close on the appointment, not on the treatment. The technician is never selling a termite job; they are selling a Thursday.

Objection handling is exactly three objections, drilled. Price, spouse, and "let me think about it." Do not build a twenty-page objection manual. Write one response to each, three sentences maximum, and drill them in role-play until they are automatic. The single most common failure is the tech who has a great pitch and no response to "how much?" — they stumble, the homeowner senses uncertainty, and the moment closes.

Give the tech something to leave behind. A single card with the program, what it covers, the cadence, and a phone number converts a percentage of the "I'll think about it" group without any further tech effort. It also protects the tech's attribution when the homeowner calls the office three days later.

Do not script a discount. If technicians can discount, some of them will discount every offer to avoid the objection entirely, and your margin on the add-on evaporates. Price authority stays in the office.

Implementation details and sequencing

Rollout order matters more than program design. The most common way this fails is launching pay and training simultaneously to the whole crew, which creates a chaotic first month that everyone remembers as evidence the program does not work.

Weeks one and two: fix the data. Make sure every add-on service type is a distinct line item in the work order, tagged to the selling technician, with a clear rule for who gets credit when the office closes a lead the tech generated. Pull your per-tech baseline for the last full season. If you cannot produce a clean attach rate per technician in a report, stop and fix that before you announce anything. This is the RevOps foundation and skipping it guarantees a comp dispute in month two.

Week three: build the scorecard with your leads, not for them. Take your two or three best technicians and your service manager into a room, list the KPIs, and set the weights together. This costs one hour and buys you the internal advocates who will defend the program when the crew grumbles. Publish the resulting matrix — every tech sees every line, every weight, and their own levels. Transparency is not a nicety here; a hidden scorecard reads as a trap.

Week four: train the offer before you announce the money. Half-day session. Two scripts, three objections, role-play in pairs, and a ride-along commitment from the manager. Announcing the spiff first means techs spend the training thinking about the money instead of the words.

Week five: launch the spiff and the pilot. Run it with a subset of the crew first — the volunteers and the two leads who helped build it — for three to four weeks. A pilot gives you real objections, real script failures, and a small set of wins you can point at when you go crew-wide. It also lets you find the ugly edge cases in credit attribution while the blast radius is small.

Weeks six through ten: crew-wide launch plus weekly cadence. Every Monday, fifteen minutes: read the attach numbers aloud, celebrate one specific win with the exact words the tech used, run one role-play. Every week, the manager rides along with one technician. The weekly cadence is the program. Everything else is scaffolding for it.

Ongoing: audit for the failure modes. Watch for offers-made numbers that spike without sales — that is a tech logging offers they did not make to protect a scorecard line. Watch for cancellation rate on new mosquito programs, which catches over-promising at the gate. Watch for callback rate climbing on general pest service, which means techs are rushing the core job to make time for the pitch. Each of those is a coaching conversation, not a firing, and catching them early is what keeps the program credible.

Adjacent lessons from other route-based trades

The mosquito-and-termite problem is a specific instance of a general one, and the neighboring trades have already run the experiment.

Lawn care faces the near-identical structure: a recurring core service with a natural upsell ladder — aeration, overseeding, grub control, tree and shrub. The lesson lawn operators learned first is that the upsell has to be pre-loaded into the route, not improvised. The techs who sell aeration well are the ones whose dispatch board already flags which properties are due, so the conversation is expected rather than invented. Pest operations can copy this exactly: flag the properties with mosquito-conducive conditions in the notes before the tech arrives, and the offer stops being a cold pitch.

HVAC and plumbing learned the harder lesson about incentives — that a poorly bounded commission on diagnostic work produces upselling that damages trust and generates callbacks. The safeguard those trades adopted is worth importing: pair every sales metric with a quality metric on the same scorecard, weighted heavily enough that a tech cannot win on volume alone. Callback rate, cancellation rate within ninety days, and review score belong on your pest scorecard for exactly this reason.

Pool service contributes the seasonality lesson. Pool techs sell equipment upgrades in a compressed window and go quiet the rest of the year, which taught operators to move weights seasonally rather than run one flat plan. Your mosquito window and your swarm window are the same problem.

The upstream effect worth naming is on hiring. Once selling is a scored, paid part of the job, it belongs in the job posting and the interview. Shops that add the scorecard without changing hiring end up with a crew half-selected for a job that no longer exists. Ask candidates to role-play an offer in the interview. It is a fifteen-minute change that compounds for years.

The downstream effect is on retention and lifetime value. A customer on general pest plus a mosquito program is materially harder to churn than a customer on general pest alone — more touchpoints, more perceived value, higher switching friction. That is the real reason to do this, and it is worth saying out loud to the crew: the add-on protects the tech's own route from erosion.

Related questions

Should I pay a percentage or a flat dollar spiff?

Flat dollar, almost always. Technicians make the offer decision at a back gate with no calculator. A memorable flat number changes behavior; a percentage of adjusted contribution does not, because nobody can compute it in the moment.

Who gets credit when the office closes the lead?

Write the rule before launch. The common structure is a smaller amount to the technician who generated the qualified lead and a smaller amount to the closer, so neither party is incentivized to withhold. Ambiguity here poisons the program faster than a low payout does.

How long before attach rates actually move?

Expect noise for four to six weeks and a readable trend by eight to twelve. Anything you measure inside the first month is mostly the two natural salespeople. Judge the program on the middle of the crew, not the top.

Do I need software or will a spreadsheet work?

A spreadsheet works fine under roughly ten technicians if someone owns updating it weekly. Past that, staleness kills it. The failure is never the math — it is that nobody updated the sheet in three weeks and the crew stopped believing the numbers.

What if a tech flatly refuses to sell?

Distinguish "won't" from "can't." Most refusals are actually fear of the price objection. Ride along, make the offer yourself in front of them twice, and see whether the resistance survives. If it does after a fair coaching window, the scorecard has told you something real about role fit.

FAQ

How do I set the weights on the scorecard the first time?

Do it in a one-hour session with your service manager and your two strongest technicians, not alone at a desk. List the KPIs first, then argue the weights. A reasonable starting shape puts route completion and service quality together at roughly a third to a half of total weight, the seasonal priority add-on as the single largest individual line, and the remaining lines small but non-zero so they stay visible. Write down why you chose each weight, because you will revisit it in ninety days and want to remember the reasoning.

Will my techs push back on being scored?

Some will, and the pushback is usually about fairness rather than the scoring itself. The two things that defuse it are transparency and route normalization. Publish the full matrix so every technician can compute their own composite, and measure attach rate rather than raw revenue so a tech on a thin residential route is not permanently losing to a tech on a dense commercial one. Most crews settle within three or four weeks once they see the math is the same for everyone.

Should the technician quote the termite price?

Generally no. A general pest technician should be selling the inspection appointment, not the treatment. Termite work involves a licensed evaluation, a graph, and a warranty structure the tech is not positioned to explain. Having them quote a number they later cannot honor is the fastest way to lose both the job and the customer's trust. Their sentence is "our termite specialist can come Thursday or Friday."

What do I do about a tech who is great at service but sells nothing?

Keep them and coach them, but be honest with yourself about the timeline. Set an explicit coaching window — eight to twelve weeks with weekly ride-alongs and role-play — and a specific target, like a defined number of offers per week rather than a sales number, because offers are within their control. If offers-per-week does not move at all during that window, the issue is willingness, not skill, and you make a role decision. Do not let it drift for a year.

How do I keep the program from hurting service quality?

Put the quality metrics on the same scorecard with real weight — callback rate, cancellation rate within ninety days, review scores — and audit them monthly. If callbacks on general pest service climb after launch, techs are rushing the core job to make time for the pitch, and the fix is route time, not more pressure. A program that raises add-on revenue while degrading the base book has not made you money.

Does this work for a two-person shop?

Yes, in a simplified form. With two technicians you do not need a nine-line weighted matrix — three or four lines is plenty, and you can set the weights together over coffee. What you still need is the same discipline: a clear offer script, a flat memorable spiff, weekly numbers said out loud, and a baseline to measure against. The mechanics scale down; the habits do not change.

Sources

• https://www.pestworld.org/ — National Pest Management Association, industry standards and technician resources
• https://www.epa.gov/mosquitocontrol — EPA guidance on mosquito control and source reduction
• https://www.epa.gov/safepestcontrol/termites-how-identify-and-control-them — EPA guidance on termite identification and control
• https://www.cdc.gov/mosquitoes/about/index.html — CDC on mosquito biology, breeding sites, and control
• https://extension.psu.edu/subterranean-termites — Penn State Extension on subterranean termite biology and inspection
• https://www.osha.gov/pesticides — OSHA guidance on pesticide-related worker safety
• https://www.sba.gov/business-guide/manage-your-business/hire-manage-employees — SBA guidance on hiring and managing employees
• https://hbr.org/2015/04/motivating-salespeople-what-really-works — Harvard Business Review on sales compensation and motivation
• https://www.servicetitan.com/ — Field service management platform used across pest and home services
• https://www.dol.gov/agencies/whd/flsa — U.S. Department of Labor on FLSA, relevant to bonus and commission structures

Related on PULSE

• How Do I Get My Lawn Techs to Sell Aeration and Fertilization Upgrades?
• How Do I Get My Pool Techs to Sell Equipment Upgrades?
• How Do I Get My Quick-Lube Techs to Sell Filters and Fluid Services?
• Should I open or buy a Mosquito Squad franchise in 2027?
• Should I open or buy a Mosquito Joe franchise in 2027?
• Should I open or buy a Mosquito Authority franchise in 2027?