ClimateTech Customer Discovery: A Five-Stage Project Plan

Then someone asks the question you keep pushing to the end of every call: who, specifically, is going to write you a check, and why?

That moment — right after the technical walkthrough ends — is where most ClimateTech founders stall. Not because the science is wrong, but because the work of translating it into a paying relationship hasn't really begun. Customer discovery in our sector isn't a marketing warm-up. It's the connective tissue between a breakthrough in a reactor and a procurement officer with the authority to approve a PO. The good news? It's a project, not a mystery. And like any project, it has stages.

Stage 1: Defining the Problem Beyond Technical Performance

Before you ever set up an interview, you have to get honest about what problem you're actually solving — and for whom. This is where the work begins to feel different from a research proposal.

The temptation is to define the problem in the language of your technology. "We've reduced catalyst degradation by 40%." "We've achieved 92% methane capture efficiency." Those are outcomes, not problems. A buyer doesn't wake up at 3 a.m. worried about catalyst degradation. They wake up worried about a regulatory deadline they can't meet, a unit-economics spreadsheet that doesn't close, or a board commitment they can't honor without a workable solution.

The DOE's Adoption Readiness Level framework makes this distinction explicit: technical readiness alone is insufficient for commercialization. Teams also need to address market, customer, regulatory, organizational, and deployment risks. In plain language, you can have a beautiful TRL 7 prototype and still be years away from a sale, because you haven't yet identified the human problem your technology dissolves.

A few questions tend to surface the real problem during early-stage work:

• What concrete cost, compliance exposure, or operational bottleneck is your buyer trying to remove?
• How are they solving it today, and how much is that current workaround costing them?
• What triggers the buying decision — a regulation, a contract renewal, a board mandate, a public commitment?
• Who inside the organization feels that pain most acutely, and who controls the budget to address it?

If you can't answer these in specific, quantified terms — something like "we eliminate a defined cost per ton of avoided emissions for an industrial operator under California's SB 253 reporting cycle" — you don't yet have a problem statement. You have a hypothesis. The whole customer-discovery campaign is designed to test it.

A pilot is not a contract. Treating it like one is the most expensive mistake a ClimateTech founder can make.

Stage 2: The Art of the Discovery Interview

Once you have a working hypothesis about the problem, you get on the phone. This is the stage most founders underestimate, because it feels less rigorous than the lab work. It is, in fact, more rigorous — and more humbling.

Two authoritative programs have built entire methodologies around this stage, and they're worth understanding. The U.S. Department of Energy's Phase Shift I commercialization program asks participating teams to conduct a minimum of 30 customer-discovery interviews and use the findings to validate customer needs, identify adoption barriers, clarify target markets, assess sales channels, and clarify how the company intends to make money. NSF I-Corps, launched in 2012, runs a seven-week experiential training format built around the same premise: researchers test markets through structured customer discovery before committing serious capital to commercialization.

To be clear, those numbers and formats belong to specific programs. They are not universal ClimateTech commandments. But the principle behind them is portable: you cannot validate a climate venture on a handful of warm conversations with friendly contacts. You need a disciplined round of interviews, with people who don't owe you a favor.

What does a disciplined interview look like? It looks mostly like listening.

• Open with the problem space, not your solution. Ask how the buyer currently handles the issue, what's working, what's failing.
• Resist the urge to pitch. If you've talked for more than two minutes without asking a question, you've lost the interview.
• Probe for the specific moment of pain. When did they last feel it? What did it cost them in time, money, or reputation?
• Ask who else in their organization cares about this problem. Procurement? Operations? Sustainability? Legal? Finance? The answer reshapes your hypothesis every time.
• End by asking who else you should be talking to. The best interviews generate the next three.

NSF describes customer-discovery interviews as a way to determine whether customers want a proposed product or service and how it should be delivered. Notice that "how it should be delivered" sits in the same sentence as "whether they want it." Delivery matters. A perfect molecule delivered through a procurement process nobody can navigate is still a no-sale.

After 25 to 30 conversations, patterns emerge. You'll start to hear the same objections, the same trigger events, the same internal champions. That's not confirmation bias. That's signal. The UNIDO Global Cleantech Innovation Programme's acceleration guidebook treats this exact output — a quantified problem, a defined beachhead customer segment, and a minimum customer-required feature set — as the formal graduation criteria out of problem discovery. If you can't write those three things down in plain language after your interview round, you haven't finished the stage.

Stage 3: Selecting the Beachhead, Targeting the First $1 Million

This is where a lot of ClimateTech founders quietly overreach. They come out of discovery with five promising segments and try to serve all of them at once. Then they wonder why nothing converts.

The principle is older than the sector: dominate a beachhead before you expand. The UNIDO guidebook formalizes this by linking the initial beachhead segment to the company's likely first $1 million in revenue. That dollar figure isn't a universal industry benchmark — it's the planning threshold inside one specific acceleration framework — but as a planning exercise it forces a useful question: of all the segments you could pursue, which one is most likely to generate the first million in real, paid-for, contracted revenue?

A strong beachhead candidate tends to share a few traits. The buyer feels the pain sharply and recently. There's a regulatory or commercial trigger creating urgency. The buyer has budget authority and a procurement pathway you can actually navigate. The deployment unit is small enough to close quickly, but the underlying market is large enough to anchor a Series A story.

