Clean energy companies grow project by project, and that growth pattern creates an organizational identity that’s very difficult to escape. The founding team develops a solar farm, a wind installation, a community energy project. Each one is a discrete effort with its own site, its own permitting, its own financing, its own construction timeline. The team gets good at this — really good. But the organization they’ve built is a project delivery machine, not a product or platform company. When the board pushes for “platform thinking” or investors ask about scalable economics, the company faces a structural transformation that most clean energy businesses underestimate. You’re not adding a platform to an existing business. You’re trying to become a fundamentally different kind of organization while the existing project machine demands every available resource.
The typical scaling path
Clean energy companies usually start with a specific asset class or geography. A founding team with development expertise — often from an established energy company, a project finance background, or an engineering consultancy — secures a first project. The company raises project-specific capital, navigates local permitting, manages construction, and delivers a producing asset. Success attracts more projects. The team grows by adding project managers, site engineers, permitting specialists, and community engagement staff. Revenue scales with the number of projects in the pipeline. The organization is built around the project lifecycle: origination, development, construction, operation. Every process, every hire, every metric is oriented toward moving projects through this pipeline. Then the market — or the investors — push for something different. “Can you build a platform that makes origination faster?” “Can you standardize the development process?” “Can you create recurring revenue from the operating assets?” The company nods and tries, but the organization is structurally configured for project delivery, and platform development requires a different operating model entirely.
Where it breaks
The break happens because project delivery and product development demand opposing organizational behaviors. Project delivery rewards reliability, predictability, and risk management. Product development rewards experimentation, speed, and tolerance for failure. The team that’s excellent at delivering a solar farm on time and on budget isn’t wired for rapid iteration on a software platform. When the company tries to run both simultaneously, the project organization always wins the resource allocation fight because projects have deadlines, customer commitments, and penalty clauses. The software team is perpetually understaffed, working on a platform that the rest of the organization doesn’t use because the project team has its own tools and processes. The optimization vs. transformation dilemma is central: the company is trying to optimize the project delivery machine while simultaneously transforming into a platform business, and the two efforts compete for the same attention, capital, and talent. The adaptation trap sets in as each project generates custom processes that become embedded in the organization, making standardization — the foundation of any platform — progressively harder.
The structural tension
The financial architecture reinforces the structural challenge. Project finance and venture capital operate on fundamentally different logics. Project finance provides cheap capital for low-risk, predictable cash flows. Venture capital provides expensive capital for high-risk, high-return bets. Clean energy companies often need both — project finance for their existing assets and venture capital for their platform ambitions. But the organization can’t serve two capital structures without two operating models. The project finance side demands conservative execution, detailed reporting, and minimal deviation from plan. The venture side demands aggressive growth, rapid iteration, and willingness to pivot. These aren’t just different investor expectations. They produce different organizational cultures, different risk tolerances, and different definitions of success. The company that tries to satisfy both with a single organization produces a confused culture where nobody is sure whether a specific risk should be avoided (project finance thinking) or embraced (venture thinking).
What I see
The clean energy companies I work with consistently underestimate how different a platform organization is from a project delivery organization. They hire a head of product, assign a small engineering team, and expect platform capability to emerge while the project machine continues at full speed. It doesn’t work. The project machine is a powerful organizational attractor — it has revenue, customers, deadlines, and momentum. The nascent platform team is a startup within a company that doesn’t operate like a startup. The companies that successfully make this transition treat it as a structural transformation, not an add-on. They create a genuinely separate unit for the platform business — with its own leadership, its own budget, its own metrics, and its own authority to operate differently. They accept that the project business and the platform business will coexist uncomfortably for years, and they design the organization to manage that discomfort rather than pretending it doesn’t exist.
If your clean energy company is stuck between project delivery and platform ambitions, the portfolio isn’t the constraint. The organizational model is. Reach out.