Inside a Bohaus Sprint: A Pool Service and Construction Company

The situation

The client is an owner-led pool service and construction company. Six route techs running weekly stops, a repair tech, a small build crew for new pools and remodels, an office manager, and the owner, who sells the construction jobs. Skimmer runs routes and chemical logs. QuickBooks handles invoicing. Construction projects run on a spreadsheet and a lot of texts.

On a route, techs see everything: a pump that is getting loud, a filter that needs replacing, a heater throwing a code. They note it in Skimmer, maybe snap a photo. Then it sits. The customer gets an invoice at month end and never hears about the failing pump until it fails.

The owner has already tried to fix this in-house. The office manager set up a few message templates and tried sending reports by hand. It lasted three weeks in the spring rush.

What the sprint finds

In Discover, the first question is whether this is a job for outside help at all.

Some AI work is fine to keep in-house. The owner uses a writing assistant for social posts and construction proposals. That is low-risk and owned. There is no reason to pay anyone to manage it.

The route problem is different. It connects Skimmer, photos, repair pricing, customer messaging and QuickBooks. It touches every customer every week. And the internal effort did not stall for lack of skill; it stalled because the office manager also answers the phone, books repairs and chases payments.

In Diagnose, service reports and repair upsells rank first. Repair work is where margin lives on the service side, and the techs are already spotting it. The system just has to carry it from the stop to the customer.

We also note what should stay with people: chemical safety decisions, construction design and pricing, and any customer complaint.

What it builds

In Build, we create a service-report and repair flow inside Skimmer.

At the end of each stop, the tech completes a short structured note: chemicals, condition, anything that needs attention, with photos. The customer receives a clean report the same day. When the tech flags equipment, the system drafts a repair quote from the company's own price list and the equipment on file. The office manager reviews and sends. Approved repairs land on the repair tech's schedule. Completed repairs flow to QuickBooks.

Hand over

In Hand over, the office manager and the lead route tech learn the system in depth. Route techs get a short session on the stop note and photos. The playbook covers the price list, the review queue, and who owns the system. The roadmap marks which next steps the company could take on itself, such as seasonal opening and closing reminders, and which might call for help later, such as connecting the construction side.

What changes

Customers see what was done at every stop. Failing equipment gets quoted before it fails. The repair tech's schedule fills from the routes instead of from emergencies. The office manager reviews instead of typing. And the owner knows which kind of project the company can handle without outside help.

What this means for your business

The hire-or-DIY question has a practical answer. Write down the job, who would own it, how much time they have, and what it costs if it goes wrong.

A pool company drafting social posts does not need help. Connecting route notes to repair quotes and billing probably does. A plumber's after-hours intake or a distributor's order entry usually does too.

If you bring in help, look for a partner who starts with your work, builds rather than advises, fixes the scope, trains your people and measures results.

That is the middle path a Bohaus Sprint is built for: six weeks, fixed scope, one live system inside your tools, and a team trained to run it without us.