How to scale a pool route past yourself

Alright, so, question I want to start with, because it's kind of the thing underneath everything we published this week. How do you actually know a pool got serviced when you weren't standing there watching it get serviced? Like, you've got a tech out on a route, twenty-something stops, and you're back at the shop or you're on your own route across town, and somewhere in the back of your head there's this little voice going, did that pool on, I don't know, Maple Street, did that one actually get done today. That's the question. And most operators, when they first hit it, they reach for the wrong answer. We'll get to the wrong answer. But that little voice, that's kind of the whole episode, honestly.

So let me back up. This week the blog was, um, it was a lot about the same moment in a pool business, which is the moment you stop being the whole company. You know the one. It's the point where you can't be at every pool anymore because there's just too many of them, so you hire somebody, or you're about to, and suddenly the job kind of changes on you. You're running people who service pools now, you're not just out there servicing them yourself. And that's a completely different job and nobody really tells you that when you start.

And where this really comes at you fast, we had a piece this week on starting a pool business in Florida specifically, and Florida's kind of the extreme version of it. Because Florida, I mean, over a million residential pools, warm basically all year, so the pools don't close for winter the way they do up north. Which sounds great, right, more pools, more money. But what it actually means is your route fills up and keeps filling up, twelve months a year, and you hit the too-many-pools moment quicker than almost anywhere. Oh, and the wrinkle with Florida, which I didn't fully realize, is Florida's one of the few states that actually licenses pool service work itself, through the DBPR, not just construction and repair like most places. So if you're starting there, the license question comes first, before you sell anything, because the whole rest of your plan sort of hangs off the answer.

And there's a pricing thing that comes out of the year-round part too, that I think is worth saying because new operators get it wrong. When the pool never closes, you price each pool to bill fifty-two weeks a year, not, like, per visit whenever you happen to show up. You're selling a year of a clean pool, and you spread that across every week, including the slower winter weeks where you've dialed the service back but you're still out there. And you build in the fact that it's Florida, so, hurricane season, storms dumping debris and knocking chemistry sideways, that's not an emergency you scramble on, that's a normal Tuesday you priced for. The operators who bill year-round and steady are way calmer than the ones who are basically freelancing pool to pool and wondering why the money's lumpy. Anyway. Point being, Florida just gets you to the scaling problem faster. But the scaling problem is the same everywhere.

So okay. The wrong answer. When an owner first gets nervous about whether the work's getting done, the instinct, almost every time, is I'll just track where my guys are. Put something on the truck, put something on the phone, watch the little dots move around the map. And I get it, I do, it feels like control. But it's the wrong tool and I'll tell you why. A dot on a map tells you a truck was parked near a pool. It does not tell you anybody got out, tested the water, brushed the walls, emptied the baskets, dosed anything. You can sit in a driveway for eight minutes and do absolutely nothing. So the location thing gives you this, like, feeling of oversight without the actual information you need. And on top of that it kind of poisons the well with your techs, because now you're the boss who's watching the dots, and good techs, the ones you actually want to keep, they hate that. So you've paid for surveillance and what you bought was resentment and still, still, you don't know if the pool got cleaned.

Here's the thing that does tell you. Every real visit leaves a record. That's the idea I kept coming back to all week, because it showed up in like four different posts wearing four different hats. When a tech actually services a pool, there's a trail. There's readings logged right there at the water, the chlorine, the pH, the alkalinity, whatever the pool needs. There's a checklist that got completed. There's a time stamp, this was done at 2:14. And there's a report that goes out to the customer. So at the end of the day, you don't go check the GPS. You look at the stops, and the ones with a completed record, those got done. And any stop that's got no record by end of day, that one didn't get done. It's that simple. You're not tracking the person. You're checking the work. And the work either left evidence or it didn't.

And once that clicks, it kind of reorganizes how you think about the whole operation, because now the record isn't just this thing you check to feel okay. It becomes the tool you run the business with. So let me walk through how that plays out, because this is where the week's stuff really stacks up on itself.

Start with the routes, because before anybody can leave a record you've got to get them to the right pools in the right order. We had a couple pieces on this, assigning routes and setting up recurring service, and the through-line there is you're building a system that produces the work automatically instead of you sitting down every week going okay who goes where. So, assigning routes. What I'd do, and what the piece laid out, is you carve your service area into zones, geographic zones, and you give a tech a zone. Or a set of days. Not a scattered list of pools all over the county, because then they're just driving all day and you're paying for windshield time instead of pool time. Group the pools that are close together, order the stops inside the zone so they're not backtracking, and, here's the one that trips people up, balance the days by service hours, not by pool count. Because fifteen little residential pools is not the same day as fifteen commercial pools with a bunch of features and a big bather load. Twelve pools might be a brutal day and twenty might be an easy one, depends what's in them. So you balance the hours.

