The listing ends.
The relationship
does not.
You are hiring a Customer Lifecycle Lead for Property, to own acquisition, activation, retention and win-back, and the ad says you want someone AI-forward. This is a concept for the part of that lifecycle that is hardest to staff: the long, quiet middle.
“Acquisition is a campaign. Retention is a thousand small moments nobody has time for.”
The premise of this conceptThe listing that has been up for six weeks
An agent has a property that is not moving, a vendor asking why, and a renewal decision coming. The data that would answer the vendor’s question already exists — views, watchlists, enquiry rate against comparable listings. It has just never been assembled into something the agent can put in front of someone.
Your own job ad, posted this month, names the lifecycle stages and says the team is AI-forward. That is unusually direct — most companies we build concepts for have not said it out loud.
What happens now
The agent builds the story by hand on a Sunday, or has the conversation without it.
What it costs
Not the listing — the next one. An agent who could not answer the vendor lists elsewhere next time.
What the concept does
Prepares the vendor conversation from data you already hold, and stops before it sends.
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 property campaign
Six moments where a buyer or a vendor is waiting on somebody else, and what each wait could hand back instead.
The search keeps working while you are not looking, and only speaks up when something genuinely fits.
You walk into the first agent conversation already knowing what the street is doing.
The vendor hears how the first open home actually went on Sunday night, not the following Thursday.
The agent walks into the hard vendor conversation with the story already assembled.
Both sides can see which condition is actually holding things up, instead of guessing at each other.
The last weeks stop being a black box, so the move can be organised around something real.
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 agent. Four moments in the lifecycle.
Acquisition, activation, retention, win-back — the stages named in your own ad. Same agent, four very different conversations.
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.
When not to send is the answer
Lifecycle tooling fails by sending the right message at the wrong moment. These checks are mostly about restraint.
Drafts are held against the Fair Trading Act 1986, the Privacy Act 2020, and the Unsolicited Electronic Messages Act 2007.
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 lifecycle, on one screen
Illustrative and fictional. No production access is requested by this concept.
| Stage | Agents | Prepared | Waiting on | Status |
|---|---|---|---|---|
| Activation — first listing live | — | Diagnosis, week one | Lifecycle owner sign-off | Awaiting approval |
| Retention — vendor conversation due | — | Evidence assembled for the agent | Lifecycle owner sign-off | Awaiting approval |
| Win-back — last listing unsuccessful | — | Nothing drafted | A person, or nobody | Held — no draft |
| Acquisition — no history yet | — | General value, no false personalisation | Lifecycle owner sign-off | Awaiting approval |
| Frequency cap reached | — | Suppressed | Next week | Held by design |
| Renewal approaching | — | Performance summary prepared | Account manager | Awaiting approval |
Agent counts are deliberately blank. This concept has no Trade Me data and does not estimate them.
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
- Agent prompt — retention, vendor conversation
- Read
- Listing performance fields (placeholder) · comparable-set definition (placeholder) · lifecycle stage definitions from your job ad
- Rules held
- Fair Trading Act 1986 · Privacy Act 2020 · Unsolicited Electronic Messages Act 2007
- Refused
- No win-back was drafted for an agent whose last listing did not sell. No personalisation was written without behavioural history.
- 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
One lifecycle stage — retention, the vendor conversation. Six weeks. Not acquisition campaigns, not the consumer side, not pricing.
Access
Listing performance fields and your comparable-set definition. No vendor records. No enquirer details. No Braze connection.
Scorecard
Prompts agents acted on. Suppressions a person agreed with. Vendor conversations agents said were better prepared. One lifecycle lead’s answer to “would you put this in front of an agent?”
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
One lifecycle stage — retention, the vendor conversation. Six weeks. Not acquisition campaigns, not the consumer side, not pricing.
Read-only access, nothing that writes
Listing performance fields and your comparable-set definition. No vendor records. No enquirer details. No Braze connection. 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: Prompts agents acted on. Suppressions a person agreed with. Vendor conversations agents said were better prepared. One lifecycle lead’s answer to “would you put this in front of an agent?” 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 Trade Me 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.