The ROI math of pool service software for a solo operator

For most solo operators past about 25 pools, yes, and the break-even is smaller than the decision feels. At $29 a month on a 100-pool ceiling, the subscription costs about $0.35 per pool per month on a 80-pool route. One invoice you would otherwise have missed, at a typical $130-150 monthly service rate, covers four to five months of that subscription on its own. Two hours of admin time recovered covers it outright at almost any rate you would pay yourself.

That is why price is rarely the real question. The question underneath it is volume. Billing and scheduling cost you time in proportion to how many accounts you carry, and somewhere between 20 and 40 pools that time stops being an evening job and starts being a real line item. Below that, the overhead of learning any system can genuinely exceed what it saves you, and nobody selling software will tell you so.

It helps to separate the two things a subscription is actually buying, because they have very different payback profiles. The first is time: hours you currently spend assembling invoices, checking who paid, and working out which visits a given month covers. The second is leakage: revenue you earned and never collected because the record of the work and the record of the money were never reconciled. Time savings are pleasant and easy to overestimate. Leakage is unglamorous, harder to see, and usually the larger number on a route past 50 pools.

Run the comparison against your own hour rather than against a market rate. If you are billing $8,400 a month on 60 pools and working roughly 40 hours a week on the route, your revenue per working hour is somewhere near $50 before costs. Six hours of billing night is not an abstract inconvenience at that rate; it is $300 of your own capacity spent on clerical work, every month, on top of the driving.

The tier you land on is set by pool count rather than by features, which simplifies the comparison a lot. Every plan, including the free one, includes every feature, so what each plan costs and where the pool ceilings sit is genuinely the whole pricing decision. There is no version that withholds invoicing or reporting until you pay more.

That matters for the payback calculation more than it first appears, because it removes the usual trap in software pricing. The common pattern elsewhere is that the affordable tier omits the one capability that would have justified the purchase, so the honest comparison is always against the expensive tier. When every plan carries every feature, the number in the worksheet is the number you actually pay, and a small operator evaluating the cheapest option is evaluating the real product rather than a demo of it.

The pool ceiling is the only thing that moves you, and it moves in one direction on its own. Growing past a ceiling raises you to the tier that fits at the next billing boundary, without proration and without cutting service off mid-month. Shrinking does not lower you automatically; that is a change you choose to make. Practically, this means the cost line in your worksheet is stable and predictable, and the only surprise available to you is the one that arrives because your route grew.

Four inputs decide this, and you already know three of them. Your pool count, your average monthly rate, roughly how many hours a month you spend on billing and scheduling, and what you would have to pay someone to do that work if you did not do it yourself. Fill those in and the answer stops being a matter of opinion.

The table below runs the same worksheet at three route sizes using a $140 average monthly rate. The admin hours are typical of operators doing billing by hand at the end of the month; use your own if you have counted them. The missed-invoice line is the one most operators underestimate, because a visit that never made it onto an invoice does not appear anywhere as a loss. It simply never shows up as revenue.

Notice what the third row does. Software as a share of billing falls as the route grows, from about half a percent at 40 pools to a fifth of a percent at 100, because the plan price is flat inside its ceiling while your billing is not. That is the opposite shape from most costs on a pool route. Chemicals, fuel and labour all scale with pool count; a flat subscription gets cheaper per pool with every account you add, right up until you cross a ceiling and move to the next tier.

The rows to treat with suspicion are the admin hours, because almost nobody has actually counted them. If you want one honest number instead of an estimate, time yourself on the next billing night, start to finish, including the part where you go back through the route sheet to work out what a customer is disputing. Most operators who do this find the real figure is meaningfully higher than the one they would have guessed, largely because reconstruction time is invisible until you measure it.

Operators expect the savings to come from the route, and on a one-truck operation it mostly does not. You already know your own route. You have driven it for years, you know which gate sticks and which dog to watch for, and reordering your stops is not going to find you an hour a day. The optimization pitch is real for a three-truck company with a new tech; it is thin for a solo operator who has the route memorized.

The money leaks on the billing side, in three specific places. The visit that got completed and never got invoiced. The customer whose autopay quietly lapsed and nobody noticed for four months. The invoice that went out and never got chased because chasing it meant reconstructing which visits it covered. None of those feel like losses at the time, which is exactly why they persist.

The uninvoiced visit is the purest version of the problem. You did the work, you used the chemicals, you drove there, and the only trace is a line on a route sheet that never became money. There is no angry customer, no bounced payment, no reminder of any kind. On a 60-pool route, missing two visits a year at $140 apiece is $280 that simply never existed, and you will not find it unless you go looking for it deliberately.

The lapsed autopay is the expensive one, because it compounds silently. A card expires, the charge fails, and unless something surfaces that failure the account keeps getting serviced every week for months. Four months on a $145 account is $580, and the conversation you eventually have to have with that customer is harder the longer it ran, because now you are asking for a lump sum rather than a monthly rate.

