No agent has published the hours the typing takes, so this page prints none. A contact with nothing written on it starts the next call blind.
The best CRM is the one you use. Two agents in one thread said it, unprompted. Nobody says it about a spreadsheet. It is an admission. For a six-person brokerage the record is whatever six people typed after the call, which is mostly nothing.
By hand today
Nothing runnable does this stage, so there is no product to concede. Nine public repositories were opened at source, and every logger in every one is a form. The best says so in its own code: “One-tap call logging is the highest-frequency write in the product, so the POST body is deliberately small”, and a person still opens the app after the call and taps. Not one repository has any telephony at all.
So the record is typed, which mostly means it is not:
“I use Follow Up Boss - there’s so many models of this but the best CRM is the one you use.”
Lien Vuong, agent, Boston, on BiggerPockets
“I use Mojo Sells, but as stated here, the best CRM is the one you use!” Steve Bracero, agent, Westboro, same URL
The sentence exists only for a category where leaving it unused is normal. The people doing the typing name the typing:
“Having to keep up with the data input from each client is a bit tough”
Gary P., principal broker, on Capterra
What it costs you each week
Zero, on the record
No agent has named the hours the typing takes, so this book prints none. The cost is paid in absence. A contact with nothing written on it is a call the next person starts blind.
Source: no hours figure exists in any fetchable source; Capterra reviews of Follow Up Boss, Top Producer and LionDesk, read 14 September 2026
A buyer answered on Tuesday from a personal phone is, on the record, a buyer nobody answered; chapter 12’s timer moves that lead away from the person working it, and chapter 20 reports on Monday a week quieter than the week was.
“I will sometimes get communication from a client and it won’t alert me.”
Haley J., real estate agent, on Capterra
The build
Open Codex. Ask for the witnesses. The tool that saw the event writes it: the calendar the meeting, the mailbox the email, the webhook the message. Nothing is summarised and nothing is invented. A contact silent for thirty days is a count, never a nag.
Open Codex in the engine folder. Connect the CRM’s own server: HubSpot’s, at mcp.hubspot.com, writes “calls, emails, meetings, notes, and tasks” on a contact (developers.hubspot.com). Connect the calendar and the mailbox through taylorwilsdon/google_workspace_mcp (github.com). The WhatsApp thread is already in chapter 8’s webhook store. Write witnesses.md once: which calendar, which mailbox, which number, and how a contact is matched, phone first, then email. Then say what you want:
Every fifteen minutes, read the calendar, the mailbox, the message store
from chapter 8 and the call log. For each event whose other party
matches a contact in witnesses.md, write it on that contact once: a
meeting with its time, place and who came; an email with its subject
and body; a message with its text and direction; a call with its time
and length. Use the event id so nothing is written twice. Never invent
an event, never summarise one, never write on a contact you cannot
match; list those in nomatch.md. Each Monday, count every contact
with no event in thirty days and print the count beside the total, with
their names.
What comes back is a script, a schedule, and two Monday numbers with names under them.
Three honest limits, which Codex will tell you about. Calls are the thin part: no public server executes a call log (Twilio’s hosted one “does not execute API calls on your behalf”, twilio.com), so a call is written by a script against the Voice REST API of the number you rent, or the CRM’s own calls endpoint; a call from a personal mobile is seen by no API and written by nobody, and the Monday number shows it as silence. A HubSpot account with sensitive data turned on blocks the activity objects (developers.hubspot.com). And Salesforce is the exception: its vendor server has one data tool, run_soql_query, and no record write (github.com), so there the writing goes by script.
What it feeds
The Monday number. The last stage reads which stage leaks. It can only read events that were written, with what was said. The number to read: interactions in thirty days with a record, beside the total from the phone and WhatsApp.
Chapter 20 reads the Monday number and says which stage is leaking. It can only count events that were written, and the next conversation is prepared from what was kept, which is why the build writes the email body and never a line saying an email happened.
The number that proves this stage worked is client interactions in the last thirty days with a record attached, beside the total from the phone and the message store. A CRM measured against itself reads complete every time.
What stays with a person
What was said in the room. A record shows a budget was mentioned. Only the person on the call heard whether it was said with hesitation. The note only a person can write, and the decision to leave something delicate unwritten.
The machine writes what happened. A person writes what it meant. A budget on the timeline is a number; that it was offered reluctantly is a note only the person in the room can write. Keeping a divorce off the record is a judgement, made each time.
What a person does write goes into fields, the nine from chapter 10 and the outcome from chapter 13, never a transcript. A transcript on a timeline is one more thing nobody reads.
The tools you already pay for
Nothing new to buy.
CRM is HubSpot through its own server, or Pipedrive through mcp.pipedrive.ai (pipedrive.com). Follow Up Boss has /calls, /textMessages and /notes on its API and one live community server, by a broker in Austin, with “full read AND write access to your Follow Up Boss account”: one person’s project, and it can delete.
Calendar and Mailbox are one community server.
Number is chapter 8’s business number, plus any rented line.
Every meeting, email, message and call on the contact, written by the tool that saw it, and a count of who has gone quiet. Nobody typed a word.
Ask: Of the conversations your team had last week, how many are on the record this morning, and who counted?
This is stage 16 of twenty, after staying in front of a client who buys in two years and before building the pitch from what you already know. The whole engine in order is the book, Building a real estate sales engine with Claude Code and Codex, end to end.