← App Prototypes
App Prototypes 2026-05-17

Rebate Stack

Rebate Stack
Prototype

RebateStack

The IRA heat-pump rebate stacker — every federal, state, utility, and manufacturer dollar you qualify for, in one number, in the order you have to claim them.

Date: 2026-05-17 Form factor: Web app (single-page; mobile-friendly) Status: Prototype

What it is

RebateStack is a single-page workspace that turns the alphabet soup of US home-electrification incentives — federal 25C, HEEHRA, HOMES, state income-tax credits, utility on-bill rebates, and manufacturer promos — into one total dollar amount and a step-by-step application sequence. The user picks a household profile (or, later, their own ZIP + income + equipment), and the app shows the live rebate stack, the per-program rationale, the application order with timing requirements, and the watch-outs that most often cause a claim to be denied.

The prototype demonstrates the end-to-end flow on five fully-modeled households spanning the four eligibility patterns that drive most denial cases: a moderate-income California household stacking the new HEEHRA-CA + utility + manufacturer rebate, a low-income Buffalo retrofit where the federal credit is wasted because there's no tax liability, a Worcester couple over the 150% AMI cap that loses HEEHRA but still recovers a third of cost via Mass Save, a Minnesota family electrifying three appliances at once under the $14,000 lifetime HEEHRA cap, and a Houston household whose state hasn't launched HEEHRA yet — $6,500 on the table if they can wait until Q4 2026.

Who it serves

Any US homeowner who has just gotten an HVAC, water-heater, or panel-upgrade quote in spring 2026 and is trying to figure out what they actually pay net of rebates. Specifically the audiences who are most often steered into a higher net cost than they need to bear:

  • Moderate-income households (80–150% AMI) who fall on the wrong side of HEEHRA's "100% covered" line but qualify for the 50% tier. They tend to either skip HEEHRA entirely (assuming they don't qualify) or claim it without realizing utility and manufacturer rebates still stack on top.
  • Low-income retiree or fixed-income households with no federal income tax liability. They're routinely advised to "take the 25C credit" by contractors who don't realize the credit is non-refundable. The credit is wasted; HEEHRA isn't — but the contractor has to file it at point-of-sale.
  • Affluent households above 150% AMI in HEEHRA-ineligible territory. They're told HEEHRA disqualification means "no rebates" — which ignores HOMES, state programs (Mass Save, NYSERDA), and manufacturer promotions worth $10k–$17k.
  • Texas, Florida, and Georgia residents in states where HEEHRA is either still in design or has been opted out of. The single best advice is "wait if you can" — and most contractors aren't going to give that advice.

The pain is concrete and recurring. Over the next 24 months, ~10M US households will replace HVAC or water-heating equipment, and DOE's own program rollout has been described as "exceedingly difficult to navigate without expert help" in the agency's Q4 2025 stakeholder briefings. Households leave $3,000–$8,000 on the table per project on average — and the contractor's interest is faster close, not maximum rebate.

Why it could be profitable

Monetization is freemium with a paid contractor handoff and a B2B white-label:

  • Free: stack calculator + application-sequence plan + watch-outs for one project per session. No account.
  • Pro ($29 one-time per project): pre-filled HEEHRA registration packet, IRS Form 5695 worksheet, state-credit forms, utility-portal walkthrough screenshots, and a contractor-validation checklist. Pays for itself if it saves even an hour of admin time.
  • Contractor lead handoff ($60–120 / lead): once a household has a verified rebate-stack quote, they can request 1–3 vetted contractors. Contractors pay per lead. The household never pays for the introduction.
  • B2B white-label ($299/mo): utilities, state energy offices, electrification non-profits, and credit unions running heat-pump-loan programs embed RebateStack into their own portals. They already spend $30–$60 per call to their call center to explain rebate eligibility; RebateStack replaces that.

Demand math: ~10M residential HVAC + water-heater replacements per year × 25% of households who'd use a calculator before signing × $29 average Pro conversion at 3% would clear $2.2M ARR before lead handoffs. The contractor handoff is the larger pool — at $80/lead and 0.5M referred leads/year that's $40M of TAM.

The regulatory tailwind is strong but time-limited: state HEEHRA programs launched on different dates between November 2025 and April 2026, and federal funding for HEEHRA is appropriated through September 2031 — but the Trump-administration FY27 budget proposal in March 2026 sought to claw back unobligated HEEHRA balances. That uncertainty is itself a wedge for a tool that helps households claim what's available now.

Form factor & scope

