Climate startup LOI campaigns: a validation blueprint

That assumption is convenient—and mostly useless for industrial ClimateTech.

A landing page can test whether a message attracts attention. It cannot tell you whether a factory can provide site access, whether engineering will approve the installation, whether safety will require a HAZOP or Management of Change review, or whether procurement will allow a new supplier into the system. A conversion is not a deployment. It is barely an invitation to start asking harder questions.

For founders working on hardware, industrial software, energy systems, carbon management, building technology, or operational decarbonization, ClimateTech B2B customer validation through an LOI is a more demanding exercise. A non-binding Letter of Intent does not guarantee revenue, and it does not force a company to buy. Its value is different: it exposes the conditions under which a pilot could actually happen.

That is the reality check. Your market does not validate the idea when people like it. It validates the idea when a real organization is willing to help you navigate the friction between interest and implementation.

Why landing pages fail for industrial ClimateTech

Landing pages are not worthless. They are simply asked to answer questions they cannot answer.

A page can help test:

• whether a specific problem statement resonates with a defined audience;
• which use case attracts the most qualified visitors;
• whether prospects understand the proposed value without a long explanation;
• which language creates enough interest for a follow-up conversation.

That is useful for message testing. It is not sufficient for deployment validation.

Industrial and enterprise ClimateTech products operate inside environments that are already full of constraints. A solution may need access to a production site, integration with existing equipment, approval from facilities, a safety review, union consultation, cybersecurity clearance, insurance documentation, and a procurement process that was designed to avoid experimental suppliers.

None of those constraints appear in a form submission.

The founder may collect 200 email addresses and still have no answer to the questions that determine whether the product can be installed:

1. Who controls access to the relevant site or asset?

2. Which team owns the operational problem?

3. Who carries the risk if the pilot disrupts production?

4. What technical evidence does engineering require?

5. Which safety process applies before installation?

6. Does procurement require an approved-vendor process?

7. What budget can legally be used for a pilot?

8. What result would justify expansion?

If the answers are missing, the funnel is measuring curiosity. Curiosity is cheap. Corporate implementation is not.

This is particularly dangerous in ClimateTech because the apparent buyer and the economic buyer are often different people. A sustainability leader may support an emissions-reduction initiative, while operations controls the site, engineering controls technical approval, finance controls the business case, and procurement controls the supplier relationship. The person who enthusiastically accepts a meeting may have no authority to approve the pilot.

The landing page does not reveal that organizational map. Interviews and operational commitments do.

A landing page measures attention. An LOI tests whether the organization will help you survive its internal process.

Map the decision before you ask for the pilot

The first mistake in B2B climate sales validation is treating the customer as a single person. In practice, the customer is a system of gatekeepers with different incentives and different definitions of risk.

A useful discovery process starts by mapping the decision-making matrix for one specific deployment scenario—not for an abstract market such as “large manufacturers” or “commercial real estate.”

For each target account, identify the people connected to five areas:

This is not a bureaucratic exercise. It is a way to find the actual source of friction before you promise a pilot date.

Suppose a startup offers an energy-management system for a multi-site industrial business. The sustainability team may be interested because the product could improve emissions reporting. Operations may object if the system requires downtime. IT may reject the connection because the device sits on a restricted network. Procurement may require a third-party supplier assessment. Finance may ask whether savings can be measured against a changing production schedule.

A founder who validates only with sustainability has validated the easiest conversation.

The better question is not, “Does the customer want this?” It is, “What must be true inside this customer for this to be deployed?”

That distinction changes the interview. Instead of asking for general reactions, ask about the last comparable project:

• How was it approved?
• Which team raised the first objection?
• What documentation was required?
• How long did vendor onboarding take?
• Who signed the pilot agreement?
• What prevented the project from moving faster?
• Which metric was accepted as evidence of success?

These questions reveal past behavior. Past behavior is usually more useful than enthusiasm about a hypothetical future.

Choose one beachhead, not a vague category

Climate founders often describe a market in terms of industries: logistics, manufacturing, agriculture, buildings, utilities. That is too broad for validation.

A beachhead should be narrow enough that the deployment conditions are recognizably similar across accounts. For example:

