Case study: a 4-truck Midwest shop that built a $180K/year water heater flush program

August 26, 2026 · 8 min read

A four-truck Midwest plumbing shop built a recurring water heater flush program worth roughly $180,000 a year, not by adding techs or chasing new customers, but by systematically turning its existing base of water heater installs into annual maintenance visits. The model is simple and repeatable: track every water heater you install or service, reach out before the annual flush is due, book the maintenance, and reset the clock for next year. The revenue compounds because every install becomes a recurring annual visit, and the only real requirement is the discipline to track the due dates and follow up. This is a case study in turning one-time work into recurring revenue through administration, not technical effort.

The quick answer

Water heaters benefit from an annual flush to remove sediment, extend life, and maintain efficiency, which makes it a legitimate, recommendable maintenance service. The shop's insight was that every water heater it had ever installed was a recurring flush candidate, year after year, and that the value was sitting in its own customer base unrealized. By building a tracked list of water heaters with annual due dates and a follow-up process that rebooked the flush before each anniversary, the shop converted a steady share of its installs into recurring annual visits. At a typical flush price across a large enough base, that compounds to a six-figure annual line. The program is a tracked list plus disciplined rebooking, and almost nothing else.

The revenue was already in the base

The key realization is that the shop did not need new customers to build this line, the candidates were already its own customers. Every water heater it had installed was a home that would benefit from an annual flush, indefinitely, and the relationship already existed. Most shops install a water heater, collect for the install, and never think about that customer again until something breaks. The Midwest shop saw the recurring opportunity in its own install history: a large and growing base of water heaters, each one a recurring annual service waiting to be booked. The revenue was latent in work the shop had already done, which is what made the program so efficient, no acquisition cost, just activation of an existing base.

The mechanism is a tracked list

The program runs on a list: every water heater, the install or last-service date, and the next annual due date. That list is the entire engine. As long as it is maintained and acted on, the program works, because every entry generates a recurring annual booking and every new install adds an entry. The Midwest shop's discipline was keeping this list current and treating the due dates as commitments to act on, not data to ignore. This is unglamorous administrative work, but it is exactly what most shops fail to do, which is why most shops do not have a $180K flush program despite having the same latent base in their install history.

Follow-up is where it lives or dies

The list only produces revenue if someone acts on the due dates by actually reaching out and rebooking the flush, and this follow-up is where these programs usually fail. The flush is non-urgent, the shop is busy with reactive work, and the due-date outreach slips, so the recurring revenue never recurs. The Midwest shop's edge was follow-up discipline: every water heater approaching its flush anniversary got contacted and rebooked, reliably, so the recurrence actually happened. This persistence, applied across a large base, is what compounds into six figures. Without it, the list is just a list, and the latent revenue stays latent. The follow-up is the difference between knowing about the opportunity and capturing it.

Why it scales without more techs

A flush is quick, so a tech can do many in a day, which means the program adds significant revenue without proportional technician cost, the same efficiency that makes any recurring-maintenance line attractive. The constraint, as with backflow testing or any recurring program, is administrative tracking and follow-up, not technical capacity. This is why the Midwest shop could build a $180K line on four trucks: the trucks had the capacity to do the flushes; what released the revenue was the system that tracked the due dates and rebooked them. The program scales with the quality of the administration, not the number of techs, which makes it one of the highest-return additions a shop with an existing install base can make.

Building your own version

Any shop with a history of water heater installs has the same latent base, and the path to capturing it is the same: track every water heater with its annual due date, and reliably rebook the flush before each anniversary. Automated lead follow-up drives the annual rebooking cycle, reaching each customer before their flush is due so the recurrence actually happens, while a phone receptionist books the visit when they respond and dispatch and booking slots it efficiently. The system handles the tracking and follow-up that the program depends on and that busy shops otherwise drop, turning your install history into the same kind of compounding recurring revenue the Midwest shop built.

The bottom line

A four-truck shop built a $180K annual water heater flush program by activating revenue already latent in its install base: track every water heater's annual due date, and reliably rebook the flush before each anniversary. The work is administrative, not technical, so it scales without more techs, and it lives or dies on follow-up discipline. Any shop with an install history has the same latent base, and a system that tracks and rebooks is what turns it into compounding recurring revenue.