The vendor's own match processor asks four decisions every run, after three clicks to reach it. Twenty sent and none liked has never been timed.
Match on fields, then send twenty. In the UK the register has a name and a product. It matches price to price and beds to beds. For a six-person brokerage the thing the client actually said on the phone lives in one head, and matches nothing.
By hand today
In the UK this stage has a name, the applicant register, and every agency suite runs one: Expert Agent, Alto. Neither publishes a price. The portal runs the same match for free: Rightmove sends alerts on matching criteria straight to the buyer, with no agent in the loop (faq.rightmove.co.uk). What nothing matches on is what the client said.
Expert Agent’s own manual shows what automatic costs: three clicks, then a dialog with four decisions by hand, every run, before a box says how many matched. Then the vendor writes the sentence against its own interest:
“If an Applicant has a price range of £0 to £0 it will match out to ALL properties.”
An applicant nobody finished matches everything, and you either send them the whole book or stop trusting the list. The register rots from incompleteness.
The form’s requirement is also the wrong object. A broker in Utah:
“We arrived at one, and they said ‘oh no, I don’t like this one’… We walked in, and they fell in love. I inquired what they didn’t like about the outside and they said they wanted a concrete driveway for the RV parking (not dirt) AN EASY FIX!!”
Paula Smith, associate broker, St George UT, on ActiveRain
A concrete driveway is a field on no form. A perfect filter would have missed the house.
What it costs you each week
Four decisions, every run
The choices the vendor manual asks of you each time the match processor opens, after three clicks to reach it. Nobody has timed the twenty sent and none liked, so this book prints no hour.
Source: Expert Agent manual, read 14 September 2026
The manual counts decisions, never minutes. The second cost is the list you stop reading. Once one unfinished applicant has matched everything, the match list reads as noise and the sending goes back to memory: you send what you recall, and the client hears from the portal first.
The build
Open Codex. Ask for the shortlist. It reads the register you keep and what each client said, and writes a shortlist with one sentence per match. A match it cannot explain in one sentence is dropped. You read the list before anyone is told.
Open Codex in the engine folder. The register is the spreadsheet you already keep, one row per property. Connect it: for Excel, the community Softeria/ms-365-mcp-server; for Airtable, Airtable’s own hosted server or domdomegg/airtable-mcp-server, which returns a hundred rows unless asked for more.
What the client said sits in two places: the three fields chapter 10 wrote, and the thread chapter 11 stored on the contact. Chapter 10 also recorded it in the Memory server from the protocol’s reference repository (github.com): one entity per client, each thing they said an observation. The sentence that fits no field, the driveway, goes there too. Then say what you want:
Read the register, every row, and tell me the total first.
For each client whose route is viewing or follow-up, read their three
fields, every observation on them in Memory, and the whole thread.
Shortlist at most three properties per client. For each, write one
sentence saying why this one for this person, in their words, and one
sentence saying what is wrong with it. Where a property misses a field
but answers something they said, keep it and say which sentence. Where
you cannot write the why in one sentence, drop it. Send nothing. Write
the shortlist in a sheet beside the register and report three counts:
clients with a shortlist, clients with nothing this week, matches
dropped as unexplained.
What comes back is the shortlist and three counts, waiting for you.
The one sentence is the whole stage. The deepest public build scores +25 for price, +25 for type, +20 for the zip code and +15 for the state, and tells the agent, never the client (github.com). Membership is exact, so a buyer who wants a three-bed at £500,000 scores zero against a £505,000 three-bed one postcode over. A model reading “somewhere for the RV” beside a row with a wide drive can say why.
Two honest limits, which Codex will tell you about. A model matching on prose can be too kind; that is why the unexplained count is reported and why a shortlist stops at three. And a call nobody wrote down matches nothing.
What it feeds
Telling them. The next stage sends each client their shortlist with its reason, on the channel they answered on. The number to read: properties the client replied about, beside the count sent, and the clients told nothing.
The shortlist you approved goes to the client with its sentence, on the channel chapter 7 picked; on WhatsApp, inside the window or by template, as chapter 8 built it. A client with nothing suitable this week is told that, which is the message the portal alert never sends.
The number that proves this stage worked: properties the client replied about, beside the count sent, and clients told nothing this week.
What stays with a person
The why, and the no. A person reads the shortlist and the flaw before the client does, and deletes the match that reads as a stretch. Telling a client that nothing suits them this month is a sentence a person sends. No alert ever will.
The tool cannot see the house from the kerb:
“Once in a while, I will have a buyer not want to see the inside of a house when we drive up. I always tell them that you can’t always tell a book by it’s cover”
Dotti Driver, Sky Realty, Austin TX, on ActiveRain
So a person reads every why and deletes the stretches, and sends the message that nothing suits them this month. The sentence that fits no field reaches Memory only if a person writes it down.
The tools you already pay for
Nothing new to buy.
Register is the spreadsheet you already keep; it gains a shortlist sheet beside it.
Memory holds what each client said, so the next run reads only what is new.
CRM gains the shortlist and its reason on the client, dated.
Three properties per client, each with a why and a flaw, read by you first. Then telling them can happen by itself.
Ask: Of the properties you sent last week, how many carried a sentence saying why this one, for this person?
This is stage 14 of twenty, after stopping viewings where nobody turns up and before staying in front of a client who buys in two years. The whole engine in order is the book, Building a real estate sales engine with Claude Code and Codex, end to end.