Build vs Buy Irrigation District Software: Orders, Deliveries and the Assessment Roll
Under roughly 150 turnouts on one canal with flat per acre assessments, buy a municipal billing package and keep the scheduling book.
On this page
Under roughly 150 turnouts on one canal with flat per acre assessments, buy a municipal billing package and keep the scheduling book. Build when allotments carry over or transfer, when your assessment roll no longer reconciles to the county, or when a delivery dispute has reached your board. Canal automation solves measurement, not administration.
The districts that should not spend a dollar on custom software
A district with one main canal, a hundred and twenty turnouts, a flat charge per irrigated acre and no carryover has a bookkeeping problem, not a systems problem. A municipal utility billing package of the kind sold by Caselle, Springbrook or Tyler will produce the bills, a spreadsheet will hold the turnout list, and an experienced secretary will hold the rest. Money spent on custom development at that scale would be better spent lining a lateral.
The same applies to a district whose orders arrive by phone on a rotation everyone already understands. If your ditch riders can carry the schedule in their heads because there are eleven users on their run, software will formalise something that is not currently failing. Boards sometimes fund a system anyway because a neighbouring district bought one, and the result is a database that a single clerk maintains alongside the book she trusts.
There is a third buy case worth naming. If your immediate pain is that manual headgates deliver imprecise flows and the canal loses water to poor control, that is an infrastructure investment, not a software one. Rubicon Water and comparable canal automation suppliers do that job properly, and no administrative system will recover water lost at a check structure.
Buy, in short, when the district administers water the same way for every account, when the assessment is uniform, and when nobody has yet asked you to prove a delivery volume in front of counsel. Those three conditions cover a large share of the districts in the western United States, and there is no shame in being one of them.
What tips a district into building
The decision usually turns on a single structural fact: whether your water administration has rules that differ between accounts. The moment allotments carry over from one season to the next, or move between parcels through a transfer, or get prorated in a shortage year, manual administration begins producing different outcomes for similar accounts. That inconsistency is what turns into a complaint at a board meeting, and it is what no general package models.
The second tip is the assessment roll. Charges in most districts attach to the parcel rather than to a customer, follow the land through a sale, and are frequently collected by the county on the tax roll. General billing software models a customer with an account and an address, which is simply the wrong shape. The mismatch shows up as ownership changes that do not propagate and a roll file the county treasurer rejects.
The third is evidence. If a landowner has ever disputed a delivered volume and the office had three sources of truth, the ditch rider card in pencil, a telemetry record at a point serving several users, and a number typed into billing at the end of the run, then your delivery record cannot support enforcement. Districts in that position are not administering water, they are negotiating it.
The fourth is people. Where a large part of district operating knowledge lives with one long serving rider who is a few years from retiring, capturing the ordering and delivery process in a system is succession planning as much as it is technology.
The real cost of each route
Buying looks cheap because the sticker is small. Utility billing packages priced per account or per bill assume a monthly cycle, and a district that bills once or twice a year finds the per bill maths favourable while the annual support minimum dominates the invoice. Ask specifically what the annual minimum is, then ask what the tax roll export costs, because several vendors treat that as a custom report chargeable each year rather than a standard feature. Two districts on the same product can pay very different amounts for exactly this reason.
Custom development runs the other way round. A first release taking in the turnout, parcel and account register, water ordering against canal capacity and offline ditch rider delivery capture runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding the allotment ledger with carryover and transfers, telemetry and manual measurement ingestion, assessment billing reconciled to the county roll, delinquency workflow and agency reporting runs $150,000 to $350,000 across 6 to 11 months. Plan on roughly a fifth of build cost annually for hosting and support.
The cost nobody puts in the board packet is staff time on data. Reconciling your register against the county assessor roll is your work, not the developer work, and it is the largest single hidden line in this category.
The costs that appear after the board has voted
Parcel reconciliation deserves its own paragraph because it derails more district projects than any technical decision. Your turnout and account register has drifted from the county roll through decades of splits, mergers, subdivisions and estate transfers that were never propagated into district records. Nobody knows how bad it is until someone joins the two lists. Budget explicitly for it, start it before development begins, and treat a developer who does not raise it in the first meeting as inexperienced in this sector.
The second is the roll deadline. Where assessments ride on the county tax roll, the treasurer has a statutory date each year by which the district file must arrive in the county format. That date, not your project plan, is the real go live constraint, and missing it by a week can mean a year of manual billing. Work backwards from it and leave a full cycle of parallel running before it.
The third is telemetry. Districts rarely have one brand of instrumentation. A build that ingests measurement usually meets three or four device families, some polled, some pushing on their own schedule, at least one behind a proprietary desktop application with no documented interface. Price the integration per device family, not as one line.
The fourth is public records. A district is a public body, so delivery and assessment history becomes discoverable and carries retention obligations. Building the record append only, with attributed corrections rather than edits, costs slightly more up front and is the difference between producing a clean history in a hearing and explaining why a row changed.
A decision test using forty deliveries
Pick forty deliveries from last season at random across at least three laterals. For each one, ask the office to produce four things without calling anyone: the volume delivered, the measurement method behind that number, the apportionment rule applied if the measurement point served more than one turnout, and the account and parcel it was charged to. Give it an hour.
Count how many of the forty are fully answerable. Count how many rest on a rider estimate treated as equivalent to a telemetered flow. Then take the same forty parcels and check each against the current county assessor record for owner and acreage. The number of mismatches is your parcel reconciliation estimate in miniature, and you can extrapolate it across the district honestly.
One more reading is worth taking while the file is open. Note how many of the forty were charged to an account whose owner has changed since the last recertification of your roll, because those are the ones that generate a delinquency you cannot enforce. If most deliveries are answerable and mismatches are rare, your problem is smaller than a build. If a third of them require a phone call to a rider, you have your case, and it is written in your own records rather than in a vendor deck.
How to sequence it and what to require
Do one lateral or one division first, in the off season, and keep the scheduling book running in parallel through the first weeks of the run. A district wide cutover in the middle of an irrigation season is the one approach worth refusing outright, regardless of who proposes it.
In procurement, ask three questions that separate firms who have done this from firms who have not. How will they model a parcel served by two turnouts and a turnout serving two parcels. What apportionment rule do they expect your board to approve for shared measurement points. And what does the rider experience look like on a canal bank with no signal, in sunlight, in a truck. Anyone answering the third with a responsive web page has not been on a lateral.
Require a written product requirements document before any code, and have your board or your counsel read it, because the contested parts here are policy questions in technical clothing. Digital Heroes puts that document first and writes it to be read by a board rather than by engineers. The firm holds Fiverr Vetted Pro status, has delivered over two thousand projects with a team past fifty people, and can sign as a US LLC, a UK LTD or an India LLP so a public body contracts under its own law. Its YouTube channel has 2.5 million subscribers if your directors would rather see the work than read another capability statement.
Finally, put ownership of the repository, the cloud accounts and the data export in the contract before kickoff. Districts outlive staff and vendors, and your successors should never have to ask permission for their own delivery history.
If you would rather scope this before committing budget, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- 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) →
- ITIF's 2025 report documents that SMEs operate at roughly 60% of large-firm productivity in advanced economies (citing McKinsey), that CRM platforms deliver a 25-40% improvement in customer retention and a 15-30% boost in sales, and that digital advertising returns about $8 in profit per dollar spent on Google Search and Ads. Source: Information Technology and Innovation Foundation (ITIF) (2025) →
- An EY survey found one in five U.S. payrolls contains errors, each costing an average of $291 to remediate, with a typical 1,000-employee organization spending roughly 29 workweeks per year fixing common payroll errors. Source: EY (Ernst & Young) (2022) →
Frequently asked questions
How much does custom irrigation district software cost?
A first release covering the turnout, parcel and account register, water ordering against canal capacity and offline ditch rider capture runs $60,000 to $130,000 across 12 to 16 weeks. A full platform adding the allotment ledger, measurement ingestion, assessment billing reconciled to the county roll, delinquency and agency reporting runs $150,000 to $350,000 over 6 to 11 months. Parcel data condition drives both ends.
How long does implementation take and when should it go live?
Twelve to sixteen weeks for a first release, but the calendar rules the schedule rather than the scope. Where assessments ride on the county tax roll, the treasurer statutory filing date is the real deadline, so plan a full parallel cycle before it. Roll out on one lateral or division in the off season and keep the scheduling book running through the first weeks of the run.
What is involved in migrating our parcel and delivery records?
More than a data load. Joining your turnout and account register to the county assessor roll surfaces decades of splits, mergers and transfers that were never propagated, and resolving them is district staff work rather than developer work. Start it before development begins and budget it as its own line. Historical deliveries are usually worth migrating only for years still open to dispute or audit.
Do we still need this if we have Rubicon Water canal automation?
Often yes, because the two solve different problems. Canal automation improves control and produces better numbers at the gate, which is genuinely valuable. It does not give you an allotment ledger per parcel with carryover and transfers, an assessment roll that reconciles to the county, a delinquency process, or an audit trail built to survive a hearing where a landowner has counsel.
How does the system handle telemetry from mixed equipment brands?
By treating each device family as its own integration and recording the measurement method on every delivery record. Districts rarely run one brand, and typically at least one instrument sits behind a proprietary desktop application with no documented interface. Price the work per family rather than as a single line, and never let a telemetered flow, a flume reading and a rider estimate be stored as equivalent numbers.
Who actually builds software for irrigation and conservancy districts?
A handful of small regional vendors, plus custom firms with public sector delivery behind them. Digital Heroes is a fit where the parcel to turnout to water right model has to be right, field capture must work without signal, and the district wants its own law governing the agreement through an American, British or Indian entity. A board can review the Fiverr Vetted Pro listing and a delivery record past two thousand projects.
What makes Digital Heroes different from a generic development firm?
The requirements document comes before code and is written to be read by your board and counsel, because apportionment rules, carryover and shortage proration are policy decisions rather than technical ones. Getting those approved on paper is far cheaper than discovering them in a delivery season. Three products, ShopScore, HeroCheckout and Section Vault, are operated by the firm itself, so long term maintenance is something it does rather than promises.
How can a district board verify a development partner before paying?
Pull the D-U-N-S record and check the registered entity is the one signing. Read what named organisations have written on Clutch and Trustpilot rather than counting stars. Ask for a reference from another public body and find out who maintains that system now, several years on. Then write repository, cloud account and data export ownership into the agreement, because districts outlive staff and vendors alike.
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.
How do I vet an agency for an ERP project?
Ask to speak with two clients who have been running an ERP the agency built for at least two years, because ERP quality shows up in year two, not at launch. Then ask for their data migration plan, their module rollout sequence, and the named senior engineers who will be on your project. An agency that leads with screen designs instead of process mapping is a red flag for ERP work.
How much does a custom ERP cost for a small business?
A small-business ERP covering two or three core modules typically runs $40,000 to $120,000, with inventory, ordering, and accounting sync being the usual starting set. Across 2,000+ Digital Heroes projects, integration count and user roles drive cost far more than screen count. A full mid-market ERP with six or more modules usually lands between $150,000 and $400,000.
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.
Why do companies replace NetSuite with custom software?
The three reasons we hear most at Digital Heroes are per-user license growth, SuiteScript customizations that became fragile, and workflows the platform cannot model without workarounds. A company adding 50 users to NetSuite takes on roughly $59,000 per year in extra licenses at the commonly quoted $99 per user rate, which is often the moment the custom math starts winning. Replacements usually keep the accounting structure intact and migrate module by module.
What should I prepare before contacting an ERP development agency?
Bring a list of your current tools and spreadsheets, a rough map of how an order or job moves through the company today, your user count by role, and the three problems costing you the most hours. You do not need a formal specification; a good agency writes that with you during discovery. Companies that arrive with those four things typically cut two to three weeks off scoping in our experience.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP 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 ERP 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 Beau.
Performance Marketing Manager · APAC · Sydney · 1 post on the site
Published · Last updated .
