Climate validation interviews: sustainability vs operations

The failure usually starts with the target persona. Sustainability teams may confirm that a decarbonization problem exists. Operations teams determine whether a solution can enter a plant, fleet, building, or production line without creating downtime, safety exposure, integration work, or budget friction.

These are not interchangeable interviews. They produce different data.

For climate startup customer discovery target personas, the core comparison is not sustainability versus operations as a matter of preference. It is a matter of system position. One function defines strategic relevance. The other often controls execution, risk, and access to money.

In 2024, UK climate tech investment reached £4.5 billion, up 24% year over year. UK AI climate tech investment reached £1.01 billion, up 128%. Capital is moving into the category. That raises the cost of weak validation. A startup that mistakes verbal support for purchasing power can scale its burn rate before it has established demand.

The user, the buyer, and the blocker are different variables

The first validation error is treating the organization as one customer.

It is not one customer. It is a buying system.

A software product for emissions reporting may be used by a sustainability manager, approved by IT, funded by finance, contracted by procurement, and defended by legal. A hardware product installed in a plant may be requested by sustainability, evaluated by engineering, operated by plant management, and rejected by finance if the payback period is unclear.

The user and the buyer are almost never the same person in climate tech.

The interview therefore needs to identify at least four roles:

1. User — the person who operates the product or changes a process.

2. Economic buyer — the person who controls the budget or can release it.

3. Risk owner — the person accountable if the intervention causes downtime, safety exposure, non-compliance, or operational failure.

4. Internal sponsor — the person who creates momentum and navigates the buying system.

A sustainability manager can be an effective sponsor without being the economic buyer. An operations director can have budget authority without being the person who discovered the problem. A procurement lead can block the deal without using the product.

That distinction changes the interview plan.

If the product changes a core operational process, interview operations early. If the product creates reporting, measurement, or disclosure outputs, interview sustainability early but do not stop there. If the product touches enterprise systems, add IT before interpreting positive feedback. If the product requires a new contract or vendor category, procurement is part of validation, not an administrative step after validation.

A sustainability interview can validate relevance. It cannot, by itself, validate throughput, budget, or purchase authority.

Sustainability interviews: strong signal, limited proof

Sustainability teams are often the correct entry point for problem discovery. They understand emissions targets, reporting pressure, internal climate commitments, and the language used by senior leadership. They can explain where the organization is underperforming against its targets.

They can also produce false positives.

The reason is structural. Sustainability professionals are expected to support decarbonization. When asked whether a solution could help reduce emissions, they may provide accurate strategic agreement without indicating a purchase decision. The interview reveals that the problem matters. It does not reveal whether the company will fund an intervention, accept operational risk, or change an existing workflow.

This is the query effect. The question itself can create a favorable answer. The respondent is not necessarily misleading the founder. The response is simply not a purchase signal.

A sustainability interview should therefore move through five parameters:

1. Current target

Which emissions, energy, waste, or resource target is active now. Do not accept a general commitment to net zero as the operating problem.

2. Accountability

Which function owns the result. If the sustainability team reports the target but operations owns the underlying activity, the product must be tested with operations.

3. Existing workflow

How the company currently measures, reduces, verifies, or reports the issue. A product that replaces a spreadsheet has a different adoption path from one that changes a production process.

4. Budget source

Whether funding exists in sustainability, operations, capital expenditure, IT, compliance, or another cost center. If the respondent cannot identify the budget path, demand is not yet qualified.

5. Trigger and timing

What event forces action. This may be a regulatory deadline, a customer requirement, an audit, an energy cost increase, a facility upgrade, or an internal investment cycle. Without a trigger, the problem may remain permanently important and commercially inactive.

The useful output is not a statement of support. It is a map of internal mechanics.

Ask for the last time the organization attempted to solve the problem. Ask what was purchased. Ask which team rejected or delayed it. Ask what data was required. Ask what the current process costs in time, money, exposure, or missed target progress.

Past behavior has higher validation value than future intent.

What sustainability teams can validate

Sustainability interviews are effective for:

