Climate problem discovery: a 5-minute interview script

That question can feel paralyzing because climate markets are full of genuine need. Emissions must fall. Energy systems need to become more efficient. Supply chains need better data. Buildings, farms, factories, and transport operators all face environmental pressure. But a large climate problem is not automatically a buyable problem for your first customer.

A short, well-structured conversation can help us separate the two. This climatetech problem discovery interview script is designed for the first five minutes of a customer discovery call: enough time to understand the person’s role, locate the relevant workflow, and decide whether the conversation deserves to go deeper.

It is not a miniature pitch. It is not a survey. And it is not a test of whether someone likes your idea.

The aim is simpler: find out what happened the last time this person encountered the problem.

The cost of assumptions in climate markets

Climate founders often begin with an important observation:

• A factory is wasting energy.
• A fleet operator is under pressure to reduce fuel use.
• A food company cannot trace emissions across suppliers.
• A property owner needs to report building performance.
• A sustainability team has committed to a target it cannot yet measure.

These observations may be correct. The risk appears in the next step, when we quietly turn them into assumptions about buying behavior.

We assume the person who feels the pain owns the budget. We assume the company has already recognized the problem. We assume the environmental impact is enough to create urgency. We assume a better technical solution will fit into the existing workflow. We assume a stated climate target comes with operational authority to act.

Often, none of those assumptions holds.

A sustainability director may care deeply about emissions but lack control over procurement. An operations leader may own the budget but be measured on uptime, throughput, or cost rather than carbon reduction. A procurement team may want cleaner suppliers but be unable to accept a solution that adds another reporting process. A building owner may support efficiency improvements but delay action until a lease renewal, retrofit, or regulatory deadline creates a natural decision point.

This is why climate startup customer discovery needs to connect environmental impact with operational reality. We are not only asking whether the problem matters. We are asking how it appears in the customer’s work, what they do about it today, and what makes action possible.

Steve Blank introduced Customer Discovery in 2003 as part of the Customer Development methodology, with a clear purpose: prevent founders from building products before validating market demand. The principle still fits climate markets particularly well, because the path from climate benefit to customer purchase can include several stakeholders, budgets, incentives, and timelines.

One hour spent learning how that path works can save between five and twenty hours of wasted engineering and development effort. That is not a reason to avoid building. It is a reason to earn the right to build the next thing.

A climate problem becomes a market opportunity only when we can see how it enters someone’s workflow, budget, and decision process.

Start with the problem, not the product

Before the call, write down the assumption you are testing in one sentence.

For example:

Mid-sized manufacturers are losing money because they cannot identify which production lines drive avoidable energy waste, and plant managers are actively seeking a way to prioritize interventions.

That sentence contains several assumptions:

• the waste is visible enough to be noticed;
• the customer can connect it to financial loss;
• the plant manager is the right person to speak with;
• existing tools do not already solve the problem;
• the problem is active rather than merely desirable to fix;
• there is a reason to act now.

Your interview should help you inspect those assumptions one by one.

Do not begin by explaining your software, sensor, marketplace, dashboard, material, or model. The moment we introduce the product, the conversation changes. People become polite. They try to help. They respond to the idea we presented rather than describing the world they actually operate in.

For an early-stage climatetech problem discovery interview, the most useful material usually comes from four areas:

1. The person’s responsibility — what they own, measure, approve, or influence.

2. A recent real event — when the problem last appeared.

3. The current workaround — spreadsheets, consultants, internal teams, manual checks, delayed action, or doing nothing.

4. The consequence — cost, time, risk, compliance exposure, missed revenue, operational friction, or environmental impact.

The fifth area is often the most revealing: what they have already tried.

A customer who has never attempted to solve the problem may still care about it, but you need to understand why no action has occurred. A customer who has built an internal tool, hired an advisor, changed a supplier, or approved a pilot has already demonstrated stronger behavioral evidence.

The 80/20 rule for discovery conversations

In a useful discovery call, the interviewee should speak for roughly 70% to 80% of the time. That ratio is not a performance target you need to enforce with a stopwatch. It is a reminder that your job is to create room for evidence.

Founders often talk too much for understandable reasons. We know the science. We can see the solution clearly. We want to provide context so the other person gives an informed answer.

But the more context we provide, the more likely we are to receive a response to our framing rather than an account of the customer’s reality.

A strong interviewer uses short questions and longer pauses. You do not need to fill every silence. A pause often gives the other person time to move beyond the polished explanation and remember what actually happened.

