What Most Water Technology Companies Get Wrong About Selling to Utilities

Almost every technology company that enters the water market arrives with the same story - a strong product and a genuine belief that the value proposition will carry the day. Then they spend two years wondering why nothing is closing. By month eighteen they are sitting across the table from a procurement director who leans back and says, “We love what you’re doing. We’re just not ready to move forward right now.” Not ready. After eighteen months.

The failure usually traces back to the institution itself. A commercial playbook assumes the buyer behaves like a customer, weighing trade-offs and moving when the math is good. Municipal water utilities don’t behave that way and were never designed to. The sales process is almost beside the point if you don’t understand the institution you’re selling into.

The institution shapes everything

The vast majority of municipal water utilities aren’t companies; they’re public agencies. And even the ones that ARE companies (i.e. American Water, Aqua, CSWR, and others) still act as quasi-public agencies.

A utility’s budget is approved by a governing board - often elected or politically appointed officials whose primary accountability is to ratepayers, not to operational efficiency. Capital projects require multi-year planning cycles, environmental review, and frequently, regulatory sign-off. The person you’re talking to (the operations manager, the technology director, the engineer) is almost never the final decision-maker. They’re a champion, if you’re lucky, and a gatekeeper if you’re not.

This isn’t inefficiency for its own sake. Utilities operate infrastructure that can’t fail. The water coming out of the tap has to be safe today, tomorrow, and fifty years from now, regardless of which vendor’s contract is still active. Caution is designed into the system for exactly the right reasons.

This changes how you should approach the market. If I can sum it up succinctly: the metric is trust.

Procurement is political and procedural

Every utility has a formal procurement process. RFPs, competitive bidding requirements, sole-source justifications, board approvals. You need to understand these; we’ve covered how utilities make buying decisions in depth separately. But understanding the process isn’t the same as understanding how to navigate it.

The real procurement decision happens before the RFP is issued. By the time a utility publishes a formal solicitation, they usually have a strong sense of what they want to buy, and sometimes who they want to buy it from. The RFP is the documentation mechanism for a decision that was already made in office hallways or at conferences, and over years of relationship-building.

This means your job is to be the company that shaped what the RFP asks for.

That requires being present long before a formal procurement cycle begins. You should be attending AWWA and WEFTEC events as an active participant: speaking on panels, joining working groups, attending after hours functions, doing volunteer events, taking tours, publishing research that utilities read. It means building relationships with utility staff (and their respective engineering firms!) at the working level, because those are the people who will write the specifications.

It also means understanding the political environment inside the utility. Who is the internal champion for innovation? Who is the skeptic? What has failed before, and why? A utility that got burned by a technology vendor five years ago carries that memory into every conversation with the next vendor. If you don’t know that history, you’re operating blind.

The pilot is not the shortcut you think it is

Every technology company wants to get to a pilot. The pilot feels like progress and it can be valuable, but pilots are frequently where deals stall.

The reason is structural. A pilot requires a utility to assign staff time, coordinate with operations, and take on some risk. That’s a meaningful internal commitment. What it doesn’t do, by itself, is create a path to procurement. Many utilities are very good at running pilots and very slow at converting them to contracts.

Before you agree to a pilot, you need to understand what happens if it succeeds. Who has the authority to move it to a contract? What is the timeline for that decision? What budget exists for it? Is there a capital plan that can fund a full deployment, and when is that plan updated?

If the answers to those questions are vague, you may be about to spend twelve months generating excellent data for a customer who has no mechanism to buy what you’re selling.

A pilot should be designed with the end in mind. Define success criteria before you start, agree on what a successful pilot would lead to, and put that understanding in writing. It doesn’t have to be a legal document, just a shared understanding both parties can point to.

Price is not the primary objection

When a utility pushes back on price it’s tempting to respond by lowering the price. Sometimes that’s the right move. More often, the price objection is a proxy for something else: uncertainty about fit, concern about implementation complexity, worry about what happens if the vendor doesn’t survive, or simply not having a budget line that the purchase maps to cleanly.

Water utilities aren’t particularly price-sensitive in the way commercial enterprises are. If the value is clear and the trust is there, they will find the budget. What they’re sensitive to is risk: the risk of choosing the wrong vendor, the risk of a failed implementation, the risk of having to explain a bad decision to a board or to the public.

Your job is to reduce perceived risk at every stage of the conversation. That means being transparent about your company’s financial position and customer base. It means showing other utility references that are actual customers who will take a phone call, not marketing case studies. It means being upfront about what your product doesn’t do, because utilities have good instincts for overselling and it will cost you trust faster than almost anything else.

What works

After years on both sides of this market, as a vendor and as an advisor to utilities and technology companies, the pattern that works looks something like this:

Build presence before you build pipeline. Publish in places utilities read. Speak at events they attend. Be useful in the community before you ask for anything.

Find champions at the working level. The engineer who will use your product every day is more valuable to your sales process than the executive who will sign the contract, because the engineer is the one who will advocate for you internally when you’re not in the room.

Run pilots that are designed to lead somewhere. Agree on what success looks like and what happens next before the pilot begins.

Sell the relationship as much as the product. Utilities are making a decision about who they’re going to be partnered with for a long time. The product matters, but so does the team, the support model, and the sense that you’ll still be there five years from now.

Be patient with the timeline and relentless on the relationship. The deals that close in this market almost always look, at some point, like they’re going nowhere. The ones that ultimately succeed are usually the ones where the vendor stayed engaged and kept showing up.

The water market is hard. It’s also among the most mission-critical and underserved technology markets in the world. The companies that figure out how to sell here tend to build something durable. It just rarely happens on the timeline they expected.

---

Adam Tank is the founder of HydroKnowledge and co-founder of Transcend and Industrial Optic, two VC-backed water technology companies. HydroKnowledge advises water technology companies on go-to-market strategy and municipal sales. Get in touch if you’re working on something in water.

FAQ

How do you sell technology to a water utility?

By understanding the institution before the sales process. Municipal water utilities are public agencies accountable to ratepayers and boards, not customers optimizing for value, so trust matters more than speed. The motion that works is to build presence before pipeline (publish where utilities read, speak at AWWA and WEFTEC events, build working-level relationships with utility staff and their engineering firms), find a champion at the operator level, and stay engaged patiently across a cycle that usually runs one to two years or longer.

When is the real buying decision made at a water utility?

Usually before the RFP is ever published. By the time a utility issues a formal solicitation, it typically has a strong sense of what it wants to buy and sometimes who from. The RFP documents a decision shaped months or years earlier in hallway conversations, at conferences, and through relationship-building. The job is to be the company that helped shape what the RFP asks for, which means being present long before the procurement cycle opens.

Are water utilities price-sensitive?

Less than most vendors assume. When the value is clear and the trust is there, utilities generally find the budget. What they’re sensitive to is risk: choosing the wrong vendor, a failed implementation, or having to defend a bad decision to a board or the public. A price objection is often a proxy for uncertainty about fit or implementation, so responding by lowering the price frequently misses the real concern.

What is the most common mistake companies make selling to water utilities?

Running a purely commercial playbook that treats the buyer like a company weighing trade-offs and moving when the math is good. Utilities are built for caution because they operate infrastructure that can’t fail, so the work is reducing perceived risk and earning trust over time. Vendors who optimize only for the RFP response, without building the upstream relationships, tend to generate conversations rather than orders.