PermitGo
We're interviewing solar CEOs and operations leaders about permitting, interconnection, and PTO.
PermitGo is an in-development software product. We're speaking with solar companies to understand where these workflows create delays, blind spots, and avoidable manual work.
This is research for product development — not a sales call.
Short audio answers, email replies, or a brief call. Under 30 minutes.
Founder-led research.
Why we're doing this
Permitting, interconnection, and PTO are still some of the hardest parts of residential solar to manage consistently.
Delays often come from fragmented communication, repeated corrections, utility follow-up, jurisdiction-specific requirements, and unclear ownership.
For operators, this creates manual work and constant status chasing. For leadership, it creates slower project cycles, weaker visibility, operational pressure, and unnecessary cost.
We're building software for this problem.
Before building, we're mapping how these workflows actually run across real solar companies — where work stalls, where information gets lost, and which problems are most costly.
What we're building
PermitGo is an in-development software product for permitting, interconnection, and PTO workflows.
The goal is to help solar teams track status more clearly, manage submissions and corrections, and reduce manual coordination across people, jurisdictions, and utilities.
The product is being shaped through direct conversations with the people doing this work and the leaders responsible for outcomes.
Who we're speaking with
Leaders who see how permitting and interconnection affect timelines, margins, cash flow, and customer experience.
People responsible for keeping projects moving, reducing bottlenecks, and improving visibility.
Those handling submissions, corrections, follow-ups, and day-to-day coordination.
How participation works
- 1Review the questions
- 2Reply by short audio, email, or a brief call
- 3Time required: under 30 minutes
- 4Participation details are shared directly
No preparation needed. No sales discussion.
If there is a fit, the conversation is used only for research and product decisions.
Example questions
- Where do permitting or interconnection delays happen most often?
- What typically causes corrections or resubmissions?
- How do you currently track project status across jurisdictions and utilities?
- Where does visibility break down for leadership?
- What work is the most manual or repetitive in your process?
- How do delays affect customer communication?
- What part of this workflow would you most want to improve?
Why participate
Your perspective helps shape a product around real operational constraints instead of assumptions.
This research is focused on where solar teams lose time, where visibility breaks down, and which parts of permitting and interconnection create the most friction.
For CEOs and operations leaders, that often means putting language and structure around problems that are already costing time and money.
Trust & confidentiality
This is a founder-led research effort focused on understanding a specific operational problem before building a product.
It is not a consulting offer, not an outsourced service pitch, and not a disguised sales process.
Responses are reviewed directly by the founder and used to inform product direction.
Sensitive operational details do not need to be shared. High-level workflow insight is enough.
You can choose the format that is easiest for you: short audio answers, email replies, or a live call.
No follow-up sales sequence.
Founder note
I'm trying to understand this space properly before building software for it.
I'm especially interested in how real teams handle permitting, interconnection, PTO, corrections, follow-ups, and status visibility in practice — especially where work becomes manual, fragmented, or hard to manage across roles.
If you're involved in this process, your perspective is valuable.
FAQ
- Is this a sales call?
- No. This is research for product development.
- Who are you speaking with?
- Solar company CEOs, operations leaders, project coordinators, and permitting specialists.
- How long does it take?
- Usually under 30 minutes.
- What do participants receive?
- Participation details are shared directly.
- What is PermitGo?
- An in-development software product for managing permitting, interconnection, and PTO workflows.
- How will my input be used?
- To shape product decisions and prioritize real operational problems.
- Do I need to share sensitive internal information?
- No. High-level process insight is enough.