Non-Revenue Water Management Software: Custom Build vs Off the Shelf
Buy the detection technology and stay manual on the rest, unless you serve more than roughly 30,000 connections. Satellite, acoustic and correlation vendors are good at finding leaks and you will not out build them.
On this page
Buy the detection technology and stay manual on the rest, unless you serve more than roughly 30,000 connections. Satellite, acoustic and correlation vendors are good at finding leaks and you will not out build them. What no vendor sells is the ledger their findings report into, and that is the only thing worth commissioning, once your system is large enough to justify owning it.
What the off the shelf products do well
The detection vendors are genuinely good and you should buy from them. TaKaDu reads events out of your supervisory control and data acquisition system and tells you something changed in the network. Asterra flies satellite analysis over your service area and hands back likely leak polygons that narrow a survey from a whole zone to a few streets. Echologics and Aquarius Spectrum do acoustic logging and correlation properly. Xylem Visenti works the pressure and hydraulic side. None of that is worth rebuilding and we would not quote it.
The American Water Works Association Free Water Audit Software is also a good instrument and it is free. It implements the M36 water balance faithfully, it produces the validity scoring, and for a small system it is an entirely rational annual exercise. Do not dismiss it because it is a spreadsheet.
Buy, or stay manual, if you serve a small system, your audit validity scores are already decent, and your losses sit in a range you can defend to a board. An acoustic survey contract every couple of years plus the audit workbook is a sensible programme, and a custom build would be an expensive way to formalise a number you already trust.
What none of these products claim to be is your source of truth for the balance itself. They each hand you findings. Nobody is offering to own the ledger.
Where they stop: allocating billed consumption to a zone and a month
Here is the specific workflow that breaks every generic tool. District metered area flow arrives every fifteen minutes. Billing arrives monthly or bimonthly on staggered read cycles, aggregated by account, and the accounts do not map cleanly onto zone boundaries because nobody drew the zones to match the billing routes. So the comparison everyone wants, what entered this zone against what was billed inside it, needs a spatial join and a time reallocation that no spreadsheet performs correctly.
That is why minimum night flow analysis is universally recommended and rarely used properly. The technique is sound: in a mostly residential zone, flow at three in the morning approximates leakage plus a small legitimate night use allowance. Doing it well needs closed zone boundaries, reliable zone metering, a night use allowance derived from your own low consumption accounts rather than a textbook figure, and somebody watching a trend rather than one night.
The second thing they miss is apparent loss, and it is invisible by design. An aging positive displacement meter under registers low flows first, so it keeps reporting a plausible number while missing a growing share of actual use. Multiply a small under registration across 40,000 meters and it becomes one of your largest single loss components while looking like nothing on any dashboard. Detection vendors have no view of it. The billing system does not either, because from its perspective the meter reported a number and the number was billed. Utilities usually discover the scale during a replacement programme, when consumption jumps and customers complain about bills that were previously too low.
The arithmetic: cost per service connection against a build
Vendor pricing in this category is usually per service connection per year, per district metered area, or per square mile of satellite coverage per pass. Restate every quote as annual cost per service connection and the picture clears up quickly.
At 8,000 connections, two satellite passes a year plus an acoustic survey contract plus the free audit workbook is a complete programme for a modest annual figure, and there is no build that improves on it. Your consultant assembles the audit in February, the validity score is mediocre, and that is an acceptable outcome at that size.
At 120,000 connections the same programme costs six figures a year and returns findings nobody reconciles. Add the consultant fee for the annual audit, the analyst time spent stitching production totals to billed consumption, and the capital you spend on parallel builds because the record only trusts part of the network. The crossover we see is between 30,000 and 50,000 service connections, and it arrives earlier if you are subject to a validated audit filing regime or if you already run district metering that nobody analyses.
One number decides this more than any other. Ask what you spent on detection last year, then ask how many verified leaks it produced and what volume was recovered. If nobody can answer, you are buying detection forever without moving the annual number, and that is a measurement problem rather than a technology one.
What a custom build actually costs
In Digital Heroes delivery experience a focused first release covering an automated monthly water balance by zone computed from source systems, real against apparent loss separation, minimum night flow analysis and a prioritised survey target list runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding vendor finding ingestion with payback tracking, meter fleet testing economics, pressure management analysis, capital prioritisation and the state audit submission runs $150,000 to $350,000 phased over 6 to 12 months.
Data migration is 10 to 25 percent, and it is spent in an unusual place: your billing system. Read cycle handling in older municipal billing platforms is frequently undocumented, and getting historical consumption out with the read dates intact is the single longest task in the project. Budget the upper end if you are mid rollout on advanced metering infrastructure, because you then have two consumption data models to reconcile for a couple of years.
Year two is 15 to 20 percent of build cost annually. It buys zone boundary changes as the network grows, billing system upgrades, new vendor finding formats, and the annual audit submission format when your state revises it.
The cost that will not fit in a software quote is metering. A build cannot compute a balance for zones that are not properly metered or whose boundaries do not actually close, and discovering that mid project is common. Fund zone metering as capital work with its own line before you fund software.
The four situations where building wins
Regulatory fit. If you are an urban retail water supplier in California, Senate Bill 555 obliges you to file validated annual water loss audits, and the validity score is part of the filing rather than a footnote. Once the audit is a regulated submission rather than an internal exercise, computing it monthly from source data instead of typing it once a year changes both the score and the defensibility. Products do not file your audit. A build makes the submission a report you run.
Scale economics. Above roughly 30,000 to 50,000 connections, per connection detection pricing plus consultant fees plus analyst time exceed the annual cost of owning the ledger.
A workflow that is your competitive advantage. For a utility that reads as accountability rather than competition. If loss reduction is a funded multi year programme you have to report on publicly, the ability to show cost per verified leak and per recovered volume by detection method, in your own system, is what keeps the funding. No vendor will ever compute that number for you, because it ranks them.
Integration sprawl. A supervisory control historian, a municipal billing system, an advanced metering head end, a Geographic Information System and a work order platform is five integrations before a single detection vendor is added. At that point you are paying for integration either way.
How to decide in a week
Take your last submitted water audit, sit down with whoever prepared it, and go line by line asking where each number came from and how it was derived. Not what it means. Where it came from. The lines nobody can answer are the project, and in most utilities that is unbilled authorised consumption, apparent loss and anything involving read cycle alignment.
Then do one piece of arithmetic. Take your three worst zones, pull twelve months of night flow data, and estimate legitimate night use from your own lowest consumption accounts rather than a manual figure. If the resulting leakage estimate is wildly different from what your audit implies, your annual number is not measuring what you think it measures.
If both come back clean, you do not need a build. Renew the survey contract, keep using the audit workbook, and spend the money on meter replacement, which is usually the better return anyway.
Two questions for every firm on your shortlist, including this one. Which legal entity signs, because assigning intellectual property under Indian, United States and United Kingdom law requires three different instruments, and a public utility should hold the one enforceable where it operates. Digital Heroes maintains an India LLP, a US LLC and a UK LTD for that purpose. And will you meet the engineers before contract rather than a bench that arrives in month two. The rest you can verify yourself: more than fifty specialists, over 2,000 delivered projects, and records on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Then fund a paid discovery phase before capital is committed. Ours ends in a signed product requirements document covering the balance model, the read cycle allocation rules, zone definitions, integration points and acceptance criteria. You own that specification whether you build with us, build with somebody else, or hand it to your engineering consultant. We are the wrong firm for you if you want a leak detector built, or if you serve a small system where the audit workbook and an acoustic contract are the right answer.
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) →
- 76% of organizations report that less than half their CRM data is accurate and complete, and 37% experienced direct revenue loss attributable to poor data quality (survey of 602 CRM users across the US, UK, and Australia). Source: Validity (2025) →
- The median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
- 73% of surveyed businesses now use a headless architecture (up nearly 40% since 2019), and 98% of those not yet using it are evaluating or planning to evaluate headless within 12 months, with 82% saying it makes delivering consistent content easier. Source: WP Engine (2024) →
Frequently asked questions
How long before a custom water loss system produces a usable monthly balance?
Twelve to sixteen weeks to a first release, but the first balance it produces will be wrong and that is expected. Plan two to three months of tuning while you reconcile against known quantities, correct zone boundaries and fix read cycle assumptions. Utilities that treat the first output as final rather than as a hypothesis to test end up distrusting the system and going back to the spreadsheet.
Who owns the data and the calculations if we commission a build?
The utility should own the repository, the cloud accounts and every derived dataset, settled in writing before kickoff. This matters more here than in most sectors because your audit submission has to remain defensible for years and a regulator may ask how a figure was derived. At Digital Heroes the client owns the code from the first commit and the system runs in the client account.
What happens if our district metered areas are not properly closed?
You find out during discovery, and it is common. A zone with an unrecorded interconnection or a valve someone opened during a main break produces a balance that looks like catastrophic leakage. The honest answer is that this is field work, not software: valve surveys and boundary verification come first. Budget it separately and start with the three or four zones you trust most.
Can we build only the balance and keep using our current detection vendors?
Yes, and that is the shape we recommend. Keep buying satellite, acoustic and correlation work from the specialists. Build the ledger they report into, with one finding object carrying a source, a location, a confidence and a status, plus the repair outcome and an estimated recovered volume. After a year you can rank detection methods by cost per recovered volume in your own system.
What is the difference between apparent losses and real losses?
Real losses are water that physically leaves the system through mains, service lines and storage. Apparent losses are water that was delivered but not billed correctly: meter under registration, data handling errors and unauthorised consumption. The distinction matters because the remedies are completely different. Real losses are fixed with survey crews and pressure management. Apparent losses are fixed with meter testing and billing corrections.
Should we replace meters on an age threshold or on test results?
Test results, sampled by cohort so the numbers are statistically usable rather than opportunistic. Track the fleet as an asset population with install date, make, size, cumulative registered volume and test outcomes, then build the replacement case on recovered revenue per meter class. A finance director will accept that argument. An age threshold argument gets deferred every budget cycle.
What happens if a council member asks why one street is prioritised over theirs?
That question is the reason to hold the reasoning in the system rather than in a consultant report. A prioritisation combining break history, zone loss trend, pressure data and replacement cost should produce a ranked list that shows its working per segment. Then the answer is a page you print, not a defence you improvise, and the next budget conversation starts from evidence.
Can we use advanced metering data instead of building a balance?
Advanced metering improves the consumption side enormously and it does not produce a balance on its own. You still need production volumes from the historian, unbilled authorised consumption logged when it happens rather than estimated in February, and the spatial allocation of accounts to zones. Metering upgrades make the ledger more accurate. They do not make the ledger exist.
Is pressure management worth modelling in the same system?
Usually yes, because it is often the cheapest real intervention available and almost nobody looks for the candidates. Zones whose night flow responds strongly to pressure changes are the ones worth targeting, and identifying them needs the zone loss trend and pressure data in one place. Most systems have several candidates they have never examined, and the payback period is short.
What happens if our billing system cannot export read dates?
Then that becomes the first task and the schedule reflects it. Without read dates you cannot allocate consumption to a month or a zone honestly, and any balance built on billed totals alone will be wrong in a way nobody notices for a year. Older municipal platforms often need a direct database read rather than the supported export, so raise it during discovery.
If we move off Power BI or Tableau later, do we lose our historical data and reports?
Your raw data is safe because it lives in your source systems or warehouse, not inside Power BI or Tableau. What you lose is the logic layered on top: DAX measures, calculated fields, and report layouts all have to be rebuilt, and that rebuild is the real switching cost. Protect yourself now by keeping transformations in dbt or in warehouse views instead of inside the BI tool, so a future migration only replaces the screens.
How many people does it take to build a custom BI dashboard?
A typical build runs with 3 or 4 people: a data engineer for pipelines and modeling, a full-stack developer for the application and charts, a part-time designer, and a project lead. One strong freelancer can handle a single-source internal dashboard, but in our experience solo builds stall once multiple integrations, permissions, and customer access are added. Team size matters less than having one person explicitly own the data model.
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.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
Who can build a custom business intelligence dashboards system?
Digital Heroes builds custom business intelligence dashboards 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 business intelligence dashboards 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 .
