Nothing in the category does this stage: every tool starts at a filter form you have already filled. The sentence comes from your own past work.
Pick an asset type and hope. Offices, say, in one submarket. A trigger if you can name one. Then the portal filter. For a six-person brokerage the answer to who actually calls sits in a year of proposals, unread.
By hand today
Nothing does this stage for you. Every tool in the category starts one step later, at a filter form you have already filled. The trade has written almost nothing down about how it chooses, so this chapter is short.
What it has written is the vocabulary, in vendor copy: define “property type, size range, submarket, and the primary trigger signal you’re targeting (lease expiration, loan maturity, long tenure, etc.)” Prospect by Buildout, prospect-by-buildout.com
Take only the sequence. Four filters, then a category. Owners.
What the category hides is who is behind the asset.
“Many properties owned by LLCs are actually small-time investors, individuals, and families.”
tresil, on Hacker News
He goes on: “whether individuals who own 1-5 properties, or huge institutional investors who own thousands.” A family with three flats and a fund with a thousand wear the same legal clothes on the title. The category does not say which one calls you. Your own past work does.
What it costs you each week
Zero published hours
Nobody has measured what this stage costs, and this chapter will not guess. The traceable cost lands four chapters on, when a wrong definition sends you to a credit bureau.
Source: none found in the instructional material the trade publishes, checked 14 September 2026
A definition that lands on anonymous holding companies pushes the whole chain into bought ownership data; chapter five shows that lane. One that lands on named owners never goes there.
The build
Open Claude Code. Ask who called. It reads a year of proposals off disk, one row per job: who called, what asset, what for. It groups the rows and writes one sentence per group, with the count behind it. You keep one, and the list is built from it.
Open Claude Code in a new folder. Point the Filesystem MCP at your proposals and closing files, add the Memory MCP so what it learns survives the session, and say what you want:
Read every proposal and closing file from the last twelve months. Write
one row per file: the date, who called and what kind of entity, the
asset, the submarket, the trigger if the file shows one (never guess;
write unknown), what I was asked to do, whether it closed. Group the
rows by what I was asked to do and by who called, and write one
sentence per group: the entity, the asset, the submarket, the problem
that made them call. Save work.csv and target.md, keep each group in
memory, and report the row count behind every sentence.
Back come a few sentences, a count under each. Fourteen rows behind a sentence is a problem people call you for; one row is a job you once took. Keep one, two at most, at the top of target.md.
Two honest limits. The Filesystem MCP reads only the folders you allow it, so work that lives in an inbox or a WhatsApp thread never becomes a row. And the sentence is a first draft: who is behind an asset is invisible until the list exists, so chapter three sends rows back here. Define, then let the list correct you.
What it feeds
The list. The next stage lists every owner in your patch from the public record, filtered on your sentence. The number to read: rows that survive the next gate, against rows in total.
The public record has no column called problem, so the next stage filters on your sentence.
The number that proves this stage worked arrives two chapters on, at the qualification gate. Lose nine rows in ten there and the sentence was a category wearing a longer coat; it comes back here.
What stays with a person
Which clients you want. The tool counts who called. It cannot say which you would take again, or turn down. You rule once, in the file the tool reads, and the next run applies it.
The tool can tell you that eleven of last year’s calls were families selling a second flat and three were funds. It cannot say which you want more of. None of this is a data problem. You choose, write it under the sentence in target.md, and the list stage reads both.
The tools you already pay for
Nothing new to buy.
CRM holds the closed deals, if you logged them.
Folders hold the proposals it never saw.
Portal filters run on asset and price, never on why an owner might sell.
One sentence naming who calls you and why, with the past work counted behind it. Then the list can be built.
Ask: If you wrote down the one problem people call you for, how many files from last year would fit it?
This is stage 1 of twenty, before listing every owner from the public record. The whole engine in order is the book, Building a real estate sales engine with Claude Code and Codex, end to end.