How to Hire a Non Revenue Water Software Development Company
Hire on one test: can the firm explain how it will allocate billed consumption to a district metered area when read cycles are staggered and zone boundaries ignore billing routes. That answer predicts everything else.
On this page
Hire on one test: can the firm explain how it will allocate billed consumption to a district metered area when read cycles are staggered and zone boundaries ignore billing routes. That answer predicts everything else. Expect $70,000 to $150,000 for a working zone level water balance, and buy a paid discovery phase before any build, because most of the risk sits in your billing extract.
Commissioning non revenue water software is like hiring an auditor who will never be allowed inside the warehouse. Everything they tell you about what is missing has to be inferred from what came in the gate, what left on an invoice and what the doors were doing at three in the morning. Get the inference wrong and you will spend a decade of capital chasing leaks that are actually meter under registration, or replacing meters while a main quietly runs into a storm drain.
That is the difficulty in buying here. The visible product is a dashboard, and dashboards are easy to demonstrate and cheap to fake. The actual deliverable is a defensible monthly balance, and its correctness depends on things a demo never touches: whether your zones are genuinely valve closed, whether the billing extract handles staggered read cycles honestly, whether the night use allowance came from your own low consumption accounts or from a textbook. A vendor can show you a beautiful screen built on numbers that are wrong in a way nobody notices for a year, by which time the annual audit has already gone to the state.
What a non revenue water software development company actually does
Building the interface is a small share of the engagement. Most of the work is data archaeology and reconciliation.
- Getting a reliable, repeatable extract out of a municipal billing system whose read cycle handling is usually undocumented and sometimes surprising.
- Reading the SCADA historian for production and zone flow, then agreeing what a suspect or flatlined signal means before it silently corrupts a month.
- Turning district metered areas into real geographic objects with the service accounts inside them, which frequently exposes zones that were drawn on a map and never valve tested.
- Deriving a legitimate night use allowance from your own customer mix rather than importing one.
- Modelling the meter fleet as an asset population with install date, make, size, registered volume and test history, so apparent loss stops being a guess.
- Normalising leak findings from satellite, acoustic, correlation and public reports into one object so payback per detection method becomes computable.
- Producing the annual audit submission in the format your state accepts, with every figure traceable to a source system rather than a typed cell.
What it really costs in 2026
These are delivery bands from our own utility work, not a published survey.
| Project tier | Cost | Timeline |
|---|---|---|
| Automated monthly water balance for three or four problem zones, real versus apparent split | $70,000 to $150,000 | 12 to 16 weeks |
| System wide balance with minimum night flow analysis and a prioritised survey target list | $150,000 to $260,000 | 5 to 8 months |
| Full programme platform: vendor finding ingestion, meter fleet economics, pressure management analysis, capital prioritisation, state submission | $260,000 to $420,000 | 8 to 14 months |
| Hosting, data feed maintenance and enhancement | 15 to 20 percent of build per year | Retainer |
Two costs are absent from nearly every quote in this sector. The first is zone validation. A balance cannot be computed for a district metered area that is not actually closed, and discovering an open boundary valve is common enough that it should be a funded task rather than an assumption. That is field crew time, not developer time, and it belongs in the project budget so nobody has to go back for money mid build.
The second is the AMI transition. A utility part way through a meter rollout has two consumption data models running side by side, manual reads and interval data, for as long as the rollout takes. Reconciling both, and handling accounts that switch mid month, is genuine additional work that a vendor quoting from a tidy assumption will not have priced. If your rollout is live or planned inside three years, say so on the first call and watch what the number does.
Signals of a strong water loss partner
- They ask for your last submitted audit before they quote. Going line by line through it, asking where each number came from, is the fastest way to scope this work honestly.
- They can describe read cycle allocation without hedging. Staggered reads across zone boundaries is the defining technical problem here, and vagueness means the balance will be wrong quietly.
- They separate real from apparent loss as an architectural decision. The two need completely different interventions, so a system that reports one blended loss figure is not useful for capital planning.
- They intend to buy detection, not build it. Satellite, acoustic and correlation work belongs to specialists. Your build is the ledger those specialists report into.
- They plan to compute cost per recovered volume by detection method. No vendor will calculate that for you, and it is the only honest basis for renewing a survey contract.
- They name what they have integrated. A historian, a municipal billing system and an AMI head end are three different problems, and the billing system is almost always the slow one.
Red flags
- A demo with a national leakage benchmark on the front page. Comparing your loss figure to someone else's is a sales device, not an operating tool.
- A textbook night use allowance. If they intend to take legitimate night use from a manual rather than from your own low consumption accounts, expect false alarms that train your crews to ignore the system.
- No plan to close the loop on repairs. A finding that never gets linked to a repair and an estimated recovered volume leaves you buying detection forever on faith.
- Proposals to replace your GIS or asset management system. Network geometry and asset condition should stay where they are. The loss platform consumes from them.
- A fixed price offered before anyone has seen a billing extract. The extract is where the schedule goes to die, and no honest number exists before someone has looked at it.
Questions to ask on the first call
- How will you allocate billed consumption to a zone and to a month when read cycles are staggered and do not match zone boundaries?
- Where will the legitimate night use allowance come from, and how will you validate it?
- What happens to a month when a zone meter flatlines or reports a suspect value for two days?
- How will you tell a burst from a slow drift in meter accuracy in the same zone?
- Which municipal billing systems have you pulled production data from, by name?
- How will a satellite polygon, an acoustic correlation and a resident report end up as the same kind of object?
- How will you estimate recovered volume after a repair, and compare it against the zone balance change?
- What do you need from our field crews, and when in the schedule do you need it?
- What is delivered on the last day, including the data model documentation and the export path?
A simple way to decide
Rather than picking between three proposals that each guessed at your situation, buy a paid discovery phase and treat it as its own deliverable. It should end with a written specification you own: the balance calculation defined for your systems, the billing extract approach with its known edge cases, the zone list with validation status, the audit output mapped to your state's format, and acceptance criteria precise enough that a different firm could build against them. That document is the asset. It converts a decade long loss reduction programme from a vendor relationship into something your utility controls, and it costs a fraction of a build to find out whether the firm in front of you understands water or understands charts.
Digital Heroes runs every engagement this way, with a product requirements document first and the client owning the repository from the first commit. Contracting goes through an India LLP, a US LLC or a UK LTD so the intellectual property assigns under your own jurisdiction, which matters when the analysis behind your capital requests has to outlive any vendor relationship. The firm has delivered more than 2,000 projects and can be checked through D-U-N-S, Clutch and Trustpilot.
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.
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- In PMI's 2014 Pulse of the Profession report on requirements management, inaccurate requirements management is cited as a leading cause of project failure, with 47% of unsuccessful projects failing to meet goals due to poor requirements management. Source: Project Management Institute (PMI) (2014) →
- The 2015 CHAOS data (based on the modern definition of success) reports that only about 29% of software projects succeed, 52% are challenged, and 19% fail, with the three most important success skills being executive sponsorship, emotional maturity, and user involvement. Source: The Standish Group (reported via InfoQ Q&A with Jennifer Lynch) (2015) →
Frequently asked questions
How much does it cost to hire a non revenue water software development company?
An automated monthly balance covering three or four problem zones with a real versus apparent loss split runs roughly $70,000 to $150,000. Extending it system wide with minimum night flow analysis and a prioritised survey list sits at $150,000 to $260,000. A full programme platform with vendor finding ingestion, meter fleet economics and capital prioritisation runs $260,000 to $420,000. Billing system integration and the state of your zone metering are the two biggest variables.
What should we test a water loss developer on before hiring?
Ask how they will allocate billed consumption to a zone and to a month when read cycles are staggered and do not align with zone boundaries. It is the defining problem in this category. A firm that has done water work will describe the allocation method and its known error cases without prompting. A firm that answers vaguely will produce a balance that is wrong in a way nobody notices until the annual audit is already filed.
Should we hire a developer or just buy leak detection technology?
Buy the detection and hire for the ledger. Satellite analysis, acoustic logging and correlation are specialised products and the vendors do them better than a custom build would. What none of them supplies is a defensible monthly balance by zone that separates real from apparent loss and shows which detection method actually paid for itself in your system. If you spend on survey contracts without measuring the return, that gap is the hire.
What hidden costs should we expect on this kind of project?
Two. Zone validation, because a balance cannot be computed for a district metered area that is not genuinely valve closed, and finding an open boundary valve is common. That is field crew time and it belongs in the budget. Second, any live AMI rollout, since manual reads and interval data run side by side for years and reconciling both, including accounts that switch mid month, is real additional work most quotes assume away.
Who owns the code and the analysis if an agency builds our platform?
You should own the repository, the cloud accounts and the right to hire a different firm, agreed in writing before kickoff. Loss reduction programmes are typically funded across five to ten years, and the analysis supporting your capital requests needs to outlive any single vendor. Digital Heroes assigns ownership from the first commit and contracts through separate India, US and UK entities so the assignment happens under your own law. Ask about data export format too.
How much does a custom BI dashboard cost for a small business?
For a small business, a focused first dashboard typically runs $25,000 to $60,000 when it covers 2 or 3 data sources, daily refresh, and 5 to 7 core metrics. Across 2,000+ Digital Heroes projects, budgets climb past that only when real-time data, complex permissions, or customer-facing access enters the scope. If a quote for a simple internal dashboard exceeds $75,000, ask exactly which of those three is pushing it there.
When is it time to move from Excel reports to an actual dashboard?
The reliable signal is when someone spends more than a few hours a week copying data between spreadsheets, or when two teams arrive at a meeting with different numbers for the same metric. At that point the spreadsheet is acting as an unversioned, single-person database, and a costly error is a matter of time. A first dashboard that automates those recurring reports typically pays for itself in recovered hours within the first year.
How long does it take to build a custom BI dashboard?
A working first version usually ships in 4 to 8 weeks, and a full production build with multiple integrations and permissions takes 3 to 6 months. In Digital Heroes delivery experience, schedules slip on data access, meaning credentials, API approvals, and cleanup of source data, far more often than on the dashboard screens themselves. Lining up access to every data source before kickoff routinely saves 2 to 3 weeks.
Will a custom dashboard stay fast once our data hits millions of rows?
Yes, if it aggregates before it displays; no dashboard should scan millions of raw rows on every page load. The standard techniques are pre-aggregated summary tables, incremental refresh, and caching, which keep typical page loads under 2 seconds even on datasets in the hundreds of millions of rows. Ask your vendor how the dashboard behaves at 10 times your current data volume; a good one gives a specific answer about aggregation, not just a bigger server.
We already pay for Microsoft 365. When does building custom actually beat Power BI?
Keep Power BI for internal reporting; at $14 per user per month for Pro it is hard to beat for employee-facing analytics. Custom wins in three cases: you are showing dashboards to customers, since embedded Power BI is priced on capacity and gets expensive fast, you need a fully white-labeled experience inside your own product, or your team keeps fighting the tool to support a specific workflow. Most companies we build for keep Power BI internally even after launching a custom customer-facing dashboard.
When does Looker make more sense than a custom dashboard?
Looker earns its place when multiple teams keep producing conflicting numbers and you need one governed definition of every metric, because LookML enforces definitions centrally. Its pricing is quote-based, and the quotes clients bring to Digital Heroes typically start in the tens of thousands of dollars per year. Under roughly 50 users with straightforward reporting needs, that spend is hard to justify against Power BI or a scoped custom build.
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.
What do I need to prepare before contacting an agency about a dashboard project?
Bring three things: a list of your data sources with who controls access to each, the 5 to 10 recurring decisions the dashboard should support, and examples of the reports or spreadsheets it will replace. That package lets an agency quote in days instead of weeks, and in our discovery work it cuts the audit phase roughly in half. You do not need wireframes or a technical spec; a good agency produces those with you.
What should the first version of a dashboard include, and what can wait?
Version one should answer 5 to 7 questions your team already asks every week, pull from your 2 or 3 most important data sources, and refresh daily. Real-time data, custom report builders, scheduled email exports, and write-back features can all wait for version two. Across our projects, teams that launch a narrow version one reach a dashboard people actually use roughly twice as fast as teams that try to cover every department at once.
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 long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
How do I make sure each client sees only their own data in a shared dashboard?
That is row-level security, and it must be enforced in the database or API layer, never by hiding filters in the interface. Each query carries the logged-in client's identity, and the data layer refuses to return rows outside their account, so a crafted URL or modified request cannot leak another client's numbers. Make any vendor show you exactly where that filter lives, because interface-level filtering is the most common security mistake we find when auditing dashboards built elsewhere.
How do I work out whether a custom dashboard will pay for itself?
Add up three numbers: hours of manual reporting it removes each month, license seats it replaces or avoids, and the value of one or two decisions it speeds up, like catching margin slippage a month earlier. Across Digital Heroes projects, internal dashboards typically pay back in 8 to 18 months, and customer-facing dashboards pay back faster when analytics is a paid feature or reduces churn. If the honest math does not clear payback within 2 years, buy an off-the-shelf tool instead.
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.
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
More from Zayn.
Director of Strategy · UK · London · 2 posts on the site
Published · Last updated .
