Plumbers Recover 11 Hrs a Month on Add-On Quotes in 2026

The water heater call that could have been three jobs

The call was a leaking water heater fitting. It took forty minutes. While the technician was down there with a torch and a flashlight, he also saw a hose bib weeping into the slab, a pressure-reducing valve well past its useful life, and a toilet old enough to be using five gallons a flush. He mentioned all three to the homeowner, who said something like send me a price on those — and meant it.

The invoice that went out that evening covered the fitting. Nothing else. Not because anyone decided against it, but because the finding lived in the technician's head, the price book lived on the office computer, and the eight hours between those two facts were full of other calls. That is the shape of the problem in almost every plumbing shop: the add-on revenue is not lost to a competitor, and it is not lost to price. It evaporates in the gap between seeing the work and quoting it.

Walk the failure backwards and it is always the same four steps, in the same order.

The technician sees the work. This part is not broken — plumbers are extremely good at spotting the next job, because they are already under the sink looking at it. What is broken is what happens to the observation.

The observation gets recorded informally, or not at all. A note in a phone, a line in the job description, a verbal handoff at the end of the day, a photo in a camera roll that never gets attached to anything. None of those are addressable by a workflow, which means none of them can trigger anything.

The office tries to reconstruct it. Somebody in the office wants to quote the PRV but does not know which model, which inlet size, or whether the homeowner asked for a price or was being polite. So they text the technician, who is on another job. The reconstruction costs more time than the original capture would have, and it happens a day later, when the customer's interest has cooled.

The quote goes out late, or not at all. And a quote that arrives five days after the visit is competing against a homeowner who has stopped thinking about it, which is a much harder sell than the one the technician had already half-closed while standing in the utility room. Shops that have already tightened this seam usually did it as part of a broader push on slow quote turnaround in plumbing.

Notice what is not on that list: nobody failed to sell anything. The whole loss happens in the plumbing between the van and the invoice.

TL;DR

• Add-on revenue is a handoff problem, not a selling problem. The technician already found the work; nobody built the path from the finding to a priced option in front of the customer.

• Six automations close that path. Structured capture in the field, price-book lookup, an option built without office typing, a send that does not wait for evening, a follow-up that runs itself, and an exception queue for the jobs that genuinely need a human.

• On the illustrative model in this post, the office side of the add-on path drops from 15.0 hours a month to 3.6 — over eleven hours recovered, at a trade where median plumber pay was $63,800 a year on 2025 data.

• The customer-facing case is unusually easy to make honestly, because the savings are published. Household leaks waste about 9,400 gallons of water a year.

Turning a photo on a phone into a priced option

Six automations, in the order a shop should build them. Each one is a single addressable step, which is what makes the chain testable rather than aspirational.

1. Structured capture at the point of discovery. The technician taps a finding type from a short list — failing PRV, old toilet, weeping hose bib, unsupported line, corroded shutoff — and attaches a photo. Not free text. A finding type is a value a rule can read; a sentence typed into a notes field is not. This single change is what makes the other five possible, and it is the one most shops skip because it feels like the least impressive.

2. Price-book lookup on the finding type. The finding maps to a priced option, or to a small set of them: good, better, best. The technician does not price anything in the field and does not need to remember what a PRV costs this quarter. The price book stays where it already lives and gets read rather than retyped.

3. Option assembly without office typing. The photo, the finding, the scope and the price come together into a customer-facing option automatically. The office's job changes from building quotes to approving the handful that need judgment.

4. Send inside the same day, not the same week. The option goes to the customer while the visit is still the most recent thing that happened at their house. This is the step with the steepest decay curve, and it is the one that manual processes lose first, because the office is busiest at exactly the hour the technicians are finishing.

5. A follow-up that does not depend on anyone remembering. One automatic check-in at forty-eight hours, on the same channel the customer already answered on. Shops that also run this pattern on their inspection work usually recognise it from the sewer camera inspection estimate follow-up workflow.

6. An exception queue, deliberately small. Anything unusual — a finding with no price-book match, a commercial account with negotiated rates, a scope the photo cannot settle — lands in a queue for a human. The point of the queue is not to catch errors. It is to keep the other thirty-odd opportunities a month from waiting behind them.

The payments side of this has quietly gotten easier. According to Jobber, digital payments accounted for more than 51% of the transactions it processed in the first quarter of 2026, a 7% year-over-year increase — the customer who receives an option on their phone is increasingly the same customer who will pay on it from the same device.