It helps to lay these side by side when you're choosing, because the tradeoffs become visible:

Once you've named your beachhead, your job isn't done. The UNIDO framework recommends validating adjacent customer segments, proposed pricing, and the total market opportunity after the beachhead has been identified. In other words, the beachhead is the proving ground, not the ceiling. You prove the beachhead first.

One more thing worth naming: the economic buyer is not always the sustainability team. Across B2B climate-tech sales, purchasing authority may sit with operations, procurement, finance, engineering, facilities, utilities, or a public-sector agency. If your beachhead candidate only has a sustainability champion and no identified budget holder, it's not yet a beachhead. It's a hope.

Stage 4: Navigating Non-Technical Adoption Risks

By this point, you've talked to enough buyers to know your problem statement holds. Now comes the work that often gets skipped: mapping the non-technical risks that determine whether your technology actually ships.

The DOE Adoption Readiness Level framework treats adoption as a multi-dimensional assessment. Five categories tend to trip founders up most often.

Regulatory and Permitting Risk

Even when the science is settled, the path through permitting, interconnection standards, or new chemical approvals may not be. A discovery conversation should ask directly: what approvals would your team need before deploying a solution like this, and how long do those approvals typically take?

Procurement and Contracting Risk

The Boston Emerging Climate Tech RFI summary from April 2025 highlighted cumbersome contracting and procurement processes as one of the recurring challenges reported by climate-tech stakeholders. A buyer can love your solution and still take 14 months to issue a PO. Build that delay into your timeline before you commit, not after.

Supply Chain and Manufacturing Risk

ARPA-E's commercialization milestones include supply-chain analysis and techno-economic analysis alongside customer engagement. A solution that requires a rare-earth input sourced from a single geopolitical region is not commercially robust, regardless of how elegant it is.

Organizational Risk

Every B2B buyer has internal politics. The person who champions your solution may not survive a reorg. The pilot site may lose its executive sponsor mid-deployment. Plan for continuity, not just initial enthusiasm.

Deployment Risk

How does your solution actually get installed, operated, and maintained? Does it require new training, new safety protocols, new integration with existing SCADA or ERP systems? Founders consistently underestimate the friction between "pilot approved" and "pilot running."

A discovery conversation that maps these risks early is worth more than ten that don't. The same RFI summary cited limited access to early-adoption pilot opportunities, insufficient funding for pilots, and regulatory complexity alongside procurement challenges. Translation: the friction is real, it's known, and the buyers you're talking to have already experienced it. Ask them about it. They'll tell you exactly where your roadmap needs to bend.

The customer doesn't buy your science. They buy the resolution to a problem they've been losing sleep over — and they buy it inside a procurement process that has to close cleanly.

Stage 5: From Pilot to Procurement

The last stage is where most ClimateTech capital quietly burns. You've secured a pilot. You're generating beautiful data. The buyer is sending enthusiastic emails. And then... silence. Or worse, a slow procurement conversation that ends in "not this year."

A pilot is not a contract. Treating it like one is the most expensive mistake a ClimateTech founder can make. The pilot is your opportunity to validate three things that interviews alone cannot: does the solution actually perform in the buyer's environment, can the buyer's organization operate it, and can the buying process close?

Three checkpoints tend to separate a healthy pilot from a stalled one.

1. Defined exit criteria at signing. What does "successful pilot" look like in measurable terms — energy saved, emissions reduced, hours of operator time removed, throughput gained? If you can't write it down before the pilot starts, you'll never know when you've earned the right to ask for a production contract.

2. A named internal champion with budget authority. A pilot led by an enthusiastic intern is not a commercial pipeline. Before you commit engineering resources, confirm who inside the buyer organization will advocate for the conversion, and whether that person controls or influences the budget.

3. A procurement conversation running in parallel. Don't wait for the pilot to end before you start talking to procurement, legal, and finance. ARPA-E's commercialization milestones explicitly include market-entry strategy alongside pilot execution for exactly this reason. The pilot produces the evidence; the procurement process converts that evidence into revenue.

One or two contracted pilot customers in the target segment is the validation milestone the UNIDO guidebook uses to mark the transition from beachhead exploration to commercial scaling. That milestone is meaningful, but it is a milestone — not the finish line. The conversion from pilot to recurring revenue is a separate, often longer, sales motion that deserves its own planning discipline.

When you reach this stage, the questions shift from "does this work?" to "does this work inside the buyer's actual organization, at the price we need, through the process they require, on a timeline that lets us grow?" Those are different questions. They deserve different conversations. And they require a founder who is willing to stay at the table after the science is no longer the most interesting thing in the room.

Your First Move This Week

Five stages, one project. The temptation, after reading a piece like this, is to file it under "someday" and get back to the lab. Don't. The lab will always be there. Your market window probably isn't.

Pick one move, today. Sit down with whatever customer notes you have — even if it's a stack of LinkedIn messages and a few remembered conversations — and try to write down three sentences: the quantified problem, the beachhead segment, and the minimum customer-required feature set. If you can write those three sentences clearly, you're ready for Stage 2. If you can't, you have your first discovery interview question: who can help me understand the buyer's pain precisely enough to write those sentences down?

That interview is your next move. Schedule it this week. The rest of the project unfolds from there.