Pools-per-Week-per-Tech: Setting the Productivity Benchmark

The Number Nobody Sources

Go to any pool-service group and someone will tell you a tech "should" run 15 stops a day, or 70 a week, or whatever figure they heard last. Push on where it came from and the trail goes cold. There is a reason for that. BLS does not track pool technicians as their own occupation. Techs get counted inside grounds maintenance work, which held about 1.3 million jobs in 2025 across a huge range of roles that have nothing to do with a chlorine tab. IBISWorld can tell you the market is worth $8.8 billion in 2025, but it will not tell you how many pools your Tuesday route should hold.

So the capacity number, the single most important input to whether you should hire, raise prices, or tighten routes, is the one number the whole industry is winging. That is the whitespace. And it is good news, because it means the operator who actually models it has an edge that most of a fragmented, 78,000-shop field will never bother to build.

Why Drive Time, Not Stops, Sets Your Ceiling

Here is the mental model most operators get backwards. They think capacity is a cleaning-speed problem, so they push techs to move faster at the pool. But cleaning time per pool is fairly stable. Skimming, brushing, testing, and dosing take about what they take. The variable that actually swings your day is the gap between stops.

A tech with an eight-hour window has a fixed budget of minutes. Every minute in the truck is a minute not billing. If your average windshield gap between stops is 12 minutes, a tech can chain 18 to 20 stops. Let that gap drift to 35 or 40 minutes because your routes are scattered across town, and the same tech clears 12 without ever "working less." The pools did not get harder. The map did.

That is why the benchmark has to be built from your geography, not copied off a forum. A dense suburban book supports numbers a rural book never will, and neither one is "right." They are just different maps.

Two operators can run identical techs and identical pools and post completely different weekly capacity, because one of them lets drive time eat the day and the other treats the route like the profit center it is.

Build the Benchmark From Loaded Labor Up

A pools-per-week number in a vacuum is a vanity stat. Tie it to money. Start with what a tech actually costs you. Grounds maintenance workers earn a median wage of $19.27 an hour as of May 2025, and your loaded cost sits well above that base once you fold in payroll tax, workers' comp, and the truck. Convert that loaded cost to a per-minute figure.

Now cost every stop honestly. Cleaning minutes plus the drive minutes to and from the stop, times your per-minute labor cost, plus chemicals. Compare that to the revenue for the visit. A stop does not become profitable the moment a tech pulls up. It becomes profitable only when revenue clears loaded labor plus that stop's slice of drive time. Run this for your real routes and you will usually find a tail of stops that look fine on the invoice and lose money on the map, almost always because they sit alone, far from the cluster.

That is your benchmark's foundation. Not "how many pools can a human physically clean," but "how many profitable stops fits inside a tech's day given what your labor costs and how far apart your pools sit." Model it and the operator range most people use, roughly 60 to 100 pools per week per tech, stops being a guess and starts being a target you can defend.

Route Density Is the Lever You Actually Control

Once you accept that drive time sets the ceiling, the growth move is obvious. You do not get bigger by cleaning faster. You get bigger by making the map tighter.

The alternative, adding trucks, is harder than it looks right now. Grounds maintenance employment is projected to grow about 5 percent from 2025 to 2035 with roughly 162,500 openings a year, and every pool operator in your market is fishing the same labor pond. A truck is a purchase. A reliable tech is a recruiting and retention problem you carry every week. With market growth cooling to 2.3% in 2025 against a 4.2% five-year trend, the profit is not going to come from a flood of new stops. It comes from running the stops you already have more tightly.

Recovering three stops a day per tech through better clustering, without lengthening the day, often beats a new hire outright. It adds revenue with zero new payroll line and no truck note.

Where OptimizeIt Fits

The benchmark needs two things: a way to shrink drive time and a way to see actual output per tech. OptimizeIt gives you both. Route optimization compresses the windshield gap so a tech recovers stops without a longer day. Tech productivity tracking shows real stops per tech against your target, so you can see who is dense and who is quietly losing an hour a day to bad sequencing. Scheduling lets you rebuild day-of-week routes around that data instead of habit.

That is the whole loop. Set the benchmark from your loaded labor and drive time, watch actual performance against it, and tighten the routes that miss. Core runs $79 a month, Plus $159, and Pro $239 on annual billing, and you can see the tiers on pricing or start on the pool service page. For the money side of the same problem, the companion piece on per-stop margin and route density goes deeper.

The Honest Take

This is not for the operator who wants a single magic number to post on the whiteboard and call it a day. There isn't one, and anyone selling you "17 pools a day, guaranteed" is selling a number with no source. It is also not for a brand-new one-truck shop still filling the route, where the constraint is demand, not capacity. Come back to this when your routes are full enough that the question shifts from "how do I get more pools" to "how many can this tech actually run at a profit." If you are ready to model that from your own data instead of a forum guess, the benchmark is worth building. If you want a shortcut number, this piece will only frustrate you, and honestly, so will the math.