Pool Service Software for Small Companies
How a 1 to 3 person pool company can evaluate route software. The jobs it must do, the questions to ask, and a one-week trial plan.
Start with the five jobs
A small pool company needs software to do five things:
- Show today's stops in the right order.
- Record what happened at each stop.
- Tell the customer what happened.
- Get the customer billed.
- Keep your customer list in your own hands.
Everything else is a bonus. A feature list with 80 items looks good in a demo. With 1 to 3 trucks you will use a handful of those features every day, and the rest will be screens you tap past.
When a spreadsheet stops working
A spreadsheet and a notes app can carry a small route for a long time. These are the signs they have stopped working:
- You cannot find the gate note while standing at the gate.
- You write the same readings in two or three places.
- A helper needs the route and you are emailing them a file.
- You sent the same invoice twice, or missed a month.
- A file did not save and you lost a day of notes.
If you are at that point, the plan in spreadsheet to route app walks through the move.
What to ask of any app
Use the same questions for every option you look at. Ask them in a demo, then test the answers yourself.
| Question | Why it matters | A good answer looks like |
|---|---|---|
| Does the full route open with no signal? | Backyards and equipment pads are dead zones | Stops, notes and history all open in airplane mode |
| How many taps to log a normal stop? | You do it at every stop | Readings and chemicals on one screen, last values prefilled |
| Can I export everything myself? | The customer list is the business | A file of customers and history, no support ticket needed |
| How is price counted? | Cost changes as you grow | A clear rule for pools, users and texts |
| Who can see gate codes? | It is access to customers' property | Separate logins, and an easy way to remove a user |
| What does the customer receive? | The report is your proof of service | A readable report with readings and photos |
| What happens if I cancel? | You may want to leave later | Access period and export window stated in writing |
Each of these has a page with more detail: offline route app, export your customer data, and flat price vs per-pool software.
Count taps and seconds
Say an app adds 20 seconds to each stop compared with how you work now, and you run 15 stops a day. That is 300 seconds, or 5 minutes a day. Over a five-day week it is about 25 minutes. These numbers are an illustration, so time your own stops.
The same math works in your favor. If the app removes retyping and saves you 20 seconds per stop, you get that time back every day. Time five stops the old way and five stops in the app, then compare.
What a 1 to 3 person company can skip at first
- Multi-depot dispatch boards
- Warehouse-style inventory counts
- Dashboards built for a large team
- Integrations with tools you do not use
Revisit the list when you hire. A second person who needs the route changes your requirements, starting with separate logins.
What matters more than it looks
- Per-user logins. A shared login means you cannot remove one person's access later.
- Seasonal and paused accounts. Pools close for winter in some regions. Ask how paused accounts are handled and whether they count toward price.
- Search. You will search for a customer by street name more often than by last name.
- Photo handling. Ask where photos live and whether they sync over cell data or only on Wi-Fi.
- Cancellation terms. Pricing and contract terms change, so read the current terms before you pay.
A one-week trial plan
- Enter or import 10 real accounts. Do not load the whole route on day one.
- Export the data right away and open the file in a spreadsheet. Check that names, addresses and notes made it out.
- Run one real day of stops in the app while your old method keeps running beside it.
- At one stop, switch on airplane mode, log the visit, then restore signal and confirm it synced.
- Send one real service report to a friendly customer and ask whether it was clear.
- On day five, compare the time per stop and the number of things you had to fix by hand.
At the end, give each option a pass or fail on the seven questions in the table. An app that fails offline use or export is hard to fix later, so weigh those two heavily.
Mistakes to avoid
- Choosing on the demo. Demos use clean data and strong signal. Your route has neither.
- Importing everything at once. A bad import of 80 accounts takes longer to clean than a bad import of 10.
- Ignoring user count. If pricing is per user, a helper who works two days a week still costs a full seat in some plans. Ask.
- Skipping the exit. Before you sign up, find out how you would leave and what you could take with you.
- Switching mid-season. If you can, move in a slow week, away from a heat wave or a post-storm cleanup rush.
If you are costing out the route as a whole, remember that software is one more line in the cost of every stop, next to fuel, chemicals and labor.
Common questions
When does a small pool company need route software?
When the spreadsheet or notes app starts costing you time at the stop, such as hunting for a gate note, retyping readings, or sharing the route with a helper by email. If none of that is happening yet, you can wait.
What features can a 1 to 3 truck pool company skip?
Multi-depot dispatch, warehouse inventory and reports built for dozens of techs can wait. Per-tech logins, offline use, photos and data export matter earlier.
How long should I trial pool route software?
Run at least one full week of real stops beside your old method. One day shows the demo, a full week shows the weak spots like dead zones, skipped stops and billing.