Brightward Solar

Brightward Solar doesn’t exist — the confusion its customers feel is entirely real. This study follows a Victorian homeowner from “I’ve been thinking about solar” to an enquiry an installer can actually act on.

High consideration, low certainty

Residential solar is a decade-long decision wearing the price tag of a car. A homeowner who clicks a solar ad is usually interested but under-informed: unsure what a system size means, whether a battery earns its place, what actually moves the savings, which incentives might apply, or why an installer needs anything more than an address to quote.

Most quote funnels respond by asking for contact details first and explaining later. That order suits the seller and wastes the one asset the visitor arrived with — attention.

This concept reverses it: education and qualification happen first, in the browser, before anyone asks for a name.

From bill to something understandable

The Savings Explorer takes three humble inputs — a postcode, a recent electricity bill, and a rough sense of whether the household uses power mostly by day or mostly after dark.

From there it works in the open:

1. Assumptions — sunlight hours by region, tariffs, export limits, each stated and adjustable.
2. Indicative scenarios — a small system and a larger one, described side by side.
3. A plain-language result — system size translated into panels and roof share, payback described as a range shaped by the inputs, not a single confident figure.

The goal is comprehension, not prophecy. A homeowner who understands why their number moves is a better customer; a homeowner handed a magic number is a future dispute.

Show the assumptions

Every solar estimate rides on assumptions: the feed-in arrangement, local weather records, roof orientation, what energy prices do next. Any tool can multiply inputs together; the honest part is admitting which inputs were chosen.

So the Explorer prints no “you will save $X”. Each assumption appears beside the result, in words, with an explanation of the direction it pushes. The outcome is presented as a range and a list of drivers — what would move it up, what would move it down.

Showing the working is not a UX nicety here. It is the difference between a tool that informs a decision and a tool that manufactures false precision to harvest a lead.

Solar plus battery, compared honestly

Usage timing rewrites the economics. A home that empties at 8am exports cheap midday power and buys it back at dusk; a battery exists to arbitrage exactly that gap. Whether the gap is worth closing depends on the household, not on the brochure.

Rather than recommending, the interface compares. Solar-alone and solar-plus-battery run over the same assumptions, and the view names the trade-off plainly: what the battery adds to the bill picture, and what it adds to the invoice. A household that runs appliances all day may learn it never needed one — which is precisely the kind of answer that makes the rest of the pitch believable.

Incentives without misleading

Victorian incentives are often the deciding question, so the experience includes a Solar Victoria eligibility pre-check — built as orientation, not gatekeeping. Three commitments are stated in the interface itself:

• Program rules change; what is shown reflects stated criteria, not insider knowledge.
• Official sources govern; the pre-check links to them rather than paraphrasing authority.
• The experience does not confirm eligibility. It indicates which programs appear relevant and what documents the official check will want.

No dollar figures are quoted for rebates anywhere in the flow. Numbers attached to government programs age badly, and a studio that rounds them carelessly looks careless everywhere else.

From estimate to qualified lead

Once the estimate makes sense, the remaining questions are practical: property context such as ownership and roof type, shading and orientation notes, the incentive context just established, and only then contact details.

The output is a structured profile — indicative system size band, usage pattern, scenario preference, incentive indications, property notes — formatted so a CRM can route it and an installer can prepare a real quote before the first phone call. The sales conversation starts halfway held.

How it would be built

Stated as engineering intent, consistent with how this very site is made:

• Static-first, on Astro. Content ships pre-rendered through the same collection pipeline serving this study; the Explorer is the only scripted surface.
• Deterministic local calculation. Estimates come from pure functions running in the browser — no server round-trips, and inputs leave the device only if the visitor chooses to enquire.
• Lightweight SVG/CSS visualization. Charts are inline SVG themed by design tokens, in the same spirit as the site’s cover plates — no charting library, no canvas, no animation framework.
• Minimal client JavaScript. The site baseline stays around a kilobyte; whatever scripting exists belongs to the Explorer island.
• Accessible forms throughout. Labels, hints and errors wired through the design system’s field primitives, with keyboard operability and visible focus treated as features rather than fixes.
• Event-based component integration. Explorer steps communicate through small custom events instead of shared mutable state, so any panel can be redesigned or removed without dragging the rest apart.
• Local-only demo data. In the concept build, submitting sends nothing anywhere: the resulting profile is displayed on screen and held in the browser until the tab closes.
• A lazy Live Project Player. The build below loads through the existing player facade — a poster until asked, then an isolated sandboxed frame you can eject or reload.

Why this concept exists

This concept demonstrates how a technical sale can provide useful value before lead capture — while keeping every assumption visible and carrying the resulting context into the eventual enquiry, instead of discarding it at the form.

It also shows the posture we bring to regulated and technical subjects: explain plainly, compare rather than push, point at official sources, and never round uncertainty into a confident-looking number.

When a real installer engages us, this is the template their case study will inherit — minus the fiction label, plus the outcomes they choose to publish.

If your quoting process currently begins with “leave your details”, this page is the shortest possible introduction to how we would rebuild it.