Wandering Interest
Selected workIndependent product
Project archive

Pool Boy

Pool Boy came out of a real pool route, not a generic app brief. The person in the field needs to know where to go, what happened on the last visit, and whether an equipment problem needs a separate repair.

Pool Boy website from the original project gallery
Project imagePool Boy website from the original project gallery
My role
Product design and AI-assisted development
Designed for
Pool service operators and crews
Product home
Pool Boy has its own site and launch
Project background

The business behind the app

My family’s pool service business in Maricopa gave me a front-row view of what the software had to handle. A weekly service route is predictable until a gate code changes, a pump fails, or a technician needs to know what the last person did. Those exceptions don’t fit well in a checklist that only says whether a stop is done.

Pool Boy is an independent product built around that experience. It is not the pool-cleaning company’s marketing site, and this portfolio page isn’t the product’s signup page. What I wanted to build was software that organizes the ordinary route and preserves the context when the day stops being ordinary.

Behind the project

Independent product

Why a route stop isn’t a repair

A pool can have a recurring service schedule and an open equipment repair at the same time. If those are treated as the same kind of record, closing one can make the other hard to find. The app keeps the visit and the ticket distinct, while keeping both tied to the customer and their service history.

What an assistant can actually do

A conversational request can create or update a service ticket. That makes a useful demo: start with a real action, check the resulting record, and see that the intended details stuck. It’s different from claiming the assistant can do every job in the product or generating an answer that sounds like it made a change.

Operating the thing you built

Releasing a field app means testing outside the development environment. I’ve had to work through differences between development builds and store releases, and look at the handoff between maps, service state, and the screens a technician uses. The job is not finished when a screen looks right on a laptop.

Pool Boy app icon
Project imagePool Boy app icon
How it fit together

The route is the organizing idea

  1. Plan the daySee scheduled stops and the work attached to them
  2. Record the visitKeep what happened with the pool and its history
  3. Follow the repairCreate, assign, or update the ticket separately