The route is the easy part. This runs the company around it.
Once you have more than one truck, the hard problems stop being about stops. They are about who can see what, which customer agreed to what price, which work never got billed, and whether the books match. POOLIO is built for that layer as well as the field.
- Owner, admin, and technician roles enforced server-side
- Customers, properties, and bodies of water as separate records
- Service plans that drive recurring invoices automatically
- Collections, statements, and QuickBooks reconciliation
Company layers
Six layers a pool company has to keep straight
Most tools cover one or two of these well. Gaps between them are where money and accountability leak.
- Step 1
People and permissions
Owners, admins, and techs each get a different surface. Role checks live in the database, so a technician cannot reach financial data by guessing a URL.
- Step 2
Customers and properties
A customer can own several properties, and each property can have several bodies of water with distinct equipment, cadence, and checklist requirements.
- Step 3
Agreements and service plans
A service plan records what the customer pays, how often, and what is included — the source of truth for the recurring invoice, not a note in someone's phone.
- Step 4
Work in flight
Estimates, approvals, work orders, parts, and change orders move through defined states, so 'where is that repair?' has an answer anyone in the office can read.
- Step 5
Money and follow-up
Invoices, autopay, aging buckets, statements, and a scheduled follow-up loop for past-due balances, all mode-aware so test and live payments never mix.
- Step 6
Books and compliance
QuickBooks mapping and reconciliation on the accounting side; recorded messaging consent and opt-outs on the communication side.
Operational outcomes
What an owner stops carrying personally
The 'who knows this' problem
Gate codes, equipment, chemistry targets, and prior skips live on the record instead of in one tech's head.
Manual monthly billing
Recurring service invoices generate from the plan on a schedule, with an admin-only override to generate a due invoice early.
Silent write-offs
Aging buckets and a collections view make it explicit when a balance is drifting, instead of discovering it at tax time.
POOLIO organizes the work and the follow-up. Results depend on your pricing, your route, and how your team uses the system — POOLIO does not guarantee revenue outcomes.
Who it is for
Where this fits
Owner plus office admin
Separate admin access for the person who bills and answers the phone, without handing over full owner controls.
Companies adding their first employees
Technician accounts with scoped access, assigned routes, and a mobile view that only shows their day.
Companies with mixed revenue
Recurring cleaning plus repairs, equipment installs, and one-off jobs billed separately but reported together.
Companies preparing to hand off the books
Consistent invoice, payment, and customer records that map into QuickBooks rather than a shoebox export.
Buyer checklist
Company-level checklist
- Are permissions enforced on the server, or only hidden in the UI?
- Can one customer hold multiple properties and pools?
- Is there an audit trail for skipped or delayed service?
- Do recurring invoices generate without someone remembering to run them?
- Is there a real reconciliation view against your accounting system?
- Can you export or correct data yourself without a support ticket?
FAQ
Frequently asked questions
What is the difference between pool service software and pool company software?
Service software focuses on the route and the visit. Company software also has to carry the business around it: who works for you and what they can see, how money is billed and collected, what the customer was promised, and what the books need. POOLIO covers the route plus the company layer — roles, service plans, billing, collections, and accounting integration.
Can I control what technicians can see?
Yes. Roles are stored server-side and enforced by database policies, not by hiding buttons. Technicians see operational data for their assigned work — stops, checklists, work orders, equipment — and do not get the financial and company-wide views reserved for owners and admins.
Does POOLIO support multiple properties per customer?
Yes. A customer can have multiple properties, and each property can have multiple bodies of water with its own equipment, checklist, and service cadence. Billing and service history roll up to the customer while staying attributable to the right pool.
How does POOLIO handle onboarding a whole company?
There is a guided onboarding wizard that walks an owner through company profile, team members, customer and route imports, service plan setup, messaging setup, and readiness checks. Imports are idempotent, so re-running one does not duplicate customers.
Does POOLIO work with QuickBooks Online?
POOLIO includes a QuickBooks Online integration architecture with entity mapping, a sync queue, conflict resolution, and a reconciliation workspace. Connection and account mapping are configured by an owner or admin before sync is enabled.
Walk through POOLIO with your company structure
Bring your route count, tech count, and billing model. We will show exactly how it maps.