Product people are trained to look for constraints.
Sometimes the constraint is obvious: budget, headcount, schedule, design capacity, manufacturing lead time, API reliability, customer attention. Sometimes it is hidden until late in the process, when the roadmap has already been sold and the business case has already been modeled.
In electrification, one of the most important constraints is often treated as if it lives outside the product.
Grid capacity.
That is a mistake.
For EV charging, data centers, industrial electrification, solar, storage, and other large load or generation projects, the ability of the grid to accept or deliver power is not just an engineering consideration. It shapes the product, the go-to-market motion, the customer promise, the unit economics, the deployment schedule, and the credibility of the company making the offer.
If the grid cannot support the project at the right location, at the right cost, in the right time frame, the product has a problem.
Capacity Is Not a Checkbox
It is tempting to talk about site capacity as if it were a yes-or-no question.
Can we get power here?
That framing is too thin.
The real questions are messier:
- How much power can be delivered or injected?
- At what voltage?
- Under what assumptions?
- What upgrades are likely?
- Who pays for those upgrades?
- How long will the utility or ISO process take?
- What queue position, study cycle, or cluster process governs the answer?
- What other projects are competing for the same capacity?
- What happens if demand grows faster than the original model assumed?
A site can look viable in a spreadsheet and become unworkable once the interconnection result arrives. The fatal line item may not be land, hardware, software, or construction. It may be a network upgrade that makes the project late, expensive, or strategically pointless.
That is why grid capacity should be considered early, visibly, and continuously.
The EV Charging Lesson
In EV charging, especially fleet charging, customers rarely buy "chargers" in the abstract.
They buy operational readiness.
A transit agency needs buses ready for morning pullout. A logistics company needs routes covered. A school district needs confidence that vehicles will be charged before drivers arrive. A public charging network needs uptime and throughput where drivers actually need to stop.
The charging hardware matters. The software matters. The site design matters. But the grid connection determines the ceiling.
If a depot needs 5 MW and the site can only support 1 MW without a long upgrade process, the product problem changes. The team may need phased deployment, managed charging, on-site storage, solar, temporary generation, route changes, or a different site. The roadmap becomes a power roadmap.
This is where product management in energy stops looking like generic SaaS.
The product manager cannot only ask, "What features should we build?"
They also have to ask:
- What physical system are we asking the customer to operate?
- What constraints will the utility impose?
- What promises can sales make without creating future pain?
- What data do we need before a site becomes a commitment?
- What flexibility should the software preserve?
The answer is rarely one feature. It is a system of decisions.
False Positives Are Expensive
The most dangerous site is not obviously bad.
The most dangerous site looks good until it does not.
It has land. It has customer interest. It has proximity to load or generation. It has a promising single-line diagram. It has an early utility conversation that sounds encouraging enough to keep going.
Then the study comes back.
The project triggers a major upgrade. The timeline slips years. The capital plan changes. A customer who thought they were buying a clean deployment is now stuck in the physics and bureaucracy of the grid.
That is not just a technical failure. It is a product discovery failure.
A product organization should treat capacity risk the same way it treats market risk, usability risk, feasibility risk, and viability risk. It is a thing to discover early, not a thing to explain away late.
This matters even more as load growth accelerates.
Data centers, fleet electrification, building electrification, hydrogen, manufacturing, storage, and generation are all trying to use the same grid as if the grid were an infinitely elastic platform. It is not.
The winners will be the teams that learn where the constraint lives before they spend too much money pretending it does not exist.
Capacity Data Is Product Data
One of the habits I have developed from working in EV charging is that I do not like treating infrastructure data as back-office material.
Capacity, charger status, session telemetry, utility rate structures, vehicle telematics, fault codes, site layouts, service history, and customer operations all belong in the product conversation.
The grid is not a spreadsheet appendix. It is part of the user experience.
If a fleet manager has to change operations because charging power is constrained, that is UX. If a developer abandons a site after six months of diligence because upgrade costs were misunderstood, that is product-market fit colliding with infrastructure reality. If a sales team cannot explain why one site can scale and another cannot, that is positioning.
The best software products in energy do not merely visualize data. They change when decisions can be made.
Earlier decisions are usually cheaper decisions.
If a team can identify weak sites before committing land dollars, if it can test scenarios before joining a queue, if it can understand upgrade exposure before making customer promises, then software has moved from reporting to strategy.
That is the line that interests me.
The Product Mindset
Grid capacity rewards humility.
Nobody gets to growth-hack physics. Nobody gets to A/B test their way out of Kirchhoff's laws. Nobody gets to wish away queue reform, transformer lead times, utility staffing constraints, or regional transmission bottlenecks.
But humility is not passivity.
The product mindset is to make constraints legible, actionable, and part of the normal decision flow. Show the trade-offs. Preserve assumptions. Help people compare options. Make uncertainty explicit. Do not let the organization drift into a confident story built on fragile capacity assumptions.
That is the real opportunity for software in the grid.
Not replacing engineers. Not pretending studies do not matter. Not turning transmission into a magic heat map.
The opportunity is to help teams reason earlier and better about where power can go, where it can come from, what it will cost, and what decisions are worth making next.
Grid capacity is not background.
It is one of the core product constraints of the energy transition.