How Do I Get My Pool Techs to Sell Equipment Upgrades?

The job the upgrade scorecard is actually hired to do

Most pool service owners describe this problem as a motivation problem. It almost never is. Ask a route tech why they didn't flag the twenty-year-old single-speed pump groaning next to a leaking heater, and you'll get a version of the same answer every time: nobody asked me to, nobody pays me for it, and the guy after me on the route is going to be annoyed if I make his day longer. The tech is behaving rationally inside the incentive system you built. If the only thing counted is stops completed and chemistry balanced, the only thing produced is stops completed and chemistry balanced.

So the job the scorecard is hired to do is not "make techs more enthusiastic." It's to redefine what the job *is*, in a form that is measurable, visible, and wired to money. That's a very different design brief. Enthusiasm decays in two weeks after a good ride-along. A published matrix that determines the size of the check does not decay.

Concretely, the job breaks into four parts. First, surface the opportunity — a tech standing at a pad three or four times a month has more equipment intelligence than any salesperson will ever get, and today that intelligence dies in his head. Second, make the flag cheap — if reporting a failing pump takes twelve minutes of paperwork at the end of a ten-stop day, it will not happen. Third, score the whole book, not one line — a tech who is a level 5 on recurring cleaning but a level 1 on flagging a variable-speed pump upgrade, a saltwater chlorinator, a new heater, automation controls, or an LED light retrofit should land a *low* composite, not an average one. Fourth, route the lead somewhere it converts — the tech does not have to close. In most well-run shops the tech's job ends at a qualified flag with photos, and a service coordinator or a lead tech runs the quote.

That last split is the single biggest unlock, and it's where most programs die. Owners try to turn service techs into closers. A few techs take to it and the rest quietly opt out, which leaves you with a program that produces revenue from two people and resentment from eight. Score the *flag* — the behavior the tech controls — and let the close belong to whoever's actually good at closing. You can still pay the tech a slice of the sale; you just don't grade them on a conversion rate they don't own.

There's a useful analogue outside pools. HVAC shops solved this a decade earlier with the same structure: the maintenance tech doesn't sell the system replacement, he documents the failing capacitor, the rusted heat exchanger, the twenty-two-year-old condenser, and hands it to a comfort advisor. Same in auto service — the lube tech does the multi-point inspection, the service writer sells the brake job. Pool service is late to this pattern, not exempt from it.

The other quiet piece of the job: protecting the relationship. Route customers see the same tech weekly for years. If that tech starts feeling like a salesman, retention suffers, and retention is the whole business — the recurring book is what makes a pool company worth buying. A good matrix explicitly weights retention and complaint rate alongside upgrade flags, so a tech who bulldozes homeowners into equipment they don't need pays for it in the composite. Upgrade volume without a retention counterweight is how you burn a route.

Building the weighted matrix — the KPI lines, the weights, and the levels

Start by writing down every offer and behavior a complete tech should produce. Most pool routes land on eight or nine lines. A workable starting set:

• Recurring service quality — chemistry within spec, stop completion, callbacks.
• Retention / complaint rate — accounts lost on the route, escalations.
• Equipment condition documentation — photos and age noted on aging pumps, heaters, filters, cleaners.
• Variable-speed pump flags — the highest-value, most defensible upgrade on most routes.
• Heater and chlorinator flags — seasonal, higher ticket, longer sales cycle.
• Automation and LED retrofit flags — lower ticket, high attach rate, easy yes.
• Service plan / membership attach — the thing that compounds.
• Quote-ready handoff quality — did the flag arrive with photos, model number, and access notes, or is the coordinator calling the tech back?
• Small parts and chemical add-ons — the everyday margin.

Now weight them. Weights are a leadership decision, not a tech decision, and they should visibly sum to something clean — 100 points is easiest to explain. A shop that's healthy on retention but starving for upgrade revenue might run recurring quality at 20, retention at 15, documentation at 10, pump flags at 20, heater/chlorinator at 10, automation/LED at 5, membership attach at 10, handoff quality at 5, add-ons at 5. A shop bleeding accounts flips retention to 30 and pulls the upgrade lines down. The weights encode strategy; that's the entire point of them.

Then score each tech 1-to-5 on each line. Define the levels in plain language *before* the first scoring cycle, or you'll get grade inflation and arguments. For pump flags, a defensible ladder looks like: 1 = no flags this period; 2 = flags occasionally, no photos, no model info; 3 = flags consistently on obvious failures; 4 = flags proactively on aging-but-working equipment with photos and age; 5 = level 4 plus the homeowner already understands the energy math before the coordinator calls. Write that ladder once, publish it, and scoring stops being a debate.

