How Engineering Consultants Quietly Decide Which Water Technology Gets Bought

A water tech founder lands a meeting with a mid-sized utility director. The pitch goes well. The director nods in the right places, asks sharp questions, and at the end says the right thing: “We’d love to find a way to pilot this.” Six months pass, and nothing moves. A treatment plant upgrade eventually gets scoped, and when the construction drawings come out, the specified product is a competitor the founder has never seen pitch this utility before. What happened?

The decision was already made, and it was not made in that meeting with the director. It was made, probably twelve to eighteen months earlier, by an engineer at Jacobs or Black & Veatch or CDM Smith, sitting at a desk in an office building two states away, drafting a preliminary engineering report for an upcoming capital project. That engineer wrote the specification. That specification named one vendor, or a short list of two or three, and everyone else was out of the deal before the founder had ever heard the project existed.

This is the invisible channel. It is how the majority of significant water technology purchases actually happen at U.S. water utilities, and it is also the thing most early-stage water tech founders either do not know about or do not know how to work within. This post is about what that channel looks like, where inside it the decisions get made, and what it takes to be on the short list when an engineering consultant sits down to draft a spec.

The consultants who run the channel

Let’s start with the names. A reasonable short list of the engineering consultancies that shape water technology decisions at U.S. utilities includes Jacobs, Black & Veatch, HDR, CDM Smith, Stantec, Carollo, Brown and Caldwell, Arcadis, Hazen and Sawyer, AECOM, Freese and Nichols, Tetra Tech, and Burns & McDonnell. Strong regional firms layer on top of those: Kennedy Jenks on the West Coast, Dewberry in the mid-Atlantic, Barr Engineering in the upper Midwest, and so on.

These firms are the engineers of record for most sizable water infrastructure projects in the country. A utility planning a new treatment plant, a pump station upgrade, a non-revenue water program, or a biosolids facility almost always hires one of these firms to do the preliminary engineering, detailed design, and sometimes construction management. The firm earns a fee that is typically a percentage of construction cost, which means it has a structural incentive to scope robust, defensible, technically unambiguous designs. At a water utility, a defensible design is one that specifies proven technology from vendors the firm and the utility both recognize.

If your product is not recognized by this short list of firms, you are effectively invisible.

Where technology decisions actually get made

There is a tempting narrative in water tech circles that says the decision happens during the utility’s procurement process. It rarely does. By the time a solicitation hits the street, the technology choice has usually already been made.

The decision points worth understanding, in rough chronological order:

The planning study or master plan. Before a utility does capital work, it usually commissions a planning study. These go by various names (facilities plan, master plan, capacity assurance study, long-range plan). An engineering consultant writes it. This is where the utility’s needs get translated into a portfolio of projects, and in many cases where the technology approach for each project gets locked in at a conceptual level. If the plan says “membrane bioreactor,” the downstream design is going to specify a membrane bioreactor. If the plan says “conventional activated sludge with tertiary filtration,” something else entirely gets built. The choice between those two paths is often made inside a planning study, and most founders have never read one.

The preliminary engineering report, or PER. Once a project is funded, the design engineer produces a preliminary engineering report. This is the document that moves the project from “we need a new filter” to “we will build an ultrafiltration system with four trains of 2 MGD capacity each, redundant air scour, integrated CIP.” At the PER stage, vendor names start appearing, sometimes directly and sometimes through specifications tight enough that only one or two vendors can meet them. If you are not being evaluated during PER, you are not going to be specified.

The detailed design package. By the time the design team is at 60% or 90% design, the specifications are being drafted. Sections in the CSI MasterFormat cover the process equipment and the instrumentation and controls. These specification sections are where vendor names, model numbers, and performance requirements live. Some utilities require open specifications with multiple acceptable manufacturers; others allow sole-source specs with a documented justification. Either way, if your product is not in the specification, it is not going to be in the bid.

The bid evaluation. Contractors bid against the specifications. The low responsible bidder wins. If the spec named three acceptable manufacturers and yours was one of them, you have a chance. If the spec named a competitor exclusively, you do not.

Most founders treat “the sale” as happening at the bid evaluation stage. It almost never does. The sale happened in the planning study and the PER, often years earlier, and everything downstream was execution of a decision that had already been made.

Why this is particularly true in water

A few structural features of the water industry make the consultant channel more dominant here than in most adjacent sectors.

Capital projects are expensive, long-lived, and highly regulated. A utility commissioning a $200 million treatment plant expansion does not have the in-house engineering depth to design it. State regulators require designs stamped by licensed professional engineers. Federal and state funding programs, including the clean water and drinking water state revolving funds, attach strings about design review and bid documents that effectively require consultant involvement. Rate-regulated public utilities face political pressure to justify every capital decision through an auditable, defensible process. The engineering consultant is the structural answer to all of these pressures.

Utility staff turnover reinforces the pattern. A utility’s lead process engineer may have been in the role for three years; the consultant relationship may span twenty. When a new technology needs to be evaluated, the utility often turns to the consultant and asks, “What are you seeing on other projects?” The consultant’s answer shapes the technology shortlist. In many cases it becomes the shortlist.

The way utilities actually make buying decisions runs through this channel much more than most founders realize. The utility director may have the final signature, but the options presented for signature were curated upstream by someone else.

What it takes to get specified

Being on a short list when a consultant drafts a spec is not a single action. It is a compound output of several things done well over a stretch of time.

Reference installations the consultant can verify. The first question any design engineer asks about a new technology is where it is operating, at what scale, for how long, with what results. Pilot data from a controlled trial at a graduate research lab does not count. A five-year operating record at a similarly sized utility counts enormously. If a consultant cannot pick up the phone and call an operator at a comparable installation, your technology is not going into the spec.

