She asked for a brochure.
She needs an answer.
Those are not the same.
A family enquires about a village for their mother. What arrives is the pack every family gets. This demonstrates the alternative: the same published material, assembled around the three things this family actually said, with one question going back the other way.
“The pack is already the most requested thing on the site. Today it arrives identical for everyone.”
Rosewell Villages · an invented exampleThe wait between asking and knowing
Three siblings in three cities are trying to work out whether their mother can afford this, whether she would be happy, and whether she would have to move again later. The pack answers all of it, somewhere, in eighty pages. Nobody reads eighty pages on a Sunday.
Every retirement group in the country already publishes the material a worried family needs. The gap is never the information. It is that the information arrives in the order the brochure was written in, not the order this family is worried in.
What happens now
One pack for every family. The questions it did not answer arrive by phone, one at a time, to whoever picks up.
What it costs
The most emotionally loaded decision a family makes, handled with a document that does not know their situation.
What the concept does
Opens the pack at the page that answers their worry, in their numbers, and stops. An advisor sends it.
Every village moment, one pattern.
Each of these is a moment your customer already spends with you. Each can carry what the phone above shows: watch the work, earn the wait, answer one thing.
Be relevant — right thing, right moment · Be respectful — short, skippable, quiet by design · Be measurable — real impact, on the record · Be Aotearoa — built here, for how Kiwis actually wait
Every wait in a retirement village decision
Six moments in a village decision where a family is waiting. Most of them are emotional before they are administrative.
A family can read the honest version before anyone has to make a phone call.
Their actual worry is answered on the first page, not somewhere in eighty.
A family stops ringing to check, because the checking comes to them.
Nobody in the family has to hold the whole week in their head.
The family hears from a person before the worry has time to grow.
The family can see the villa moving instead of ringing to find out that it is not.
Four steps, every time.
- The signalSomething in your own systems 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 a customer 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, 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 on this page carries its source. Overseas figures are shown as overseas figures — we have not found a published New Zealand equivalent, and we will not invent one.
One enquiry. Four families.
The same published pack, assembled four ways. Nothing sends without an advisor, and the situations that need a person say so.
A template sends the same thing to everyone and changes the name. What matters here is the case that should get something different — or nothing at all.
The rules beside each draft are placeholders. A pilot replaces them with your actual policies. We have not seen those, and this concept does not guess at them.
The checks that run before a family reads anything
This is the most emotionally loaded category assembl builds in, so the guards are the interesting part, not the assembly.
Drafts are held against the Retirement Villages Act 2003, the Fair Trading Act 1986, the Privacy Act 2020, and the Health Information Privacy Code 2020.
Press run to see what it catches — and what it refuses to produce at all.
One room. Your people, your agents, every action on the record.
Every concept on this page would run inside a private room like this: your team and the agents in the same space, drafts appearing with receipts, a named person saying yes. It runs on infrastructure you approve — and what is said in the room stays in it.
receipt sources: your rate card · rules: yours · held for approval
Client information stays in your room. Six months later, “where did this come from?” is one line, not a search.
Yours
Runs where you approve — your own room, your own record. Nothing in it leaves it.
On the record
Every agent action lands as a line a person can read — not a log only a vendor can open.
People decide
Drafts wait for a named person. The room shows who said yes, and when.
This panel is a concept picture, not a live room — a pilot stands up the real one, on infrastructure you approve.
The enquiries, before anything sends
Illustrative and fictional. No production access is requested by this concept.
| Enquiry | Count | Prepared | Waiting on | Status |
|---|---|---|---|---|
| Worried about cost | — | Pack opened at the exit fee | Advisor sign-off | Awaiting approval |
| Worried she will not settle | — | Pack opened at village life | Advisor sign-off | Awaiting approval |
| Siblings in three cities | — | One pack, three covering notes | Advisor sign-off | Awaiting approval |
| Describes current care needs | — | Nothing assembled | A named advisor | Held — no pack |
| Mentions a bereavement | — | Nothing assembled | Nobody — deliberately | Held — no pack |
| Contact details incomplete | — | Pack held | Verification | Parked |
Counts are blank because this is a demonstrator. There is no Rosewell, and therefore no data.
Every draft carries its own working.
Not a log somebody has to go and find. The provenance travels with the work — what it read, which rules it held, who must approve it, and what it refused to do.
This matters most on the day someone asks why it said what it said.
- Artefact
- Information pack — family worried about cost
- Read
- Invented published material for an invented village group · enquiry fields: region preference, stated worry, care-needs language, bereavement language. No health records.
- Rules held
- Retirement Villages Act 2003 · Fair Trading Act 1986 · Privacy Act 2020 · Health Information Privacy Code 2020
- Refused
- No fee was calculated. No recommendation was made. No pack was assembled where the enquiry described current care needs or mentioned a bereavement. No urgency was used.
- Approver
- A named person. Unsent until then.
- Prepared
- —
- Reference
- —
What this will never do
It does not send. It prepares, and a named person sends. It does not publish to any channel, commit spend, move money, or make a decision that belongs to a person. It does not pretend to be a person — every draft says it was prepared by a machine and approved by a human.
No production access is requested by this concept.
Scope
In a real engagement: one enquiry type, start to finish, six weeks. Not the sales conversation, not pricing, not the care assessment.
Access
Published pack material and the field names that mark stated worry, region preference and any care or bereavement language. No health information. No resident records.
Scorecard
Packs an advisor sent without rewriting. Held cases an advisor agreed should have been held. Calls the pack avoided. And whether an advisor would put their name to what arrived.
Fail any line of the scorecard and we change the design or stop.
What a pilot actually asks of you.
Written out in full, because the honest version of this 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. Expect about two hours a week — reading drafts, not managing a project.
One situation, not the business
In a real engagement: one enquiry type, start to finish, six weeks. Not the sales conversation, not pricing, not the care assessment.
Read-only access, nothing that writes
Published pack material and the field names that mark stated worry, region preference and any care or bereavement language. No health information. No resident records. No production credentials, no write permissions, no access to anything the pilot does not need.
Your actual rules
The policies, limits and words the drafts must be held against. Every rule 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: Packs an advisor sent without rewriting. Held cases an advisor agreed should have been held. Calls the pack avoided. And whether an advisor would put their name to what arrived. 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
Pick a verb.
Not “book a demo”. Any of these is a real next step, and the last one is a perfectly good answer.
What is the one constraint we have got wrong?
Every concept is built from the outside. There is always something about how Rosewell actually runs that we could not see. One line is enough.
Opens your mail app to assembl@assembl.co.nz. Nothing is collected by this page.