Composite = the sum of (weight × level) across all lines. With 100 weight points and a 1-to-5 scale, the theoretical range is 100 to 500. Real crews cluster between 240 and 380, and that spread is the coaching map. What matters is not the absolute number but the *shape* — where somebody is a 5 and where they're a 1.

Three rules keep the matrix honest. Publish it. Every tech sees every line, their own levels, and the ladder definitions. A secret scorecard is just a manager's opinion with arithmetic on top. Set floors. A minimum acceptable level — say a 2 on flagging — on every line, so nobody can specialize their way out of the parts of the job they dislike. A tech who is 5/5/5 on service and 1 on every upgrade line still fails the floor. Re-weight when the world moves. Utility rebate window opens on variable-speed pumps, or a supplier changes heater terms, or spring open-season hits — change the weights overnight, publish the change, and the crew re-aims the next day. Re-weightability is the feature owners underuse most.

Score monthly. Weekly is noise on a route business — a tech might only encounter three genuine upgrade candidates in a week, so weekly scores measure luck. Quarterly is too slow to change behavior. Monthly, with a fifteen-minute one-on-one where the tech sees their own matrix, is the cadence that sticks.

How the upgrade flag moves through the RevOps stack

The scorecard is the measurement layer. Underneath it there has to be a plumbing layer, or you're grading techs on a process that doesn't exist. The flag has to get from a wet concrete pad to a quote to a scheduled install, and every handoff in that chain is a place the lead can die.

The critical design constraint is step D. Capture has to happen at the pad, on the phone, in under sixty seconds. Photo, dropdown for equipment type, dropdown for observed condition, a free-text line. That's it. Anything more and the flag rate collapses — and no amount of scorecard pressure fixes a capture flow that costs the tech his lunch break.

Step F is where most small shops leak. If the flag lives only in the field service work order and never becomes a tracked opportunity with an owner and a next action, it evaporates. This is the ordinary RevOps discipline every sales org already applies to inbound leads, applied to a channel most pool companies don't realize they own: their own route techs are the highest-intent lead source in the business, and they're free.

Step K matters more than it looks. Attribution has to be automatic and visible. If a tech flags a heater in March and the install happens in May, the tech needs to see that revenue land against his name, or he learns that flagging is unpaid work. Set the attribution window generously — ninety days is common, a full season is defensible for heaters — and show it on the scorecard.

One more thing worth wiring: a feedback loop on rejected flags. When a coordinator kills a flag as not viable, that reason should go back to the tech. Techs who never hear back stop flagging; techs who learn that "pump is loud but only four years old" isn't a lead get sharper within a month or two.

What this costs — comp design, tooling, and the real ranges

There are two budgets here and they're independent: what you pay techs, and what you pay for software.

Comp design. Three structures work, and they suit different crews.

*Flat spiff per qualified flag.* Pay a fixed amount — commonly in the $15–$40 range per flag that survives coordinator qualification, regardless of whether it closes. Simple, fast feedback, and it correctly prices the behavior the tech controls. The risk is flag spam, which you control with the qualification gate and by tracking a flag-to-viable ratio on the scorecard.

*Percentage of closed upgrade revenue.* Typically low single digits of the sale — 2% to 5% is the common band — paid to the flagging tech. Bigger upside, better alignment with actual revenue, but slower feedback and it punishes techs on routes with less affluent homeowners.

*Composite-driven bonus pool.* A monthly pool sized as a percentage of upgrade gross margin, split by composite score. This is the structure that most directly rewards the whole book, because a tech can't win the pool on upgrade flags alone if his retention line is a 1. It's also the hardest to explain, so publish a worked example.

Most shops end up with a hybrid: small flat spiff for immediate feedback, plus a composite-driven quarterly bonus for the whole-book behavior. Whatever you pick, the number has to be big enough to notice. A spiff that adds $30 a month to a paycheck buys you nothing; one that adds $200–$400 in season changes how somebody spends their afternoon.

Tooling. The honest answer is you can run this on a spreadsheet for free, and plenty of good shops do — list the KPIs, set the weights, score 1-to-5, let a formula roll the composite. The costs are your time to build it and the very real risk of a stale sheet nobody opens. If you want it maintained without the upkeep, PULSE's free Pulse Check Matrix is this exact model pre-built — define KPIs, weight them, score each tech, get one composite number per tech, browser-only, no login.

Beyond free, the market splits into categories with genuinely different jobs:

