Solution · Solar + Storage
Proposal economics that survive real tariffs.
Solar and storage products often promise savings with one model, then have to explain outcomes later with another. WattShift gives teams a tariff-aware economic engine they can use before install and after activation, so proposal logic and operating truth stay closer together.
Customer outcomes
Keep the savings story intact from proposal to operation.
The core job is not a prettier calculator. It is making proposal savings, battery dispatch, export behavior, and post-install reporting speak the same economic language.
Model savings before install
Forecast customer value against real tariff structures, export schedules, system assumptions, and battery behavior.
Operate against live value
Use runtime economics to guide charge, discharge, self-consumption, and export decisions after activation.
Prove what actually happened
Turn bill impact, export value, and dispatch outcomes into customer-facing reporting that can survive scrutiny.
Proposal to operate
Modeled vs. realized economics need one foundation.
A proposal engine needs to know what electricity and export value are likely to look like for a real customer. A battery or reporting workflow later needs to explain what actually happened under that same tariff reality.
Tariff and export truth first
Region-specific rates, export structures, eligibility, and assumptions need to be modeled before the savings claim exists.
Dispatch and reporting later
The installed asset still needs live value signals and a clean way to explain realized savings, export revenue, and operating outcomes.
- Solar production peaks during midday, reducing grid consumption.
- Battery storage captures excess solar for evening use.
- Net grid import is reduced through renewable generation.
Product routing
Integrate the APIs where the solar workflow needs truth.
Proposal economics break when tariff logic, export value, dispatch rules, and proof live in separate systems. WattShift keeps the surfaces connected without forcing the same product workflow on every team.
Software use cases
Software teams that need the same economics before and after install.
One of the strongest remaining ideas in the handoff packet was to keep this page aimed squarely at software teams rather than installer marketing.
Solar + storage teams need economics strong enough to survive the handoff from estimate to reality.
Use docs to test the core workflow. Use contact when the main question is packaging, production rollout, or a broader solar plus storage motion.