Climate-tech procurement cycles — why your B2B sale takes 18 months

Climate-tech founders selling to enterprise customers consistently underestimate procurement cycle length. The deal that "should close next quarter" closes 18 months later, or doesn't close at all. Understanding why — and what compresses the cycle — separates the climate-tech founders who hit their sales targets from those who repeatedly miss.

Why climate-tech cycles are unusually long

• Multi-stakeholder decisions. Climate procurement touches sustainability teams, operations, finance, sometimes board. Each is a separate buy-in. Each has their own concerns: sustainability cares about emissions math; ops cares about workflow disruption; finance cares about ROI; board cares about strategic positioning.
• Capex framing. Most climate-tech sales involve capital expenditure (or contracts that look capex-like). Capex approval cycles are slower than opex.
• Verification requirements. "Does it actually deliver the claimed carbon reduction?" The buyer needs to verify in pilot. Pilot takes 3-6 months. Post-pilot deliberation takes another 3.
• Budget cycles. Even if everyone agrees, the budget may sit in next fiscal year. Most climate-tech deals close in Q1 or Q4 of the customer's fiscal year, regardless of when the pitch lands.
• External requirements. ESG reporting requirements (SBTi, CDP, regulatory mandates) drive purchasing. Customers wait until their reporting deadline forces them to act.

The realistic stages of a climate-tech enterprise deal

Stage 1 — Awareness (1-3 months). You've made contact, they've expressed interest. Conversations are happening. No commitment yet.

Stage 2 — Champion development (2-4 months). One person at the customer is championing your solution internally. They're presenting to colleagues, gathering technical questions, asking you to respond to them.

Stage 3 — Technical evaluation (2-4 months). Pilots, proof-of-concept, technical review. The customer's engineering or science team is validating the claims.

Stage 4 — Procurement (3-6 months). Once the technical evaluation is positive, the deal moves to procurement. RFI, RFP, vendor onboarding, legal review, MSA negotiation, security review. This is where deals stall most.

Stage 5 — Budget alignment (timing-dependent). The deal is approved but the budget sits in next fiscal year. Often 3-9 months of waiting.

Stage 6 — Close + onboarding (1-2 months). Signature, kickoff, deployment. Anti-climactic after the previous 12-18 months.

Total: 12-18 months for most climate-tech enterprise deals. Some close faster; some take 24+ months.

What compresses the cycle

• Strong internal champion who can navigate the org. This is the single biggest variable. Found a champion who can navigate procurement faster? You're at 9-12 months. No champion? You're at 24+.
• Established reference customer in their industry. A peer who's already deployed dramatically accelerates technical evaluation. "Company X is using this" beats any deck.
• Pilot programme with defined success criteria. Joint planning of "if we hit these metrics in 90 days, we go to full deployment" pre-aligns expectations. Removes the "let's keep evaluating" trap.
• Procurement-friendly contract terms. MSAs already aligned with the customer's standard terms, security questionnaires answered preemptively, DPAs ready. Procurement is rejection-by-default; preemptive answers move it forward.
• Aligning to their fiscal year. Position deals to land Q1 budgets (US), April UK, July JP, etc. Forcing a Q3 close in a customer's slow quarter doesn't accelerate it.

What lengthens the cycle (avoid these)

• Selling to the wrong stakeholder first. Going through sustainability when finance has to approve the cheque means you've added a stakeholder rather than removed one.
• Pilot scope creep. Pilots that expand beyond original scope take 2-3x as long without producing better proof.
• Custom contract terms. Every redline at every customer creates a 4-12-week delay. Standardised contracts that 80% of customers accept beats bespoke contracts.
• Disappearing during evaluation. The customer's enthusiasm peaks at conversation 3 and decays from there. Weekly cadence even when "nothing's happening" keeps the deal alive.

What to model financially

• Sales cycle: 12-18 months for enterprise (climate-tech-specific; longer than general SaaS).
• [CAC payback](/glossary/payback-period): 18-30 months post-close, depending on contract size.
• Win rate from qualified pipeline: 15-25% for early-stage climate-tech.
• Cash conversion: customers often pay annually upfront, which improves your cash position even on long-cycle deals.

The implication: at any given quarter, your active pipeline should be ~4-6x your quarterly revenue target. Founders who run 1-2x pipeline coverage routinely miss because climate-tech cycles slip.

What to do today

1. Map every active enterprise deal to its current stage. If you can't, you don't have a sales process yet.
2. Identify the strongest champion in each deal. If you don't have one, the deal is at the early end of the cycle regardless of how many conversations have happened.
3. Standardise contract terms now, before the first enterprise close. Custom-per-deal is 2-3x slower in aggregate.
4. Plan budget alignment with customer fiscal years. Some deals can't close on your preferred timeline; better to know now than at the moment.