Energy markets are being structurally transformed, and the companies building for this transformation are being whipsawed by the very forces they’re trying to serve. The grid is moving from centralized, dispatchable generation to distributed, variable renewables — and that shift changes everything: market design, pricing mechanisms, regulatory frameworks, and the organizational demands on every company operating in the space. The structural challenge isn’t technical. Grid tech companies have the engineering talent. The challenge is that these companies are building products for a market whose rules change every time policy shifts, whose structure varies by jurisdiction, and whose future architecture is genuinely uncertain. You’re not building for a stable market. You’re building for a market that’s being reconstructed in real time.
The typical scaling path
Grid tech companies typically start with a specific technical capability — battery management systems, demand response platforms, grid flexibility analytics, virtual power plant software. Early customers are utilities or grid operators in a single market, often the market where the founding team has relationships and regulatory knowledge. The first deployment works. The technology proves itself. Then the company tries to scale geographically, and discovers that every new market has different regulations, different grid architectures, different market designs, and different procurement processes. What worked in Germany doesn’t transfer to Spain. What worked in California doesn’t transfer to Texas. Each market entry requires partial rebuilds of the product, the sales approach, and often the business model. The company grows, but it grows heavy — adding market-specific teams, regulatory specialists, and custom product configurations that make the organization increasingly complex with every new geography.
Where it breaks
The organizational break happens at the intersection of two timescales. The product development timeline needs to be fast — iterate, ship, learn, improve. But the market environment changes on a regulatory timeline — policy shifts that take years to develop can invalidate a product strategy overnight. Companies invest eighteen months building a demand response platform optimized for a specific market design, then the market design changes and the product needs fundamental rearchitecting. This creates organizational whiplash. The strategy shifts every time policy shifts, and the team never gets the stable ground needed to build repeatable processes. Scaling breakpoints hit harder in this sector because the complexity isn’t just organizational — it’s jurisdictional. The strategy-execution gap widens every time a regulatory change forces a strategic pivot that the organization hasn’t had time to absorb. And the decision architecture fractures because market-specific knowledge is distributed across regional teams who can’t coordinate fast enough to respond to cross-market opportunities. The organization has expertise in five jurisdictions and coherent strategy in none of them.
The structural tension
The deepest tension is between project-based revenue and platform revenue. Grid tech companies want to be platform businesses — recurring SaaS revenue, scalable product, venture-scale economics. But the market buys like an infrastructure market — project by project, deployment by deployment, with long procurement cycles and heavy customization requirements. Energy storage installations are projects. Grid flexibility deployments are projects. Demand response programs are contracts with specific terms and durations. The company’s investor pitch says “platform.” The revenue structure says “project.” This creates an organizational identity crisis that manifests everywhere: in how engineering prioritizes (generic platform vs. customer-specific deployments), in how sales operates (product demo vs. solutions consulting), and in how the company measures success (ARR vs. project backlog). The optimization vs. transformation question is constant — when does incremental improvement to the current model give way to a fundamental rethinking of how the company creates and captures value?
What I see
The pattern I see repeatedly is energy companies trying to force SaaS economics onto infrastructure markets, and the organizational contortions that result. The founding team — usually brilliant engineers who understand grid physics — designs an elegant platform. Then reality intervenes. The first customer needs customization. The second customer needs a different customization. The third customer is in a different regulatory jurisdiction and needs the product rebuilt for a different market design. Within two years, the “platform” is a collection of customer-specific deployments held together by an engineering team that’s stretched across too many configurations. The organization that was supposed to scale a product is actually scaling a services business, and nobody has redesigned the team structure, hiring profile, or economics to reflect that reality. The companies that navigate this well are the ones that make the structural choice explicitly — either truly building a platform that says no to customization, or honestly building a project business with platform aspirations and designing the organization accordingly. The ones that get stuck are the ones trying to be both simultaneously, telling their investors they’re a platform while their revenue says they’re a systems integrator with aspirations.
If your grid tech company is scaling geographies faster than it’s scaling its operating model, the structure needs to catch up. Reach out.