Tools and KPIs for running a pool service business in 2027

What to take away

The tools, and what each one is for

Skimmer is built for residential pool routes: scheduling, chemistry logging, invoicing and a customer app. It suits one to a few trucks and prices per month per route or per pool, with the current tiers published on its site.

Typical monthly tiers for a one-truck plan run from about 50 to 150 US dollars, moving with truck count and whether card processing is bundled. The differentiator is the customer app: a client sees the visit and pays without a call.

Pool Brain covers the same residential ground with route scheduling, water testing records and billing, and it is common among owner-operators running two or three trucks.

Ask for a two-truck quote, because plans in this band are priced by route. The differentiator is how a reading is stored, as a number against a pool or as a note on a visit. Only the first one builds a trend.

Pool Office Manager leans toward service companies that also do repairs, because work orders and parts attach to the pool record.

Pricing depends on user seats and on the repair modules you switch on, so there is no single list price to compare. The differentiator is the repair record: whether a work order pulls parts and equipment from the same pool file as the chemistry log.

Evosus is heavier and aimed at retailers and builders as well as service divisions, so it fits a company with a storefront.

It is quoted per installation rather than sold at a monthly tier, so treat it as a capital decision. The differentiator is the shared item file: a counter sale and a route part come out of the same inventory.

Paythepoolman is the low-cost entry point for a single owner-operator who wants billing and stop records without a full platform.

Subscriptions here typically sit under 50 US dollars a month, with card processing quoted separately, so compare the all-in cost per stop. The feature to check is autopay, since billing is the reason to pick it.

Accounting is separate. QuickBooks Online and Xero both handle recurring invoices, sales tax and the paper trail the IRS expects. The route software tracks the stop; the accounting software tracks the money.

Both publish monthly tiers, typically from about 20 to 100 US dollars a month, rising with user seats and payroll add-ons. Check which of the two your route tool already connects to before you switch.

Two things no tool does for you: decide which accounts are worth keeping, and set the price of a stop. Both live in the pricing and profit model.

What is actually new for 2027

Little in the tool stack changes on January 1. Three things do carry a date.

Four monthly KPIs, defined

Measure these on the same definitions every month, or the trend line is noise.

A callback is a stop that earns nothing and burns fuel, so tag every one at the moment it is logged. Untagged callbacks become a number nobody can act on.

Chemical spend per stop is the one owners misread. Rising spend with flat readings usually means a dosing or testing habit, not a price problem. Track it per 10,000 gallons if you want to compare pools of different sizes.

The cost side of these ratios comes out of the pricing model, which is where you decide what a stop is supposed to cost before you measure what it does cost.

Feature payback, in the order it arrives

Route optimization sits last on purpose. Density is set when you accept or refuse an account. An algorithm moves stops around; it cannot add a pool to a street.

The reports worth building

Build three: chemical cost per account for the season, callbacks by technician and by account, and visit completion by route day. Each points at one action, whether that is repricing an account, retraining a person or redrawing a day.

Skip the dashboard of everything. It gets opened for a month and then ignored.

Where the measures show a training gap rather than a pricing gap, the fix belongs in the hiring and training program, not in the software.

Your system is a security responsibility

A route system holds home addresses, gate codes, alarm details and payment methods for hundreds of households.

National Institute of Standards and Technology: NIST Small Business Quick-Start Guides is written for firms with no IT department and covers the basics in the order they matter. Cybersecurity and Infrastructure Security Agency: Cyber Guidance for Small Businesses.

Route-specific steps:

Access removal is the step owners skip. A former technician with a live login and every gate code on the route is a problem you built.

Records, retention and inspected accounts

Business records live in the same system or beside it. Internal Revenue Service: What kind of records should I keep? sets the standard plainly: the records must clearly show income and expenses and support the documents behind purchases, payroll and assets.

The same source gives the periods: three years from the filing date for most tax records, four years for employment tax, and property records until the limitations period expires after disposal. A state rule that asks for longer wins.

Export your history on a schedule and keep a copy you control, so changing vendors never puts your data out of reach.

Commercial pools add a second use. Centers for Disease Control and Prevention: Operating and Managing Public Pools, Hot Tubs and Splash Pads describes what public aquatic facilities must maintain, including documented water testing and working recirculation.

Retention for those logs is set by the local health department. One to three years of daily test records is typical, so confirm the period with your county. Three years of logs also covers the tax window.

Serve those accounts and your visit log becomes part of what the facility shows an inspector, so it has to be complete and exportable on demand. What you may sign off on depends on your licensing and compliance position, which varies by state and county health department.

Testing a candidate tool

Test against your worst account, not a demo pool. Enter a real pool with an odd surface, a spa and an automated controller. Record a real visit. Produce an invoice. Then export everything and read what comes out.

Four questions before you commit. Can I export my complete history at any time? Can a technician finish a visit record where the signal is poor? What happens to my data if I stop paying? How are logins removed? Those answers sort serious tools from attractive ones faster than a feature grid.

Apply the same discipline to standardized equipment, as in the equipment and setup guide, and to any service claim you make in marketing and growth. A reporting claim has to be one the system can keep.

Last, check that the workflow the software imposes matches the one you designed. A tool that fights the route wins.

Common questions

Can a small route run on a spreadsheet?

Yes, until someone else has to cover the day. The breaking point is coverage, not size: the moment a technician who has never seen the pool needs its history, a spreadsheet is not enough.

Should technicians enter readings at the pool or afterward?

At the pool. Readings typed from memory in the truck carry errors, and those errors lean toward what the number was supposed to be. A chart built on them shows a pool that does not exist.

How many measures should an owner track?

Few enough to review all of them every month. Four is a workable start, and a fifth should have to name the decision it changes before it earns a line on the page.

What if the system goes down mid-route?

Keep a paper fallback for the visit record and expect to use it a couple of times a year. Rebuilding a day from memory is how a chemistry history turns into fiction.