A generic New Zealand electricity retailer, not a real one, seen from eight homes on one street: a household switching in, one moving house, one opening a bill 40% higher than last month's, and one plugging in a new EV. Each journey runs the same nine stages. The part that matters most is the wait, and what the customer sees while they wait.
Three public figures and one empty slot. The wholesale price is what the grid charges by the half hour; the residential price is MBIE's modelled average for the area across every retailer; the market share says who sells power on this street. No public dataset carries a retailer's plan, so that slot stays empty until the retailer connects its own.
Every journey runs entry, intent, context, recommendation, commitment, action, wait, fulfilment and resolution. The striped block is a wait the customer can see. Below, the hours each stage takes as the retailer is (hollow) and with its levers on (filled).
The cohort is billed every month with Auckland's seasons in the usage. Switch-ins, moves, bill shocks and plan changes happen at the rates on the sources list, and each one costs the retailer contacts, back-office work, and sometimes the customer.
All PROPOSED. Switch any on and the year runs again for the whole cohort. The dollar figure on each is that change on its own against the retailer as it is: cost to serve saved, plus the margin kept when a customer stays, less any wholesale saving.
None of these three are public for any NZ retailer. Move them to your own and the ledger follows.
Five levels of authority, set per job by the retailer. Nothing here is running today: each row is a PROPOSED assembl concept. The evidence column says who measured the result, and whether anyone checked it independently. Credit decisions, disconnection and any change to a customer's price stay with people.
Start with exports the retailer already has: a billing extract, a CRM contact log, and the switch and move event log. Files are read inside this browser tab. Nothing is uploaded or sent anywhere, and columns that look like personal information are ignored on load.
Generated in this page from the simulated cohort, so a demo never touches real data. The billing file carries a customer name column and two broken rows, and the contacts file an agent name column, to show the mapping, validation and privacy steps.
The lab site sends these on a window event (assembl:live). Standing alone, this page uses a snapshot (prices, generation and weather taken 23 October 2026; retailers and residential prices 25 October 2026, top ten retailers only) and says so. No retailer system is connected.
Read-only by design: the connector reads bills, contacts and switch events and never writes to billing. Anything that changes a customer's plan, price or payment goes through the authority levels above.