Booking is solved for $10 a month. The brief the caller needs is sold by nobody, so Claude Code writes it from the timeline the moment a booking lands.
A booking link and a blank page. The call lands in the calendar. What the person said, and why they replied, stays in the inbox. At a forty-person consultancy the caller opens the thread five minutes before and reads upward.
By hand today
“a crisp handoff around the prospect’s pain, current system, urgency, and likely fit”
A job advert for a Sales Development Representative at Hauler Hero, on Ashby, read 7 September 2026
That is what a company with a sales team asks the first person to write for the second. Four things: the pain, the system they use today, how urgent it is, and whether they fit.
In a smaller company the person who wrote the message often takes the call, and the brief is skipped because “I remember them”. You wrote to dozens of people that week. You remember the company name. You do not remember that they said the current system was “held together with spreadsheets”, which is the sentence the call should open with.
The booking is the easy half. One founder on Hacker News, asked whether a booking link puts people off: “we already filter for the non serious people” (zwayhowder). The link works. The brief is what nobody writes.
What it costs you each week
$10 a seat, a month, for Calendly Standard. Booking is solved and cheap. The brief, the part the caller actually needs, is not sold by anyone. So it is written by hand, or not at all.
Source: Calendly pricing page, read 7 September 2026
cal.com is free to self-host and will create the contact and the meeting in your CRM when someone books. What no booking tool does is read what the person said and put it on a page.
Count one thing in your own week: calls booked, and how many had a brief attached before the call began. Nobody notices the gap, because the caller improvises and the call still happens. What is lost is the opening, spent asking questions the person already answered in writing.
The build
Claude Code: a one-page brief from the timeline. When a booking lands, the tool reads everything the lead ever said and writes the page the caller needs. Profile, problem in their words, hypothesis, agenda, questions, watch-fors.
The brief is only possible because of chapter ten: every reply, step and note is on the lead’s timeline in the words it happened in.
Open Claude Code in the folder that holds your CRM access and the research files. Connect the booking tool so a new booking arrives as an event. Type:
When a lead is labelled interested and a booking for them arrives, read that
lead's full timeline in the CRM, the company research, and every message and
reply in order. Write a one-page brief: who they are, the problem in their
own words quoted from their reply, what we think is going on, an agenda for
the call, the questions to ask, and what to watch for. Add four short lines:
pain, current system, urgency, fit. Flag a booking that has a day but no
time, a person who is already open in another of our pipelines, and any
research that has not been checked since we first wrote to them. Save the
brief on the lead and email it to whoever is taking the call. Never send
anything to the prospect.
What comes back is a page, not a dossier. The problem section quotes the reply rather than paraphrasing it, so the caller can use the person’s own phrase. The hypothesis is marked as a guess. The watch-fors are the awkward things: a reply that said “not before the new financial year”, a title that changed since the research was done.
The flags matter as much as the page. A booking that says “Thursday” with no time is not a booking. A person already open in another pipeline means two people at your company may be talking to them. Unchecked research may describe a company that has since changed its name.
The brief is saved on the lead as an attachment and a timeline row, and a copy sits in briefs/ beside the other files. The caller gets it by email the moment the booking lands.
The one public brief-writer found reads a hand-typed file and is a toy. ArkOne’s own lane is the pattern, at docs/api/book-demo.md line 113: when someone books a demo, an internal briefing email goes out with profile, problem, hypothesis, agenda, questions and watch-fors. The other half is docs/crm-module.md lines 402 to 406: the lead page shows the person’s own facts read-only, with a door to the page that owns each, so the caller is never sent in blind. The reader builds their own version. There is no demo to download.
What it feeds
Reading the weekly number. A call with a brief is a counted event. Booked, briefed, taken, and what came of it. Proof: calls booked with a brief attached against calls booked.
Chapter twelve reads the weekly number and needs this stage to produce clean counts. A booking is an entry into the “in conversation” stage. A call taken is an exit, one way or the other.
Two numbers prove this stage worked. Calls booked with a brief attached, against calls booked, which should be equal. And the count of leads in conversation, read from the CRM rather than from memory.
What stays with a person
The call, and whether to take it. The tool writes the page. A person decides if this call is worth an hour, and then does the talking.
Whether to take the call at all is a judgement about fit that the four lines inform and do not make. A founder who reads the brief and politely declines the call has used this stage well.
The call itself is the point of the whole engine. The moment the person relaxes because you quoted their own sentence back to them is not a thing a tool produces. It is a thing a tool makes room for.
The tools you already pay for
Nothing new to buy.
Calendar: the free or paid booking tool you have; a booking becomes an event.
CRM: the timeline from chapter ten is the source; the brief lands back on the lead.
Mailbox: the brief arrives as an email to whoever takes the call.
The research: the company file from chapter three, checked before it is trusted.
No meeting-prep product and no SDR. The timeline you already keep, read once.
Every booked call arrives with its page. Then the weekly number has something true to count.
Ask: Who took your last booked call, and what did they know walking in?
This is chapter eleven of twelve, after logging everything without typing and before reading the weekly number. 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.