Single-page web app, sized for mobile and desktop. The prototype is scope-locked to the rebate-stacking workflow — it does not search for contractors, does not file forms on the user's behalf, and is not a financing or loan-origination product. The minimum viable scope demonstrated here is:

  1. Pick a household profile (sample).
  2. See the live rebate stack (federal + state + utility + manufacturer) with per-program rationale.
  3. See the project cost and net out-of-pocket.
  4. See the application sequence — point-of-sale steps before install, post-install steps with timing windows, and tax-year steps.
  5. See the watch-outs that most commonly cause a claim to be denied for households with this exact profile.
  6. Copy or download a plain-text plan suitable for emailing to a contractor or saving with the project paperwork.

How to run it

  1. Open index.html in any modern browser (Chrome, Firefox, Edge, Safari).
  2. Pick any household from the left rail. The headline, rebate stack, equipment panel, application sequence, and watch-outs update together.
  3. Use Copy plan to put the full plan on the clipboard. Use Download .txt to save it as a file you can email to a contractor or attach to a rebate application.

No build step, no API keys, no accounts. The sample data is embedded inside index.html as a <script type="application/json"> block, so the page works directly from file:// with no local server.

What's in this prototype

  • Stack engine that surfaces every program a household qualifies for and notes when one explicitly excludes another (HEEHRA vs. HOMES on the same measure).
  • Five fully-modeled households: Pasadena CA (moderate), Buffalo NY (LMI, no tax liability), Worcester MA (above 150% AMI), St. Paul MN (multi-appliance retrofit), Houston TX (pre-launch HEEHRA state).
  • Rebate-program reference built into sample-data.json for federal 25C, HEEHRA (with state launch status), HOMES, state credits across CA/NY/MA/MN/CO/TX, seven utility programs, and spring 2026 manufacturer promos.
  • Application sequence engine that orders rebate claims by their hard timing constraints — point-of-sale (HEEHRA), 30 days (manufacturer), 60–90 days (utility), tax year (25C + state).
  • Per-household watch-out feed — the household-specific gotchas (no tax liability, lifetime cap usage, contractor-list eligibility, recycling-receipt requirements).
  • Copy / Download plan that produces a clean plain-text version suitable for emailing or attaching to the rebate paperwork.

Roadmap

  • Replace the household picker with a 90-second wizard: ZIP → income → equipment chosen → recompute live.
  • Add a contractor-search panel that ranks contractors by state Qualified Contractor List membership, AHRI cert, and manufacturer authorization (Mitsubishi MVP, Carrier Authorized Dealer, etc.).
  • Add HOMES energy-modeling pre-check: estimate whether the project clears the 20% or 35% savings thresholds before paying for a formal modeler.
  • Add a "rebate-stack PDF" export branded for B2B partners (utilities, credit unions, electrification non-profits).
  • Add Mexico- and Canada-side analogs (Hydro-Québec heat-pump rebate, BC Hydro, CFE in MX) to support cross-border installer audiences in the Northwest and Southwest.

Sources

Requirements

RebateStack — Requirements

Goals

  • Compute the exact total rebate dollar amount a household qualifies for across federal, state, utility, and manufacturer programs, in under 5 seconds.
  • Make every dollar in the stack auditable — show the program, the cap, the eligibility rule, and the rationale for the exact dollar figure.
  • Surface the application sequence with hard timing constraints (point-of-sale, 30-day, 60–90-day, tax-year) so a homeowner doesn't forfeit a rebate by claiming things in the wrong order.
  • Flag the household-specific gotchas that most commonly cause claims to be denied, in plain language, before the install contract is signed.

Primary user

A US homeowner who has just received an HVAC, water-heater, or panel-upgrade quote and is comparing net cost after rebates. They are typically:

  • 30–65 years old, mobile- or laptop-first, evaluating a $5k–$32k home-improvement project that the household budget is sensitive to.
  • Aware that "there are rebates" from the IRA but unsure which apply, whether they stack, and whether they'd lose them by accepting a quote today vs. waiting.
  • Comfortable filling out an online form but not comfortable reading a 60-page state program manual.
  • Unwilling to spend $400 on a rebate-navigation consultant — the project budget is already strained.

The job-to-be-done: "In the next 10 minutes, tell me how much I actually pay net of rebates, in what order I have to claim them, and what would disqualify me — before I sign the contractor's quote."

