Customer Lifecycle Lead · Property — a concept

The lifecycle,
already assembled.

A working concept of the intelligent, automated property journey this role is built to create — Acquisition, Activation, Retention and Win-back, orchestrated across email, push, in-app and content cards, with the proof built in.

See the journeys

Built on your Braze + data layer — orchestration, not replacement.

The Kiwi's view

Every journey starts with real intent.

Tap through the phone: a first-home buyer's search, understood and assembled — not a wall of 200 listings and a spammy alert. This is the experience the lifecycle journeys below actually orchestrate.

The Trade Me promise, delivered: be the place Kiwi look first — by being the place that already gets it.

9:41Trade Me Property5G · 84%

Property

Watching your search
Lifecycle journeys

Acquisition. Activation. Retention. Win-back.

The four journeys this role owns — each a triggered, agentic ecosystem, not a batch send. Pick one to see its trigger, the journey logic, and the messages that fire across channels.

Journey logic
What the Kiwi receives
Intent signals → next best message

Segmentation you don't have to hand-build.

Real-time intent, not last month's segment. Tap a signal to see the next best action the journey fires — personalisation at scale, driven by behaviour.

Next best action

Every signal is a fork in the journey. The agent reads it and picks the message that moves the Kiwi forward — no manual segment build, no batch-and-blast.

GenAI content studio

Copy for the moment, in seconds.

The brief asks for GenAI to cut time-to-market. Here it is: pick a journey moment and a tone, generate on-brand variants ready to test. Days of copywriting become a click.

Ready to test
Hypothesis-driven experimentation

Every journey earns its logic.

Not opinions — tests. A live hypothesis, two variants, and the result promoted into the journey automatically.

Hypothesis: a price-drop push at 7pm beats the 9am send for return-to-site.
Variant A — 9am
Variant B — 7pm
What we are actually asking

What this will never do

It does not send. It drafts, and a named person sends. It does not publish, write back to Braze, buy media, commit spend, or contact a member directly. It never uses Trade Me data — every figure and journey on this page is illustrative. And where the right answer is to say nothing, it says nothing: a win-back after a listing that did not sell is suppressed, not sent.

No production access is requested by this concept.

The pilot ask

Scope. One lifecycle stage — retention, the vendor conversation — for six weeks. Not acquisition campaigns, not the consumer side, not pricing.

Access. Listing performance fields and your comparable-set definition. No member records, no enquirer details, no Braze connection.

Scorecard. Journeys shipped without rewrite. Suppressions a person agreed with. One lifecycle lead's answer to whether they would keep it.

Fail any line of the scorecard and we change the design or stop.

Three ways to reply

Pick a verb.

Not “book a demo”. Any of these is a real next step, and the third one is a perfectly good answer.

The unfinished pane

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.

Send it →

Ko tā mātou he whakarite i te mahi. Mā te tangata te whakatau. We prepare the work. A person decides.
assembl NZ Limited · NZBN 9429053514950 · assembl@assembl.co.nz · Tāmaki Makaurau Auckland, Aotearoa New Zealand

Lifecycle copilot · for the marketer