How do you build a water utility software go-to-market motion in 2027?

The go-to-market motion in one picture

Most software categories let you draw a straight line from a marketing touch to a signature. Water utilities do not work that way, and the single biggest mistake a founder makes in this market is designing a motion that assumes they do. A water utility is a public body or a regulated private operator. It buys against a capital plan, a rate case, a regulatory deadline, or a catastrophe — and rarely against a quarter-end discount. The motion has to be shaped around those triggers, not around your pipeline coverage math.

The practical shape is four converging streams feeding one qualification gate, then a proof artifact, then a procurement gauntlet that you cannot shorten but can prepare for. Roughly 30% of qualified pipeline comes from inbound (AWWA and WEF publications, Smart Water Magazine, Water & Wastewater International, Engineering News-Record's water coverage), 25% from outbound aimed at the GM, COO, and Director of IT, 30% from partner-led motion through engineering firms, 10% from conferences, and the remainder from existing-ERP channel plays inside the SAP and Oracle install bases.

The partner stream deserves emphasis because it is the one most software teams underweight. Engineering and consulting firms — Black & Veatch, CDM Smith, AECOM, Stantec, HDR, Brown and Caldwell, Jacobs, Arcadis, Burns & McDonnell — write the master plans, the AMI business cases, and frequently the RFP language itself. A vendor with no relationship at that layer is reading a scope document that was authored around somebody else's architecture. The meter manufacturers occupy a parallel position: Itron, Sensus (Xylem), Aclara (Hubbell), Badger Meter, Master Meter, and Mueller Water Products all carry install-base relationships that predate your company by decades.

Notice that the loop closes back into vendor scan rather than terminating at signature. Utilities buy in modules across years, and the second and third purchases are evaluated nearly as formally as the first. That is why net retention in this category behaves less like classic SaaS expansion and more like a series of small re-wins.

The adjacent categories rhyme. Electric and gas utility software runs the same committee structure with different regulatory pressure, wastewater and stormwater ride the same GIS and asset-management spine, and municipal ERP shares the procurement gauntlet almost exactly. If you build the motion correctly for water, the sales assets port sideways with modest rework — which is a real argument for investing in the artifacts rather than in headcount early.

Who owns what across the revenue org

The five-seat committee is not a persona exercise; it is a veto map. AWWA's State of the Water Industry work has consistently found utility technology purchases pulling in multiple stakeholder groups, and in practice deals above roughly $150K in annual contract value touch five distinct owners. Each one can stop the deal for a different reason, and each one requires different material.

General Manager / Director of the Water Utility owns the product call. This person is measured on service reliability, rate stability, and staying out of the newspaper. They respond to peer proof — what did the utility two counties over do, and did it work. Give them a one-page outcome narrative and three reference names, not a feature matrix.

COO signs. Water utility software touches non-revenue water loss, customer billing, and asset reliability simultaneously, which puts it in front of the operating budget rather than the IT budget. The COO wants the recovery math: dollars of treated water currently unbilled, dollars of emergency repair avoided, staff hours redirected. Bring a model they can hand to their finance team without you in the room.

CIO / Director of IT owns integration and holds the loudest veto. The realistic integration surface includes SAP IS-U and Oracle Customer Care & Billing on the enterprise CIS side, Itron, Sensus, Aclara, Badger Meter, Master Meter, and Mueller Mi.Net on the AMI side, Bentley OpenFlows and Esri ArcGIS on the modeling and GIS side, and IBM Maximo or Trimble Cityworks on asset and work management. Showing up without day-one connectors to the specific stack in front of you is the fastest way to be disqualified before the demo.

Director of Operations owns SCADA, treatment, and distribution. This seat is skeptical by professional obligation — they are responsible for water that people drink. They care about data provenance, sensor reliability, false-positive rates on leak alerts, and what happens when your service is down during a main break. Answer operationally, not commercially.

Director of Customer Service owns billing, collections, and portal experience. High-bill complaints after an AMI deployment are the classic post-go-live disaster, and this seat has usually lived through one. Show the complaint-handling workflow, the consumption-alert configuration, and what the call center sees when a customer phones in.

On your side of the table, the ownership split that works is: AE owns the GM and COO relationship, solutions architect owns the CIO and Director of IT, customer success owns Operations and Customer Service from the sandbox forward, and the partner manager owns the engineering firm and meter manufacturer relationships as a standing account, not per deal. The revenue leader's job is making sure no single seat goes dark for more than three weeks in an active cycle. Utilities go quiet during rate cases, budget season, and emergencies — silence is usually not a loss signal, but you need a named person watching each thread to know the difference.

Hiring sequence matters more here than in most categories because domain credibility is not fakeable. The first five hires are founder-led sales plus a lead enterprise AE from Itron, Sensus, Oracle CC&B, SAP IS-U, or Trimble Cityworks at roughly $250K OTE, a customer success director who has actually run a utility, a solutions architect fluent in the integration surface above, and a product marketer with a real AWWA and WEF network. Hires six through fifteen add regional enterprise AEs, mid-market AEs, SDRs, a partner manager for the engineering firms, implementation architects, a leak-detection specialist, and an RFP specialist — that last role pays for itself faster than anyone expects when responses run 200 to 450 questions. Past that, add VPs, regional GMs for EMEA, APAC and LATAM, and a chief water strategist recruited from a major utility GM seat, typically around $20M ARR.

Metrics, targets, and realistic ranges

Segment by account count, not by revenue, because account count drives both your pricing and the buyer's complexity.

Large utilities at 100,000+ accounts — the DC Waters, Las Vegas Valley Waters, Sydney Waters, Severn Trents of the world — run 12 to 15 month cycles and land at $1M to $4M ACV. These deals require board or commission approval, multiple site visits, and usually a formal RFP. Do not model them as repeatable until you have three.

Mid-market utilities at 10,000 to 100,000 accounts close in six to nine months at $120K to $1M ACV. This is where a well-run motion actually compounds. The committee still has five seats but they sit in the same building, procurement is lighter, and the reference network is dense.

Small utilities under 10,000 accounts — municipalities, special districts, rural water associations — close in three to six months at $15K to $120K ACV. Margin here depends entirely on implementation discipline; a bespoke deployment at this ACV destroys the unit economics.

On pricing, the per-account subscription band runs roughly $0.40 to $4.00 per water account per month depending on module attach, layered on top of per-meter economics where AMI is in scope. Published and street pricing across the AMI vendors clusters between roughly $0.50 and $1.80 per meter per month, with meter hardware in the $80 to $400 range depending on size and communication module. Software-only categories price differently: GIS-centric work management around $50 to $120 per user per month, Esri ArcGIS Utility Network and Solutions for Water in the $5K to $50K annual range plus named users, Bentley OpenFlows WaterGEMS and SewerGEMS in the $5K to $40K annual range, Innovyze InfoWater Pro and Info360 roughly $10K to $80K annually, and full enterprise CIS from Oracle or SAP running from a few hundred thousand into the millions.

Operating benchmarks worth holding yourself to: win rate 26% to 38% on qualified opportunities, net retention 108% to 122%, CAC payback 18 to 30 months, and gross margin 62% to 78% once hardware is blended in. That margin band is the one founders underestimate — every point of hardware pass-through drags it down, and the discipline of separating hardware revenue from software revenue in your own reporting is what keeps the board conversation honest.

Multi-year structure is the most reliable close lever available. Five-year agreements close materially more often at a 12% to 18% discount, and they align with how utilities budget capital anyway. The trade is real: you buy predictability and lose pricing flexibility during a period when your product will change substantially. Build an annual uplift and a module-attach path into the paper rather than trying to renegotiate mid-term.

The ROI model that moves the COO is the non-revenue water calculation. AWWA's water audit methodology puts NRW in a wide band, commonly cited in the 15% to 35% range for utilities that have not invested in loss control. Run it concretely: a utility producing 50 million gallons per day, billing around $2.50 per thousand gallons, generates roughly $45M in annual revenue. At 25% NRW, the loss is on the order of $11M. A program that recovers even a fifth of that changes the utility's financial position more than any software line item on the budget — and billing-accuracy improvements from AMI stack on top. Build the calculator with their own numbers, from their own water audit, and let them argue with themselves.

The adjacent expansion math is worth modeling early too. A utility that buys AMI analytics almost always has wastewater and stormwater assets under the same organization, and often shares GIS with the electric department in a combined municipal utility. The second-territory or second-utility-type expansion is your cheapest revenue in the model, and it should be a named motion with an owner, not something you hope happens at renewal.

Where the motion breaks down

Five failure modes account for most of the losses, and four of them are preventable with preparation rather than talent.

Demo-only selling. Deals without a working sandbox on the customer's own historical data close roughly a third slower and lose more often to incumbents. A generic demo asks the utility to imagine; a sandbox on their AMI, billing, and work-order history shows them their own leaks. This is the single highest-leverage artifact in the category and it should be built before the second AE is hired.

Missing integrations at first contact. The CIO veto is fast and final. If the utility runs Oracle CC&B and you cannot name the certified API path, or they run Cityworks and you cannot describe the work-order handoff, the evaluation ends in the technical screen. Build connectors for the three or four stacks that dominate your target segment before you build the fifth feature.

Compliance gaps. EPA Safe Drinking Water Act obligations, the Lead and Copper Rule Revisions, PFAS drinking water standards, and America's Water Infrastructure Act risk and resilience requirements all shape what the utility must document. Layer on cybersecurity expectations — utilities increasingly ask for NIST Cybersecurity Framework alignment and formal security questionnaires — and you have a document package that either exists or costs you the deal. General Counsel and the Director of Operations both hold vetoes here.

No engineering firm relationship. If a master plan or AMI business case was written by a firm that has never heard of you, you are responding to an RFP shaped around a competitor's architecture. Getting into those documents early is a partner-management function with a multi-quarter lead time — it cannot be spun up when the RFP drops.

No third-party air cover. Utilities shortlist conservatively. Presence in AWWA and WEF programming, analyst coverage of the utility CIS and smart water categories, and trade press visibility all function as risk reduction for a GM who has to defend the choice publicly. A vendor with none of it struggles to make shortlists at all.

There is a sixth failure mode that is subtler and more expensive: winning the wrong deal. A large utility that wants a heavily customized deployment at mid-market pricing will consume your entire engineering roadmap for eighteen months. The discipline of declining that deal is the hardest thing to teach a first sales team, and the second-order damage — a reference customer who is unhappy because you overcommitted — lasts years in a market this interconnected.

Watch the false-positive rate on leak and anomaly alerts as a leading churn indicator. Operations teams stop trusting a system that cries wolf, usage collapses quietly, and you find out at renewal. Instrument alert acknowledgment and field-verification rates from day one and review them in the same cadence as pipeline.

How to sequence the build

Sequence the company against the motion rather than against a generic SaaS playbook. The gating question at each stage is which failure mode you have retired.

Stage one is a single reference utility and a working sandbox. Nothing else matters. Founder-led sales, one mid-market utility that will let you load their historical AMI and billing data, and a documented outcome you can point at. Expect this to take longer than you planned because data access requires trust you have not earned yet.

Stage two is integration depth and the compliance package. Pick the two or three stacks your target segment actually runs — usually one enterprise CIS, one AMI vendor, and Esri — and build real connectors. In parallel, assemble the regulatory and security documentation as a standing artifact, not a per-deal scramble.

Stage three is the partner layer. Engineering firm relationships and meter manufacturer alliances take two to four quarters to produce pipeline, which is exactly why they must start before you need them. Treat the partner manager as a demand-generation hire, not a business-development afterthought.

Stage four is segment expansion and module attach. Single-module vendors stall in the low hundred-and-single-digits on net retention; the vendors reaching 115% and above are the ones attaching CIS, GIS, asset management, work order, customer engagement, and leak detection into the same account over multiple years.

The operating cadence that holds this together is unglamorous. Weekly: enterprise pipeline standup Monday, sandbox results review Wednesday, partner alignment Friday. Monthly: module-attach review comparing single-module accounts against full-suite accounts, service-territory rollout pace against plan, and a renewal-risk board. Quarterly: a GM advisory council convened around AWWA ACE, WEFTEC, or a WateReuse event, a roadmap review on leak detection and smart water, and a regulatory update covering whatever moved on LCRR, PFAS, and AWIA.

Time outbound against the regulatory and environmental calendar rather than your fiscal one. Compliance deadlines, drought declarations, rate case filings, and the aftermath of a publicized main break all create genuine urgency that no discount can manufacture. A sales team that tracks those windows in the same system as its pipeline will outperform one that runs on activity metrics alone — and that timing discipline is the closest thing this market has to a repeatable growth lever.

Related questions

How is water utility software different from electric utility software?

The committee and procurement path are nearly identical, but the value story differs. Electric centers on outage management, demand response, and grid reliability; water centers on non-revenue water, treatment compliance, and pipe asset condition. Combined municipal utilities buy both, often through one IT organization.

Can you sell water utility software without hardware?

Yes, and the margins are better. Software-only plays in GIS-centric work management, hydraulic modeling, leak analytics, and customer engagement all sell independently of meter deployment. You give up the per-meter revenue stream but avoid the hardware drag on gross margin and the supply-chain exposure.

What triggers a utility to replace its customer information system?

Usually vendor end-of-life, an AMI deployment the current CIS cannot support, a rate structure change the billing engine cannot model, or accumulated technical debt surfaced during an audit. CIS replacements are multi-year, board-approved projects — treat them as a separate motion from analytics sales.

How do small rural water systems buy differently?

They buy through cooperatives, state rural water associations, and circuit-rider programs rather than formal RFPs. Cycles are shorter, ACV is small, and the decision often sits with one or two people. Channel and self-serve motions work here where enterprise field sales does not.

Does AI leak detection replace acoustic surveying?

No — it triages it. Satellite, acoustic, and AMI consumption data triangulate to prioritize where crews survey, which raises hit rate per field day. The field program remains; the software decides where it goes. Pitch it as crew productivity, not crew replacement.

FAQ

What is a realistic sales cycle by segment?

Twelve to fifteen months for large utilities above 100,000 accounts, six to nine months for mid-market utilities between 10,000 and 100,000 accounts, and three to six months for small systems under 10,000 accounts. Board or commission approval adds eight to eighteen weeks on top of the commercial close at the enterprise end, and that step is not compressible.

What ACV should I plan for?

$1M to $4M for large utilities, $120K to $1M for mid-market, and $15K to $120K for small systems. These are annual contract values on multi-year paper — most utility agreements run three to five years, so total contract value is several multiples of ACV and should be reported separately to avoid flattering your growth rate.

How do I compete against the AMI incumbents?

Do not attack meter parity. Itron, Sensus, Aclara, Badger Meter, Master Meter, and Mueller have decades of install base and hardware supply chains you cannot match. Win a wedge instead — leak analytics, GIS-centric work management, or customer engagement — and integrate with their networks rather than replacing them. Partnership beats displacement in this category.

Should I build into the SAP and Oracle install bases?

Yes. Large utilities running SAP IS-U or Oracle Customer Care & Billing represent a concentrated, identifiable target list with certified integration paths already documented. Selling alongside an entrenched CIS is far easier than proposing to replace it, and the CIO who just finished a CIS implementation has no appetite for another one.

How should I position AI-driven leak detection?

As triangulation, not magic. Satellite imagery, acoustic sensors, and AMI consumption anomalies combined produce a prioritized survey list. The measurable outcome is leaks found per field crew day and main breaks avoided — an avoided emergency repair on a large main runs well into six figures once you count water loss, road restoration, and service disruption.

When does the partner motion start paying back?

Plan on two to four quarters from first engineering firm conversation to influenced pipeline, and longer to co-authored specifications. Because those firms shape the RFP language on major projects, the relationship has to exist before the project is scoped. Start it while you are still founder-selling, even though it will not show in this quarter's number.

Sources

• https://www.awwa.org/
• https://www.wef.org/
• https://www.epa.gov/dwreginfo/lead-and-copper-rule
• https://www.epa.gov/sdwa/and-polyfluoroalkyl-substances-pfas
• https://www.epa.gov/waterresilience/americas-water-infrastructure-act-2018-risk-assessments-and-emergency-response
• https://www.nist.gov/cyberframework
• https://www.itron.com/
• https://www.xylem.com/en-us/products-services/analytics-software-services/sensus/
• https://www.esri.com/en-us/industries/water/overview
• https://www.bentley.com/software/openflows/

Related on PULSE

• [How do you build a forestry management software go-to-market motion in 2027?](/knowledge/gp0122)
• [How do you build an aquaculture software go-to-market motion in 2027?](/knowledge/gp0121)
• [How do you build a livestock management software go-to-market motion in 2027?](/knowledge/gp0120)
• [How do you build a medical device software / SaMD go-to-market motion in 2027?](/knowledge/gp0117)
• [How do you build a specialty pharma distribution software go-to-market motion in 2027?](/knowledge/gp0116)
• [How do you build a clinical trial software (Veeva / Medidata) go-to-market motion in 2027?](/knowledge/gp0115)