Nobody stands up and says “we’re pivoting to defense.” It’s the quarterly revenue review where the defense contract is the only deal that closed, so engineering resources shift. Then the next quarter, the defense product needs a feature, and the climate monitoring roadmap slips. Then the best climate-focused engineer leaves because they can see where the resources are going, even though the mission statement hasn’t changed. The pitch deck still leads with impact. The roadmap is ordered by revenue potential. The gap between stated mission and operational reality widens until the mission is something you point to on the website, not something that governs how resources are allocated.
In climate tech, this pattern is acute because the tension is real: the planet needs transformation, the business model needs revenue, and those two things pull in different directions more often than anyone admits.
Mission drift is a structural inevitability, not a failure of values
Mission impact in climate tech operates on long timescales — regulatory adoption, infrastructure build-out, behavioural change. Revenue operates quarterly — board meetings, burn rate, milestone triggers. When a decision has to be made between a high-impact opportunity that pays off in three years and a moderate-revenue deal that closes this quarter, the system chooses the quarter. Not because anyone decided the mission doesn’t matter — but because the decision architecture weights near-term survival over long-term impact. Every individual decision is rational. The cumulative effect is a company that has drifted from its founding purpose through a thousand small course corrections, each one defensible, none of them deliberate. The mission didn’t fail. It was outcompeted by quarterly survival logic in the organisation’s own decision architecture.
The drift is visible in where resources go, not in what the company says
The pitch deck leads with impact. The roadmap is ordered by revenue potential. Customer prioritisation follows margin, not mission alignment. The highest-impact use cases are “on the roadmap” but never reach the top. The enterprise contract that pulls the product away from its original purpose gets signed because the company needs the revenue. Then the next one. Meanwhile, the company still recruits with the mission, still presents at climate conferences, still tells the story. People who joined for the mission start noticing the gap. The best ones leave.
HawkEye 360’s public trajectory from commercial RF monitoring to defense-heavy revenue is a clean example: the commercial market existed in theory but the defense procurement cycle closed faster and paid better. Umbra’s 2024 NRO Strategic Commercial Enhancements extension and SDA contract tell the same story from the SAR side — commercial ambitions increasingly routing through defense contracts visible in publicly disclosed awards. Neither company made a dramatic strategic decision to pivot. The resource allocation decisions made that decision for them, one quarter at a time.
The mission narrative provides organisational coherence even after the operational reality has diverged
People need to believe their work matters. The mission story lets them maintain that belief without examining the evidence too closely. And the founders need it too — the mission is their identity, their reason for building this company instead of optimising ad clicks. Acknowledging the drift means acknowledging a kind of failure that’s harder to stomach than missing revenue targets. It also creates a coordination problem: naming the drift publicly risks losing the mission-driven talent that’s still holding the company together. So the mission stays on the wall and the operations continue their slow pivot toward whatever the market will pay for.
Investors rarely push on this because mission drift usually correlates with improved unit economics — the commercial use cases that drive drift are typically more profitable than the impact-first ones. Between 2021 and 2022, five EO companies went public promising commercial customers. Combined projections exceeded $5.7 billion by 2025. Actual revenue came in under $680 million. Most of it came from the military. The market rewarded the drift — or rather, the market was the drift. The commercial climate markets these companies were built to serve didn’t develop the institutional infrastructure required to absorb the products.
Making mission operational requires structural choices, not renewed commitment
The drift becomes visible when you stop looking at what the company says and start looking at where resources actually go. Track it concretely: what percentage of engineering time goes to mission-aligned features versus commercially-driven ones? Which customers get prioritised in the roadmap and why? Where does the company say no — and is “not aligned with our mission” ever the reason?
The structural question isn’t whether the mission matters. It’s whether the decision architecture gives the mission any operational weight. If mission alignment isn’t an explicit factor in resource allocation, prioritisation, and customer selection — with real consequences and real trade-offs — then the mission is narrative, not operational. Making it operational requires structural choices: ring-fencing impact work, building mission-alignment into the product roadmap process, creating accountability for mission metrics alongside financial ones. These are design choices. The default is drift.
Earth observation companies drift toward defense revenue because it’s easier to close. Defence & dual-use companies are often climate companies that drifted. Climate adaptation companies drift toward well-funded reinsurance clients and away from the underserved municipal buyers who need them most. Energy markets companies drift toward regulatory arbitrage and away from grid transformation. For investors, mission drift is a portfolio risk that organisational due diligence can detect before the investment by mapping where resources actually go versus what the deck says.
Track where the resources actually go. That’s the mission — regardless of what the website says. Map the gap between stated mission and operational resource allocation.