The Pay Structure Is the Job Description
Most owners pick a pay structure based on what they have seen elsewhere, or what is easiest to explain. That is a mistake. How you pay a tech is the single biggest signal about what you actually want from them. Get it wrong and you spend the next six months fixing the problems it creates.
There are three real options: hourly, per stop, and salary plus bonus. Each one works. Each one has a downside. Here is what you need to know before you make a decision.
Hourly Pay
Straightforward to set up. In most markets, an experienced pool tech earns somewhere between $18 and $26 an hour, depending on cost of living and what they can actually do. Someone who can rebuild a pump, diagnose a salt cell, and backwash a DE filter without being told is worth more than someone who adds chemicals and moves on.
The problem with hourly is that you are paying for time, not output. A slow tech is an expensive tech, and there is no pressure in the pay structure to keep pace. If your route has 22 stops and the tech finishes 18 before knocking off, that is four unhappy customers and no obvious consequence for the person responsible.
Hourly works best when you are with the tech every day, or when the work is genuinely variable enough that rushing would be dangerous. If someone is doing a lot of equipment repair and filter tear-downs, hourly makes sense. For straight maintenance stops, it starts to drag.
Per Stop Pay
This is where it gets interesting, and where most owners underestimate the risk.
Per stop pay ties income directly to stops completed. It creates self-motivation. A good tech on a per-stop structure does not need to be pushed. They know that finishing 24 stops instead of 22 means more money, so they move.
Let us work through a real example. Say you charge the customer $110 a month for weekly service. That is roughly $27.50 per visit. You pay the tech $14 per stop. On a 22-stop day that is $308. If they run the same route hourly at $22 and take eight hours, that is $176. The per-stop structure costs you more but aligns incentives, and a motivated tech who does the route in six hours earns more per hour than they would on wages.
The downside is the one nobody talks about clearly enough. Per stop pay quietly encourages rushing. Not dramatically, not obviously, but over weeks it shows up. A 17-minute stop that should include brushing walls, checking the salt cell, and testing both before and after dosing starts coming in at 11 minutes. The chemical numbers pass. The filter looks fine. But the brushing gets skipped. The cell is starting to scale but the tech does not mention it because mentioning it means slowing down.
That is not a character problem. It is a pay structure problem. You built a system that rewards speed and then hoped professionalism would fill the gap.
What to Pair With Per Stop Pay
If you use per stop pay, you need two things working alongside it.
First, a checklist that is actually enforced. Not a list they sign off on and you never look at. A real process with photos, chemical readings logged, and notes on anything flagged. This slows the bad stops down without slowing the good ones. A tech who does the work right is not penalized. A tech who is cutting corners now has to at least lie specifically instead of just moving on.
Some operators use getLucci for this because the stop record lives in the same place as the route, and you can pull up any customer visit and see what was logged. Not a pitch, just a practical reason some people use it.
Second, a quality bonus. Pay per stop as the base, then add a monthly bonus tied to something measurable: customer retention, zero callbacks in the month, or a percentage of upsells on equipment issues they caught and reported. Even $150 to $200 a month is enough to make a tech think twice before skipping the cell inspection.
The combination works because it keeps the efficiency upside of per stop while giving the tech a real financial reason to care about quality.
Salary Plus Bonus
This is the structure that scales best once you trust someone. Set a base salary that covers a standard week, then build a bonus tied to route performance, revenue collected, and customer feedback.
The catch is that it takes more management to set up fairly. You need to define what good performance actually looks like, and you need the data to back up whether they hit it or not. Without that, the bonus becomes arbitrary, and a smart tech figures that out fast.
Salary also gives a tech stability, which matters if you want them to stay. Turnover on a pool route is expensive. Retraining someone who does not know your customers' equipment costs you time and goodwill.
A Practical Starting Point
For a first hire on a straight maintenance route, per stop with a quality bonus is the most common structure that actually holds up. Start the per-stop rate somewhere that gets them to a reasonable hourly equivalent on a normal day, pair it with a logged checklist, and tie a monthly bonus to no callbacks and no lost accounts.
As trust builds and you add repair work to their scope, move toward salary plus bonus. The math gets cleaner and the relationship gets more stable.
There is no perfect pool technician pay rate. There is only the structure that fits what you need the tech to do, and the systems you put around it to make sure the work actually gets done.
If you are building out your first route or adding a second truck and want a simple way to track stops, chemical logs, and customer notes without a lot of setup, getLucci is free for your first 50 pools.