The CRM is true for an hour after the Friday update. Codex writes every send, reply, stop and step to the lead as it happens, in the words it happened in.
Friday afternoon, typing up the week. The CRM is true for an hour after the update and drifts for the other six days. At a thirty-person distributor the update is a chore the founder does last, if at all.
By hand today
“logging activity, tracking touches, maintaining clean account and contact data, and making sure the team can trust what is in the CRM”
A job advert for a Sales Development Representative at Hauler Hero, on Ashby, read 7 September 2026
That is a duty in a sales hire’s advert. Typing what happened into the system so that the rest of the company can trust it. Another advert tells the hire to “Log activity in real time”, an instruction only written down because nobody does it.
In a smaller company the log is whatever the founder remembers on Friday. Sent Tuesday, replied Wednesday, called Thursday, and by Friday the call note reads “good chat, follow up”. One user on Hacker News on why CRMs go stale: “most of the time colleagues don’t bother to update records properly” (flavaz).
The cost arrives when someone opens the lead before a call and has to rebuild the story from three inboxes.
What it costs you each week
$39 a seat, a month, for the Pipedrive plan where email sync begins. That buys email logged. LinkedIn, calls and a stage move are still typed. The typing is the part that was supposed to go away.
Source: Pipedrive pricing page, read 7 September 2026
Every CRM prices email capture as an upgrade and stops there. The LinkedIn message, the call you took, the moment a lead moved to “in conversation”: those are typed by a person or they are not recorded.
Count the two kinds of row in your own CRM this week: rows a system wrote, and rows a person typed. The ratio is what this chapter changes.
The build
Codex: every event becomes a row. Sends, replies, stops, pauses and steps from the last three chapters land on the lead as they happen, in the words they happened in. Nothing is overwritten. Nothing is invented.
Three rules shape the build, and they matter more than the code. The timeline only grows: a row is never edited or deleted, so the story of a lead is the order things happened. An update never blanks a field: if a new record arrives with no phone number, the one you already had stays. And only real events are logged, with the actual words in the body. A sync, a view or a check is not an event.
Open Codex in the folder that holds sends.log, replies.log and due.json from chapters seven to nine, with write access to your CRM. Type:
Read sends.log, replies.log and due.json. For every send, reply, stop, pause
and step change, write one activity to the lead in the CRM: the time, the
kind, and the actual words in the body. Only append; never edit or delete
a row. When you update a lead, change only the fields you have new values
for, and never blank one. Do not log a view, a sync or a check, only things
that happened. When I paste a LinkedIn reply or type a call note and name
the lead, attach it as I wrote it. Each run, tell me how many rows you
wrote, and list every lead with no event in thirty days.
What comes back is a short receipt each run: rows written, leads touched, and the silent list: leads with no event in thirty days. When you paste a LinkedIn reply, Codex asks which lead if it cannot tell, attaches the words, and labels it with the seven labels from chapter eight.
Everything is saved on the lead in the CRM. A line per row also goes to capture.log, so at the end of the week you can count rows the system wrote against rows a person typed.
Two open-source CRMs, Twenty and EspoCRM, already bind synced email to a person and write it to a timeline. Neither captures a LinkedIn message, a call or a stage move. This build captures all three.
The pattern is ArkOne’s own CRM, at docs/crm-module.md: line 22, every meaningful event lands on an append-only activity timeline; line 61, upserts never blank a field; lines 94 to 98, only real events are logged, with the content in the body, because the timeline is what the next conversation is prepared from. The reader builds their own version. There is no demo to download.
What it feeds
The handoff to a call. The next chapter builds a brief from the timeline. It can only do that if the timeline is true. Proof: rows the system wrote against rows a person typed.
Chapter eleven hands a warm reply to a call, and it reads the timeline to do it. A timeline with the actual words of each reply gives the caller the person’s own language. A timeline of “good chat, follow up” gives them nothing.
Two numbers prove this stage worked. Rows written by capture against rows typed by hand, week on week. And leads with no event in thirty days, a short list someone reads on Monday.
What stays with a person
What was said on the call. The tool records what a system can see. The note only a person can write is still written by a person.
A call has no log file. What the other person said, what they meant, and what you promised exist in one head until they are written down. The tool cannot capture that, so it makes the note easy to attach and keeps it in the words you typed, on the day you typed it.
The second judgement is the stage move. The tool can see that a reply arrived. Whether it means the lead is now in conversation is a reading of tone, and a person makes it. The tool logs the move with the time and who decided it.
The tools you already pay for
Nothing new to buy.
CRM: the one you have, on whatever plan; the timeline is written to it, not bought from it.
Mailbox: the same seats, already producing the send and reply logs.
A text file: capture.log, for counting captured rows against typed ones.
LinkedIn: the reply pasted by hand, attached in the words it was written in.
No sync plan and no data hygiene hire. The files from the last three chapters, written onto the leads.
Log only what happened, in the words it happened in. Then the caller walks in with the whole story.
Ask: When did your CRM last record something nobody typed?
This is chapter ten of twelve, after following up without remembering and before handing a warm reply to a call. The book, Building a real outbound engine with Claude Code and Codex, end to end, runs the whole engine in order, from writing down the market to reading the weekly number, one chapter per stage. A free starter edition for firms under fifty people is coming through the 100k programme.