Worked example

The scenario is illustrative; the identifiers are real. Take a shop running a field service platform for dispatch and Stripe for billing. The technician taps failing PRV and attaches one photo before leaving the driveway; the finding type resolves against the price book and an option is assembled and sent the same afternoon rather than the following week. When the homeowner approves it, Stripe emits quote.accepted, and the workflow listening on that event moves straight to invoice.sent without anybody in the office rekeying a line item — a path that turns roughly 36 add-on opportunities a month into 34 quoted inside 48 hours instead of 13, while the office time spent on each one falls from 25 minutes to 6. The invoice.paid event closes the loop for the accounting side and releases the job for review. The two or three findings a month that have no price-book match — an odd commercial fitting, a scope the photo cannot settle — go to the exception queue instead, which is the only part of the chain where a human is still required to type.

What the missed add-ons actually cost

The useful way to size this is not "how much revenue are we leaving on the table," which nobody can answer honestly. It is "how many findings does the shop generate, and how many of them become a priced option in front of a customer within two days." That number is countable.

Illustrative model for a four-technician residential shop; opportunity counts and ticket sizes are planning assumptions, not measured data.

Two rows deserve attention. The first row is the largest and the cheapest to fix — twelve findings a month that never became a record at all, which structured capture converts almost mechanically. The last row is the smallest and the most expensive, because a five-day-old quote on a $1,250 ticket is the one a homeowner takes to a second bidder.

The housing stock is running in the shop's favour here. According to Jobber, the average U.S. home is now roughly 44 years old, and homeowners spend about 0.6% of home value on maintenance annually against a recommended 1–4%, implying more than $190 billion of deferred maintenance nationally. The average U.S. home is now about 44 years old. The findings are out there; the constraint is the shop's ability to convert an observation into a priced option before the week turns over.

There is also a genuinely honest customer-value story to attach to the options themselves, which matters because add-on quoting has a deserved reputation for being pushy when it is not grounded in anything.

All figures published by the U.S. Environmental Protection Agency's WaterSense program.

Those numbers do the selling that a technician standing in a hallway should not have to do from memory. According to the U.S. Environmental Protection Agency, the average family's household leaks waste nearly 180 gallons per week, or about 9,400 gallons a year — a figure that turns "you have a weeping hose bib" from an opinion into an arithmetic problem the homeowner can check.

The same is true of fixture replacement. According to the U.S. Environmental Protection Agency, replacing an older, inefficient toilet with a WaterSense-labeled model saves a household about 13,000 gallons and $130 a year — which is the difference between an upsell and a payback calculation the customer can do themselves.

Where the add-on quote should be built

Time-to-live figures are planning ranges based on typical implementation scope, not vendor commitments.

Row one is the honest first answer, and it is worth exhausting before spending anything. If your field service platform already supports mobile estimates against a price book and your technicians will actually use them, configure that and stop — the platform comparison in ServiceTitan versus Sera for plumbing companies is the right place to start that assessment. Row two is not a joke either: a shop generating eight opportunities a month does not have an automation problem, it has a habit problem, and automating a habit nobody has yet is an expensive way to learn that.

Orchestration earns its keep at the seam, which in plumbing is almost always between three systems that were never designed to talk: the field app the technicians tolerate, the price book that lives in the office platform, and the messaging channel the customer actually answers on. This is where US Tech Automations typically starts — reading the finding type and photo out of the field app, resolving it against the existing price book, assembling and sending the option, and routing only the findings with no price-book entry to a human. The upstream half of that, getting the finding captured in a form a rule can read at all, is the same problem covered in stopping missed job details from technicians after close.

The break-even, line by line

Illustrative model built on the opportunity counts above; per-step minutes are planning assumptions, not measured data.

Eleven and a half office hours a month is the recovered figure, and it is worth being precise about what it is and is not. It is real time, at a labour rate the wage data puts a floor under. It is not a revenue projection. The obvious next multiplication — twenty-one extra options quoted inside 48 hours, times an average ticket — is deliberately absent from that table, because the acceptance rate on those twenty-one is the one number in this whole chain nobody can know in advance, and inventing it would make the model more confident and less true.

What the model does support is a straightforward staffing argument. According to the U.S. Department of Labor's O*NET OnLine, plumbers, pipefitters and steamfitters earned a median of $63,800 a year — $30.67 an hour — on Bureau of Labor Statistics 2025 wage data. Office hours and technician hours both come out of a payroll that is not getting cheaper.