• cold-storage facilities with high refrigeration loads;
• municipal buildings with centralized HVAC controls;
• food-processing sites with predictable thermal demand;
• fleet operators with depot-based charging constraints;
• mid-sized manufacturers with a defined waste-heat stream.

The point is not to make the market look smaller. The point is to make patterns visible.

If every prospect has different infrastructure, approval rules, operating schedules, and economic logic, the startup is not learning one market. It is conducting a collection of unrelated sales conversations and calling the resulting confusion segmentation.

The UNIDO framework treats one or two contracted pilot customers in the target segment as a transition from beachhead exploration toward commercial scaling. That milestone is useful because it forces a concrete distinction: a target segment is not validated by a list of interested companies. It begins to earn credibility when real customers accept the conditions of a pilot.

The 30-interview threshold is about patterns, not a badge

Thirty structured customer discovery interviews is a practical threshold for reducing anecdotal bias. It is not a magical number, and it does not turn weak questions into research. If the interviews are scattered across unrelated buyer types, the total is decorative.

The goal is to identify repeated operational behavior.

A structured interview should capture more than a prospect’s opinion about the product. Record the current workflow, the cost of inaction, the existing workaround, the internal approval path, and the evidence required to change it.

A useful interview record includes:

• the exact operational problem and where it occurs;
• how often the problem appears;
• who notices it first;
• what the company does today;
• what the current solution costs in money, time, risk, or emissions;
• what has already been tried;
• which team owns the relevant budget;
• what would block a pilot;
• which result would count as success;
• the next action the prospect is willing to take.

Do not turn this into a performance where every answer is interpreted as support. A prospect saying that the problem is “interesting” is not evidence of urgency. A prospect agreeing that decarbonization matters is not evidence of a funded buying process. A referral to another colleague is not necessarily momentum—it may simply be a polite way to transfer the conversation elsewhere.

The evidence becomes stronger when the prospect describes a recent comparable purchase, names the internal owner, explains the approval path, and agrees to a specific next step.

Separate stated pain from paid pain

A common interview failure is asking questions that make agreement effortless:

• Would you use a tool that reduces emissions?
• Would better energy data be valuable?
• Would you be interested in a pilot?
• How important is sustainability to your organization?

Most corporate respondents can answer yes without making any commitment. The questions are socially easy and commercially weak.

A stronger line of inquiry asks what the company has already done:

1. What triggered the current project?

2. What budget was used?

3. Which alternative was rejected?

4. What caused the last delay?

5. Who had to approve the decision?

6. What evidence was missing?

7. What would have to happen for the organization to repeat the investment?

This approach creates productive discomfort. That is the point. Customer discovery is not a search for compliments; it is an attempt to discover the conditions that can kill the sale.

You should also compare responses by role. If operations describes a high-priority issue but finance has no budget and procurement cannot onboard the supplier, the opportunity is not yet validated. If several buyers in the same segment describe the same trigger, same workflow, and same approval barrier, you have a pattern worth testing.

The first 50 customers should generally be closed through founder-led sales. That does not mean the founder must remain the salesperson forever. It means the company should not outsource the learning before it understands the objections, internal politics, and language that determine adoption.

A sales team can scale a repeatable motion. It cannot manufacture one from a founder’s assumptions.

Turn the LOI into an operational experiment

A climate startup Letter of Intent is often treated as a ceremonial document: both parties sign, everyone feels encouraged, and the founder adds a logo to a pitch deck. That is the least useful version.

A strong non-binding LOI is a structured product experiment. It defines what the customer is willing to explore, under which conditions, with which success criteria, and what happens next if the pilot works.

The document should be specific enough to create friction. If it is so vague that nobody needs to involve procurement, engineering, or site management, it has not tested the buying process.

At minimum, an LOI for a ClimateTech pilot should clarify:

• the customer entity and target site;
• the operational problem being addressed;
• the proposed pilot scope;
• the expected installation or integration requirements;
• access responsibilities;
• the customer and startup points of contact;
• the required safety, security, and compliance reviews;
• the data that will be shared;
• data ownership and confidentiality expectations;
• the pilot start conditions;
• the duration or completion condition;
• the agreed success metrics;
• the process for reviewing results;
• any commercial discussion that may follow;
• the fact that the LOI is non-binding except for provisions explicitly stated as binding.

