The Real Problem Isn't Tech
Energy tech in India isn't failing because the tech is hard. It's failing because two people think they're building the same thing and aren't.
A founder at a solar monitoring startup hires a CTO in month 6. Founder spent 18 months in the field. Knows that customers care about performance alerts at 7 AM. CTO comes from a logistics scale-up. Thinks the system needs multi-tenant SaaS infrastructure first. By month 14, they're in a standoff. Founder wants custom integrations for top 5 customers. CTO wants modular, reusable components. Both are right. But no decision-making framework exists.
Why Energy Tech Amplifies This
Most software startups can get away with loose role definition for 18 months. Energy tech can't.
A DISCOM customer expects your platform to integrate with their legacy SCADA system built in 1997. That's not a nice-to-have. That's the deal. A founder can't spec that. A CTO must. But the founder also needs to know why the customer actually wants it—whether it's regulatory compliance, or cost reduction, or avoiding a specific failure mode.
Energy tech decisions create long tails. You pick a database in month 8. In month 28, when you're integrating with 12 DISCOMs, changing it costs 4 weeks and 20% accuracy loss. Founder can't make that call alone. CTO can't make it alone either.
The Equity Mess
Here's where it gets destructive.
Founder hires CTO at Series A with 1.2% equity. Fair market rate for that stage. But the actual responsibility map is: Founder owns product, sales, fundraising. CTO owns architecture, hiring, velocity. That's more like a co-founder role.
By month 20, the CTO has built the core system, hired the team, and is now fighting with the founder about roadmap. The CTO thinks: I should have 4-5%. The founder thinks: You executed what I asked. The CTO looks at comparable exits and sees CTO equity percentages at 3-8%. Resentment hardens.
Then they split. Founder keeps the cap table advantage. CTO leaves with technical debt and no leverage to fix it. Next CTO inherits a broken system they didn't design.
Clarity Solves It
One founder at an EV charging network startup (Series B, ~$50M valuation) did this right. On day 1 with the CTO, she wrote a one-page doc:
Founder decides: customer segment, go-to-market motion, which deals to pursue, board composition. CTO decides: tech stack, hiring, architecture, velocity targets. Joint decision: product roadmap (founder inputs customer need, CTO inputs feasibility and time cost). Override clause: founder can override CTO on product. CTO can override founder on technical risk. But overrides require a 48-hour written explanation sent to the advisory board.
They've never needed the override. Because both understand the frame.
Equity: Founder 60%, CTO 8%, ops lead 4%, advisory shares 8%. She told the CTO upfront: You're not co-founder level because you don't own the customer problem. But you're tier-1 leadership. Vesting was 4-year standard, but with a 1-year cliff. Both committed.
The India Timing Angle
India's energy stack is still forming. APIs don't exist yet. Billing integrations don't exist. SCADA standards are still being debated.
This means your CTO isn't just building—they're defining what gets built. That's co-founder work. But if you don't name it, the CTO feels invisible, and the founder feels threatened.
The best energy tech founders in India (Serena Solar, Oklo, Verdigris) solved this by hiring CTO-level people early and giving them decision rights explicitly. Not hoping alignment would emerge.
What This Means for Your Round
If you're raising Series A in energy tech, investors will ask about your CTO. They're not asking if you have one. They're asking: Does your CTO own their decisions, or are they executing your spec?
If the answer is "executing my spec," they're a senior engineer. You'll cycle through 3-4 of them. If the answer is "we decide together on tech strategy, I decide on customer strategy," you have a CTO. You'll keep them.
Write the decision framework now. Before resentment sets in. Before the cap table gets messy.
The energy tech wave in India is real. But it's being slowed by preventable founder-CTO fractures. The ones solving it aren't smarter. They're just explicit.