A helpful rhythm looks like this:

• Ask about the person’s role.
• Ask for a recent example.
• Stay with the example.
• Ask what happened next.
• Follow the trail to time, money, ownership, and decisions.
• Only then explore whether the problem is recurring.

The phrase recent example matters. Compare these two questions:

• How does your company manage supplier emissions?
• Tell me about the last time your team needed supplier emissions data for a decision.

The first invites a general description. The second asks the interviewee to retrieve a real event. You may hear about a reporting deadline, an Excel file assembled by three teams, missing supplier information, an external consultant, or a decision that was postponed because the data was not ready.

That is the kind of detail we can build around.

A simple listening map

As you listen, capture notes under five headings:

This map keeps a climate conversation from drifting into broad opinions about sustainability. It brings us back to behavior.

The five-minute climate problem discovery script

The script below is intentionally short. It is an opening sequence, not a complete interview. If the person gives a useful answer, follow it rather than rushing to the next question.

You can adapt the words to your market, but keep the underlying order.

Minute one: establish context

“To start, could you briefly describe your role and the part of the business you’re responsible for?”

Listen for the connection between the person and the problem you are studying. Are they accountable for energy cost, emissions reporting, fleet operations, procurement, maintenance, compliance, or something else?

Then ask:

“How does this issue show up in your work today?”

This is deliberately broad, but it keeps the question grounded in their role. You are looking for their language. They may not use your preferred category label, such as decarbonization, carbon accounting, or climate risk. Their words may be more operational: delayed maintenance, unreliable data, high peak demand, supplier pressure, audit preparation, or missed project deadlines.

Do not correct their terminology. Their language will later help you improve your positioning and your interview questions.

Minute two: locate a recent event

“Can you walk me through the last time your team had to deal with this?”

If the response remains general, gently narrow it:

“When was that?”

“What triggered it?”

“Who became involved?”

“What did you do first?”

A recent event gives us sequence. Sequence reveals ownership.

For example, a company may say that it struggles with carbon data. A recent-event conversation might show that the finance team requests the data once a year, the sustainability team gathers it manually, suppliers respond inconsistently, and the final report is approved by legal. That is a very different product opportunity from a simple assumption that the company needs a better carbon dashboard.

The goal is not to make the problem sound worse. The goal is to see its actual shape.

Minute three: understand the current workaround

“How are you handling that today?”

This is one of the most important questions in b2b climate interview questions because customers already have a way of surviving most problems. The workaround may be poor, expensive, or frustrating, but it is still your competitor.

Ask:

“What tools, people, or processes are involved?”

“What part takes the most time?”

“What tends to go wrong?”

“Have you tried changing this process before?”

A workaround can tell us how much urgency exists. If a team has assigned two people to maintain a manual process every month, paid for outside analysis, or created a temporary internal system, we have evidence that the problem has moved beyond abstract concern.

If the workaround is simply to ignore the issue until the next reporting cycle, that is also useful evidence. It may mean the problem is not urgent, the buyer is elsewhere, the consequences are unclear, or the company lacks a triggering event.

None of these answers is a failure. They are signals that help us navigate toward a better customer segment.

Minute four: explore consequences

“What happens when this is not solved well?”

Avoid supplying the answer. Do not list cost savings, emissions reductions, compliance benefits, or revenue opportunities and ask which one matters. Let the interviewee identify the consequence first.

Follow with:

“Who feels that consequence most directly?”

“How does the team measure it?”

“What does it delay, increase, or put at risk?”

In climate markets, the environmental consequence and the business consequence may sit in different places. A missed emissions target may affect the sustainability team, while the cost of inefficient equipment affects operations. A supplier-data gap may create reporting risk for one team and procurement friction for another.

This separation matters when we later identify the buyer, champion, user, and economic decision-maker.

You are also listening for specificity. “It makes reporting harder” is a starting point. “We need three weeks of manual reconciliation before an audit” gives us a workflow, a time burden, and a clear moment when the problem matters.

Minute five: test existing commitment

“What have you already tried?”

Then:

“Have you spent money, changed a process, run a pilot, or assigned someone to address it?”

This is a better early indicator than enthusiasm. Someone may say your proposed solution sounds useful, but past action tells us whether the problem has earned attention inside the organization.

If they have tried something, ask:

“What worked, and what did not?”

“Why did you stop or continue?”

“What would need to happen for you to try another approach?”

That final question should still focus on behavior and process, not a hypothetical purchase promise. You are learning about the conditions for action: a budget cycle, a regulatory requirement, a customer request, a measurable payback, a technical integration, or executive sponsorship.

At the end of five minutes, you may know enough to decide whether to continue. If the problem is real and the person has relevant experience, keep exploring. If the conversation reveals a different problem, follow it. If there is no recent example, no workaround, and no consequence, do not force the interview toward your original idea.

Questions that create evidence, and questions that create compliments

The most dangerous response in customer discovery is often a kind one.

People want to encourage founders. They may say the concept is interesting, the mission is important, or the solution sounds promising. Those reactions are pleasant but weak. They do not tell us whether anyone will change behavior.

The difference usually comes down to the time orientation of the question.

Hypothetical questions are not useless forever. They can become relevant after we understand the current workflow and have evidence of a real problem. But they should not carry the weight of validation at the beginning.

If someone says they would buy, ask what happened the last time they bought something similar. If they say the company would pay, ask which budget paid for the current workaround. If they say the product would be valuable, ask what decision it would change.

That move brings the conversation back to observable behavior.

Enthusiasm tells us that an idea is easy to imagine. Past action tells us whether the problem is strong enough to change a workflow.

Climate-specific signals hidden inside ordinary answers

Climate discovery is not just traditional B2B discovery with the word carbon added. Environmental outcomes introduce specific forms of complexity that we need to make visible.

The person who owns the impact may not own the purchase

A sustainability team may define the target, but operations may control implementation. Procurement may negotiate the contract, finance may approve the budget, and IT may decide whether integration is possible.

Ask:

• Who is responsible for the outcome?
• Who controls the process that must change?
• Who pays for the current workaround?
• Who needs to approve a new approach?
• Who would be blamed if the project failed?

These questions help us map the buying environment without turning the call into an org-chart exercise.

Climate urgency often arrives through another door

The customer may not describe the trigger as climate action. It may appear as:

• a major customer asking for emissions data;
• a tender requiring environmental reporting;
• a new disclosure obligation;
• an energy price increase;
• an equipment replacement decision;
• a supply-chain risk review;
• an internal capital-allocation target;
• a physical-risk event;
• an investor or board request.

If we only ask whether the company wants to reduce emissions, we may miss the actual moment that creates a budget and a deadline.

Impact needs a clear chain

Climate investors and customers increasingly want to understand how a product connects to real environmental outcomes. Lowercarbon Capital, which manages more than $1.1 billion in assets, explicitly evaluates how proposed solutions affect greenhouse gas concentrations in the atmosphere.

That does not mean every discovery call needs a full lifecycle assessment. It does mean we should avoid vague impact language.

Ask:

• What environmental outcome are you trying to change?
• How do you measure it today?
• Which activity produces the relevant emissions or resource use?
• What decision would change if the measurement were available?
• What prevents the organization from acting on the information?

The answers help us distinguish between a product that creates a report and a product that enables a meaningful intervention.

Turning five minutes into a real interview

A five-minute opening can become a twenty- or thirty-minute conversation when the interviewee gives you something concrete. The key is to follow depth rather than cover every question.

Use prompts such as:

• “What happened after that?”
• “Can you give me an example?”
• “How often does that occur?”
• “Who else was involved?”
• “What did that require from your team?”
• “What happened when the process failed?”
• “How did you decide what to do next?”
• “What did you compare it with?”
• “Why did you choose that workaround?”

These are not clever questions. That is their strength. They help us stay close to the customer’s experience instead of performing expertise.

Take notes using the customer’s own terms. If several people describe a “reporting scramble,” do not immediately translate it into “automated carbon intelligence.” The repeated phrase may contain a better understanding of the problem and a more credible starting point for a minimum viable test.

A useful note has this shape:

• Situation: A customer request arrives two weeks before a tender deadline.
• Current process: Sustainability gathers supplier data manually from procurement and finance.
• Pain: Several suppliers use incompatible formats, so the team cannot reconcile the numbers quickly.
• Consequence: The company delays the submission or submits with estimates.
• Existing commitment: The team has already paid for outside help during the previous reporting cycle.
• Open question: Is the main buyer sustainability, procurement, or the commercial team responsible for the tender?

This is much more valuable than a note saying, “Companies need better emissions data.”

How many interviews are enough to see a pattern?

One conversation can reveal a lead. It cannot establish a segment.

For each specific target customer segment, aim to complete between five and ten interviews before drawing firm conclusions. The phrase specific target segment is doing important work here. “Climate companies” is not a segment. Neither is “large businesses interested in sustainability.”

A segment might be:

• operations leaders at regional logistics companies managing diesel fleet transitions;
• sustainability managers at food manufacturers responding to retailer emissions requests;
• facilities leaders at multi-site commercial property groups planning energy retrofits;
• procurement teams at manufacturers that must collect supplier-level environmental data.

The narrower segment helps us compare like with like. Otherwise, every difference can be explained away by industry, company size, regulation, budget, or role.

After each call, record:

• the exact problem described;
• when it last occurred;
• the trigger;
• the current workaround;
• the people involved;
• the consequence;
• any existing spend or internal effort;
• the customer’s next decision point;
• your confidence level in the evidence.

Do not count positive comments as validation. Look for repeated behavior:

• several people describe the same recent trigger;
• the same workaround appears across organizations;
• the problem is owned by a recognizable role;
• the consequence is meaningful enough to create action;
• customers have already spent money or time;
• the timing of the problem is predictable;
• interviewees can identify what would need to change.

You may also find that the strongest early adopters are not the customers with the biggest stated climate ambitions. They may be the organizations already experiencing a painful operational event connected to climate pressure.

For targeted cold LinkedIn outreach, a response rate in the range of 15% to 25% can be a reasonable working expectation, although it will vary by audience, message, relationship, and timing. Keep the invitation focused on learning from their experience, not presenting a product. A short request for a conversation about a specific workflow is easier to evaluate than a broad invitation to discuss the future of sustainability.

Reading the pattern without forcing it

Once you have several interviews, resist the urge to average everything into a single customer persona. Climate markets often contain several adjacent problems that look similar from a distance.

Suppose you speak with ten companies about industrial energy efficiency. You may find three distinct patterns:

1. Plant managers need rapid diagnosis during production disruptions.

2. Finance leaders need reliable data before approving capital projects.

3. Sustainability teams need evidence for customer and regulatory reporting.

All three relate to energy and emissions. They do not necessarily share a buyer, a trigger, a product, or a sales motion.

This is where alignment matters. We are looking for the combination of:

• a recurring problem;
• a reachable customer;
• a clear trigger;
• an existing workaround;
• a measurable consequence;
• a plausible path to purchase;
• a credible connection to climate impact.

If one piece is missing, we do not need to abandon the idea. We may need to narrow the segment, change the entry point, or separate the user from the buyer.

A minimum viable test could then be very small. Instead of building a complete platform, we might offer a structured audit, a manual analysis, a workflow prototype, or a narrowly scoped pilot around one decision. The test should expose whether the customer will give access, time, data, budget, or operational commitment.

That is stronger than asking whether they like the concept.

A ready-to-use version of the script

You can keep this version beside you during a call:

1. “Could you briefly describe your role and the part of the business you’re responsible for?”

2. “How does [problem area] show up in your work today?”

3. “Can you walk me through the last time your team had to deal with it?”

4. “What triggered it, and who became involved?”

5. “How are you handling that today?”

6. “What tools, people, or processes are involved?”

7. “What happens when it is not solved well?”

8. “What have you already tried, changed, or paid for?”

9. “What would need to happen for you to try another approach?”

You will not always ask all nine. The best calls rarely sound like a questionnaire. Let the answers determine the next question.

The five-minute structure simply gives us a reliable way to begin: role, recent event, current behavior, consequence, commitment.

The next step after the call

Within a few minutes of ending each conversation, write down what you learned before the details blur together. Separate evidence from interpretation.

For example:

• Evidence: The interviewee described a supplier-data request from last quarter.
• Evidence: Three people spent several days reconciling spreadsheets.
• Evidence: The company hired a consultant for the previous reporting cycle.
• Interpretation: A workflow product may have value.
• Still unknown: Whether procurement or sustainability owns the budget.
• Next test: Interview the person who approved the consultant and compare the process.

That last line keeps discovery moving. Every interview should leave you with a sharper question, not just a warmer feeling about the idea.

You do not need a perfect script, a large research budget, or a finished product to start. You need a specific customer segment, a recent problem, and enough discipline to listen before explaining.

Begin with five conversations. Ask about what happened, not what might happen. Follow the workaround. Notice who acts, who pays, and what creates urgency. Then let the pattern—not the pitch—decide what you build next.