Pool service has a structural quirk that decides how the whole system should be built: the thing you service is not the person who pays. You visit a property fifty times a year, and the customer might be an owner who has never met the technician, a property manager with eleven addresses, or a renter with the gate code.
Configure around the customer and the equipment history ends up scattered across visit notes. Configure around the property and every quote you write for the next decade gets easier.
The property record is the whole system
Everything a pool tech needs to know and everything the office needs to write a quote lives at the address. Get this right in week one and the rest of the configuration is straightforward.
- Equipment: pump, filter, heater, cleaner, automation — make, model, and age for each. This is the single most valuable field set in the trade and almost nobody fills it in.
- Pool volume, surface type, and sanitiser — the numbers that make chemical dosing a calculation instead of a habit.
- Access: gate code, lock location, dog, "do not use the side gate" — the things that cost a return visit when a route is covered by someone new.
- Route and day assignment — the property belongs to Tuesday, and Tuesday belongs to a tech. Both need to be a field, not a memory.
- Prior repairs and observations, including the ones nobody acted on. A noise logged in June and again in July is a quote in August.
Two pipelines, again
The route is not a pipeline. It is a recurring schedule that either happened or did not, and it should be configured as recurring work with a completion record, not as jobs somebody creates each week.
The repair side is a pipeline, and it is where the margin lives: flagged → quoted → approved → parts ordered → scheduled → complete. Keeping it separate from the route is what stops equipment quotes disappearing into a schedule that is already full.
Give the technician exactly two fields
This is the part where most pool software rollouts fail. The office designs a twenty-item inspection form; the tech has a hundred stops a week and a phone in the sun; the form gets skipped, and a skipped form is worse than none because it creates false confidence in the data.
What survives an August afternoon is small:
- Anything worth a photograph? One tap, one picture, attached to the property. No typing.
- Anything worth a quote? A single flag that puts the property on the office list for tomorrow morning.
Chemical readings, if you capture them at all, should be numbers with defaults — not free text. Everything else belongs to the office, because the office is sitting down.
The automations worth having on day one
- 01Service summary after each visit
A short message with a photo, sent automatically on completion. In a trade where the customer is usually at work when you visit, this is the only evidence they ever get that the service happened. It is the cheapest retention tool in the business.
- 02Repair flag to office queue
The tech flags, the office receives it as a task the same day. The gap between observation and quote is where the $38,000 goes.
- 03Seasonal open and close list
In seasonal markets, the list of last year's customers with their open dates should assemble itself in February, before the phones start. This is a report, not a project.
- 04Off-season contact
Three or four useful, non-selling messages across the quiet months. Route customers who hear nothing for four months are the ones who do not come back, and they never tell you why.
Billing is recurring, and it is where churn shows up first
Monthly route billing has a useful property: it fails visibly. A card that declines, an invoice that goes unpaid for six weeks, a customer who asks to skip a month — each is a churn signal weeks ahead of the cancellation, and each is sitting in your billing data already.
Set the flags while you are configuring, not later. A route customer whose payment has failed twice is not an accounts problem; they are a retention problem that accounts happens to have noticed first.
The pool is the customer. The person just pays for it.
Common questions
Should a pool service CRM be organised around customers or properties?
Properties. You service an address fifty times a year, and the payer may be an owner, a renter, or a property manager with eleven pools. Model it as one billing customer with many properties, or a single management account becomes eleven half-duplicated records you reconcile by hand.
What equipment details should a pool company record?
Make, model, and age of the pump, filter, heater, cleaner, and automation, plus pool volume, surface type, and sanitiser. Equipment age is the best predictor of what you will be quoting next season, and having it on file turns a repair quote into a ten-minute job that reads as informed.
How much should pool techs record at each stop?
Two things: a photo of anything worth photographing, and a flag for anything worth quoting. A twenty-item form does not get filled in at a hundred stops a week, and a form that gets skipped is worse than no form because it creates false confidence in the data.
How do I stop route customers cancelling over the off-season?
Contact them during it. Three or four useful, non-selling messages across the quiet months keeps the spring call a continuation rather than a cold approach. Also watch billing — a card that has failed twice is a retention signal weeks before the cancellation arrives.