The solar economy, connected
Property + service experienceStudio
Sites + interactive applicationsShop
Offers + client commerce
Demand meets delivery
12-month illustrative scenario · no Vital Energy operating data connectedModel boundary and monthly ledger
Constant monthly inputs; zero opening backlog; new orders can complete in the same month; no cancellations or seasonal change. Capacity represents the entire delivery chain, including external approvals. Fractional projects represent expected volumes. Revenue is modeled at completion, not cash collected. Contribution excludes overhead, tax, financing and acquisition costs. No household savings, market size, or emissions forecast is implied.
| Month | Orders | Completed | Backlog |
|---|
Research agenda and evidence
| Question | Evidence to collect | Experiment |
|---|---|---|
| Where does work stall? | Stage timestamps, rework, approval delays | Compare time to completion before and after guided intake |
| Who benefits? | Owner bills, provider costs, labor hours, system output | Track household, worker and provider outcomes separately |
| Does continuity improve service? | Equipment history, repeat faults, renewal and handoff outcomes | Test a property record that persists across providers |
| What should we build next? | Measured friction, affected users, delivery cost | Rank interventions by observed constraint and testable benefit |
Structure: Daniel’s brief and HomeGrid direction. Process reference: DOE solar process guide. Scenario inputs: invented for experimentation, not benchmarks. Property and service-contract primitives are recorded gaps in the HomeGrid memory; their live implementation has not been independently verified here.