Choose a solar panel
Choose an inverter architecture
Choose home storage
Location, PVWatts and roof fit
8.46 kW solar + 27.0 kWh storage
Production currently uses the selected state planning yield.


PVWatts: ZIP-based output uses a 1 kW reference system with your tilt and azimuth, then scales that yield to the configured array. Changing ZIP, tilt or direction clears the prior PVWatts result until you run it again.
Usage balance: monthly utility kWh entered in the battery section is now shared with the main monthly balance. Missing months use the annual household-use fallback, so both sections always evaluate the same active usage profile.
Battery dispatch: the storage screening uses an average-day approximation within each month and a 90% round-trip-efficiency assumption. It is intended to show direction and scale, not promise a specific bill reduction.
Roof analysis: Google Solar capacity is based on imagery, roof modeling and a reference panel layout. Changing the address clears the prior roof result until you analyze the new address.
Economics: solar price uses the current state benchmark when available. Storage is included only when you enter its installed cost. No incentives are assumed here.
From broad benchmark to monthly home-energy screening
The builder starts with state electricity-rate and price benchmarks. PVWatts adds ZIP, tilt, azimuth and monthly production; Google Solar checks modeled roof capacity. Annual household kWh is distributed by calendar days as a neutral fallback, while entered monthly utility-bill kWh replace that fallback month by month. Battery screening then splits household use into an adjustable daytime share and non-solar-hours share so solar can first serve daytime demand before surplus is routed to storage. This remains a screening model, not an interval-meter, hourly battery-dispatch or utility-billing simulation.
For outage planning, move from the annual/monthly builder into the dedicated battery tools. The runtime planner separates stored energy, continuous power, motor-start surge and recharge-window limits. The 3-day simulator then follows battery SOC across 72 hours and compares three ways to improve the same resilience scenario: add full battery units, increase the modeled outage solar threshold, or reduce average critical load.
Do not treat the 3-day simulator's minimum base-solar result as the DC system size from this builder. PVWatts and roof sizing describe a physical solar array and expected production; the outage threshold is only an average available AC-power assumption during the modeled effective solar window.