Water Utility Software: Build vs Buy for a Mid-Size System
Under roughly 3,000 connections with one pressure zone, buy. Cityworks or a hosted billing package plus your advanced metering portal is the right answer and owning software will cost more than it returns.
On this page
Under roughly 3,000 connections with one pressure zone, buy. Cityworks or a hosted billing package plus your advanced metering portal is the right answer and owning software will cost more than it returns. Build in the middle band, somewhere past 8,000 connections, where the products were designed for someone else and your staff are paying the difference in spreadsheets, apparent losses and regulatory exposure.
What the off-the-shelf products actually do well
Say the unpopular part first. If you serve under about 3,000 connections, run one pressure zone, file a monthly operating report and quarterly bacteriological results, and your crew is four people, buy. Cityworks or a hosted billing package plus your metering vendor's portal will carry you, and anyone telling a small system to build is selling something.
The packaged products are genuinely good inside their own boundaries. Cityworks and Lucity are real computerised maintenance management systems and they do the maintenance management job properly: work orders, crews, costs, inspection cycles, service requests. Tyler Munis, Springbrook and CentralSquare handle utility billing with the rate structures, penalty rules and receipting a finance director needs, and they carry the audit position that goes with public money. Esri ArcGIS holds your network geometry better than anything you would write. Sensus FlexNet, Badger BEACON, Itron and Aclara deliver interval reads reliably and give you a consumption graph and a leak flag.
Two of those deserve extra credit. Billing packages absorb rate ordinance changes and state receipting rules on your behalf, which is a body of work no utility should own. And ArcGIS is the closest thing this industry has to a durable standard, so anything you build should read from it rather than copy it.
None of that is in dispute. What is in dispute is the space between them.
Where they stop: the work order does not know about the meter
Watch one main replacement travel through your stack.
A crew replaces a six inch main on Elm Street. The foreman closes the work order. The as-built sketch reaches the geographic information system technician three weeks later. The valve exercised during the shutdown never gets logged because the valve module was never bought. Two customers on that block get zero-consumption reads for the next cycle because their meters were pulled and reset, and billing does not know a construction event happened, so it estimates. Six weeks later a customer is standing at the counter with a catch-up bill.
That chain is one missing link repeated four times: the work order does not know about the meter, and the meter does not know about the pipe. Nobody sold you the link and nobody will, because each vendor's product boundary is exactly where their revenue stops.
The same gap shows up in leak alerting. You are paying for hourly interval reads across thousands of endpoints. The vendor portal flags continuous flow and produces a few hundred alerts a month, of which the great majority are irrigation, so your customer service representative stops opening the list. The portal cannot distinguish a running toilet, which is small, constant and stable, from a service line break, which is large, started at two in the morning and still climbing, because that distinction needs your own 24 months of history per account plus your pressure zone map. It also cannot correlate a zone pressure dip with a consumption jump on three adjacent accounts, because it does not have your supervisory control data.
Then the valve nobody flagged. A main breaks at midnight, the crew closes the valve grid from the map, and the map does not say valve 3117 has not seated since 2021. Two hundred more customers lose water than needed, which sets the footprint of a boil water advisory. That fact lives in a foreman's memory and it retires when he does.
The arithmetic: per-connection cost against the cost to build
Do this with your renewal quotes on the table rather than a vendor's model.
Add the annual cost of every system in the chain: the maintenance management licence, the billing package, the metering analytics module, the customer portal add-on, the reporting tool. Divide by active service connections and by twelve. Most mid-size systems land somewhere between $0.40 and $0.80 per connection per month once everything is counted.
Now the crossover. A focused first release at $95,000, plus year two at 18 percent, is about $112,000 across two years, or roughly $4,700 a month. At $0.55 per connection per month that breaks even near 8,500 connections. A full platform at $275,000 plus year two is about $13,500 a month, which needs somewhere around 24,500 connections on licence arithmetic alone.
Here is the part that makes this category different from most. The build cost does not scale with connections. The work of joining interval reads to a service point, computing a running average, or generating a state submission is the same at 8,000 connections as at 40,000. The subscription side scales. The maths therefore gets steadily better the larger you are, which is why the honest answer at the small end is buy and at the very large end is that you have already built.
Two figures belong on the buy side and both are usually missing. The staff hours held in the load-bearing spreadsheet that joins two vendor systems. And apparent losses from stopped and slow meters, which are invisible in every packaged report because the report shows what the meter said and the meter said very little.
What a custom build actually costs
Bands from Digital Heroes delivery experience for a system in the middle of this market.
- First release. Interval read ingestion joined to the service point and pressure zone, the asset spine with condition state, and one high value workflow, usually leak triage or compliance sampling. $60,000 to $130,000 in 12 to 16 weeks.
- Full platform. Adds supervisory control historian integration, offline field mobile, hydraulic model exchange, the customer portal and generated state submissions. $150,000 to $400,000 phased over 6 to 12 months.
Data migration runs 10 to 25 percent of the build, and in a water utility it is mostly reconciliation rather than movement. If your service point identifiers and your billing accounts do not share a reliable key, somebody is matching records and verifying a sample in the field before the useful part starts. On a 12,000 connection system that is four to six weeks. Budget it rather than discovering it in week nine.
Year two and beyond runs 15 to 20 percent of build cost annually. That money maintains metering vendor interfaces, which are rate limited and change; the state report formats, which change more often than the rules do; and the mobile app your crews use in a trench.
The four situations where building wins
Two together is a case. One is a preference.
- Regulatory fit. Your service line inventory under the Lead and Copper Rule Revisions needs a material on both sides of the meter with a basis of evidence, and the replacement programme under the Lead and Copper Rule Improvements will run for years against it. Add locational running annual averages for total trihalomethanes and haloacetic acids under the Stage 2 Disinfection Byproducts Rule, the annual Consumer Confidence Report due by 1 July, and risk and resilience obligations under America's Water Infrastructure Act. None of that is generic and vendors build to the federal floor.
- Scale economics. You are past the connection crossover above and every acquisition adds another billing system rather than another customer.
- A workflow that is your competitive advantage. For a public utility read that as the thing your board judges you on: non-revenue water. If you cannot separate real loss from apparent loss in an AWWA water audit because the answer needs interval reads, production meters and the district metered area map together, no single product holds all three.
- Integration sprawl across three or more systems. A metering head end, a billing package, a maintenance management system, ArcGIS and a historian. When the connective tissue is one long-serving employee, that person is a system with no backup and no documentation.
How to decide in a week, then buy a written specification
Five days, no procurement required.
Monday, find every spreadsheet that joins data from two vendor systems and is load-bearing for a decision or a filing. Tuesday, take last month's leak alert list and work out how many were genuinely actionable. Wednesday, ask two vendors for an integration between the systems you already own and see whether the answer is a data export. Thursday, pick ten service lines at random and try to produce material, basis of evidence and a photograph. Friday, compute the per-connection stack cost.
If there are no load-bearing spreadsheets and the service lines answer cleanly, buy and stop. That is a well run utility and a build would be an expensive way to prove it.
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 asset data model, the service line record, the read ingestion contract and acceptance criteria, and you keep that 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 Section Vault, 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 any control path through an application. Anything we build against your operational network is read only, and a developer casual about that boundary has never been near one.
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.
- McKinsey found that tech debt can amount to 20-40% of the value of a company's entire technology estate before depreciation, and CIOs report that 10-20% of the budget for new products is diverted to resolving tech-debt issues. Source: McKinsey & Company (2020) →
- Only 16% of respondents said their organizations' digital transformations had successfully improved performance and equipped them to sustain gains over the long term; even in digitally savvy industries such as high tech, media, and telecom, self-reported success rates did not exceed 26%. Source: McKinsey & Company (2018) →
- Bersin by Deloitte research found organizations that use HR technology and employee-centric design to build a flexible, empowering workplace are more than 5 times more effective at improving employee engagement and retention than their peers, and 2.5 times more likely to reach 'high-impact' status by leveraging HR for digital transformation. Source: Bersin by Deloitte (2017) →
- In a McKinsey global survey of 1,259 respondents, only about 20% said their organizations excel at decision making, and just 37% said their organizations' decisions were both high quality and high in velocity. Source: McKinsey & Company (2019) →
Frequently asked questions
How long does a first release take for a utility with 15,000 connections?
Twelve to sixteen weeks for interval read ingestion joined to service points, the asset spine and one workflow such as leak triage. Add four to six weeks if your service point identifiers and billing accounts do not share a reliable key, because that reconciliation has to finish before anything downstream is trustworthy. A full platform with historian integration and generated state submissions phases over six to twelve months.
Who owns the code and the operating history if a developer builds this?
You own the repository, the database and a documented export, and it belongs in the contract at signing rather than at final payment. You are a public entity with a forty year asset horizon. A vendor that folds should cost you a migration, not your operating history. Digital Heroes assigns ownership at the first commit and contracts through an India LLP, US LLC or UK LTD entity.
Is it safe to connect custom software to our SCADA system?
Only read only, and only through an architecture your operational technology staff design. The right answer involves a one way path or an equivalent boundary, no control commands from the application, and a security review before any code conversation. Expect that discussion to add several weeks and a real cost. A developer who treats the operational network boundary casually has never worked behind one.
Can a custom system pull data from a Sensus or Badger metering platform?
Yes, through the vendor interface, and the practical constraints are rate limits and read latency rather than access. Ask any candidate whether they have pulled from that specific head end in production. Teams that have not usually discover the limits in month four and rewrite the ingestion layer. Pull the reads into your own store so you can join them to zones, districts and account history.
What is the difference between real loss and apparent loss?
Real loss is water that left the system through leaks, breaks and overflows. Apparent loss is water delivered and consumed but not billed, mostly through stopped or slow meters, unauthorised consumption and data handling errors. They need entirely different responses, one a capital programme and the other a meter change-out list. Separating them needs interval reads, production meters and the district map joined together.
Should a small system with 2,000 connections build anything?
No. Buy a hosted billing package, use your metering vendor's portal, and put the money into inspection and valve exercising instead. Revisit the question if you acquire a neighbouring district, because acquisitions are what pull small utilities into the middle band where products designed for someone else start costing real staff time and the arithmetic changes quickly.
Can document extraction handle contract laboratory result reports?
It handles them well, which is unusual enough to be worth saying. Laboratory reports are semi-structured, they vary by laboratory, and a model reads analyte, result, units, method, collection date and sample site identifier reliably enough that a person reviews exceptions instead of keying everything. Route low confidence extractions to a human queue. Never let unreviewed values reach a compliance calculation.
What happens to our data if we later replace the billing system?
That is exactly why the join belongs in something you own. If interval reads, service points, assets and compliance records live in your own store keyed to a stable identifier, a billing replacement becomes an interface change rather than a migration of your operating history. Utilities that keep everything inside vendor products replay the same painful migration every time a contract ends.
How should a service line inventory record be structured?
Utility-side material and customer-side material as separate fields, each with a basis of evidence, a date, the person or record that established it, and a photograph where the line was physically observed. Unknown is a valid state and should be tracked as one. If a developer proposes a single material field, they have not read the rule and will learn on your budget.
What should we ask a developer before signing a utility contract?
Ask what data model they would propose for a service line before anything else. Then ask which systems they have integrated by name rather than in general. Then ask what happens when supervisory control is involved, and listen for read only and a boundary review. The service line question is the sharpest domain test in this category because regulation, mapping and the physical world all disagree.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
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 is the biggest mistake first-time software buyers make?
Choosing the lowest quote without asking why it is the lowest. A bid 40% under the field usually gets there by skipping tests, documentation, and code review, which are invisible in a demo and brutal to pay for later; every stalled project Digital Heroes has been asked to rescue tells some version of that story. The second mistake is signing without a written scope, which reliably turns the winning cheap quote into 1.5x to 2x the price by launch.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
Is a solo freelancer enough for my project, or do I really need an agency?
A solo freelancer is a fine choice for a well-defined build under roughly $15,000 to $20,000 with a limited lifespan: an internal calculator, a scripted integration, a prototype. Above $50,000, or for any system your business will depend on for years, you are buying continuity as much as code: enforced code review, cover when someone is ill, and support that outlasts one person's career plans. Price the risk of a single point of failure, not just the hourly rate.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
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.
Does the tech stack matter, and which one should I ask for?
It matters less than agencies imply, provided it is boring. A mainstream stack, something like React or Next.js on the front end, Node.js or Python behind it, and PostgreSQL for data, means thousands of developers can maintain your system if you ever change vendors. Apply one test: ask how hard it would be to hire a replacement developer for the proposed stack, and walk away from anything built on an agency's in-house framework.
How long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
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 .