Those three are all the same failure: the record of the work and the record of the money living in different places. When the visit, the readings and the invoice that visit belongs to are one chain, an uninvoiced visit is visible rather than invisible. That is the actual mechanism behind the payback, and it is worth being precise about it instead of accepting a vague claim about efficiency.

It is also why the comparison against a spreadsheet is not really about the spreadsheet. A spreadsheet is a fine list. What it cannot do is notice that something is missing from it, which is the point where a spreadsheet stops holding up on a growing route.

A worksheet that only counts benefits is a sales page with a table in it, so it is worth being equally specific about what does not change. Software does not win you customers. It does not set your prices, and it will not tell you that the 30-minute pool you charge $110 for should be $150. It does not do the service. On a solo route, the work is still one person, one truck, and the same number of stops on Tuesday.

The migration cost is real and routinely understated. Getting the customer list in is an afternoon if the list is already in a spreadsheet, but the first month is genuinely slower than the last month of doing it the old way, because you are running the new system while still checking it against the old habits. Budget one imperfect billing cycle. Operators who expect that are fine; operators who expected instant relief are the ones who quit in week three and conclude the category does not work.

There is also a discipline problem no product solves. A record only helps if the work gets recorded, which means the visit has to be completed in the app at the pool rather than reconstructed on Sunday from memory. If that habit does not form, you have bought a more expensive version of the notes app and none of the leakage arithmetic in this post applies to you. The honest version of the payback claim is conditional: it holds if the record is kept at the time, and it does not hold if it is not.

None of that argues against the purchase on a route past 40 pools. It argues for costing the decision properly, which means putting the setup afternoon, the slow first cycle, and the new habit on the same page as the $348 and the recovered $310. The case survives all three comfortably. It just should not be made by pretending they are free.

Under about 20 pools with a fixed route and a paper book, software wins you very little, and it is worth saying so plainly. At 15 accounts you can hold the whole operation in your head. Billing night is 40 minutes. You know without checking who has not paid, because there are fifteen of them and you saw eleven of them this week. Adding a system to that is real setup work in exchange for savings that round to nothing.

The other genuine no is a route you are actively winding down. If you are two years from selling or retiring and the account list is stable or shrinking, the payback window may simply be shorter than the work of migrating. The one caveat there runs the other way: a buyer pays more for documented, systematized accounts than for a route that lives in the seller's memory, so the records can be worth more at the sale than they were during the service.

A third case is worth being honest about even though it is not really about size. If your billing is genuinely simple and genuinely current, meaning every visit is invoiced within a week and you can name your outstanding balance from memory right now, then the leakage half of the payback does not apply to you and only the time half remains. That is a much smaller number, and it may not clear the bar. Some operators run tight books on paper, and telling them otherwise would be a sales pitch rather than arithmetic.

There is a middle case worth naming too. If you are under the 20-pool ceiling, the free plan carries every feature with no card and no clock running, so the cost side of this worksheet is genuinely zero and the only thing you are spending is setup time. That is a different calculation from the one above, and it is the reason a small route does not have to decide this on price at all. What a small route should weigh instead is what a one-truck operator actually needs from software before worrying about tiers.

A solo operator running 62 pools around Henderson bills on the last Sunday of the month, working from a route sheet and a notes app. Across one year, two completed visits in July never made it onto an invoice, and one customer's autopay had lapsed back in April without anyone noticing until the account came up in a year-end review. That is about $310 of service delivered and never collected, against a subscription in the $29-79 band.

The $310 is the honest headline, and it is worth being careful about what it does and does not prove. It does not prove software would have caught all of it automatically. It proves that the money was lost in a place nobody was looking, and that the annual cost of looking is smaller than the annual cost of not looking. On a 62-pool route at $348 a year for the Startup plan, one missed autopay running four months roughly pays for the year.

The second number on that route is quieter. Billing night ran about six hours a month, reconstructing which visits belonged on which invoice from a notes app. Six hours is 72 hours a year. Whatever you think your own hour is worth on a Sunday evening after a week of pools, multiply it by 72 and put it next to $348.

Put the two together and the shape of the decision is clear enough without any vendor claim attached to it. Roughly $310 of leakage found in a single year, plus 72 hours of clerical time, against $348 of annual subscription. Even if better records had caught only half the leakage and saved only a third of the hours, the arithmetic still lands comfortably on the same side. That is the useful test: assume the software works less well than promised, and check whether the answer changes. On a 62-pool route it does not.

It is worth noting what this scenario is not. It is one operator's year, not a measured average, and your route will produce different numbers. The point is not the $310. The point is that the operator did not know the $310 existed until he went looking, which means the figure on your own route is currently unknown to you as well, and it is not zero.

One caution on the revenue side of any worksheet like this: taking card payments carries processing costs regardless of which software you use, typically around 2.5-3.5% per transaction across the industry. That is a cost of getting paid faster, not a cost of the software, but it belongs in the arithmetic if you are moving customers onto cards as part of the same change. The structural differences between how vendors charge are covered separately in how the pricing models differ.