The short answer
A CRM models the customer. Field service software models the job. Plumbing runs on a third record that neither category ships by default: the assembly, fixture or line at a specific address, carrying a date.
That is why plumbing shops that buy either category correctly still end up with a spreadsheet, a wall calendar, or a second subscription bolted onto the platform they already pay for.
The HVAC version of this question has a clean answer, which I wrote up in CRM vs field service software for HVAC: measure the share of revenue that must be sold before it can be scheduled. Ported to plumbing, that test misfires, because it assumes your problem is unsold work sitting in a pipeline. In plumbing the work is not unsold. Nobody has thought of it yet, including the customer.
Why the plumbing version of this question is different
Plumbing is the trade with the weakest natural repeat cycle, and every software decision follows from that.
PipelineOn's 2026 plumbing retention guide states the problem plainly: HVAC has a seasonal forcing function built into the physics, where spring brings the AC tune-up and fall brings the heat tune-up, and the weather sells the second visit for you. Plumbing has no such cycle. A water heater can run 10 to 12 years with zero scheduled service. A drain cleared in 2024 gives the homeowner no reason to call in 2025.
That guide puts typical plumbing retention at 40 to 60 percent year over year. Main Street Wealth, which underwrites plumbing acquisitions, calls the trade structurally different from HVAC or pest control because most demand is event driven: a clog, a leak, a failed water heater.
By the numbers
Plumbing agreement books trade at 1.5 to 2.5x ARR in Main Street Wealth's 2026 underwriting model. HVAC books trade at 2.0 to 3.0x, pest control at 2.5 to 4.0x. That gap is not a quality judgment. It is the market pricing the absence of a calendar.
So the question is not "which category manages my work better." It is "which system manufactures a reason to go back," because your trade does not manufacture one for you.
The three records, and the one plumbing runs on
Every platform in this market is built around a primary key. There are three candidates, and only one of them survives a decade.
| Record type | What software calls it | Good at | Cannot answer |
|---|---|---|---|
| The person | Customer, contact, lead | Follow-up, marketing, reviews | "Which address has a tank older than eight years" |
| The event | Job, work order, ticket | Dispatch, tech time, parts, invoice | "What is due next year that nobody has called about" |
| The thing | Asset, device, assembly | Due dates, test history, install dates, warranty clocks | Nothing, if the platform actually has it |
A CRM is keyed on the person. Field service software is keyed on the event. Plumbing's compounding revenue is keyed on the thing, and the thing outlives both.
The tank you installed in 2018 does not belong to the customer record, because that customer may have sold the house. It does not belong to the job record, because that job closed and got invoiced seven years ago. It belongs to the address. If your system cannot key on the address, then in 2027, when that tank is at end of life, you find out the same way a stranger would: the phone rings, or it does not.
I covered the revenue side of this in plumbing lead generation without buying leads. Main Street Wealth shows the stake: top operators capture more than 35 percent of water heater replacements inside their existing base, and buyers value that captive stream at 4 to 6x EBITDA versus 2.5 to 4x for retail acquired install work.
The trigger test
One number settles the category question for a plumbing shop.
What share of next year's revenue could you put on a calendar today, without waiting for anyone to call you?
Count the work with a date attached to something you already know about: backflow assemblies due for annual test, agreement inspections owed, water heaters past eight years in homes you have served, tankless descaling, filter changes, sewer warranty inspections, multifamily preventive work. Divide by projected revenue.
- Under about 5 percent. A pure break-fix shop. Field service software is the whole answer, and anyone pitching you a sales pipeline is selling a feature you will never open.
- Roughly 5 to 25 percent. Where most residential shops sit, and where the pain starts. Enough triggerable revenue that forgetting it costs real money, not enough that anyone built you a process. The spreadsheet zone.
- Above about 25 percent. Backflow route work, a real agreement book, or a property portfolio. Asset records have to be first-class, and a platform that treats them as an afterthought will cap your growth.
Notice what this ignores: how many trucks you run, the axis every buyer guide sorts on. A two-truck shop with 400 backflow assemblies on an annual route has a harder data problem than a six-truck shop doing nothing but drain calls.
If the trigger test puts you above 25 percent and every platform you have demoed treats assemblies, permits and install dates as custom fields, that is the case for a system built around your actual records. We build custom CRMs for trades that model the address, not just the invoice.
The proof both categories missed it: backflow has its own software industry
The strongest evidence that general platforms do not solve this is that a whole separate industry grew up to fill the hole, and it sells to plumbers who already own a field service platform. Tokay has published dedicated backflow administration software since 1986. Syncta sells test management to testers and purveyors, SwiftComply to utilities, and Inspect Point claims more than 16,000 users.
Read what Inspect Point says the problem is, in its own copy:
When you're responsible for inspecting or servicing multiple devices across multiple properties, it's easy to lose track of due dates, renewal cycles, or jurisdiction-specific submission windows. Manual reminders and calendar-based tracking often fail, leading to missed tests, non-compliance, and penalties for both the contractor and the customer.
Then read the fix it sells: device-level tracking including location and test history, customer-wide views showing due and overdue devices, digital asset records, and hundreds of regional test forms.
That is a product description of the third record. No vendor builds "customer-wide views of due and overdue devices" unless the platforms already on the market cannot produce that list. Syncta claims its users average eleven more backflow tests per week than non-users. Take the vendor number with the usual scepticism, but the direction is not in doubt: the constraint on a backflow route is not wrench time, it is knowing who is due.
Tip
If you do backflow work, ask your current platform to produce one report: every assembly you tested last year, its address, its serial number, and its next due date. If the answer involves exporting invoices and reading line item descriptions, you do not have an asset record. You have a job ledger with the word "backflow" typed into it.
The credential is a record too, and in California it has a date on it
There is a second date-bearing record neither category models, and getting it wrong makes a scheduled job invalid rather than merely late: the tester's certification.
California is the live example. In a letter dated June 17, 2025, the State Water Resources Control Board formally recognised ASSE International's 5110 Backflow Prevention Assembly Tester certification as meeting Section 3.4.1 of the state's Cross-Connection Control Policy Handbook, and per ASSE that recognition runs until July 1, 2027. From July 1, 2026 through June 30, 2027, testers must hold certification from an organisation recognised under the handbook. Effective July 1, 2027, only organisations accredited by ANAB to ISO/IEC 17024 qualify.
Three dates inside a two-year window, each determining whether a test your technician performs gets accepted by the purveyor.
Now ask where that lives in your software. A dispatch board schedules a person against a time slot. It does not know the person holds a credential, that the credential expires, or that dispatching them after that date produces a report the water authority will reject. Gauge calibration is the same shape.
The status your dispatch board does not have
Plumbing is permit-heavy in a way that breaks the standard job lifecycle, and the tell is that no field service platform has a status for it.
Take the City of San Diego. A simple no-plan permit covers water heater replacements except tankless types, water and sewer piping repairs, gas line repairs, drain replacement, water softeners and pressure reducing valves. Tankless installs need the plan permit path instead. And the sequencing matters: the permit issues once you apply and pay, and only once issued can an inspection be scheduled.
So a routine tank swap, the most ordinary job in residential plumbing, has a state where the water is hot, the customer is happy, the technician has left, and the file is not closeable because an inspector has not been out. Your job statuses are scheduled, in progress, complete, invoiced. None is true.
Shops handle this with a whiteboard, and permits get missed. That is not a discipline failure, it is a missing state in the data model, and it is the same error as the backflow due date: a workflow with a third-party clock on it, running outside the system of record.
The problem that happens before either system
In plumbing, more revenue is lost before a record exists than inside either category. As a plumber posting in r/Plumbing put it: "Customer calls, I'm elbow deep in a drain, call goes to voicemail, they never leave a message. By the time I call back they already booked someone off Google." A 411 Locals study, cited in SMBcrm's 2026 plumbing CRM comparison, found 62 percent of calls to small businesses go unanswered, and a person standing in water dials the next result rather than leaving one. More on that in answering service vs missed call text back. If your trigger test came out near zero and your calls go unanswered, fix the phone before you buy anything.
What "our field service software already has a CRM" means for a plumber
It usually means a customer list, a note field, and automated review requests. Useful, and none of it an asset register. The platform is excellent at the job record, competent at the customer record, and treats the thing at the address as a custom field you may populate yourself.
The vendors that do solve it say so specifically. FieldCamp describes modelling the book of business so each property holds its plumbed fixtures, with each fixture carrying its own service history. BuildOps sells customer hierarchies surfacing multi-property relationships. That is different language from "manage your customers," and the difference is the product.
What owners underestimate is capture. From r/Plumbing, on why data quality decays even inside a good platform:
The bigger issue in practice is remembering to log the job at all. If it takes more than a minute or two after finishing the job most guys just skip it and move on to the next call.
If recording a water heater serial takes ninety seconds, it does not get recorded, and the trigger-test thesis collapses. Capture has to be a photo of the data plate or a barcode scan, not a form.
Watch out
Check cost before you fall in love with a feature list. SMBcrm's 2026 breakdown puts ServiceTitan at roughly $245 to $398 per technician per month, quote-only, plus a $5,000 to $50,000 implementation running two to twelve months. A solo plumber in r/Plumbing put the fit problem memorably: trying ServiceTitan was "like trying to fly a boeing 747 just to fix a leaky faucet."
The exit-value argument nobody makes
If you ever intend to sell, the record type you chose is a line in the valuation model.
Main Street Wealth's 2026 plumbing underwriting math builds enterprise value by stream: agreement ARR at 1.5 to 2.5x, captive replacement EBITDA at 4 to 6x, multifamily and commercial recurring at 5 to 8x, retail one-time at 2.5 to 4x, new construction at 3 to 4x. Two shops with identical EBITDA transact at very different numbers on that mix alone.
Buyers want exportable transaction-level data, and per that analysis, spreadsheet-run shops still transact but at a 0.25 to 0.5x ARR discount. Worse, most operators have meaningful captive replacement revenue and cannot prove it. Proving it means a cohort report tying installs to the customer base over years. If install dates live in invoice line items rather than asset records, that report does not exist, and unprovable revenue gets valued as retail one-time work at roughly half the multiple.
Renewals work the same way. They do not happen because customers remember. They happen because something with a date fired.
The demo script
Ignore the dispatch board. Every vendor demos it well because it is the strongest part of every product here. Ask for these five things live instead.
- The eight-year list. "Every water heater we installed more than eight years ago, with address and install date." The highest-value report in residential plumbing, and most platforms need an export and a spreadsheet.
- The address with two owners. "One property, two different past customers, continuous fixture history." If history is stapled to the person, property management and resale work will bleed.
- The due list. "Every backflow assembly due in the next 60 days, with serial number and purveyor form." If you do compliance work, this report decides the purchase.
- The expiring credential. "Flag a technician whose tester certification expires before a job already on the board." Almost nothing does this, and the reaction tells you whether they know the trade.
- The permit state. "Every job physically complete but waiting on an inspection." If the answer is a custom tag someone must remember to apply, it will not be applied.
Then: how many taps to record a new water heater's serial, model and install date? More than about three and the asset register will be empty in a year.
The decision framework
| Your situation | What you actually need |
|---|---|
| Break-fix drain and emergency work, triggerable revenue under 5 percent | Field service software alone. Skip the CRM pitch, spend the difference on call answering. |
| Calls going to voicemail during the day | Neither. Software cannot organise a lead that never arrived. |
| Residential service with an agreement book you want to grow | Real asset records and cheap field capture. Weight the eight-year list heavily. |
| Backflow or compliance route work above roughly a quarter of revenue | Device-level tracking with jurisdiction forms. Expect a specialist tool alongside, or a build. |
| Property management, multifamily or rental portfolios | Property-keyed history. Test with the two-owners question first. |
| Heavy permit work, repipes and sewer replacement | A job state between complete and closed, and a report on it. |
| Planning a sale in the next three to five years | Exportable transaction-level data and a provable attach rate. Start recording install dates now. |
When a custom build is the honest answer
Most plumbing shops should buy. Field service platforms have solved dispatch, mobile invoicing and payments well, and rebuilding that is a bad use of money.
The build case appears when the trigger test comes out high and the records you need are the ones no vendor treats as first-class: a compliance route business paying two platforms to describe one workflow, a multifamily book where customer-keyed software fights the property hierarchy, or a shop with so many workarounds that the spreadsheets are the real system of record.
The threshold is the same as for any trade. When annual software spend approaches roughly 1 percent of revenue and you still keep parallel spreadsheets for the records driving your recurring revenue, owning the data model becomes a straight comparison against renewal. That math is in custom CRM vs off-the-shelf CRM.
We build custom CRMs for plumbing and trade businesses around the records that actually generate revenue: the property, the assembly, the install date and the permit state. If you have run the trigger test and nothing on your shortlist can produce the eight-year list, that is a conversation worth having.
The bottom line
The CRM versus field service software framing offers a plumbing owner two records and asks them to pick. Both are real, and for most shops neither is where the compounding revenue lives.
Your trade has no season. Nothing in the calendar tells a homeowner to call you, so every repeat job either arrives as an emergency or arrives because your system fired on a date attached to a thing at an address. Field service software runs the job beautifully once it exists. A CRM runs the conversation. Only an asset record creates the job.
Run the trigger test. If the number is near zero, buy field service software, fix your phones, and stop reading buyer guides. If it is meaningful, evaluate platforms on one question instead of dispatch: can it tell you what is due next year, at which address, on which device, without anyone calling you first.
Sources
- Plumbing Customer Retention in 2026, PipelineOn, on the absence of a seasonal forcing function in plumbing, 40-60 percent typical retention, and service agreement pricing and inclusions
- How Private Equity Values Plumbing Service Contracts (2026 Math), Main Street Wealth, on ARR multiples by stream, captive replacement attach rates, churn bands and the spreadsheet-run discount
- Backflow Prevention Software, Inspect Point, on device-level tracking, due and overdue device views, and the stated failure of calendar-based tracking
- Backflow Assembly Testing Solution, Syncta, on assembly records, purveyor forms and reported tests-per-week gains
- Backflow Prevention Software for Water Utilities and Tokay Software, on the scale and age of the dedicated backflow compliance software category
- ASSE 5110 Backflow Prevention Assembly Tester Certification in California, ASSE International, on the June 17 2025 SWRCB recognition letter, the July 1 2026 and July 1 2027 dates, and the ISO/IEC 17024 accreditation requirement
- Plumbing/Gas Permit, City of San Diego Development Services, on which plumbing work needs a permit and the permit-then-inspection sequence
- Best CRM for Plumbers in 2026: 6 Options Honestly Compared, SMBcrm, on ServiceTitan, Jobber and Housecall Pro pricing and the 411 Locals unanswered-call figure
- Plumbers, what app/software do you use to handle scheduling, dispatching, invoicing, and job tracking?, r/Plumbing, quoted operators on intake before software, job logging friction and platform fit
- Quickbooks for plumbers is it worth with a CRM?, r/Plumbing, on double entry and sync problems across two systems
- Plumbing Software, Scheduling and Invoicing and Plumbing Field Service Software, on property-keyed fixture history and multi-property customer hierarchies