• Defining the language of the problem inside the organization.
• Identifying target metrics and reporting obligations.
• Locating executive pressure and external commitments.
• Finding business units with visible emissions or resource gaps.
• Understanding how climate performance is presented to the board, customers, regulators, and investors.
• Identifying internal sponsors who can introduce the startup to operations, finance, or procurement.

They are weaker for:

• Confirming operational feasibility.
• Measuring downtime tolerance.
• Establishing training requirements.
• Proving integration access.
• Confirming the buyer’s budget authority.
• Setting a credible payback threshold.
• Establishing vendor qualification requirements.

The interview is valuable. The conclusion must stay narrow.

If the sustainability manager says the problem is material, the next action is a cross-functional interview. It is not a product build. It is not a sales forecast. It is not permission to increase headcount.

Operations interviews: lower enthusiasm, higher commercial signal

Operations leaders use a different decision function.

They evaluate whether the intervention affects uptime, output, safety, training, maintenance, staffing, quality, and existing equipment. They do not need the climate case to be morally persuasive. They need the operational case to be tolerable.

This often makes the interview less comfortable for founders. Operations may reject a solution that sustainability supports. The rejection is useful. It exposes the bottleneck before the startup spends engineering capacity on a deployment model the plant cannot absorb.

The correct question is not whether operations likes the product. The question is whether the product can enter the operating system with an acceptable risk profile.

For operations, the interview should establish:

• The process being changed.
• The baseline performance of that process.
• The current failure cost.
• The time available for installation or transition.
• The people who must be trained.
• The systems and equipment that must integrate.
• The conditions under which the intervention will be stopped.
• The operating metric that determines success.
• The person accountable for approving the change.

Avoid asking whether the company would use the product. Ask what happened during the last comparable change.

If a plant manager says the solution could reduce energy use, follow with operational questions. When can installation happen. Which line is available. What is the permitted downtime window. Who signs the method statement. What happens if the product fails during a production cycle. How is the result recorded. Which team owns the maintenance burden.

These questions reduce social desirability bias. They force the conversation into constraints.

Operations is not one persona

“Operations” is still too broad for a target market definition.

Depending on the product, the relevant interviewee may be:

• Plant manager.
• Head of engineering.
• Maintenance director.
• Energy manager.
• Facilities lead.
• Fleet manager.
• Chief operating officer.
• Site reliability or asset performance lead.
• Process owner for the affected production stage.

Each sees a different bottleneck.

A fleet manager may focus on vehicle availability and route performance. A plant engineer may focus on installation, controls, and maintenance. A COO may focus on multi-site rollout and capital allocation. A facilities lead may focus on building access, tenant disruption, and contractor coordination.

If the startup interviews only senior executives, it may obtain strategic approval without deployment data. If it interviews only technical operators, it may obtain a valid use case without a route to budget.

The target persona must be defined by the decision being made, not by the title that sounds most relevant to climate.

Side-by-side comparison

The table is not a substitute for segmentation. It is a routing mechanism.

If the sustainability interview produces a target but no budget, route to finance. If operations produces a deployment constraint but no urgency, route back to the business case. If both functions agree but procurement has no approved vendor path, the bottleneck is commercial infrastructure.

The buying system is the real customer discovery surface

Climate tech customer validation strategies often fail because they measure interest at the top of the funnel and ignore friction below it.

A buyer evaluates more than the climate outcome. The organization evaluates the total intervention.

The relevant functions are distinct:

• Operations evaluates downtime, staffing, training, maintenance, and output.
• IT evaluates integration, data access, security, architecture, and support.
• Procurement evaluates vendor qualification, contract structure, insurance, payment terms, and supplier risk.
• Finance evaluates payback, budget source, accounting treatment, and capital allocation.
• Legal evaluates liability, warranties, data rights, compliance, and contract exposure.
• Sustainability evaluates target alignment, measurement quality, and reporting value.

A product can pass one function and fail another. This is normal. The failure should be recorded as a system constraint, not treated as irrational resistance.

Build a function-to-risk map

After each interview, record the answer against five fields:

1. Claim — what the respondent says the product would improve.

2. Evidence — what existing data supports the claim.

3. Owner — who is accountable for the affected result.

4. Constraint — what can stop adoption.

5. Next commitment — what the respondent will do next.

The fifth field matters most.