And then keep the tech on the same route. Don't rotate everybody around every week. When a guy runs the same pools over and over, he learns them. He knows this one's got a busted gate latch, he knows the dog on this one, he knows this pool always runs low on chlorine in August because there's a big oak dumping stuff in it. That knowledge is worth real money and you throw it away every time you shuffle the routes. So consistency, on the route side, is not just about the tech's comfort, it's about the quality of the work. And it feeds retention, which, hold that thought, we're gonna come back to it.

The recurring scheduling piece is kind of the other half of that. The idea is you set a frequency per pool, once, and then the visits just, they generate themselves onto the route. So this pool's weekly, service day Tuesday, and every Tuesday from now on it shows up on the route without you booking it. Instead of treating every visit like a fresh appointment you have to schedule. And you set that cadence by season, weekly through swim season when the pool's getting used hard and the sun's eating your chlorine, and then you scale it back, biweekly, in the cooler months when the pool's just kind of sitting there. Set it once per customer, adjust it seasonally, done. And the reason that matters for the whole record idea is, if the visit's already on the route, then a missing record actually means something. Like, the system expected a visit there today, and there's no completed record, so now you know to go ask. If you're booking everything by hand you don't even have a clean expectation to check against.

And the recurring setup is also what makes the messy stuff, the skips and the holidays and the reschedules, not blow up your week. Because a skip, when the visit's already on the route, a skip is a thing you record and move, not a thing that just silently vanishes. Customer's out of town and doesn't want service, or it's a holiday and you're not running, you note it, the visit's marked skipped, and it's still visible so nobody's wondering later whether that pool got missed or got skipped on purpose. There's a difference and the record holds it. Same with reschedules, you bump the day, the system knows, the next one still generates on the normal cadence. The alternative, where every skip and holiday is you manually remembering to not send somebody and then manually remembering to catch it up, that's, that's how pools fall through the cracks. And which, by the way, connects to the thing every operator dreads, which is, what do I do when a tech's out sick. A guy calls in and now a whole zone of pools has nobody. And this is where the zoned routes really earn their keep, because if the routes are geographic and clustered, covering for a sick tech is, you hand somebody the whole zone for the day, or you split it clean between two people by area. It's a bad day but it's a manageable bad day. If your routes are scattered lists of pools all over the map, covering for one person is a nightmare, you're basically rebuilding the day from scratch. So the structure you set up when everything's calm is exactly the thing that saves you when it's not.

Okay so now you've got techs on consistent zoned routes, visits generating automatically, and every completed visit dropping a record. Now managing multiple techs gets, honestly, a lot less painful. We had a piece on this too and the big unlock is you stop managing by calling around. You know the, the operator who's constantly on the phone, hey did you finish, hey where are you, hey did you get to the Hendersons. That's exhausting and it doesn't scale and it makes you the bottleneck. Instead, you set one service standard, this is what a serviced pool looks like at our company, every tech does it the same way, and then the completed-visit records show you who did what. You're not hovering. You just look at the record. Did the readings get logged, did the visit get completed, did the report go out. And you can look at productivity that way too, but, again, by service hours, not just raw pool count, because the guy doing the big commercial accounts is gonna have fewer stops and be working just as hard as the guy banging out twenty little backyard pools.

And I'd throw in, because the piece made this point and I think it's right, the records also protect your good techs. Because when you can see the actual work, you can see who's genuinely good, and you can pay them for it and give them feedback that's based on something real instead of a vibe. Techs leave when they feel micromanaged and unseen. The record kind of solves both at once, it lets you back off the hovering and it lets you actually see the work. So you keep your good people, which, in this business, with how hard it is to hire, is like half the game.