The language must remain accurate. A non-binding LOI does not guarantee revenue. It does not oblige the company to purchase the product after the pilot. It does not prove product-market fit. What it can demonstrate is narrower and more valuable: a buyer is willing to allocate organizational attention to a defined test.

That is a meaningful step because attention inside a large organization has a cost.

Define success before the equipment arrives

A pilot without agreed success criteria is a demonstration, not validation.

For a software product, success might involve data coverage, workflow adoption, forecasting accuracy, or a measurable reduction in manual work. For hardware, it may involve installation time, uptime, safety performance, output quality, or compatibility with existing equipment. For an energy or emissions solution, the parties may need to agree on a baseline, measurement method, operating conditions, and acceptable variance.

The metric must be connected to the buyer’s decision—not merely to the startup’s preferred dashboard.

A sustainability team may care about emissions reductions, while operations cares about production continuity and finance cares about total cost. If the LOI includes only an emissions metric, the founder may complete a technically successful pilot that nobody is prepared to buy.

A better pilot scorecard contains three layers:

1. Technical result — did the product work under the defined operating conditions?

2. Operational result — did it fit into the customer’s workflow without unacceptable disruption?

3. Commercial result — did the outcome justify a next-stage purchase, expansion, or contract?

The parties should also specify what would invalidate the result. If performance depends on a narrow temperature range, a particular load profile, or uninterrupted data access, those conditions belong in the document. Hidden dependencies create disputes later and encourage both sides to reinterpret the pilot.

Use the LOI to expose deployment friction

The most valuable information in an LOI campaign may come from what the customer refuses to sign.

A prospect may accept the use case but reject the proposed site because access is restricted. Another may agree to a pilot but require a lengthy vendor review. A third may want the product installed only during a maintenance shutdown. A fourth may have a labor agreement that affects who can operate or service the equipment.

These are not administrative details. They are product requirements.

Track each objection by category:

• site access;
• technical integration;
• safety review;
• cybersecurity;
• insurance and liability;
• union or workforce requirements;
• procurement onboarding;
• data sharing;
• budget ownership;
• pilot timing;
• expansion authority.

Then look for repetition across accounts. If every prospect requires a different installation process, the startup may need a services model, a channel partner, or a narrower use case. If safety documentation blocks every pilot, the company has a product-readiness problem—not a lead-generation problem.

The best LOI campaign does not collect signatures. It reveals the exact conditions that stand between a signed document and a usable pilot.

Build the campaign around evidence, not logos

Founders naturally want recognizable companies on a slide. Logos create a reassuring visual shortcut, especially in fundraising. But a logo without a deployment path is a piece of decoration.

An LOI campaign should be managed as an evidence pipeline. Each prospect should move through observable stages:

• problem confirmed by the operational owner;
• use case matched to a specific site or asset;
• decision-making group mapped;
• deployment constraints documented;
• success metrics agreed;
• internal sponsor identified;
• procurement and safety pathway understood;
• LOI reviewed by the relevant stakeholders;
• pilot conditions accepted;
• contracted pilot executed.

The progression matters because a prospect can move backward. A sustainability sponsor may support the project until engineering reviews the integration requirements. A procurement team may approve the supplier while finance rejects the budget. A site manager may agree in principle but have no available installation window.

Do not hide these reversals. They are market information.

A simple internal evidence table can keep the team honest:

This structure prevents a familiar form of founder bias: treating every positive conversation as progress while ignoring the missing step that actually determines conversion.

Do not confuse a champion with a buyer

A champion is useful, but a champion is not the whole account.

The champion helps the project move through the organization. They explain the internal context, introduce decision-makers, and protect the initiative when priorities shift. But the champion may not control budget, site access, technical approval, or procurement.

During discovery, ask the champion what they can personally approve and what requires another team. The question is direct by design. If the answer is unclear, the pilot is not ready for an LOI—or the LOI must include the missing stakeholders.

Founders often avoid this because they fear slowing down the deal. That is backwards. The hidden stakeholder will slow it down later, after the startup has spent time customizing the product and preparing a proposal.

The goal is not to create a large committee for every conversation. The goal is to identify the smallest group that can make the pilot real.

Procurement is part of the product