• Field service management (ServiceTitan and peers) — priced by custom quote, commonly running into several hundred dollars per technician per month all-in. This is where the raw numbers live: average ticket, close rate, membership sales, upgrade attach, straight off the work order. It won't hand you a weighted matrix, but it's the system of record and the capture surface.
• Scorecard and coaching platforms (Ambition and similar) — custom quote, typically mid-tens of dollars per user per month at scale. Genuinely multi-KPI weighted scorecards piped to TVs and Slack, tied to coaching cadences. Closest paid cousin to the matrix method.
• Gamification and recognition (Spinify, Hoopla) — commonly around $10–$20 per user per month for the lighter tiers, quote-based for others. Leaderboards and competitions. Strong on motivation, lighter on rigorous weighting; pairs with a matrix you define elsewhere.
• Commission and attainment tracking (QuotaPath) — free tier available, paid plans commonly from around $15 per user per month. Tracks attainment across multiple plan components, so you can show each tech how the mix drives their spiff.
• Enterprise incentive comp (CaptivateIQ, Xactly) — custom pricing, built for multi-component plans at scale. Justified once you're multi-location with complex plans and audit requirements; overkill for a single-branch route business.
• General CRM with custom dashboards (Salesforce, from roughly $25 per user per month up) — you build the matrix yourself, but every input is there and the scorecard lives next to the pipeline.

For a shop under about fifteen techs, the sane stack is: your existing field service software for capture, a free weighted matrix for scoring, and payroll for the money. Add a paid scorecard or comp layer when manual scoring genuinely becomes the bottleneck — not before.

Choosing the stack and shortlisting without wasting a quarter

Build the matrix before you shop. This is the step everyone skips and it's the one that determines whether the software helps. Every tool on the market gets better once you know your nine lines and your weights, and several become unnecessary. Spend a week on a spreadsheet with your lead tech and your service coordinator, score last month retroactively, and see whether the composite matches your gut about who your best techs are. If it doesn't, your weights are wrong — fix them before any vendor call.

Then decide where the teeth live. There are only two real answers and you can pick both. *Visibility* — leaderboards, dashboards, public scorecards — works on crews with competitive personalities and a shop culture where a TV in the bay actually gets looked at. *Pay* — commission engines, spiff tracking, composite bonus pools — works on everybody, always, and is the one to build first if you can only build one. Visibility without pay is a poster. Pay without visibility is a mystery check.

Shortlist criteria that actually predict success, in rough priority order:

1. Does it capture at the pad? If the tech's phone can't take the photo and file the flag in under a minute, nothing downstream matters.
2. Can you control the weights yourself? You need to re-weight overnight when a rebate window opens. If changing a weight requires a support ticket, it's the wrong tool.
3. Does it show the tech their own numbers? Not a manager report — the tech's view, on their phone, including the gap to the next level.
4. Does it attribute across time? Flag in March, install in May, credit in May's scorecard.
5. Does it export? You'll want the data in payroll and you'll eventually want it out of this vendor.

Run a genuine pilot before rolling out: two or three techs, thirty to sixty days, with the matrix published to the whole crew but pay unchanged. That does two things — it debugs your ladder definitions cheaply, and it lets the skeptics watch without money on the line. Then turn on pay for everyone at once. Staggered pay rollouts breed conspiracy theories.

Expect a rough first quarter. Flag volume usually spikes in weeks two and three as techs test the system, then drops when the qualification gate rejects the junk, then settles into a real baseline by month three. Judge the program on month four, not month one. Track three health numbers alongside the composites: flags per tech per month, flag-to-viable ratio, and flag-to-close rate. Those three tell you whether the problem is capture, quality, or the coordinator's quoting — three completely different fixes.

Watch the failure modes. Techs who bulldoze homeowners show up as rising upgrade lines and rising complaint rate — that's why retention is on the matrix. Coordinators who sit on flags show up as a collapsing flag-to-close rate with healthy flag volume — that's a sales problem, not a tech problem, and blaming the crew for it will kill the program faster than anything else. And the quiet one: a matrix nobody looks at. If you're not doing monthly one-on-ones with the actual scorecard on the screen, you don't have a program, you have a spreadsheet.

A decision path for picking your structure

The right structure depends mostly on crew size, whether your techs close or hand off, and whether you already have a field service system of record.

Two branches deserve comment. If your techs genuinely close — common in small owner-operator shops where the owner *is* the senior tech — you can score close rate directly, but keep the flag line separate so a tech who quotes rarely but closes everything doesn't look like a star. And the "under 10 techs" branch is not a consolation prize. At that size the matrix is more transparent, not less: everyone sees everyone's lines, the owner knows every route personally, and you can trim to five or six KPI lines if your service menu is narrow. Small crews often get more behavior change per dollar than large ones, because the feedback loop between flag and paycheck is short enough for people to feel it.

The same skeleton transfers, incidentally, to the neighboring trades you may already run or may buy into — landscape maintenance flagging irrigation controllers, HVAC maintenance flagging system replacements, pest control flagging exclusion work. The lines change; the weight-score-composite math doesn't.

