Turn every bill shock into a trusted moment.
Your app makes households wait while bills are assembled. Assembling turns that wait into a reward they keep — power bill credit at launch, with more rewards rolling out. One line of code. You keep 55%.
the smallest credible next step.
fail any line of the scorecard and we change the design or stop.
No production access is requested by this concept. No live customer, price, reward or purchase is involved. Scope, privacy, security and commercial terms require joint approval before any pilot begins.
"the concept looks right except for one thing — [your constraint here]."
Every wait in a power account
Six moments between choosing a plan and opening a winter bill — the whole relationship happens in the gap between using power and finding out what it cost.
The comparison gets made against this household’s actual use rather than an average nobody lives in.
The silence gets named, so it stops reading as something gone wrong.
The bill explains itself in the order a person actually asks — what changed, why, and what happens next.
Most hold calls are one fact. Putting the fact in the wait ends the call before it starts.
The first question in an outage is whether it is only you. Answering that stops a call and stops a worry.
The hard bill arrives with the options already worked out, before anyone has to ask for help.
Four steps, every time.
- The signalSomething you already record says a person is now waiting, and roughly how long for.
- The predictionHow long this one will really take — not the average, this one.
- The valueSomething worth their attention goes into that window: an answer, a credit, a thing prepared while they wait.
- The exchangeThey get value. You get someone who stayed, and one optional answer you have always wanted.
This is the reward layer, running for real on this page. Drag to scratch it. Nothing is collected and nothing is sent — it is here so the idea is something you do, not something you read.
US retailers lose an estimated $37.7 billion a year to customers who abandon because of long queues, split roughly $15.8b to competitors and $21.9b abandoned outright (Adyen with 451 Research). The New York State Department of Labor reported a 48% reduction in hang-ups after introducing virtual queuing. Theme parks moving to virtual queues reported a 36% lift in per-capita spending, because guests spent the wait somewhere that sold something. A Seattle-Tacoma Airport study found 63% of passengers said they shopped or ate more because they saved time in the security queue.
Every figure here carries its source, and overseas figures are shown as overseas figures. We have not found a published New Zealand equivalent and we will not invent one.
What a pilot actually asks of you.
Written out in full, because the honest version is short and most of it is your time, not your money.
One named person
The approver. Every draft stops with them and nothing reaches a customer until they say so. About two hours a week, reading drafts rather than managing a project.
One situation, not the business
One wait on one customer segment, for six weeks — the first bill after a switch. Not the whole book, and nothing that changes a tariff.
Read-only access, nothing that writes
Read-only access to billing and meter-read events already emitted, and your published plan terms. No customer data leaves your environment and nothing writes to an account or a rate.
Your actual rules
The policies, limits and words the drafts are held against. Every rule shown on this page is a placeholder standing in for yours. An afternoon with whoever owns them is usually enough.
Six weeks, then a real decision
Scored on: Drafts a billing lead sends without rewriting. Contacts about a first bill against a control. Whether the bill needed explaining twice. And: would that lead be annoyed if you switched it off? Fail any line of that and we change the design or stop. You keep everything drafted either way.
A fixed fee, agreed in writing first
No number is published on this page, because it depends on which situation you pick. Whatever it is, it is agreed before any work starts and it does not move.
Run the pilot.
Say yes to the six weeks above, and add anything you would change first. Nothing here is fixed — most pilots move a line or two before they start, and the notes below are how that happens.
Opens your mail app to assembl@assembl.co.nz with your notes in it. Nothing is collected by this page.
- Six weeks, one situation, scored against a written line
- Read-only access, nothing production
- A named approver — nothing sends without them
- A fixed fee, agreed in writing before anything starts
- Stop any time. You keep what was drafted