And I want to actually sit on the keeping-good-techs thing for a second, because I think it's underrated how much of running a crew is just not losing the people you've already trained. A good pool tech takes months to get good. They've got to learn your standard, learn the routes, learn the pools, build up the customer relationships. And then if they walk because the pay's stagnant or they feel like a robot being watched on a map all day, you're back to square one, you're hiring and training again, and meanwhile the pools they knew are getting a stranger who doesn't know the busted gate latch or the dog. So what I'd do, and this is straight out of the piece, is you pay clearly, like, the tech knows how they make more money and it's not a mystery. You give steady feedback, small and often, not a big scary annual review. And you give people somewhere to go, a lead tech role, a route they own, training a new hire, something, so the good ones can see a next thing. It's not soft stuff, it's, it's the cheapest retention there is, because keeping a tech you've got is a fraction of what it costs to replace them, same math as the customers honestly.

Now here's where the record turns outward, and this is the part I think a lot of operators sleep on. That same record, the one you're using internally to know the pool got done, it's also the single best thing you can put in front of the customer. We had a piece this week on what actually goes in a service report, and the short version is, specific beats vague every single time. A good report shows the date and time you were there, the water readings you took, the chemicals you added and how much, the cleaning and the equipment checks you did, and if you found a problem, a photo of it, and then what the customer should expect or do next. And on the readings, list the real ones, the free chlorine, the pH, the alkalinity, with the actual numbers, not just "water looks good," because the numbers are the proof you actually tested and they build into a history. If there's ever a question later, a liability thing, somebody got a rash, the water went cloudy, you've got a dated record of the chemistry on every visit, and that has saved operators from claims that weren't their fault. Same with the chemicals, say how much you added, not just "added chlorine," because the dose tells you later what was going on with that pool. And the photo thing, I want to sit on that for a second, because a photo does the work that a number just can't. You can write "skimmer basket cleaned" and the customer's eyes glaze over. You send a before-and-after photo of a basket that was packed full of leaves and now it's clean, and now they get it, now they can see what they're paying for. A picture of the sparkling water. A picture of the one tile that's cracked so they know it's coming. That's the stuff that makes a customer feel like something happened at their house today.

And I know what some of you are thinking, because it's the first thing everybody thinks when I say send a detailed report after every visit, which is, great, more paperwork, I'm already slammed, when am I supposed to write all that up. And the answer, and this is the part that I think is genuinely kind of elegant, is you don't write it up. The report is built from the record the tech's already leaving. The readings they logged at the water, the chemicals they entered, the checklist they ticked, the photo they snapped, that's the report. It just, it assembles itself out of the stuff that already got captured during the visit and goes out to the customer. So it's not a second job stacked on top of the service. It's the same record you're using internally, pointed a different direction. Which is why I keep hammering on the record being the spine, because the same thirty seconds of a tech logging what they did at the pool is doing, like, three jobs at once. It's your proof the stop got done, it's how you manage the team, and it's the customer's report. One input, three payoffs.

And this is where the whole week kind of ties together, because that report, that outward-facing record, is your retention engine. We closed the week on keeping customers from canceling, and the finding, if you want to call it that, is almost boring, which is why I like it. And it matters because when you lose a customer you're losing the whole run of that account, years of it, plus what it costs to go find and break in a replacement. So churn is quietly one of the most expensive things in a pool business, and it barely shows up on any report because it's a thing that didn't happen. Keeping who you've got is just way cheaper. People don't stay because you're the cheapest. They stay because you're predictable and because they can see the value. Predictable meaning, same tech, same day, every week, the pool's always clean, they stop even thinking about it. And the seeing-the-value part, that's the report landing in their inbox after every visit, so the thing they're paying for isn't invisible. Because that's the trap with pool service, when you do it right the customer sees, nothing. The water's just clean, like it's supposed to be, and they start to wonder what they're even paying for. The report is what makes the invisible visible. So when the bill shows up, it's not a surprise, it's the eighth thing they heard from you this month, and seven of those were "here's your clean pool."

And so, when somebody does try to cancel, and usually it's over price, what I'd do is not immediately discount. Ask why first. A lot of the time it's not really the price, it's that they don't feel like they're getting anything, which, if you've been sending good reports, you've already been fighting. And if it really is budget, offer a smaller tier before you slash the rate, because the second you discount you've told them the price was fake to begin with. Same thing with raising prices, the operators who can raise without losing accounts are the ones who've been proving the value all along, so the increase doesn't feel like a grab.

So that's, like, the machine. Routes and scheduling produce the work, the record proves it got done and lets you manage the team without hovering, and the report turns that same record into the thing that keeps customers paying. It all kind of runs on the record.

