Water Treatment Service Software: Build vs Buy for a Multi-Truck Dealer
If your revenue is installs plus straightforward service calls, buy. Jobber or Housecall Pro will schedule, dispatch and invoice you profitably for years.
On this page
If your revenue is installs plus straightforward service calls, buy. Jobber or Housecall Pro will schedule, dispatch and invoice you profitably for years. Build when recurring salt and filter work is a real share of income, because the service clock runs on media life and gallons treated rather than on a 90 day calendar interval, and no field service product has ever modelled that.
What the off-the-shelf products actually do well
Most dealers should buy, and a smaller shop doing mostly installs with a light book of recurring plans should not spend six figures replacing anything.
ServiceTitan, Jobber and Housecall Pro are strong at what they were built for. A job gets scheduled, a technician gets dispatched with the address and the history, a photo gets attached, a card gets taken at the door, and an invoice lands in QuickBooks the same evening. That chain works, and rebuilding it is a poor use of money. ServiceTitan carries the deepest reporting and the call booking screens if you have someone sitting at them. Jobber is priced for a smaller operation and publishes its plans openly, which is more than most of this category does. FieldEdge and Smart Service sit alongside QuickBooks for shops that never want to leave it.
Give them credit for one more thing that only shows up later. Payments, card on file, financing handoffs and the tax handling on a service invoice are jurisdictional, fiddly and expensive to write. Buying that is the right call almost every time.
Buy if your recurring book is small, your salt deliveries are occasional rather than a route, and your install base fits in one person's memory. That is a real business and it does not need custom software. It needs the field service tool configured properly and somebody who actually closes jobs the same day.
Where they stop: a softener has a clock and a calendar does not know it
Your install base is the asset. Every softener, filter bank and reverse osmosis unit you have put in has a service clock, and the clock is not a date.
Sediment cartridges run on a six or twelve month cycle depending on incoming water. Carbon media exhausts on gallons treated, so a 1.5 cubic foot unit on 22 grain water serving a family of five reaches service long before the same unit on softer water serving a couple. Resin beds and reverse osmosis membranes have multi-year lives that shift with feed pressure and chlorine exposure. Salt runs out on an interval you can predict from regeneration frequency.
Field service platforms model recurring work as a calendar interval: every 90 days, every six months, generic. That is the whole gap. The system cannot turn a 2021 install of a specific valve on a specific water chemistry into a due date, so the due list lives in an operations lead's head and in a binder, and heads forget in ones and twos. A cartridge changed as a courtesy and never ticketed. A salt drop confirmed by text and never invoiced. Forty and ninety dollar misses across six hundred accounts and twelve months.
The second gap is that the equipment record does not exist as an object at all. The install lives on a paid invoice from three years ago. That means no warranty coverage per component, no water test result at time of sale to compare against, and no way to answer which customers are running a media type you are about to discontinue.
The third is routing. Salt delivery is a capacity-constrained logistics problem with bag counts, truck limits and delivery windows. WorkWave Route Manager can route deliveries and ServiceTitan can dispatch service, and the two halves of your day never share a map.
The arithmetic: seat cost against the cost to build
Open your last invoice and find the per-user line, because that is the number that grows with hiring rather than with revenue.
A focused first release at $85,000, plus year two at 18 percent, is roughly $100,000 across two years, or about $4,200 a month. At $150 per seat per month the crossover sits near 28 seats. At $250 a seat it falls to about 17. At $80 a seat you need more than 50 users before licence fees alone make the case, and most dealers with 50 field users have other problems first.
Seats alone rarely decide it, though, and pretending otherwise is how these projects get sold badly. The number that decides it is recovered billing. Run one honest count: how many recurring services were performed last quarter, and how many were invoiced. Then how many accounts are past due for a media service nobody flagged. Multiply by your average service ticket.
On the dealers we have built for, that reconstruction alone surfaces several hundred overdue accounts on day one, because it is a one-time pass over years of QuickBooks and legacy records rather than a new process anybody has to adopt. If the recovered figure covers the first release inside a year, the seat arithmetic is a footnote. If it does not, the seat arithmetic will not save the case either, and you should configure what you already own.
What a custom build actually costs
Bands from Digital Heroes delivery experience for an established dealer with multiple trucks.
- First release. Equipment registry with media life rules, automatic due dates and work order generation, salt delivery confirmation and billing on drop, and the historical install base reconstruction. $50,000 to $120,000 in 10 to 16 weeks.
- Full platform. Adds unified dispatch and salt routing, an answering agent for after-hours calls, estimate follow-up, review requests and recurring billing. $150,000 to $350,000 phased over 6 to 12 months.
Data migration runs 10 to 25 percent of the build and in this trade it is the interesting part rather than the boring one. Getting install dates, model numbers, media types and water test results out of Wintac, Smart Service or a decade of QuickBooks line items is what produces the overdue list that pays for phase one. Budget it as work, not as a formality, because the invoice descriptions were written by whoever was at the counter that day.
Year two and after runs 15 to 20 percent of build cost annually. That covers media life rules as you change suppliers, route logic as you add a truck or a second yard, payment processor changes, and the mobile app updates that arrive when phone operating systems do.
One cost sits outside all three lines and it is the one owners resent later. Somebody inside the business has to own this system: approve rule changes, decide what a courtesy service is worth, and answer the technician who says the due date is wrong. That is a few hours a week from a person who already has a job. Dealers who skip it get a well built system that quietly drifts back to the binder inside a year.
The four situations where building wins
Two together is a case. One is not.
- Regulatory fit. You service commercial buildings and your customers operate water management programmes under ASHRAE Standard 188, which means documented control locations, control limits, validation sampling and corrective actions on a schedule. That is a compliance record with your name on it, not a service ticket. Certification records against NSF/ANSI 44, 53 and 58 for the equipment you install belong in the same place.
- Scale economics. Your seat count has passed the crossover above and you are still adding office users to keep up with billing reconciliation.
- A workflow that is your competitive advantage. A salt plan priced per household on regeneration frequency, or a whole-home guarantee that depends on retesting water at every service and showing the customer the before and after numbers. If what wins the job is the thing the product cannot record, you are competing with one hand behind you.
- Integration sprawl across three or more systems. A field service platform, QuickBooks, a routing tool, a review platform and a phone system that none of them talk to. Roll-ups feel this hardest: three acquired dealers on three different systems, and the private equity sponsor wants one view of the recurring book.
How to decide in a week, then buy a written specification
Five days, using records you already have.
Monday, pick fifty accounts on recurring plans at random and check whether each was serviced and invoiced in the last cycle. Tuesday, pick twenty installs from three years ago and try to name the media type and install date without opening a paid invoice. Wednesday, count after-hours calls that went to voicemail last month and how many became jobs. Thursday, time your operations lead reconciling truck tickets to invoices for one week. Friday, add the seat cost and the recovered billing figure together.
If the fifty accounts were all billed, the twenty installs were all identifiable and reconciliation takes under two hours a week, buy and configure. That is a genuinely good outcome and it costs you nothing.
If the week says build, the next step is a paid discovery phase rather than a proposal. Digital Heroes runs discovery to a signed product requirements document covering the equipment registry, the media life rules, the billing triggers and acceptance criteria, and you keep the document whichever firm builds from it. We contract through an India LLP, a US LLC or a UK LTD so intellectual property assigns under your own law, we run our own products including HeroCheckout, and you meet the named engineers before signing. Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S are all checkable.
We are the wrong firm if you want ServiceTitan ripped out on day one. The right first move is nearly always a layer on top through the interface it already exposes, funded by the billing you recover.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The federal government spends about 80% of its IT budget on operations and maintenance of existing systems rather than on development or modernization, with many critical systems being decades old. Source: U.S. Government Accountability Office (GAO) (2025) →
- OECD research finds that digitalisation offers SMEs opportunities to improve performance, spur innovation, enhance productivity and compete more evenly with larger firms; it reports that increased use of online platforms produced significant multi-factor productivity gains in SME-heavy sectors such as hospitality and retail, while smaller firms lag in adoption due to skills, resource and financing gaps. Source: OECD (2021) →
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
- One in four US employees report lacking career advancement opportunities; 48% of employees who participated in mentorship programs report high job satisfaction versus 29% of non-participants, and access to advancement opportunities ranges from 33% at organizations under 10 employees to 74% at those with 1,000+. Source: Gallup (2025) →
Frequently asked questions
How long before a recurring billing engine is actually running on real jobs?
Ten to sixteen weeks for a first release covering the equipment registry, media life rules, automatic work order generation and billing on service completion. The historical reconstruction usually lands earlier than that, often in week four, because it is a read-only pass over your existing records. That report gives your operations lead something to work immediately while the rest of the build continues.
Who owns the customer list and the code if an agency builds our system?
You should own the repository, the cloud accounts, the database and a documented export before the first line is written. Your install base and customer list are the business, and renting access to them is the outcome you are trying to escape. Ask whether anything runs on the agency's own hosting. Digital Heroes assigns ownership at the first commit under an India LLP, US LLC or UK LTD contract.
Can we move years of install history out of Wintac or Smart Service?
Usually yes, though the quality varies enormously. Install dates and customer records extract cleanly. Model numbers, media types and water test results are often buried in free text invoice descriptions written by whoever was at the counter, so expect a matching exercise with human review rather than a clean import. Ask for a data audit before anyone quotes features. That audit is where these projects quietly fail.
What is the difference between a service interval and a media life rule?
A service interval fires every 90 days regardless of what the equipment did. A media life rule computes the due date from the unit model, the media type, the water hardness and iron at the time of sale, and the estimated gallons treated since the last service. On hard water the same softener reaches carbon service months earlier. The interval bills evenly and services wrongly.
Should a dealer with two trucks build anything at all?
No. Configure Jobber or Housecall Pro properly, get every technician closing jobs the same day, and put a reminder discipline around the recurring book. Revisit the question when you pass a few hundred recurring accounts, when someone spends a full day a week reconstructing who was serviced, or when you acquire a second dealer on a different system. Software cannot fix a discipline problem.
Can an answering agent handle a 9pm softener emergency call?
It can triage and book one, which is what you are actually buying. It recognises the caller, pulls the equipment on file, distinguishes a stuck regeneration flooding a garage from a routine salt reorder, books the emergency into the real dispatch calendar against a technician certified for that work, and texts a confirmation. Anything unusual gets taken as a clean message and flagged. It should never diagnose.
What happens to our historical water test results in a new system?
They should become structured fields on the equipment record rather than a scanned attachment, because hardness in grains per gallon, iron and chlorine at the time of sale are the inputs to every future due date. If they only exist on paper test slips, scope a capture project or accept that older units run on a default interval until the next visit retests them.
Can commercial water treatment compliance records live in the same system?
They can, and for dealers serving buildings with water management programmes under ASHRAE Standard 188 that is a strong reason to build. Control locations, control limits, sampling results, deviations and corrective actions form a record your customer will be audited on. Treating that as a service ticket with photos attached is how the record fails when someone asks for twelve months of it.
How do salt routes and service dispatch end up on one board?
By modelling deliveries and service calls as the same kind of scheduled work with different constraints. A salt drop carries bag count against truck capacity and a delivery window. A service call carries a technician certification and a duration. Put both on one map, let the optimiser rebalance when an emergency lands, and the truck stops backtracking. Two separate tools will never do this.
What should we ask a developer before signing a water treatment contract?
Ask them out loud how they would schedule a carbon media service for a specific softener on 22 grain water. If they reach for a generic recurring task every 90 days, they do not understand that the equipment drives the clock. Then ask whether they have shipped route optimisation with real vehicle capacity and window constraints, because salt logistics is not a to-do list.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
If we build for 20 users now, will the software cope with 500 later?
It should, without a rewrite, if it was built on a standard cloud stack; going from 20 to 500 users is mostly a hosting configuration change costing hundreds a month, not a second project. What actually breaks under growth is sloppier work: database queries never indexed for volume and features designed assuming one office's worth of data. Before signing, ask the vendor what happens to the system at ten times today's data, and listen for a specific answer.
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .