Eko Playbook — Real Estate

The assistant you've been dreaming of. Now available.

We build it. We seed it. You run it.

A listing assistant in your own AI — loaded with all your listings, your preferences, your custom workflows and your daily briefing before you type a word. It drafts. You approve. Nothing sends itself.

Notion Drive Gmail Calendar Web
Eko Media Limited · Auckland · as at 9 August 2026
Why it exists

Take the day. Nothing drops.

Agent walking the fairway, his assistant glowing above his phone
ON THE 9TH“Seaview's week-4 update is drafted — approve it whenever you like.”
Agent on a fishing charter, earbud in, assistant on the phone beside him
OFFSHORE“22 through Saturday's open. The draft will be ready when you dock.”
Agent laughing at lunch with friends, assistant quietly on the phone
AT LUNCH“Photographer's email filed. Nothing needs you before 3pm.”
Agent courtside at her daughter’s netball, assistant on the phone at her side
COURTSIDE“Settlement confirmed — the review request is drafted for after the game.”

The assistant holds the thread — drafts ready, files filed, nothing sent without you. The business keeps moving; the send button waits for you.

Watch — 37 seconds

See it working.

Your Listing Assistant — drafted by AI, approved by you.

Step 0 — zero access needed

What flows in. What comes out.

Your listings syndicate to the public portals automatically — so that's where we seed from. No access to your agency's website or systems. No IT project. No head-office ticket.

Trade Merealestate.co.nzhomes.co.nzOneRoofRateMyAgent
Your conversations, email, calendar and the portals flow into your assistant; appointments, updates, review requests, stories, posts and briefs come out

Portals seed your stock · the discovery interview seeds your knowledge · your real past updates seed your voice. Pre-loaded listings stay marked portal-sourced until you verify them. Client and vendor personal details are never touched.

Step by step

Four steps. Your time: 30 minutes.

1

Discovery — three legs

① Outside-in audit② AI extraction③ Expert interview

What AI says about you · what your AI already knows · what only you know. Anything answered once is captured and never asked again.

Eko · before your session
2

Build the memory home

Listings database + Drive folders + your voice file — with the rules installed: draft-and-approve, confirmed saves, the legal fence.

Eko · before your session
3

Seed & verify

Your live stock pre-loaded from the portals; sold history becomes a story backlog. Then a clean start: zero inherited memory, one source of truth.

Together · the 30-min session
4

Handover

Installed in your ChatGPT, Claude or Gemini. Connectors on, cheat sheet in hand, one real vendor update already drafted together. Memory audits at week 2 and month 1.

You · from day one
The assistant at four work stations: read, database, load, deliver — handing the finished phone to its owner
YOURS, FOREVERNotion listing memory · Drive files · your voice — in accounts you own. Leave anytime, keep everything.
NEVER TOUCHED Agreements · S&P · vendor IDs — not connected, not read, not requested. Ever.
A day with it

Seven phrases do everything

YOUR AI · project: Listing Assistant

Reads your calendar, listing memory, inbox flags and market headlines — when you ask. Never watches your accounts on its own. Never sends anything itself.

Make it yours

Same brain. Your choice of character.

Attitude, energy, formality, mannerisms — set in the assistant's instructions, installed in the AI you choose. Try the same briefing four ways:

▶︎ REAL RECORDINGS Every voice below was captured from ChatGPT's own voice mode — the engine your assistant actually speaks through. Character and voice are chosen with you at setup, and you can change them any time.

Recorded from your AI's real voice mode — what you hear is what you get. Exact voice options vary by platform (ChatGPT · Claude · Gemini), so the final pick happens with you in the session.

After handover — the engine

Your admin becomes the signal AI reads

The flywheel: sold, tell the story, page video post, all linked, AI reads you, AI recommends you — every sale feeds the next123456

It starts at ① SOLD → ② tell the story → ③ page·video·post → ④ all linked → ⑤ AI reads you → ⑥ AI recommends you. Then the next sale starts further ahead.

Reviews, on timeDrafted at settlement, in your voice. Sent by you.
Updates that compoundSaved weekly — the campaign story writes itself.
The sold storyIt interviews you while it's fresh. One capture, many assets.

Not one lever. A rack of them.

Sold-story enginepage · video · GBP · socials per sale Suburb pagesown the questions buyers ask Content-rich articlesanswers AI can quote Directory layerevery surface, paste-ready, identical Review velocitysignal where shortlists are built GBP cadencesuburb-anchored, always current

And every lever links to every other. Published once, it's a post. Published as a linked network, it's a citation.

DefaultForward to Eko

Say “sold”, forward the capture. We build the set — you approve before it publishes.

Self-serveDo it yourself

Same capture — the assistant drafts it all; you publish it your way.

Our side of the glass

You talk to yours. We work with ours.

Your capture lands with us, and we sit down with our own AI to do the technical half — the part that makes it citable:

Working alongside AI to place content, write schema and link it together
EKO × AI · BUILD LOG
① Placethe story onto your citable hub ② Schemastructured data so machines can lift your facts ③ Linkpage ↔ video ↔ GBP ↔ socials ↔ profiles ④ Measurere-run the same questions, dated, before/after

Your side: seven phrases. Our side: place · schema · link · measure — approved by you before anything goes live.

YOUR BRAND, PRE-LOADEDLogos · exact colours · fonts · compliance lines — every draft comes back on-brand, unprompted.
ONE NETWORK, ONE NAMEIdentical name-address-phone across every directory and profile — consistency is how the machine becomes certain it's you.
Beyond the playbook

Name a task. We build the workflow.

Anything you do by hand — or pay another subscription for — we can usually build inside the assistant you already run.

Listing copy, every channel Open-home follow-up drafts Buyer-enquiry triage Call & meeting summaries Monthly market digest Newsletter drafting Translations for multilingual buyers Photo sorting & captions Anniversary & check-in reminders …name yours
01 · You name itDescribe the chore

In plain words — "every Monday I waste an hour doing X."

02 · We scope itHonest feasibility first

If today's frontier models can do it reliably, we build it. If they can't yet, we say so and park it — we don't fake it.

03 · It runs in your assistantSame rules apply

Same memory, same voice, same approval-first posture — and one subscription fewer on the credit card.

Same models underneath — built where your memory and voice already live. Scoped and quoted per build; approval gates matched to what it touches.

The assistant guarding a locked folder while passing a draft across the desk for approval
The rules · and what it won't do

Why you can trust it at 9pm on a Tuesday

Say “approved” or it doesn't save.Every save confirmed back. No silent writes.
It drafts. You send.Never emails a vendor, never posts, never publishes.
It never invents a number.Unknown means it asks — or marks it unknown.
Vendor privacy by default.First names only unless the vendor approves more.
It won't act on its own.Briefings and checks happen when you ask. Nothing auto-sends.
It won't touch the legal layer.Not connected, not read, not summarised.
It won't game reviews.No incentives, no scripting. Real or it's worthless — to the platforms, the machine, and your licence.
Setup honesty.Portal-sourced until verified · your voice from your real updates · unknowns marked, never filled.
Next step

One 30-minute session

Audit done. Build done before we meet. You leave having drafted one real vendor update with it. From there — seven phrases.