Groundwater Agency Software: Build a Custom Allocation Ledger or Buy What Exists?
The threshold is roughly 300 metered wells, or the moment allocations become transferable, or the first time a published pumping figure is formally contested.
On this page
The threshold is roughly 300 metered wells, or the moment allocations become transferable, or the first time a published pumping figure is formally contested. Below all three, do not build: a disciplined spreadsheet plus a consulting hydrologist is cheaper, faster and entirely defensible, and we would rather say so than take the project. Above any one of them, a first release covering the allocation ledger, meter ingestion and a pumper portal runs $70,000 to $150,000 over 12 to 18 weeks, with a full basin platform at $200,000 to $450,000. The complication is that there is no dominant product to buy, which changes the shape of this decision entirely.
When is off the shelf genuinely the right call here?
Start with an honest statement about the market. There is no dominant packaged product for groundwater allocation administration. What agencies actually run is a consulting hydrologist's database, a utility billing package bent into an unfamiliar shape, a geographic information system (GIS) doing duty as a system of record, and spreadsheets holding the balances that matter. That is not a scandal, it is a small market with highly local rules.
So the buy decision here is narrower than usual, and it has one clear answer. Buy Esri ArcGIS, or keep the deployment you already have, for parcel and well geometry, mapping and spatial analysis. It is solved, your consultants and your county already use it, and reproducing spatial tooling inside a custom platform is money burned. Integrate at $15,000 to $32,000 and stop there.
Buy nothing else, and build nothing, if you administer a few dozen wells on annual paper reports, allocations are not transferable and no figure has ever been formally contested. At that scale the calculation is genuinely tractable in a sheet, and the control problem is solved by a competent hydrologist reviewing it.
And wait if your agency is still two years from adopting the rules the software would encode. You will pay to implement a draft and pay again when the final version differs. Spend the interval writing the rules down instead. That costs nothing, and it is the input the build needs anyway. Agencies routinely discover during design that nobody has ever written down who may report on behalf of a tenant, or when a submission becomes official.
When does a custom build actually pay off?
Four triggers, and any one of them is enough.
- A number you published has been contested. The exposure is not the disputed volume, it is that every other figure in the basin becomes negotiable once one has been successfully challenged.
- Credits are about to become transferable. A basin that allows credits to move is operating a small commodity registry, and the first time the same 40 acre feet is sold to two neighbours in one week, a spreadsheet has no answer.
- Telemetry volume has outgrown manual entry, typically somewhere above 300 metered wells with logger data arriving daily.
- The person who understands the spreadsheet is within sight of retirement. This is the most common trigger we see and the most rational one.
The mechanism that earns the money is structural rather than featureful. An allocation stops being a number in a column and becomes a double entry ledger: initial assignment, annual accrual, metered debit, carryover, transfer in or out, and adjustment with a reason code and the staff member who made it. The balance is derived, never typed. Once that exists, the report an attorney demands is a statement of account, which is a form of evidence everyone in the room already understands.
The second structural choice is that raw readings are permanent and corrections supersede rather than overwrite. Agencies lose disputes on process, not on hydrology, and process is exactly what retained raw data and reason codes buy you.
How do they compare on the things that matter in this industry?
Whatever you are shown, by a consultant or a vendor or a developer, test it on five things.
The meter replacement scenario. A meter is swapped in June and the replacement starts at zero. Ask to see it modelled. Anyone who has done regulated measurement work separates raw reading from derived volume immediately and asks what happens to the old totaliser final read. Anyone proposing a single current reading field on the well record has built asset trackers, not ledgers.
What a correction does. The answer you want involves superseding records and retained history. The answer you do not want is an update statement plus an audit log table nobody reads.
Measured versus estimated. When a logger drops offline for eleven days, the gap fill must be flagged as an estimate permanently, and the annual report must show what share of the volume was measured. That single column has ended more disputes than any amount of extra precision.
Public records handling. Redaction rules and an export path built for a records request rather than improvised under a deadline. Cheap to build early, painful to retrofit, and a genuine differentiator between people who have worked with public agencies and people who have not.
Ownership and retention. Your allocation ledger is a public record with a retention period measured in decades. It cannot sit inside a vendor's cloud tenancy. Ask who holds the repository, the database and the accounts, and settle it before kickoff rather than at renewal.
What does total cost of ownership look like at your scale?
Take an agency administering roughly 1,400 metered wells across two management areas with different rules, three telemetry vendors plus a manual tail, transferable credits permitted from next water year, fees collected on the county tax roll, and an existing Esri deployment. The full platform prices at $384,000, and with a 10 percent contingency, because at least one meter vendor will turn out to have no usable export, the committed number is $422,000 across about thirteen months.
Inside that: allocation ledger $44,000, telemetry ingestion for three vendors $51,000, pumper portal $34,000, staff review queue $18,000, annual statements $17,000, credit registry $42,000, enforcement case management $37,000, parcel synchronisation $32,000, fee billing and tax roll export $34,000, GIS integration $22,000, board reporting and transparency pages $24,000, records redaction and export $16,000.
An agency with one meter vendor, one management area and no credit trading, buying only the first release, lands at $95,000 to $120,000 instead. Well count matters less than you would expect. A ledger serving 300 wells and one serving 3,000 are the same engine. Rule diversity, meter vendor diversity and whether money is collected against parcel records somebody else controls are what set the number.
Running cost is 18 to 25 percent of build, roughly $76,000 to $106,000 a year on the full platform, plus $8,000 to $20,000 for meter vendor interface changes, $8,000 to $22,000 for ordinance amendments, $4,000 to $10,000 for county roll format changes, $8,000 to $18,000 for hosting with decades long retention, and $5,000 to $15,000 for legal review of enforcement templates. For a public agency the genuine risk in that list is not the total, it is that the line has to survive a general fund budget cycle every year.
What does the hybrid look like, and when is it the honest answer?
Because there is no platform to buy, the hybrid here takes a different shape, and it is the shape most agencies should choose. Buy the pieces that already exist, build only the ledger, and keep the people you already trust.
Concretely: keep Esri ArcGIS for geometry and integrate to it. Keep your consulting hydrologist for the science, the basin model and the annual reporting narrative, because none of that is a software problem and replacing it with a dashboard would be a mistake. Keep the county assessor as the authoritative parcel record and synchronise against their roll rather than maintaining a rival copy. Then build the one thing nothing else provides, which is the allocation ledger with permanent raw readings, reason coded adjustments and a statement of account.
That is the $95,000 to $120,000 first release, not the $422,000 platform. It removes the class of argument that costs agencies hearings, and it defers every expensive module until there is a reason for it. Credits at $30,000 to $60,000 wait until the basin plan actually permits transfers. Enforcement at $28,000 to $55,000 waits until the ledger it generates notices from is trusted. Fee billing waits until parcel synchronisation is proven.
The hybrid stops being right in one situation worth naming. If several agencies intend to share one system while each keeps its own ordinance, that is a genuinely multi tenant build and it is an architecture decision rather than a configuration one. Deciding it later is expensive, so decide it in week one even if the joint powers arrangement is still being negotiated.
Which should you choose, by operator size and stage?
Under about 100 wells, annual paper reports, no transfers. Spreadsheet plus consulting hydrologist. Spend the money on writing the rules down and on a documented review step before any figure is published. That is the whole defence at this scale and it costs almost nothing.
100 to 300 wells, some telemetry, no credits yet. Build the ledger and the ingestion only, at the bottom of the first release band. Bring the manual tail in through the portal in a second phase. Launch with the wells that are already metered rather than waiting for full telemetry coverage, which is the most common way agencies spend a year not solving anything.
300 to 1,500 wells, one or two management areas, enforcement happening. The $95,000 to $120,000 first release, then add enforcement case management once the ledger is trusted and staff have stopped correcting it by hand. Confirm your county's tax roll file format and deadline before you scope billing, not during acceptance testing.
Large basin, multiple management areas, transferable credits, joint powers. The full platform toward $422,000 is defensible, phased across thirteen months, procured against your own reporting deadline rather than in one contract. Sequence is fixed: ledger, ingestion, portal, parcels, billing, enforcement, credits, transparency. Anything that generates a legal notice waits until the record it cites has proved itself through a full water year.
When the shortlist is down to two and you need a tiebreaker, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. 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.
- Analyst estimates place CRM implementation failure rates broadly between roughly 30% and 70% (Johnny Grow cites Forrester at 47%), with low user adoption repeatedly cited as a leading cause of failed CRM projects (this being Johnny Grow's own analysis, not a Forrester attribution). Source: Johnny Grow (industry analysis citing Gartner/Forrester) (2025) →
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- McKinsey found that currently demonstrated technologies can fully automate about 42% of finance activities and mostly automate a further 19%, indicating roughly 60% of finance work is technically automatable. Source: McKinsey & Company (2018) →
- 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
What does it cost to move off a consultant's database or spreadsheet?
The migration itself is usually modest, because the volume of historical data is small compared with most industries. The work is reconstructing provenance: which reads were raw, which were corrected, by whom and why. In many agencies that history does not exist and cannot be recovered, so the honest approach is to import balances as an opening position with a clearly marked cutover date.
Say that plainly in the record. An opening balance carried forward with a stated basis is defensible. An opening balance presented as though it were derived from postings that were never made is not, and it will be found.
What if our hydrology consultant retires or changes their rates?
This is the closest thing to a vendor pricing risk in this category, and it is a real one. Ask now what it would cost to have a second firm pick up the annual reporting, and whether the model, the database and the query logic are documented well enough for that to be possible.
Splitting the roles is the practical answer. Keep the consultant for the science and the basin model, where their judgement is the value, and move the ledger into a system the agency owns outright. Then a change of consultant is a procurement rather than a crisis, because the numbers stay with you.
How long before staff are actually using it?
Twelve to eighteen weeks for a first release covering the ledger, ingestion, the pumper portal with a staff review queue, and annual statements. The engineering is not the risk.
The schedule risk is policy. Agencies routinely find during design that the rules for who may report on behalf of a tenant, how corrections are accepted and when a submission becomes official have never been written down. Those need board time, which has to be scheduled weeks ahead, so start the rule capture before the build rather than alongside it.
Should we buy Esri ArcGIS or build our own mapping?
Buy it, or keep the deployment you have. Parcel and well geometry, mapping and spatial analysis are solved problems, your consultants and your county already work in that environment, and reproducing any of it inside a custom platform is money spent for nothing.
Integrate at $15,000 to $32,000 and hold the line there. The mistake we see is a custom platform slowly growing its own mapping features because a board member liked a screenshot. The ledger is what nothing else provides, and it is where the budget should go.
Could a utility billing package handle allocations instead?
Some agencies try, and it goes wrong at the same point every time. Billing packages model a customer, a service address and a consumption charge. Groundwater allocations attach to parcels in some basins and to wells in others, a well can serve several parcels, parcels split, and unused allotment carries forward across a multi year window.
You can force that shape into a billing product, and then the balance lives in an exported spreadsheet again, which is where you started. If your only need is invoicing against a volume somebody else calculates, a billing package is fine. If the balance itself is the disputed thing, it is not.
How much does each meter or telemetry vendor add?
Twelve thousand to twenty eight thousand dollars per vendor, and the spread is set by vendor cooperation rather than technical difficulty. Some publish a clean interface, some offer only a portal export, and some produce a file per device per day that has to be collected and normalised.
Budget $8,000 to $20,000 a year across all vendors for interface changes, because loggers get replaced and firmware moves. Ingestion is the first thing to break and the last thing anyone notices, so build an alert for silence rather than relying on someone spotting a missing well.
When should we add credit trading?
Not in the first release. Get issuance, transfer and retirement provably correct first, with serialised credits moving through a strict state machine so the same acre feet cannot be sold twice. That registry is $30,000 to $60,000 and it produces nothing until the basin plan actually permits transfers.
Do not build matching and pricing at all in year one. A marketplace sitting on a registry that has not yet survived a water year creates disputes rather than liquidity, and trading by phone works perfectly well while the ledger proves itself.
Who owns the code, the database and the records if we hire a developer?
The agency does, in the agency's own name, with the developer holding access rather than ownership, agreed in writing before kickoff. Allocation ledgers are public records with retention measured in decades and they cannot sit inside a vendor tenancy you do not control.
Ask the same question about every component: hosting accounts, backups, the GIS licence, the meter vendor portals. A successor agency staff member in fifteen years needs to be able to produce the record and explain how it was derived, and that is a procurement decision you make now, not later.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
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.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
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.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
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.
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.
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
More from Zoe.
Senior Brand Designer · New-york · 8 posts on the site
Published · Last updated .
