Carbon capture is where deep-tech R&D meets industrial-scale project development, and the organizational collision between those two worlds is where most companies stall. The science works — direct air capture, enhanced weathering, biochar, ocean-based removal. The engineering is progressing. But the organizational challenge is that carbon removal requires a company to operate simultaneously as a research organization, a hardware manufacturer, and a project developer. These are three different businesses with three different operating models, three different cultures, and three different timescales. The founder is usually a scientist who understands the chemistry or physics intimately. What they’re rarely prepared for is the organizational transformation required to move from “we proved it works in the lab” to “we’re deploying at megaton scale.”
The typical scaling path
Carbon removal companies start in the lab. A founding team — often out of a university or national laboratory — develops a novel process for capturing or sequestering carbon. Early funding comes from government grants, ARPA-E, or deep-tech venture capital. The first milestone is demonstrating the technology at pilot scale: proof that the chemistry works outside controlled conditions, at costs that suggest a path to commercial viability. Then comes the scaling gap. Moving from pilot to first commercial facility requires project development capabilities — site selection, permitting, construction management, offtake agreements, project finance. These are skills that don’t exist in the founding team and can’t be hired piecemeal. The company needs to build an entirely new organizational muscle while simultaneously maintaining its R&D operation and convincing offtake buyers that future capacity will deliver at specified costs. The team doubles or triples in size, but the new hires come from industrial project development — a culture and operating cadence that’s foreign to the research-origin team.
Where it breaks
The organizational break is predictable: the R&D culture and the project development culture collide. Research teams iterate, experiment, and tolerate failure as data. Project development teams plan, execute, and treat deviation from plan as a crisis. The R&D team wants to keep optimizing the process. The project team needs to freeze the design and build. These are not personality conflicts — they’re structurally incompatible operating modes that the company is trying to house under one roof. The founder leadership transition is especially acute because the scientist-founder’s expertise — and identity — is in the research. Handing operational authority to a project development leader feels like ceding control of the thing that makes the company special. Decision architecture collapses as technical decisions (which process variant to deploy) become entangled with commercial decisions (which customer commitment to honor) and neither function has clear authority. The scaling breakpoints hit at unusual headcounts because the company’s complexity isn’t driven by team size — it’s driven by the structural gap between what the lab team does and what the deployment team needs.
The structural tension
The deepest tension is temporal. Carbon removal companies sell future capacity. Offtake agreements commit the company to delivering removal credits years from now, at costs they haven’t achieved yet, using processes they’re still optimizing. This means the organization is simultaneously operating in three time horizons: the present (running existing operations), the near-term (building the next facility), and the future (selling capacity that depends on cost reductions they haven’t proven). Each time horizon requires different organizational capabilities and different decision frameworks. The present demands operational discipline. The near-term demands project management rigor. The future demands R&D agility and commercial creativity. Most carbon removal companies are organized around one of these time horizons — usually the one that matches the founder’s background — and underinvest in the other two. The result is an organization that’s excellent at one thing and structurally incapable of the other two things it needs to do simultaneously.
What I see
The pattern I see most often is scientist-founders who have built something remarkable in the lab and then hit a wall when the organization needs to become something they don’t recognize. The company needs a COO who can manage industrial-scale project development. The company needs a commercial team that can sell offtake agreements to buyers who don’t understand the underlying science. The company needs a finance function that can structure project finance deals. These aren’t hires the founder knows how to evaluate because they come from industries the founder has never worked in. So the company either hires wrong — bringing in people from adjacent industries who don’t quite fit — or hires late, trying to stretch the research organization past its structural capacity. The companies that navigate this transition successfully are the ones that treat the organizational transformation as seriously as the technical one. They don’t try to scale the lab team into a deployment organization. They build a different organization for a different stage and give it the authority to operate differently.
If your carbon removal company is stuck between lab and deployment, the chemistry isn’t the bottleneck. The organization is. Reach out.