Functional requirements

  • FR1: Render a left-rail picker of pre-loaded sample households, each tagged with state and AMI %.
  • FR2: For each household, surface a header card with location, utility, household size, AMI band, and the existing equipment being replaced.
  • FR3: Render an equipment panel listing every new appliance/system being installed with model name, manufacturer, category, and installed cost.
  • FR4: Compute the rebate stack using the household's state HEEHRA launch status, income band, equipment categories, and the live program data in sample-data.json.
  • FR5: Render the stack as a table with one row per program (federal 25C, HEEHRA, HOMES, state credit, utility, manufacturer), showing dollar amount and a colored tag identifying the program type (federal / state / utility / mfr / no-stack).
  • FR6: For every program row, render a per-row rationale in plain English explaining how the dollar amount was derived (rule cited, cap applied, eligibility band, exclusion noted).
  • FR7: Show a total stack, project cost, and net-out-of-pocket footer that mathematically agrees with the row sums.
  • FR8: Render the application sequence as an ordered list with a "when" label (point-of-sale, 30 days, 60–90 days, tax year) and an action description.
  • FR9: Render a household-specific watch-out list (no-tax-liability disqualifies 25C, contractor-list eligibility for HEEHRA, lifetime-cap exhaustion, retroactive-claim ineligibility, etc.).
  • FR10: Update every panel reactively when the user picks a different household — header, stack, sequence, watch-outs, and topbar pills all update together.
  • FR11: Provide Copy-plan-to-clipboard (with document.execCommand('copy') fallback for file://) that emits a clean plain-text rebate plan including header, stack, totals, sequence, and watch-outs.
  • FR12: Provide Download-plan-as-.txt that saves the same plain-text plan with the household ID in the filename.
  • FR13: Surface a topbar pill with the total rebate amount and a second pill with the net out-of-pocket cost so the household sees the headline number at all times.
  • FR14: Run from file:// with no remote scripts, no API keys, and no build step. Inline the sample data inside index.html to avoid the fetch CORS restriction on local files.
  • FR15: Collapse to a single column under 1100px viewport width and tighten further under 600px (mobile-first usability for homeowners reading the page in a kitchen, not a desk).

User stories

  • As a moderate-income California homeowner with a $14,500 heat-pump quote, I want to know if HEEHRA-CA covers half of that, so I can confirm my net cost is under $2,000 before I sign.
  • As a low-income Buffalo homeowner with no federal tax liability, I want to be told plainly that the 25C credit is wasted in my case, so I don't budget for it and over-extend.
  • As an above-150% AMI Worcester couple, I want to know that Mass Save still covers $10,000 of a $32,000 whole-home heat pump, so I don't bail on the project assuming HEEHRA disqualification ends rebates.
  • As a Minnesota family electrifying three appliances at once, I want to know my running HEEHRA lifetime cap so I don't trip the $14,000 limit on a future project.
  • As a Houston homeowner, I want to know that Texas HEEHRA isn't live yet so I can make an informed wait-or-go decision before signing this spring's quote.
  • As a homeowner who already got the contractor quote, I want to copy the rebate plan and email it to the contractor so they fill it in correctly at point-of-sale.
  • As a homeowner who cares about privacy, I want my income and address details to stay client-side and never touch a server.
  • As a state energy office staffer using this tool to triage homeowner phone calls, I want to skim a one-screen summary in under 30 seconds for any caller.

Non-functional requirements

  • Performance: First paint < 1s on a 4G connection; total bundle (HTML + CSS + JS + inlined data) < 100 KB gzipped.
  • Privacy: No analytics, no third-party fonts, no remote scripts. Income, AMI, ZIP, and equipment details never leave the browser.
  • Accessibility: Semantic HTML5 (header, main, aside, article, footer); WCAG 2.2 AA contrast on dark theme; all interactive controls keyboard-reachable; skip-link present.
  • Resilience: Clipboard write falls back to document.execCommand('copy') when navigator.clipboard is unavailable (which happens for file:// in some browsers).
  • Responsiveness: Three breakpoints — desktop (>1100px), tablet (600–1100px), phone (<600px).
  • Data integrity: All program rules, caps, and state launch statuses live in sample-data.json::rebate_programs so updates only happen in one place when DOE publishes new state launch dates.

Out of scope (for the prototype)

  • Live contractor search and booking.
  • Actual filing of rebate forms — no e-signature, no API integrations.
  • Loan / financing origination (e.g., on-bill financing or green-bank pairing).
  • Non-US programs (Canadian provincial heat-pump rebates, Hydro-Québec, BC Hydro).
  • Commercial property rebates (this is residential-only).
  • Live ZIP-to-utility lookup — the sample data hardcodes utility per household.

Open questions

  • Should the Pro tier ($29/project) include a follow-up email cadence for households who don't complete their claim sequence (Day 14 utility-rebate reminder, Day 60 utility-deadline reminder)?
  • For the B2B white-label channel, do utilities prefer to embed via iframe or via a small JavaScript widget that pulls from their existing customer-account context?
  • Is there appetite from green-bank loan programs (Connecticut Green Bank, NYCEEC, Inclusive Prosperity Capital) to white-label this as part of their loan-application flow?
  • How fast should we add residential solar + battery to the stack? Solar has its own 25D credit and state programs, but it complicates the UI and creates an ROI-calculator scope expansion.
  • If FY27 budget appropriations claw back unobligated HEEHRA balances mid-year, what's our update cadence for the state-launch tracker?

More from App Prototypes