CitizenSolar Case Study Skeletons

Hero: CitizenSolar Case Study Skeletons

These public scenario skeletons show how CitizenSolar structures readiness review, evidence mapping, and intake routing for representative storage-first examples.

• • Use the index to move from scenario recognition into regional mapping or structured intake.
• • Each skeleton is representative only and does not describe a real customer, live deployment, or measured outcome.

Scenario index table

Each row connects the representative scenario to its regional anchor and public intake path.

How to read a skeleton

A skeleton is a structure for review, not proof of execution.

• • Read the scenario first, then the buyer class and flagship pack.
• • Use the evidence focus to decide what information is still missing.
• • Use the review path to pick the next public intake or review route.
• • Treat the boundary text as mandatory context, not optional fine print.

Evidence path explanation

The case-study layer sits on top of the regional and intake stack, so a reviewer can move from representative scenario to the public route that best matches the next question.

• • Finance-Fit Intake for structured finance, beneficiary, and supplier-risk context.
• • Regional mapping pages for Texas, Netherlands, California, and Bulgaria context.
• • Supplier Candidate Intake for hardware or OEM diligence.
• • Community Energy Bank and Orchestration Readiness Review when shared-storage or telemetry questions are primary.

Public follow-up

Use the public intake routes when the next step is to move the conversation forward.

• • Start Finance-Fit Intake when the project needs structured evidence collection.
• • Use the matching regional page when the scenario needs jurisdiction-specific mapping.
• • Open Supplier Candidate Intake, Community Energy Bank, or Orchestration Readiness Review when that becomes the primary question.