The stage where everything stops fitting in one head.
Two or three techs is where informal systems break. The owner cannot see every stop, the office admin needs access without full control, and customers start noticing when service varies by who showed up. POOLIO gives that stage structure without corporate overhead.
- Roles for owner, admin, and technician enforced server-side
- Consistent checklists so service quality does not vary by tech
- Dispatch and coverage when someone is out
- Recurring billing and collections handled by the system
Growing pains
Six things that break at three techs — and the fix
- Step 1
Onboarding a new tech
A tech account with assigned stops, per-pool checklists, and property context means training is about pools, not about tribal knowledge.
- Step 2
Inconsistent service
Required checklist items gate stop completion, so the same standard applies whoever runs the route.
- Step 3
The phone
A shared inbox with customer history means whoever answers can answer, without calling the tech who was there.
- Step 4
Coverage days
Reassign a route on the dispatch board with bulk actions and undo when the plan changes twice before 9am.
- Step 5
Billing drift
Recurring invoices generate from plans, and completed repair work sits in a billing queue until someone acts on it.
- Step 6
Access boundaries
Technicians reach operational data only. Financial views stay with owner and admin roles at the database level.
Operational outcomes
What a small company gains
Delegable office work
An admin can run billing and customer communication inside clear boundaries.
Service you can audit
Chemistry, photos, and timestamps per stop across all techs, comparable week to week.
Revenue that does not depend on memory
Missed-money views surface unquoted requests and unbilled completed work.
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
Typical setups
Owner + 2 route techs
Two recurring routes, owner handles repairs and billing, admin views on a laptop at night.
Owner + office admin + techs
Admin owns invoicing, collections, and the inbox; owner keeps payments and company settings.
Route techs + one repair tech
Route blocks stay stable while repair work is dispatched around them.
Seasonal help
Add and remove technician accounts without losing the service history they created.
Buyer checklist
Checklist at this stage
- Can you give office access without giving away everything?
- Is service documented identically across techs?
- Can a route be reassigned in under a minute?
- Do customers get the same answer from anyone who replies?
- Is unbilled completed work visible?
- Does history survive an employee leaving?
FAQ
Frequently asked questions
We have two techs and one person in the office. Does POOLIO fit?
That is the shape POOLIO is designed around. Owners and admins get the business views — billing, collections, dispatch, customers — while technicians get a scoped mobile view of their own assigned work.
Can our office admin do billing without full owner access?
Yes. Admin and owner are separate roles, enforced by database policies rather than hidden buttons, so an admin can run day-to-day billing without owner-level controls.
How do we keep service consistent between techs?
Checklists attach to each body of water, and required items gate completion. The service record is identical in structure regardless of who ran the stop, which is what makes coverage days work.
What happens when a tech quits?
The route, history, gate codes, equipment notes, and customer conversations belong to the company record, not the departing person's phone. Reassign the route and the context travels with the property.
Can we grow into POOLIO without buying features we don't need yet?
Dispatch, recurring work order templates, parts, broadcasts, and the accounting integration are there when you need them. Nothing forces you to configure them on day one.
See it with your team structure
Tell us your roles and route count; we will show exactly who sees what.