Related questions

Should pool techs quote the upgrade themselves or hand it off?

Hand off in most shops. Score the tech on the qualified flag — photos, model, age, access notes — and let a service coordinator or lead tech build the quote. You get better close rates, and you don't lose good techs who don't want to sell.

How much should I pay per upgrade flag?

Either a flat spiff commonly in the $15–$40 range per qualified flag, or 2%–5% of closed upgrade revenue. Whichever you pick, size it so a good month adds a few hundred dollars — small spiffs change nothing.

How often should I re-weight the KPI matrix?

Review monthly, change when strategy changes — a rebate window, a supplier shift, spring open-season. Overnight changes are fine as long as you publish them clearly. Frequent small tweaks keep the crew aimed without confusing them.

What if the flags come in but nothing closes?

That's a quoting problem, not a tech problem. Check flag-to-viable ratio and flag-to-close separately. Healthy volume with a collapsing close rate points at the coordinator, the pricing, or the follow-up cadence — fix that before pressuring the crew.

Does this work for a three-tech company?

Yes, and it's often more effective. Trim to five or six KPI lines, publish the matrix, and score monthly. With a small crew everyone sees exactly where they stand, and the gap between flagging behavior and the paycheck is short enough to feel.

FAQ

What if my techs just refuse to sell anything?

The scorecard makes refusal visible immediately — they score a 1 on every upgrade line and their composite drops well below the crew. Because pay follows the composite, the financial signal arrives without a confrontation. Most techs adjust over two or three pay cycles once they see the ladder and the money. If someone stays at the floor after a quarter of coaching, you have documented data rather than a gut feeling, which makes the decision straightforward either way.

Do I need special software to run this?

No. A spreadsheet with your KPI lines, weights, 1-to-5 scores, and a sum-of-weight-times-level formula does the whole job. Dedicated tools — including PULSE's free Pulse Check Matrix — just save the upkeep and make the scorecard shareable. The method is what changes behavior; the tool only removes friction. Buy software when manual scoring becomes the bottleneck, not before.

Won't pushing equipment upgrades hurt my customer relationships?

Only if you don't measure the downside. Put retention and complaint rate on the matrix with real weight, so a tech who pressures homeowners into unnecessary equipment pays for it in the composite. Framed correctly the flag is a service — a homeowner running a twenty-year-old single-speed pump usually wants to know what a variable-speed swap does to their power bill.

How do I handle a tech who says selling isn't their job?

Redefine the job in writing. The flag — documenting aging equipment with a photo and a model number — is inspection work, not sales work, and it belongs in the role description. Set a floor of a 2 out of 5 on flagging. Anyone below the floor drops their composite regardless of how good their chemistry work is, and the pay difference makes the expectation concrete without an argument.

How long before I see revenue from this?

Expect a noisy first quarter: a flag spike in weeks two and three, a drop when the qualification gate rejects junk, then a real baseline by month three. Heaters and pumps also carry seasonal lag, so credit flags for ninety days or a full season. Judge the program on month four.

What if a tech is excellent at cleaning but terrible at flagging?

That's exactly the pattern the composite is built to expose. A level 5 on recurring service can't carry a composite when the upgrade lines are 1s, and the published matrix shows the tech precisely which line to move. Pair it with a ride-along on the weak line — most flagging deficits are a confidence or a workflow problem, not an ability problem.

Sources

• https://www.energy.gov/energysaver/swimming-pool-pumps — U.S. Department of Energy on pool pump efficiency and variable-speed savings
• https://www.energystar.gov/products/pool_pumps — ENERGY STAR certified pool pump specifications and rebate context
• https://www.servicetitan.com/ — field service management platform for trades
• https://www.quotapath.com/ — commission tracking and quota attainment
• https://www.captivateiq.com/ — incentive compensation management
• https://www.xactlycorp.com/ — sales performance and compensation management
• https://spinify.com/ — sales gamification and leaderboards
• https://www.salesforce.com/ — CRM dashboards and custom reporting
• https://hbr.org/2015/04/motivating-salespeople-what-really-works — Harvard Business Review on sales compensation design
• https://www.phta.org/ — Pool & Hot Tub Alliance, industry standards and education

Related on PULSE

• [How Do I Know Where, When, and How Many People to Schedule at Each of My Multi-Unit Retail Locations?](/knowledge/tl0001)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)
• [How Do I Know How Many Cooks and Servers to Schedule Each Shift at My Pizza Restaurant?](/knowledge/tl0003)
• [How Many Salespeople Should I Schedule Each Day on My Furniture Store Floor?](/knowledge/tl0004)
• [How Do I Decide How Many Reps to Schedule at Each Store in My Mattress Retail Chain?](/knowledge/tl0005)