Corporate procurement is often treated as a late-stage obstacle, as if the startup first needs to prove demand and only then deal with supplier requirements. In ClimateTech, procurement can shape the offer from the beginning.

Large B2B buyers increasingly use third-party supplier scorecards, including EcoVadis, which scores suppliers from 0 to 100 across four themes, and climate disclosures associated with CDP. A startup that cannot answer basic questions about environmental management, labor practices, governance, emissions, data security, insurance, or supply-chain risk may be screened out before the product is evaluated on its technical merits.

This does not mean a young company must imitate a multinational’s compliance department. It means the founder should understand the buyer’s minimum supplier threshold before promising a deployment.

Ask procurement:

• Is there an approved-vendor process?
• Which documents are required before a pilot?
• Are insurance limits specified?
• Does the customer require security or privacy assessments?
• Are sustainability scorecards used in supplier selection?
• Can a pilot be purchased through an existing partner?
• What contract terms typically create delays?
• Who has authority to approve a non-standard supplier?

The answers may change the go-to-market model. A startup could discover that selling directly to each enterprise creates too much onboarding friction, while partnering with an established engineering contractor or energy-service provider makes deployment viable. Or it may discover that the product needs a more complete documentation package before serious buyers will engage.

That is not a failure of sales. It is a finding about the market’s buying infrastructure.

Safety and site access belong in early discovery

Industrial ClimateTech founders sometimes defer safety questions because they believe the product is too small or temporary to require serious review. The customer may disagree—and the customer’s safety team gets the final vote.

Depending on the deployment, the company may need to address hazard analysis, Management of Change, electrical or mechanical safety, worker training, emergency procedures, and maintenance responsibilities. Site access can be equally decisive. A pilot that requires installation on a restricted asset is not feasible simply because the operations manager likes the concept.

The LOI should therefore identify the deployment prerequisites rather than bury them in a later statement of work. A pilot is not ready if nobody knows:

• where the system will be installed;
• who can authorize access;
• who performs the installation;
• what shutdown or maintenance window is available;
• who is responsible for operation and service;
• what happens if the system affects production;
• which safety review must be completed first.

The earlier these conditions appear, the less likely the startup is to build a sales pipeline full of impossible pilots.

What a credible validation campaign should produce

At the end of the campaign, the founder should have more than signed documents. They should have a clearer picture of the market’s operating reality.

A credible result includes:

1. A defined beachhead segment with comparable sites, workflows, and buying conditions.

2. At least 30 structured interviews from relevant roles—not a random collection of interested contacts.

3. A decision map showing operations, engineering, finance, procurement, facilities, utilities, and sustainability responsibilities.

4. A recurring problem pattern supported by observed behavior and existing spending or effort.

5. A deployment specification covering site access, integration, safety, data, and staffing.

6. A pilot scorecard accepted by the customer before the test begins.

7. Non-binding LOIs that describe real engagement conditions rather than vague enthusiasm.

8. One or two contracted pilot customers in the target segment, consistent with the UNIDO beachhead validation milestone.

9. A record of rejection reasons that informs product scope and sales strategy.

10. A decision about the next constraint—whether the company needs better product readiness, stronger documentation, a channel partner, or a different segment.

Notice what is missing: a large email list, a high landing-page conversion rate, and a collection of flattering quotes. Those assets may help with awareness. They do not resolve the operational questions that decide whether a climate solution reaches a site and survives contact with a procurement department.

The founder’s final reality check

An LOI campaign is not a softer version of selling. It is a more honest version of discovery.

The process will force uncomfortable distinctions. A sustainability contact may be an advocate but not a buyer. A technically impressive product may fail a site-access requirement. A promising pilot may have no budget owner. A customer may support the climate goal while rejecting the integration burden. A corporate logo may sit on the first page of the document while procurement quietly prevents the project from moving.

Good validation does not remove these frictions by optimism. It makes them visible early enough to do something about them.

Use the landing page to test the message. Use structured interviews to test the problem. Use the decision map to test the buying process. Use the LOI to test whether the organization will commit people, access, information, and internal coordination to a defined experiment.

Then take the result into the real world. Ask the customer to name the site, the owner, the approval path, the success metric, and the next commercial decision. If those answers remain vague after the conversation, the market has not rejected you—but it has not validated you either.