Named relationships with the engineers who write the specs, rather than the firm’s business development leads. Engineering firms are large, distributed, and organized by practice area. A relationship with the Jacobs corporate business development team does not mean much to the Jacobs process engineer in the Denver office who is drafting a PER for a utility in Colorado. The engineers who write specs are process engineers, instrumentation engineers, and project managers in specific regional offices. Their names appear on the stamped drawings. Learning who they are, building individual relationships with them, and treating them as the actual customer is the work.

A technical story that reduces, rather than increases, the engineer’s perceived risk. Design engineers are evaluated on whether their designs work and whether they come in on budget. They are not evaluated on whether they used the most innovative technology available. A vendor pitch that emphasizes novelty, first-of-kind status, or proprietary breakthroughs makes the engineer’s job harder. A pitch that emphasizes operating track record, standard installation patterns, published performance data, and familiar maintenance practices makes the engineer’s job easier. The second vendor gets specified more often. This is also what separates a water technology demo that actually converts from one that does not.

Visible presence at the conferences the design community actually attends. AWWA’s ACE, WEFTEC, and the state-level AWWA and WEF sections are where consultants present their work and see what other firms are doing. Technical paper sessions, particularly the ones where engineers present project case studies, are where technology reputations get built. Being on the panel, being referenced in a paper, or being visible in the exhibit hall with credible technical staff is a different signal than a trade show booth. The conferences that actually matter for this purpose are the ones where the people who write specs gather.

Published case studies and technical content that engineers can cite. A well-documented case study from a named utility, co-authored with a consulting engineer, carries far more weight than marketing collateral. It shows up in literature searches, gets forwarded between engineers, and gives the specifier something defensible to reference during design review. This is part of why a serious content strategy matters in water tech differently than it does in most other B2B markets.

Mistakes founders consistently make

A few patterns show up repeatedly among water tech founders who underinvest in the consultant channel.

The first is selling only to utilities. A founder will build a list of twenty target utilities, book meetings with their directors and CIOs, and spend two years running that playbook. The meetings go well, but nothing gets specified. The founder blames the sales cycle, when the actual problem is that no engineering consultant in the country has the product on a reference list. The standard playbook for selling to water utilities still matters, but without the consultant channel, it produces conversations rather than orders.

The second is treating consultants as gatekeepers to be routed around. There is a temptation to view the consultant as an obstacle between the vendor and the utility. Founders sometimes pitch the utility on skipping the consultant’s process, or frame the consultant as a defender of incumbents. This almost always backfires. The consultant is the utility’s trusted advisor on exactly the kind of decision the founder wants to influence. Being seen as an adversary to that advisor destroys credibility fast.

The third is treating every consultant as interchangeable. The relationship that matters is with the specific office and practice area that serves your target utility segment. A great relationship with Black & Veatch’s power practice does not help you sell membrane bioreactors. A great relationship with Carollo’s Western U.S. water and wastewater treatment group might be worth more than every other consultant relationship combined, depending on your product.

The fourth is underestimating the timeline. Getting specified through the consultant channel is a multi-year effort. It takes reference installations, which take time to build and then operate. It takes credibility, which accumulates slowly. It takes specific relationships with specific engineers, which cannot be shortcut. A fundraising deck that models consultant-channel specifications as a six-month sales cycle is telling investors something that does not match how the industry actually works.

The second-order risk

There is a version of this story that goes too far. A vendor that becomes known primarily as the consultant’s preferred product can run into a different problem: the utility itself starts to see the vendor as the consultant’s pick, not the utility’s pick. Utility staff who want to exercise their own judgment may push back against what feels like a prearranged answer.

The strongest position is to be credible with the consultants and visible to the utilities in parallel. The consultant relationships get you specified. The utility relationships give you a reputation independent of any single consultant’s preference. Each channel reinforces the other, and neither works as well alone. This is part of why moving water technology deals from pilot to procurement is structurally harder than it looks: the motion has to run through two parallel tracks without letting either one dominate.

Practical starting plays

For a founder who has not yet invested in this channel, a few starting moves translate to measurable progress within a year.

Identify the three or four engineering firms that design the majority of capital projects in your target geography and application area. Bid tabs from recent similar projects are publicly available for most public utilities; the engineer of record is usually listed in the front matter of the bid documents. Patterns will emerge quickly.

For each firm, identify the specific office and practice group that handles your application. Then identify the senior process engineers and project managers inside that group. Those names are the target list.

Reach out with technical content, not sales pitches. A thoughtful technical brief on a specific design consideration lands better than a product overview. A published case study from an operating installation lands better still.

Attend the state-section AWWA and WEF conferences in your target geography. These are smaller than the national shows, and the specifying engineers actually go to them. Sponsor a technical session if the spend is justifiable. Submit a paper if you have a story worth telling.

Build operating reference installations as fast as possible, and treat those references as shared infrastructure for the consultant channel. A reference plant with a willing operator, published performance data, and an open invitation for design engineers to tour is worth an enormous amount over time.

The bottom line

The purchasing decisions water technology founders care about most are almost always made inside documents written by engineering consultants, months or years before any procurement event. Founders who build directly to the utility and ignore this channel spend a lot of time in meetings that cannot convert into orders. Founders who invest in the consultant channel, patiently and credibly, build a position that compounds over time.

There is no shortcut. The channel is slow, relationship-heavy, and reference-driven. It rewards patience, technical credibility, and the willingness to treat design engineers as the real customer for a meaningful portion of the sales motion. For water tech founders who learn how it actually works, it is often the difference between a product that gets specified and a product that does not.

---

HydroKnowledge advises water technology founders on go-to-market strategy, including how to build credibility with engineering consulting firms and position products for specification. Get in touch if you are building a product that depends on the consultant channel to reach water utilities.