Energy Terminal

The episode contains a handful of genuinely useful, domain-specific insights - particularly around county-to-county ordinance copying, historical developer interactions buried in planning records, and early political risk signals - but roughly half the runtime is consumed by origin stories, motivational framing, and generic startup advice that adds little for a B2B operator.

“30 to 50% of our projects are getting canceled or delayed due to permitting risk. And each project of those can cost from 2 to 5 million in signed cost.”

“counties and the townships kind of talk to each other and use each other's ordinances and policy approaches to make their own decisions”

There are some fresh, domain-specific angles - monitoring social media and meeting minutes for pre-opposition signals, spotting risk from neighboring-county ordinance cascades - but these are diluted by a substantial volume of recycled lean startup and entrepreneurship advice that circulates widely.

“it might be that, okay, there was an election last year, and there's one county commissioner who just got elected who is very vocal about solar projects. And so in this context, you know, even though they only represent one vote, they're a sufficiently loud voice”

“a County maybe 15 years ago had a really negative interaction with a solar developer. And maybe that project kind of never really became very publicly known”

Emily and Camila are genuine domain practitioners - Emily with real consulting experience navigating global permitting, Camila with technical depth - and they've done the customer discovery work rigorously; however, they are early-stage founders rather than senior operators who have deployed capital or products at meaningful scale.

“having spent a lot of time working in energy, working in the climate space and knowing that local politics and permitting”

“after once again talking to more than 300 people, going through all this process and becoming experts and basically shadowing the best teams that do this job on a day to day basis”

The episode lands several concrete, credible numbers - cancellation rates, per-project sunk costs, interview counts, grant size - and describes specific product mechanisms like scraping old county websites and human-in-the-loop review, but named customer examples and outcome data from live deployments are absent.

“30 to 50% of our projects are getting canceled or delayed due to permitting risk. And each project of those can cost from 2 to 5 million in signed cost.”

“It was $110,000 grant from Stanford. But instead of the grant being awarded to the company, it would be awarded to an individual.”

The hosts do generate a couple of genuinely productive follow-ups - pushing on shifting political risk and asking for non-obvious permitting factors - but they consistently affirm rather than probe, never challenge a claim, and spend significant time on soft biographical questions and student-motivation content.

“what's maybe a risk factor that's a little less obvious. What's something that's come up that no one would ever think of when it comes to permitting risk?”

“That's great advice and something that I think a lot of developers would be wise to heed.”