Software for a route that never stops moving.

It is one system for the weekly operation: recurring route scheduling, water chemistry logs per pool, equipment and repair history, dispatch, customer messages, and billing. The route, the chemistry, the repair, and the invoice all read from the same pool record, so a stop completed in the field updates everything at once.

The first release covers one complete path, from a scheduled stop to a sent invoice: the recurring route, the pool record, chemistry entry in the field, dispatch, customer messages, and billing tied to the stop. Openings and closings, green-to-clean recoveries, and multi-crew reporting come after the core week works.

Each pool is set to its cadence once, weekly or every other week, and the visit is generated automatically. Routes are built by day and by neighbourhood so crews drive a tight loop instead of crisscrossing town. New accounts drop onto the nearest route, vacation skips pause the stop without deleting the record, and a completed stop rolls the next visit forward on its own.

Every reading is logged against the specific pool at the visit: chlorine, pH, alkalinity, cyanuric acid, salt, and phosphate, with what was dosed and how much. The pool carries a running history the whole crew can see, so a tech at the pad can compare today against last week and dose accurately. The trend shows which pools are heading toward trouble before they turn green.

A green pool becomes a one-off job on the same record, not a side conversation. The recovery visits, the extra chemistry, and the filter work are logged against the pool, the customer sees the plan and the cost, and the recurring visits resume once the water is balanced. The history shows what was tried and what worked, so the next green pool is not a fresh guess.

A failed pump or a cracked filter is logged against the pool with the equipment model, the warranty state, and the repair history. The repair is scheduled as its own visit, separate from the weekly route, so it does not push the rest of the day late. When the repair is done, the charge is billed from the same record, instead of living in a different system from the cleaning route.

Completing a stop in the field triggers the invoice: the recurring visit, any repair or extra work, and the card on file. Monthly billing runs from the same record, so a paused account is not charged and a one-off job is not forgotten. Ageing invoices flag for a polite reminder instead of waiting for someone in the office to notice.

Yes, for the books. The route system should connect to the accounting tool you already use, so invoices and payments flow across without retyping. The route system runs the week: routes, chemistry, repairs, and customer messages. The accounting tool keeps the ledger, the tax records, and the year-end reports.

The system sends an automatic message when the tech is on the way and another when the visit is done, with what was tested and what was adjusted. A short note after every visit shows the work behind the scenes and builds trust, and customers who see the record are more likely to refer you. The messages come from the visit record, so nobody in the office types them by hand.

A skip pauses the stop for the weeks the customer is away without deleting the pool or its history. The route rebalances around the gap, the billing pauses with it, and the visits resume automatically on the return date. A one-off change never touches the base route, so the rest of the week stays intact.

Openings and closings are seasonal jobs on the same pool record, with their own checklist, parts, and charges. They are scheduled around the weekly route in the shoulder season, so the opening season does not break the regular weeks. The checklist and the photos from the close sit on the record for the next opening.

The tech keeps working without a connection. The route, the pool record, the gate code, and the chemistry entry all live on the device, and readings and photos sync when the signal returns. A design that needs a live connection to log a reading will fail at exactly the property with no signal. Test it with the connection off, not only in the office.

Yes. Each crew keeps its own route, and the owner sees all of them on one board. A pool belongs to one route, a repair never double-books a tech, and the board shows what is done, what is late, and what needs a return visit. The morning routine that breaks around the fifth crew is the usual point where one shared record stops being optional.

Buy a maintained platform when it covers the operation. Platforms built for pool service already handle routes, chemistry logs, dispatch, customer messages, and billing, and that is the right call for most operators. Build custom when the operation breaks the template: several crews across franchise territories, chemistry rules your insurer or regulator requires, a repair and parts workflow no platform supports, or reporting your owners require. Compare the platform fee against the cost of owning the system before you decide.

For a small, well-defined task with someone technical managing it, freelancers are often cheaper. The pattern that goes wrong is a non-technical buyer coordinating several freelancers becoming the project manager, the tester, and the person who discovers the pieces do not fit. A pool service management company earns its fee when the work needs coordination across the route, the chemistry record, repairs, billing, and customer messages: one accountable party, one phase price, and checkpoints against the whole week. If your need is one screen or one fix, hire the freelancer.

The first paid phase may cover a bounded audit, a proof of concept, a recovery plan, or a small first release. The final price depends on how many pools and crews the system covers, how many routes it must keep in balance, whether chemistry rules, repairs, openings and closings, and customer messages are in scope, what it needs to connect to, and whether data needs moving over. The agreed phase is priced in writing before it starts. First phases start at $10000 for a bounded first release; a full first platform is a larger engagement, with the guide putting a custom MVP at $80,000 to $140,000 and a full platform at $160,000 to $260,000. Our build vs buy guide works through the cost bands for each phase in detail.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the week routine agreed at the start: a route built from the map, a chemistry log that follows the pool, a repair slotted in without losing the day, a skip that pauses the billing, and an invoice that goes out when the stop is done. Progress is reported in plain language: what changed, what's next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads. Our job is to make the work checkable; your job is to check it against your business.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

We need one person who owns the operation, access to the relevant users and systems, timely answers on business rules, and someone who can accept or reject each milestone. A weekly working session is usually enough once the scope is stable. Your team should not have to manage developers day to day. The team that scopes your project is the team that does the work: no handoff to another vendor after you sign, and you can talk to the people doing the work directly.

Yes. Takeover is a common first engagement, and it always starts with an audit: where the code lives, how your data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live. Code that is understandable and fit for the next release stays; only the parts blocking reliability get replaced. AI-built prototypes from Lovable, Replit, Bolt, or v0 can be assessed as starting points. And if you already paid another vendor and have nothing working, the audit tells you which story you have before you spend more.

Ask for the quote to name everyone who will use the system, including your own crew. Every platform has two products: what customers see, and what your people use all day: the route, the chemistry record, the repair log, the billing, and a record of who did what. When that second product is quoted as an 'admin panel' on a single line, it becomes the overrun. Our quotes treat your team's screens as their own scope, with their own users. Then the phase names the workflow, what 'done' looks like, the price, and the exclusions, all before paid work starts. You review working software at agreed checkpoints, and when new information changes the scope, you hear the effect on price and timing before anything is approved.

Every launch includes post-launch warranty cover for defects in the agreed scope, release support, and small screen corrections. After that, work can continue as another fixed phase or an ongoing product engagement. The code and accounts stay under your control either way.