Wandering Interest
Selected workFamily business / field operations
Project archive

Maricopa Pool Cleaning

Helping run a pool service business in Maricopa showed me what the work looks like from the route, the customer’s driveway, and the office. Most of the problems that shaped Pool Boy first showed up here as ordinary work that had to get done.

Maricopa Pool Cleaning website from the original portfolio archive
Project imageMaricopa Pool Cleaning website from the original portfolio archive
Setting
Maricopa, Arizona
My part
Helping run the family business and supporting field operations
Related build
Pool Boy, a separate software product
Project background

The route behind the software

Maricopa Pool Cleaning is a family-run service business. It handles recurring maintenance alongside work such as filter cleaning, equipment issues, and one-off visits. A recurring route starts with a familiar list, but the day can change as soon as a tech discovers something that needs its own repair or a customer needs a different time.

My wife started the business, and I helped run it. I got to see the work from both sides: what a tech needs to know at the stop, and what the business needs later to schedule follow-up or explain what happened. This is a case about operations, not the website build; Wandering Devs covers the website separately.

Behind the project

Family business / field operations

The difference between a route and a work queue

Recurring pool maintenance is mostly scheduled ahead of time. A pump lid, an equipment problem, or a follow-up visit can enter that schedule at any point. Keeping routine stops moving without forgetting the exception takes more than knowing which customers are on which day.

What information has to survive a handoff

Someone who wasn’t at the last stop needs enough history to answer the customer or pick up a repair. That can include what was already checked, what still needs a part, and who is supposed to handle the next visit. Those are the details that get lost when the only record is a completed checkbox or a conversation.

What came out of it

Pool Boy grew out of those constraints, but the service business and the software are separate. Working on the route gave me a way to judge the product: does it make the next stop or handoff clearer, or does it just add another thing the tech has to enter?

How it fit together

Three jobs the business has to keep in sync

  1. Run the routeSchedule recurring stops and accommodate changes
  2. Handle exceptionsFollow up on repairs and other nonroutine work
  3. Keep customers informedKeep service expectations and the next action clear