A meeting, introduction, data export, site visit, paid assessment, or pilot scoping session is stronger than a positive opinion. The commitment should have an owner and a date. Do not convert every next step into a sales opportunity. Convert it into a measurable validation event.

For example:

• Sustainability provides the target methodology.
• Operations provides the process baseline.
• IT confirms the integration boundary.
• Finance identifies the budget route.
• Procurement lists supplier requirements.
• Legal identifies liability conditions.

If no function accepts the next action, the account has interest but no movement.

Problem discovery interviews need operational history

A climatetech problem discovery interview should not begin with a product description. Product-led questioning creates demand for the idea presented, not evidence of the underlying problem.

Use the sequence below.

1. Establish the last real incident

Ask when the problem last created a measurable cost, delay, compliance issue, missed target, or internal escalation.

If the respondent cannot identify a recent incident, the problem may be strategic rather than urgent. Strategic problems can still become markets, but they usually require a stronger trigger and longer sales throughput.

2. Reconstruct the current workaround

Ask what the team does today.

The workaround may be a spreadsheet, manual inspection, consultant engagement, equipment replacement, offset purchase, reporting process, or decision to tolerate the loss. The workaround reveals the competitive baseline. The startup is not competing only with other vendors. It is competing with inaction and internal labor.

3. Quantify the operational burden

Do not force false precision. Establish the unit that the organization already uses.

Possible units include:

• Hours of staff time.
• Production downtime.
• Energy consumption.
• Material loss.
• Number of site visits.
• Maintenance events.
• Compliance exposure.
• Capital expenditure.
• Missed customer or regulatory requirement.

The goal is not to produce an impressive climate number. It is to establish a baseline that the buyer recognizes.

4. Identify the decision gate

Ask what must be true for the organization to proceed.

The gate may be a payback period, safety review, integration approval, board decision, procurement qualification, grant condition, or site-level performance threshold. The gate defines the product requirement more accurately than a feature request.

5. Ask for access to the system

A serious validation process eventually requires access to data, workflow, equipment, users, or decision-makers.

If the respondent will share a baseline, introduce the implementation owner, or allow a scoped assessment, the signal is stronger. If the respondent will only offer opinions, keep the account in discovery.

This is where the b2b climate sales target buyer becomes visible. The buyer is the person who can convert a validated problem into an approved transaction, or who can stop that conversion.

Minimum viable test: four parts, one commercial boundary

A technical pilot is not automatically validation.

A pilot can prove that a product works under selected conditions. It does not prove that the organization will buy, renew, expand, or accept the operational burden.

A Minimum Viable Test, or MVT, should contain four elements:

1. Operational baseline

A defined measurement of the current process before intervention.

2. Intervention

The specific product, workflow change, installation, or service being tested.

3. Measurement metric

The result that determines whether the test produced value. This can involve emissions, energy, cost, downtime, output, maintenance, or another accepted unit.

4. Boundary

Exit criteria that define what happens after the test. The boundary must include commercial purchase options, not only technical success.

The fourth element is the missing component in many climate pilots.

Before starting, agree on the decision tree:

• If the intervention meets the operational threshold and the measured result supports the business case, the customer advances to a defined purchase or rollout discussion.
• If the intervention meets the climate target but creates unacceptable downtime or training burden, the product requires redesign.
• If the intervention works technically but no budget owner appears, the account is not commercially validated.
• If the baseline cannot be measured, the test cannot produce a defensible result.

A pilot without an exit criterion is a research project with a customer attached.

The MVT should also specify who owns measurement. If the startup owns all measurement, the result may be challenged later. If the customer owns all measurement, the test may never complete. Assign responsibility before deployment.

For hardware, include installation conditions, maintenance access, safety controls, and failure response. For software, include integration requirements, data permissions, user roles, security review, and workflow adoption. For services, include deliverables, internal labor, decision cadence, and the point at which the customer can operate without the provider.

A climate tech MVT should be small enough to run within existing operational capacity. If the test requires a new team, major capital approval, or a cross-enterprise transformation, it is not minimum viable.

What to do when sustainability says yes and operations says no

This is a common outcome. It is also one of the highest-value findings in discovery.

