Your Pilot Went Well. So Why Isn't It Turning Into a Contract?

The question I hear most often from water technology companies is not “how do we get pilots.” If you’re still working on getting into the building, start with how to sell to water utilities first. Pilots are relatively accessible. Utilities are often willing to run a proof of concept, particularly if the vendor absorbs the cost.

The question I hear most often is: “We have five pilots. None of them are converting. What are we doing wrong?”

This is among the most common and expensive problems in water technology sales. The pilot portfolio grows, the team celebrates each new logo, and the revenue line stays flat. This piece focuses on the design of the pilot itself, and on why so many of them stall.

Why pilots stall

Pilots stall for a small number of reasons, and diagnosing which one applies to you is the first step.

The problem is real, but not urgent. The utility agreed to a pilot because the technology is interesting and the cost was low. But the problem it solves isn’t on anyone’s priority list this year. The pilot completes successfully, the report sits in someone’s inbox, and nothing happens. There’s no urgency driving a procurement decision.

The champion has no path to a budget. Your internal champion at the utility believes in the product. They don’t have the authority to approve a contract, and the capital or operating plan has no line item this purchase maps to cleanly. They can’t make a case to leadership because they don’t know how to fund it.

Success was never defined. The pilot ran for six months and generated data. But there was no agreed-upon definition of what success looked like, no threshold that both parties committed to in advance, and no agreed next step if that threshold was met. The utility views the pilot as interesting information; you view it as a green light. Neither party is wrong, but the ambiguity works against you.

The utility is running your pilot alongside three others. This is more common than vendors realize. Utilities often run multiple pilots in a given technology category simultaneously. They may have no intention of converting any of them to a contract before they have data across all of them. If you don’t know you’re in a competitive pilot situation, you can’t manage it.

The product doesn’t meet the bar. Sometimes the candid answer is that the pilot revealed product gaps: performance below expectations, or an integration and operations burden the utility’s team can’t carry. This is the hardest conclusion to reach, but it’s important to distinguish it from the other causes.

How to design pilots that convert

The goal of a pilot is to create a documented, agreed-upon basis for a procurement decision, and that is a different thing from demonstrating that your technology works. Designing for the first changes several things about how you structure the engagement.

Define success before you start, in writing. How you present in the initial evaluation also matters; see our guide on what makes a great water technology demo. What specific metrics, at what thresholds, over what time period, would demonstrate that the technology delivers the value you’re claiming? This definition should be agreed to by both parties before the pilot begins, and actively negotiated, so the utility owns it instead of passively accepting what the vendor wrote into the agreement.

If the utility is unwilling to define what success looks like in advance, that’s important information. It may mean they aren’t serious about procurement, or that they don’t trust the technology enough to commit to a standard. Either way, you want to know that before you invest in the pilot.

Agree on what happens if the pilot succeeds. “We’ll take the results to leadership” isn’t an answer. Who specifically? When? What’s the timeline for a decision? Is there a budget mechanism a purchase can flow through? Is there a capital plan that can fund a full deployment, and when is that updated?

You aren’t trying to extract a commitment to buy before the pilot demonstrates value. You’re trying to establish that there’s a credible path from a successful pilot to a procurement decision. If that path doesn’t exist, if the champion doesn’t know how the purchase would be funded or who would approve it, the pilot is likely to stall regardless of results.

Involve the decision-makers alongside the champion. The technical champion is your advocate inside the utility, but they aren’t the decision-maker. The pilot design should create natural touchpoints with the broader decision-making team: mid-pilot briefings, results presentations, site visits by leadership. If the people who will eventually approve a contract have never seen your technology or met your team, a successful pilot report is still asking them to take a significant leap of faith.

Build in a clear decision point. The pilot should have a defined end date and a defined decision process. At the end of the pilot, there should be a meeting in which the results are reviewed against the agreed success criteria and a decision is made: proceed to procurement, extend with defined additional criteria, or conclude without moving forward.

The third outcome isn’t a failure if it was reached in good faith. It’s information. The failure mode is a pilot that neither succeeds nor fails but simply continues indefinitely because no one has forced a conclusion.

Pricing the pilot

Subsidized or free pilots are often necessary to get in the door, particularly with utilities that have no prior relationship with your company. But they create a dynamic worth managing carefully.

When the pilot is free, the utility has limited skin in the game. They agreed to it because the cost of saying yes was very low, not necessarily because they’re seriously evaluating a purchase. A pilot with a nominal cost, or a pilot structured as a paid proof of concept with a credit toward the full contract, changes the dynamic. The utility has made a financial commitment, which signals genuine interest and creates a stronger internal justification for proceeding to procurement.

Not every utility will agree to a paid pilot. But it’s worth asking, and the response tells you something about how serious they are.

What to do with stalled pilots

If you have pilots that have been sitting without progress for more than six months past the agreed evaluation period, you have a decision to make. You can let them sit, which costs you time and opportunity cost, or you can force a conclusion.

Forcing a conclusion means going back to the champion and being direct: the pilot has been complete for X months, the results met the agreed success criteria, and we need to understand the path forward. If there’s no path (no budget, no timeline, no decision authority) it’s better to know that now than to continue investing in the relationship at the same level.

Sometimes this conversation unlocks something. The champion has been meaning to escalate but hasn’t. The budget conversation is further along than you knew. There’s a procurement window opening that you weren’t aware of.

Sometimes it confirms the deal isn’t happening. That’s also valuable: it lets you stop managing a stalled relationship and redirect your time toward accounts where a path exists.

The utilities that convert pilots to contracts are the ones where someone on both sides of the table was accountable to a clear next step. Build that accountability into every pilot you run.

---

HydroKnowledge works with water technology companies on go-to-market strategy, sales process design, and pipeline acceleration. Get in touch if your pilots aren’t converting.

FAQ

Why don’t water technology pilots convert into contracts?

Usually for one of a few diagnosable reasons: the problem the pilot solves is real but not urgent enough to drive a purchase, the champion has no path to a budget line, success was never defined in advance, the utility is running several competing pilots at once, or the pilot exposed a genuine product gap. Naming which one applies to a specific stalled pilot is the first step, because the fix is different for each.

How do you design a water utility pilot that converts?

Design it around the procurement decision it needs to trigger. Define success in writing with the utility before it starts, with specific metrics and thresholds both sides own. Agree on what happens if the pilot succeeds: who approves the purchase, on what timeline, and through what budget. Involve the broader decision-making team alongside the technical champion, through mid-pilot briefings and results presentations. And build in a firm decision point with a defined end date, so the pilot reaches a conclusion.

Should a water technology pilot be free or paid?

A paid pilot, even at a nominal cost, gives the utility skin in the game and signals genuine intent, which strengthens the case for converting to procurement. Free pilots are often necessary to get in the door with a utility that has no prior relationship, but they leave the utility with little commitment. Not every utility will agree to pay, and the answer itself tells you how serious they are. The pricing choice is covered in depth in how to price your water tech pilot.

What should you do with a pilot that has stalled?

Force a conclusion rather than letting it sit. Go back to the champion directly: the pilot has been complete for some months, it met the agreed success criteria, and you need to understand the path forward. Sometimes that unlocks a budget conversation or a procurement window you didn’t know about. Sometimes it confirms the deal isn’t happening, which is also valuable, because it frees you to redirect time toward accounts where a real path exists.