Sound familiar?
What pool service companies tell us before a project starts.
- Routes are rebuilt by hand whenever someone cancels, moves or a new customer signs up.
- Techs write readings on paper or in a text, and the office cannot find last month's numbers.
- Repair quotes for pumps, heaters and filters get sent late or never.
- Customers ask whether the pool was serviced, and we have no easy way to show them.
- Monthly invoices are made by hand and some customers are missed.
What we build
Each one is a working piece you can open and check when it's done.
Route and stop updates
New customers, pauses and cancellations flow into the route sheet or app, so techs see a current list each morning.
n8n, Make and Zapier automation Google Sheets and Apps Script automationService log from the phone
Readings, chemicals added and notes entered in a short form at each stop and stored per pool, with a note when a number is out of range.
Web apps and MVPs Google Sheets and Apps Script automationCustomer service updates
A short message or email after each visit saying what was done, with photos if the tech took them.
n8n, Make and Zapier automation API integrations and data syncRepair quotes from the field
A tech flags a failing pump or heater, the office gets the request with photos, and a quote goes out the same day.
CRM setup and lead pipelinesRecurring billing
Monthly invoices built from the stops completed, sent and matched to payments, with a nudge for the ones that are late.
QuickBooks, Xero and HubSpot integrations Stripe integration and billingWeather and skip handling
Rain-outs and skipped stops logged and rescheduled, with the customer told when the visit moved.
n8n, Make and Zapier automationPool service software we work with: Skimmer, Pool Brain, Jobber, Housecall Pro, Service Fusion.
And the general tools around it: QuickBooks, Google Sheets, Stripe, Twilio, Zapier, Make, Airtable.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Pool service log
Example: a company with five techs wants each stop recorded on a phone, with chlorine, pH and notes saved per customer and a flag when a reading needs a follow-up.
Google Forms, Apps Script, Google SheetsExample project
Visit confirmation
Example: a weekly cleaning customer gets a short message after each stop saying the pool was serviced and what was added.
SMS, email, the route app's dataExample project
Monthly invoices from completed stops
Example: a small pool company bills monthly. The count of completed stops is pulled, invoices are drafted in the accounting software, and a person approves them.
QuickBooks, Google SheetsQuestions people ask first
We use a pool route app. Do we have to leave it?
No. We start from what it does well and connect what it does not, using the integrations it supports or its exports.
Can our techs use this without training?
We keep the stop form to a few fields on a phone, so it takes a minute to learn.
Who owns what you build?
You do. It is built in your own accounts, with notes on how it works.
How do we start?
Tell us which software you use and the chore that costs you the most hours each week. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com