Climate tech is not SaaS. The operating model assumptions you’ve developed investing in software companies — clean recurring revenue, low marginal costs, rapid iteration cycles, product-led growth — don’t transfer cleanly to companies that have hardware components, regulatory dependencies, project-based revenue, government customers, and multi-year development timelines. This isn’t a minor difference. It’s a structural incompatibility that leads to misaligned expectations, inappropriate benchmarks, and organizational advice that makes things worse. When you apply SaaS operating model expectations to a climate tech company, you’re measuring a different animal with the wrong ruler — and the organizational guidance that follows from those measurements pushes the company toward a structure that can’t support what it actually does.
Where SaaS benchmarks mislead
SaaS benchmarks assume specific structural conditions that climate tech companies don’t have. Revenue per employee benchmarks assume software margins — but a company with hardware manufacturing, field deployments, or installation services carries a fundamentally different cost structure. Sales efficiency metrics assume a sales cycle measured in weeks or months — but a company selling to government agencies, utilities, or large industrial customers faces procurement timelines of twelve to twenty-four months. Churn metrics assume customers can evaluate the product quickly and switch easily — but a company providing infrastructure-grade climate analytics is embedded in its customers’ operational workflows in ways that make churn measurement meaningless. Net revenue retention looks different when your customer is a municipality with annual budget cycles. Every SaaS benchmark carries embedded assumptions about the operating model, and when those assumptions don’t hold, the benchmark becomes noise disguised as signal. Worse, it becomes guidance disguised as analysis — because when you tell a climate tech founder their sales efficiency is below benchmark, you’re implicitly telling them to restructure their sales operation for a motion that doesn’t match their market.
What climate tech operating models actually look like
Climate tech companies typically operate hybrid models that combine elements of hardware manufacturing, software development, project delivery, and professional services. An earth observation company runs satellite operations, data infrastructure, analytics software, and customer support — four distinct operating models under one roof. A clean energy company manages project development, construction, asset operations, and platform software. A carbon removal company runs R&D, manufacturing, project deployment, and offtake sales. Each operating model has different talent requirements, different process cadences, different cost structures, and different scaling dynamics. The organizational challenge isn’t picking one model — it’s running several simultaneously without the accidental complexity that comes from trying to manage fundamentally different operations with a single organizational design. The companies that do this well have distinct operating units with clear boundaries. The ones that struggle try to force everything into one framework — usually the SaaS framework that their investors understand best, which produces an organization shaped by investor expectations rather than operational reality.
The metrics that actually matter
For climate tech companies, the metrics that predict organizational health and scaling capacity are different from SaaS dashboards. Decision velocity — how quickly the organization makes and implements significant decisions — predicts execution speed more accurately than pipeline metrics. Role clarity — whether people know what they own and what they don’t — predicts team performance better than engagement surveys. Structural dependency — how many critical processes or knowledge domains are concentrated in single individuals — predicts organizational fragility. Scaling readiness — whether the current operating model can absorb the next stage of growth — predicts whether the investment thesis can be executed. These aren’t vanity metrics. They’re structural assessments that tell you whether the organization can deliver on the financial projections. A climate tech company with excellent market metrics and poor structural metrics is a company that will hit a wall — and the wall will be organizational, not commercial. I’ve seen this pattern repeatedly: the board celebrates pipeline growth while the organization’s decision architecture is silently capping the conversion rate those metrics can produce.
What investors should evaluate differently
Three aspects of climate tech operating models require investor attention that SaaS frameworks don’t provide. The hardware-software interface — if the company has both, how are the two operating models structured? Are they separate units with clear boundaries, or are they entangled in ways that slow both? The government-commercial balance — companies with government revenue carry specific organizational overhead — compliance, security, procurement management — that affects the entire organization, not just the government-facing team. What percentage of organizational capacity goes to serving government requirements versus building commercial products? And the project-to-platform trajectory — many climate tech companies want to transition from project-based revenue to platform revenue. Where is the company on this trajectory, and does the organizational design support the transition or resist it? These are structural questions that financial analysis can’t answer and SaaS benchmarks can’t illuminate. They require an assessment framework built for the specific operating model complexity that climate tech companies carry — one that treats organizational structure as a primary variable in investment performance, not a secondary consideration behind market and technology.
SaaS benchmarks applied to climate tech aren’t just inaccurate — they generate wrong organisational advice. Reach out.