How Much Does Water Utility Software Cost in 2026?
A custom water utility platform runs $60,000 to $400,000, and the number is set almost entirely by how many vendor systems you make it talk to, not by how many service connections you serve.
On this page
A custom water utility platform runs $60,000 to $400,000, and the number is set almost entirely by how many vendor systems you make it talk to, not by how many service connections you serve. A utility joining one meter data system to one billing system sits near the bottom. A utility that also needs read only data out of a SCADA historian sitting behind the operational technology boundary adds a security architecture review, a network conversation with your operations staff, and real weeks before anyone writes ingestion code. That one decision, whether SCADA is in scope, is the single largest swing in most quotes we give.
The bands a water utility build falls into
Two tiers matter, and both assume a utility somewhere in the 8,000 to 60,000 connection range where the off the shelf products were designed for somebody else.
A focused first release runs $60,000 to $130,000 and ships in 12 to 16 weeks. For a water utility that is normally three things: ingestion of interval meter reads from your advanced metering infrastructure into a store you control, an asset spine that treats pipes, valves, hydrants, meters and pumps as objects with their own condition and history, and one high value workflow on top. Leak triage and compliance sampling are the two that show a number to the board fastest.
A full platform runs $150,000 to $400,000 phased across 6 to 12 months. That adds SCADA historian integration, a field mobile application that works without signal, hydraulic model exchange, a customer portal fed by both billing and interval data, and generated state submissions.
There is no credible tier below $60,000 for a utility of this size, because the reconciliation work between geographic information system records and billing accounts has to happen before any feature is trustworthy, and that work alone is measured in weeks.
What drives a water utility build up
SCADA is the first and largest. If your historian is a Wonderware or Ignition instance on an air gapped operational technology network, the integration is a security architecture conversation before it is a code conversation. Expect 3 to 5 weeks and a real dollar amount added, and treat a developer who is relaxed about that boundary as a warning rather than a bargain.
Data quality is the second. If your service point identifiers and your billing account numbers do not share a reliable key, someone is running a reconciliation project with field verification attached. On a 12,000 connection system budget 4 to 6 weeks before development on the interesting features begins. Discovering this in week nine is far more expensive than planning for it in week one.
The number of distinct state report formats is the third. Each one is a discrete build, because vendors build to the federal floor and leave the state layer to you. Two formats is not twice the price of one, but it is not free either.
Then the age of your billing system. A modern Tyler Munis instance exposes an interface. A twenty year old billing system exposes a nightly flat file, and everything downstream has to live with that latency, which changes design rather than just cost.
What keeps the number down
Keep Cityworks or Lucity. If work order management already works, replacing it is the expensive mistake. Build the layer that joins meter data, geographic records, billing and compliance, and let the maintenance management system keep doing what it does well. Utilities that try to replace a functioning computerised maintenance management system spend a large share of the budget reproducing features nobody complained about.
Scope SCADA out of phase one. Almost every workflow that pays for itself early, leak classification, apparent loss ranking, sampling schedules, service line inventory, runs on meter data plus geographic data plus billing. Historian data makes zone level analysis better later. It is rarely what makes the first release worth having.
Do the key reconciliation with your own staff. A meter technician and an office manager who know why route 14 has three accounts flagged wrong will resolve mismatches faster than any contractor, and every match they close before kickoff is a week you do not pay for.
Start with one state report format, the one with the most painful filing cycle, and add the rest once the underlying sample and result records have proved themselves against a real submission.
A worked example that adds up
A 15,000 connection utility, Sensus advanced metering infrastructure, Tyler Munis billing, Cityworks retained, ArcGIS in place, no SCADA in phase one. Scoped the way we would actually price it.
- Data audit and service point to billing account key reconciliation, four weeks, $26,000
- Interval read ingestion into your own time series store, three weeks, $20,000
- Asset spine for pipes, valves, hydrants, meters and pumps with condition states, three weeks, $20,000
- Leak triage with alert classification trained on your own consumption history, three weeks, $22,000
- Compliance sampling schedule with automated extraction of lab result documents, two weeks, $16,000
Fifteen weeks, $104,000, in the upper half of the first release band because the key reconciliation was real work.
Now the return, with your own rates. Suppose the apparent loss ranking identifies 600 meters whose consumption trend against install date and cumulative volume implies roughly 15,000 gallons a year of under registration each. That is 9,000 thousand gallon units. At a volumetric rate of $6.20 per thousand gallons, changing those meters recovers about $55,800 a year in revenue you are already delivering water for. Add the two days a month your distribution superintendent currently spends rebuilding the same spreadsheet, and the first release is paid back well inside two years on recovered revenue alone.
How the spend phases
Phasing matters more in a utility than almost anywhere else, because your capital calendar and your rate case do not care about a software roadmap.
Phase one is the $104,000 above across fifteen weeks. It produces two things a board understands: a ranked meter change out list in dollars, and a sampling calendar that alerts before a window closes rather than after.
Phase two is field capability, roughly ten weeks and $60,000 to $80,000. Offline mobile for crews, valve exercise records that write a condition flag back to the asset, a shutdown planner that routes around known bad valves, and service line inventory updates captured from a phone in the trench with a photo attached.
Phase three is the outward facing work, roughly twelve weeks and $80,000 to $110,000. Read only SCADA integration, the customer portal showing the hourly curve that ends a high bill argument in two minutes, and generated state submissions.
That is roughly $250,000 to $290,000 over about nine months of active build, inside the full platform band, with each phase defensible on its own if a budget cycle interrupts you.
The ongoing costs nobody quotes
Plan for 15 to 20 percent of build cost per year. On a $260,000 platform that is $39,000 to $52,000 annually, and most of it is not hosting.
The real line is integration maintenance. Meter data vendor interfaces change, billing system upgrades move fields, and geographic schemas get edited by whoever maintains them. A utility that treats integrations as finished discovers a silently stalled feed when a compliance alert fails to fire, which is the worst possible way to find out.
Time series storage grows on its own. Hourly reads on 15,000 endpoints accumulate constantly, and you need a retention and aggregation policy decided deliberately rather than a bill that surprises the finance director in year three. Ask for that policy in writing at design time.
Then staffing. One person, usually an operations analyst or a technically confident superintendent, needs to own the system: approve rule changes, review flagged alerts, sign off on report changes. Without that named owner a custom platform decays into a system nobody trusts, and an untrusted alert list is worse than no alert list.
Comparing a build against your current renewal
Build the comparison from documents you already have. Add up the annual maintenance on your maintenance management system, your billing system, your advanced metering infrastructure analytics module if you pay for one separately, and any analytics dashboard subscription.
Then add the costs that never appear on a renewal notice. The staff hours consumed by manual reconciliation, which for most utilities of this size is a meaningful fraction of a salaried post. The apparent losses you cannot currently quantify, which is revenue for water you have already treated and pumped. The exposure carried by a sampling schedule that lives in a spreadsheet with one person who understands it.
The structural difference is that a build is a capital item with an annual maintenance line and no per connection or per seat escalator, and it belongs to a public entity with a forty year asset horizon. Vendor renewals rise, get bundled, and eventually get replaced by the vendor's next product line, at which point you migrate again.
None of that argues for replacing everything. It argues for owning the join between systems, which is exactly the part no vendor will ever sell you, because selling it would require them to cooperate with a competitor.
When buying beats building
If you serve under roughly 3,000 connections with one pressure zone, your compliance load is a monthly operating report and quarterly bacteriological samples, and your crew is four people, buy. Cityworks or a hosted billing package plus your metering vendor's portal is the correct answer, and the overhead of owning custom software would consume the benefit. Anyone recommending a build at that size is selling rather than advising.
Buy as well if you have nobody internally who can own a system. A platform with no named owner rots inside eighteen months, and a supported product with a vendor help desk is genuinely safer than an unmaintained bespoke one.
Build when the signals are concrete. Someone maintains a spreadsheet that joins two vendor systems and that spreadsheet is load bearing for a filing or a decision, which means you already built a system, badly, with no backup. You asked two vendors for an integration and both quoted you a data export. Your non revenue water is high and you cannot separate real loss from apparent loss because the answer needs meter data, production meters and the zone map in one place. Or you are a regional authority absorbing neighbouring districts and every acquisition brings another billing system and another set of workarounds. That last case is where custom wins hardest, because the products are priced and designed per system and you are trying to operate as one utility.
If you want that decision made properly rather than quickly, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Almost half of all the activities people are paid almost $16 trillion in wages to do in the global economy have the potential to be automated by adapting currently demonstrated technologies. Source: McKinsey Global Institute (2017) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- SMS reminders that stated the specific cost of the appointment to the health system reduced missed appointments in Trial One, with the DNA (did-not-attend) rate falling from 11.1% (control) to 8.4% (specific-costs message) - an odds ratio of 0.74 (95% CI 0.61-0.89), i.e. roughly a 24-26% relative reduction - at no additional cost. (Trial Two replicated this at an 8.2% DNA rate.). Source: PLOS ONE (Hallsworth et al.) (2015) →
- 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) →
Frequently asked questions
How much does custom water utility software cost for a 15,000 connection system?
A focused first release covering meter data ingestion, an asset spine and one core workflow runs $60,000 to $130,000 and ships in 12 to 16 weeks. A fully scoped example at that size, including four weeks of service point to billing account reconciliation, comes to about $104,000 across fifteen weeks. A full platform adding SCADA integration, offline field mobile, a customer portal and generated state submissions runs $150,000 to $400,000 phased over 6 to 12 months.
Connection count barely moves the figure. A 15,000 connection utility and a 40,000 connection utility with the same vendor stack cost about the same to build for.
What does it cost to run each year after launch?
Budget 15 to 20 percent of build cost annually, so $39,000 to $52,000 on a $260,000 platform. The largest component is integration maintenance rather than hosting, because metering vendor interfaces, billing upgrades and geographic schema edits all break assumptions on their own timetable.
Time series storage is the second line and it grows continuously with hourly reads, so agree a retention and aggregation policy at design time rather than discovering the bill in year three.
How long does it take to build a water utility management system?
Twelve to sixteen weeks for a first release if your data is in reasonable shape. The variable that stretches this is the key between geographic service points and billing accounts. If those do not match reliably, add 4 to 6 weeks of matching and field verification before feature development starts.
SCADA integration adds a further 3 to 5 weeks, most of it in the operational technology network security review rather than in code. A full platform runs 6 to 12 months in phases, with each phase live as it lands.
Is this better value than extending Cityworks?
Cityworks is a capable maintenance management system and if work order management is the whole problem you should keep it and stop there. It cannot solve problems that span systems it does not own, meaning the join between interval meter data, geographic records, billing and compliance, because those data sets live in other vendors' products.
Most utilities that build keep Cityworks for what it is good at and construct the connecting layer around it. Replacing a working maintenance management system is usually where budgets get consumed with nothing visible in return.
How much does SCADA integration add to the cost?
Expect 3 to 5 weeks added to the schedule and a corresponding share of the budget, with most of that time in the security architecture review rather than in writing ingestion code. The correct design is read only, with no control path through the application and a one way boundary between the business network and the operational technology network.
Because it rarely drives the earliest financial return, we usually recommend keeping SCADA out of the first release and adding it in phase three once leak triage and compliance are live.
Why does reconciling GIS and billing data cost so much?
Because it is field work as well as data work. On a 12,000 connection system it typically takes 4 to 6 weeks to match service point identifiers to billing accounts, resolve records renumbered years ago, and send someone to verify the ones that cannot be resolved from a desk.
You can reduce this materially by having your own meter technician and office manager work the mismatch list before kickoff. Every match they close is time you do not pay a developer for, and they will be faster at it.
Does the price go up if we serve more connections?
Barely. The engineering work is the same at 8,000 connections as at 40,000, which is precisely why the economics improve as you get larger. What moves the number is the count of distinct systems to integrate, the number of state report formats you must generate, and whether SCADA is in scope.
Data volume affects architecture rather than build price. Hourly reads on a larger endpoint count need a time series store with sensible partitioning, but that is a design decision made once, not a per connection charge.
What does it cost to add service line inventory and state reporting?
Service line inventory as a real record, with material on both the utility side and the customer side, a basis of evidence field and photo capture from the field, typically sits inside the field mobile phase at roughly $60,000 to $80,000 alongside valve and hydrant records. State submission generation is priced per format, because each state portal is its own build.
Automated extraction of contract laboratory result documents is worth adding early. Lab reports are semi structured and vary by laboratory, and having results land against the sample site record removes the manual keying step where violations originate.
Who owns the code and the data, and how does that work in a public procurement?
You should own the repository, the database and the cloud accounts, with a documented data export, and it should be written into the contract at signing rather than negotiated later. As a public entity with forty year assets you cannot have operational history locked inside a vendor you do not control.
Practically, that also makes your next billing system procurement cheaper. If the asset records, service point history and compliance record live in your own database, swapping billing becomes one integration change rather than a full migration, which removes the incumbent's strongest bargaining position.
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.
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.
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 many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
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.
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.
How much should a small business expect to pay for custom software?
Across 2,000+ Digital Heroes projects, a small business system that replaces spreadsheets or one core workflow typically lands between $40,000 and $80,000, with more complex first versions running up to $150,000. The two levers that move the number most are integrations and user roles, not the team's hourly rate. Any quote under $15,000 for a full production system means the vendor has not understood your scope yet.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
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 .
