saascode
climate, energy & agtech·run 101 · May 2026

SolarRunbook

A shared installer and homeowner workspace that tracks proposal, permitting, materials, inspection, interconnection and incentive steps while preserving each external authority's actual status.

Genesis score5.57/10
Make SolarRunbook real.0/500
500 more votes and SolarRunbook is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
5–7Typical active tool stack supplied
30+ panelsTarget install tier
Authority-ownedExternal approvals
The case

The supplied research validates severe tool fragmentation, public or accessible integration surfaces and established solar software budgets. It finds specialized design, sales and permit products but no confirmed product combining permit progress, interconnection queues and a homeowner view at the stated scope. SolarRunbook can win as an orchestration and evidence layer, not as the authority that issues a permit, passes an inspection, connects a system or determines an incentive.

Who pays — and why

The owner, operations director, project leader, or customer-experience lead at a residential solar installer handling high-complexity projects.

What it unlocks
A jurisdiction- and utility-specific project runbook with required artifacts, owners, dependencies and expiry-aware evidence
A shared timeline that distinguishes submitted, acknowledged, under review, approved, scheduled, completed and verified states
Installer, subcontractor and homeowner views with scoped access, redaction and an immutable history of corrections
How Genesis scored it
5.57across seven criteria
tension 6temporal 5blindspot 5buyer 5leverage 8convergence 5why-not 5
8
Asymmetric leverage

A reusable adapter and runbook library scales, though each authority's changing process creates maintenance work.

6
Productive tension

Customers want a single status while legal authority remains distributed across jurisdictions, inspectors, utilities and incentive administrators.

5
Why nobody did it

Fragmented portals explain the historical difficulty without proving that a barrier recently disappeared.

Why it scored well

The workflow is concrete, fragmentation is validated and jurisdiction-specific adapters can compound into a useful operational library.

What's holding it back

Buyer detail and timing proof are thin, jurisdiction coverage is service-heavy and incumbent solar platforms can expand into orchestration.

Signals detected5 sources crossed
Signalcompetitive research carried in Genesis

Signalcustomer signal carried in Genesis

Signalcompetitive research carried in Genesis; observed market reference, not fixed product pricing

Signalcompetitive scan carried in Genesis

Signalintegration research carried in Genesis

Direction briefsolarrunbook.md
solarrunbook.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.