Hiring your way out is the alternative, and it is the expensive one. According to the U.S. Department of Labor's O*NET OnLine, employment in the trade stood at 504,500 in 2024 and is projected to grow 5% to 6% through 2034, with about 44,000 openings a year — a market where the marginal hour is bought back through workflow more cheaply than it is recruited.

Which shops this fits

This is written for the owner or operations manager of a two-to-fifteen technician residential or light-commercial plumbing company that already dispatches from software, already has a price book, and already generates more findings than it quotes. If your technicians routinely mention work that never turns into a sent option, the six steps above map directly onto your week.

It fits especially well if you have already tried the two standard remedies. The first is a sales push — commission on add-ons, a spiff, a Monday meeting about "looking for the next job." That works for about a month and then fades, because the technicians were never the bottleneck. The second is a rule that technicians must write up every finding before leaving site, which fails for the opposite reason: it adds unstructured text at the busiest moment of the day and still leaves the office to reconstruct it.

Two shops should not start here. A solo plumber who quotes from the van already has capture, pricing and sending in one head with no handoff — their leak is follow-up, not assembly. And a shop that is still quoting from paper needs a price book in a system first, because a workflow cannot look up a number that only exists in a binder. Recurring compliance work is a partial exception worth noting: shops with a book of testable assets often get more from automating backflow test report renewal reminders before they touch discretionary add-ons at all.

FAQs

Does this turn my technicians into salespeople?

No — it does the opposite. The technician's contribution shrinks to a tap and a photo, roughly three minutes, and the pricing conversation moves off the driveway and into a document the homeowner can read without anyone standing over them. Shops that have tried commission-based add-on programs usually find this version easier to get adopted, precisely because it asks for less.

What if the finding does not match anything in our price book?

It goes to the exception queue and a human handles it. This is by design and the queue should stay small. If more than roughly one in ten findings is landing in exceptions, that is a signal the finding list is too narrow or the price book has gaps — both fixable, and both better discovered as a visible queue than as a quote that silently never went out.

Our field app has an estimates feature. Isn't this already solved?

Sometimes it is, and you should check before spending anything. Native mobile estimating solves this when technicians actually build the estimate on site and the price book is complete. It does not solve it when the estimate still requires office assembly, when the follow-up is manual, or when the photo lives in one system and the price in another. The test is simple: count how many findings from last month became a sent option within two days.

How do we keep the follow-up from feeling like pressure?

Send one, on the channel they already used, with the published savings figures attached rather than urgency language. A single check-in at forty-eight hours carrying an EPA water-savings number reads as information; four messages in a week read as a chase. The restraint is also what keeps the automation from becoming the thing the office has to apologise for.

Will this work if we run more than one system?

That is the normal case, and it is the case orchestration exists for. Most shops have dispatch in one platform, billing in another, and customer messaging in a third. The workflow layer reads from each rather than replacing any of them — which is why the implementation window is measured in weeks rather than the quarter a platform migration would take.

What should we measure to know it is working?

Two numbers, both countable: findings captured per technician per week, and the share of findings that become a sent option within 48 hours. Revenue is the outcome you want, but it is a lagging and noisy measure that will not tell you which step is broken. The capture rate tells you whether the field is participating; the 48-hour rate tells you whether the office path is clear.

Key Takeaways

• The add-on is lost in the handoff, not the sale. Your technicians already found the work; nothing carried the finding to a priced option.

• Structured capture is the unglamorous prerequisite. A finding type is a value a rule can read; a sentence in a notes field is not.

• Speed decays fastest at the send. A quote arriving on day five competes against a homeowner who has stopped thinking about it.

• Keep the exception queue small and visible. Its job is to stop three hard findings from blocking thirty easy ones.

• Model the hours, not the revenue. Over eleven office hours a month is defensible; an acceptance rate on quotes you have not sent yet is not.

• Ground the options in published figures. Household leaks waste about 9,400 gallons of water a year — that is arithmetic the customer can check, not a pitch.

If you want the chain from the worked example — a tapped finding type and a photo resolving against your existing price book, an option assembled and sent the same afternoon, a single automatic follow-up, and only the price-book exceptions reaching a person — wired across the dispatch, billing and messaging systems you already run, US Tech Automations builds that layer without a platform migration. Scoping and pricing for workflow engagements are at ustechautomations.com/pricing, and the broader overview is at ustechautomations.com.