Do not average the responses. The functions are measuring different variables.

Sustainability has identified strategic value. Operations has identified execution risk. The product must address both or choose a narrower use case.

Use the disagreement to isolate the bottleneck:

1. If operations rejects downtime, redesign the deployment sequence, target a non-critical asset, or prove installation during an existing maintenance window.

2. If finance rejects the payback, reduce implementation cost, identify a different budget source, or change the value metric.

3. If IT rejects integration work, narrow the data requirement or provide a standalone workflow.

4. If procurement rejects vendor risk, prepare qualification material, insurance coverage, references, and contract terms.

5. If legal rejects liability, define operating responsibility, warranty limits, and failure procedures.

6. If sustainability cannot define the target metric, the use case is not ready for a climate claim.

The wrong response is to return to sustainability and collect more agreement. That increases confidence without increasing throughput.

A useful account is one where the objection has a named owner and a possible resolution path. An unusable account is one where every function agrees in principle and nobody commits to the next step.

Early adopters are defined by constraint, not enthusiasm

The first 50 customers in climate tech will not necessarily be the organizations with the strongest public climate language. They are more likely to be organizations where the problem has a live operational trigger and where a buyer can authorize a controlled test.

Look for four conditions:

• The organization has a measurable problem now.
• The problem has an owner outside the sustainability function.
• The organization has a path to fund or approve an intervention.
• The organization can run an MVT without blocking core operations.

A company with ambitious targets but no owner is a weak early adopter. A company with moderate public ambition, a visible cost problem, an accountable operations leader, and an open budget path may be stronger.

This is the distinction between market size and market access.

Market research sustainability work often overweights public commitments because they are easy to find. Procurement behavior is harder to observe. It requires interviews, document access, and direct evidence of prior purchases. The second source is more useful.

Track account progress using system variables rather than sentiment:

• Number of functions interviewed.
• Existence of a named operational baseline.
• Identified budget owner.
• Defined decision gate.
• Data access granted.
• Deployment window available.
• Procurement path known.
• MVT exit criteria agreed.
• Commercial next step accepted.

Do not assign a high probability to an account because a senior person is enthusiastic. Assign probability when the system has reduced uncertainty.

The interview sequence

The sequence should follow the buying system. Do not interview randomly.

Phase one: problem and target

Start with sustainability or the team that reports the climate problem. Establish the target, current workflow, internal language, and trigger.

Output: a defined problem statement and the first operational owner.

Phase two: execution

Interview the person who runs the affected process. Establish baseline, downtime tolerance, training burden, integration conditions, and failure risk.

Output: an operational constraint map.

Phase three: economics

Interview finance or the budget owner. Establish the budget source, payback requirement, cost classification, and approval path.

Output: a commercial threshold.

Phase four: deployment

Interview IT, procurement, legal, and the implementation owner as required by the product.

Output: a route from pilot to approved vendor and operating deployment.

Phase five: commitment

Return to the internal sponsor with a narrow MVT proposal. Include baseline, intervention, metric, boundary, owner, and timing.

Output: a paid test, a defined commercial evaluation, or a documented reason to stop.

If phase five cannot happen, do not label the account validated. Return to the bottleneck.

The final decision is binary

A climate startup does not need every interviewee to approve the product. It needs enough evidence to decide whether the account can move.

Use this final gate:

• Yes — the problem has a named owner, an operational baseline exists, the buyer or budget path is known, and the MVT has a commercial boundary.
• No — the account has enthusiasm but no baseline, no authority, no deployment path, or no decision after the test.
• Yes — sustainability confirms target relevance and operations accepts the intervention conditions.
• No — one function supports the concept while another carries unresolved risk.
• Yes — the next action transfers effort from the startup to the customer through data, access, approval, or payment.
• No — the next action is another conversation with no new evidence.

Sustainability interviews locate climate relevance. Operations interviews test whether the intervention can survive contact with the business. Finance, IT, procurement, and legal determine whether it can move through the buying system.

Treat the interviews as separate measurement instruments. Record the output. Find the bottleneck. Run the smallest test that can expose it.

That is climate validation. Not agreement. Not activity. A purchase path that remains intact when every function applies its own constraints.