But. Okay. I want to wander back down to the ground for a minute, because I think if I stopped there I'd be, I'd be selling you a slightly dangerous idea. Which is the idea that the system is the business. It's not. The system is only ever as good as the actual work happening underneath it. You can have the prettiest records and the cleanest routes and the best reports in the county, and if the tech in the truck is doing bad work, all you've built is a really efficient way to document bad work. So let me spend the last bit down where the work actually happens, because we had two pieces this week that live down there.

One was on setting up the truck. And I love this one because it's so, it's so unglamorous and it matters so much. The rule the piece landed on was safe first, then fast. Safe first meaning, your chlorine and your acid do not ride together in the cab, ever. They go in separate, ventilated containers, kept apart, because if those two get to mixing you've got a genuinely dangerous situation in an enclosed space you're sitting in all day. So that's non-negotiable, that's the safe-first part. And it's not just the storage, every truck should carry the same basic safety gear, gloves, eye protection, water to rinse a splash, and everybody should actually know where it is. This is the kind of thing you never think about until the day you need it and then it's the only thing that matters.

And then fast, once it's safe, is about the truck being set up so a stop takes twelve minutes instead of twenty. So there's kind of two tiers of stuff on the truck. There's the daily kit, the stuff you touch at every single pool, the test kit, the brush, the pole, the net, your main chemicals, and that lives within arm's reach, staged the same way every day, you're not digging through the bed for it. And then there's the repair parts, the fittings and the o-rings and all the little stuff you only need sometimes, and those go in labeled bins, organized by zone, so when you need a two-dollar fitting the stop doesn't stall out for ten minutes while you hunt for it. And honestly the thing that quietly kills a day is the searching, a couple minutes of rummaging times twenty stops adds up fast. A zoned, labeled truck is one of the biggest productivity levers there is and it costs you basically nothing but an afternoon of setup.

And then the other ground-level one, and this is the real, this is the craft, we had a piece on lowering cyanuric acid. And cyanuric acid, CYA, stabilizer, whatever you call it, it's the quiet one. It's the thing that sneaks up on you. Because here's what happens, you're running those stabilized trichlor tabs, the little pucks, super convenient, everybody uses them, and every time one dissolves it's adding a little more cyanuric acid to the water. And CYA doesn't go anywhere on its own, it just, it accumulates. And a little is good, it protects your chlorine from the sun. But it climbs, and climbs, and once it gets too high, it starts strangling your chlorine, like, the chlorine's still in the water but it can't do its job, and now you've got a pool that reads like it has sanitizer but isn't really sanitizing. And that's the kind of thing that turns into a green pool and an angry customer, and you're standing there going, but the numbers looked, okay-ish.

Now, before the fix, the judgment call, because it's not like every raised CYA is an emergency. You kind of want to be somewhere in the thirty to fifty range, that's the sweet spot, enough to protect your chlorine from the sun but not so much it's choking it. And once you're up around eighty, a hundred, that's when it's actually costing you, that's when you act. In between, you're just watching it, you're not draining a pool over a reading of fifty-five. So it's a, it's a know-your-thresholds thing, not a panic thing.

And the part that surprises people, when you do have to bring it down, there's no chemical that lowers cyanuric acid. You can't dose your way out of it. The only way it comes down is you replace water. You do a partial drain and refill to dilute it, trading out a chunk of the high-CYA water for fresh. Or where water's scarce, out west, there's mobile reverse osmosis that filters it out on site without draining, costs more but in a drought it might be your only move. But mostly it's drain and dilute. And the real fix, the thing that keeps you from ever getting there, is getting those pools off the straight trichlor tab diet before the CYA stacks up, because the tabs are what's feeding it. Catch the climb early. Which, again, comes back to, a good tech, running the same pool every week, logging real readings, is the one who notices CYA creeping up at sixty, seventy, and does something about it before it's at a hundred and forcing a drain and a mad customer. The record catches it. But only if the person leaving the record actually knows what they're looking at.

So that's, I think that's the whole thing, and it loops back on itself, which I like. You scale past yourself by building a system, routes, recurring visits, records, reports. The record is the spine of it, it's how you know the work got done, how you manage the team, how you keep the customer. But it's only worth anything if the work underneath it is real, if the truck's set up right and the tech catches the cyanuric acid before it's a problem. The system makes good work visible and repeatable, it doesn't make bad work good. So you build both, the machine and the craft, and the operators who win don't treat those as two separate jobs.

Alright, that's what I've got for this week. If any of that was useful, go ahead and follow the show so the next one shows up for you. That's it for me, I'll catch you next week.