Software for pool and spa companies
A pool company earns most of its service revenue in two compressed windows and spends both of them answering the phone. Meanwhile the service history for every property lives in the technician's head or a notebook in the van.
Field service and construction. The category platforms already exist. We build the thirty percent they refuse to: the integrations, the follow-up, the reporting, the customer-facing portal.
Sub-niches covered: Pool installation and construction, Seasonal opening and closing, Weekly maintenance routes, Retail plus service operations, Hot tub and spa service, Commercial and municipal pools.
You likely have this problem if:
Openings and closings are booked by phone in a two-week rush.
Service history per property lives in a technician's head.
Installation projects and service work are managed separately.
Retail purchases are not connected to the service relationship.
A different technician cannot service a property competently.
What breaks operationally:
Opening and closing bookings are taken by phone in a two-week rush.
Service and chemistry history per property is not recorded anywhere durable.
Installation projects and service work are managed in different places.
Retail sales are not connected to the service relationship they came from.
What we build:
Season booking with deposits. Customers book openings and closings themselves months ahead against real capacity, with a deposit that makes the booking real.
Property service history. Equipment, chemistry readings and past work held against the property so any technician can service it.
Installation project tracking. Builds tracked with permits, excavation, equipment and inspection milestones alongside the service book.
Retail and service link. Purchases and service tied to the same customer, which is where the repeat revenue actually comes from.
Why take deposits on seasonal bookings?
Because a free booking is a placeholder and a paid one is a commitment. Companies that take a deposit fill the season earlier and have far fewer no-shows in the two weeks where every truck hour counts.
How much service history is worth recording?
Equipment installed, chemistry readings and work performed. That is enough for a different technician to service the property competently, which is the actual point — history that only helps the person who wrote it is not worth capturing.
Should installation and service share one system?
They should share the customer and property record even if the workflows differ. Keeping them apart is how a company sells a pool and then never converts the owner to a service plan.
Can self-serve booking handle capacity properly?
Only if it books against real crew and route capacity rather than an open calendar. Otherwise you have moved the overbooking problem from the phone to the schedule, which is worse.
Last reviewed 22 August 2026