A lead does not carry dates. It carries its messages in order, and the next one is the first not yet sent. A reply stops it, out of office pauses it.
A reminder, a calendar, a memory. The second message depends on somebody noticing that the first one got no answer. At a twelve-person agency the noticing is done by the founder, on the train.
By hand today
“My follow ups are always 4 levels deep, and in the final mail, I make sure I tell that it’s the last one.”
hunter-2, on Hacker News, read 7 September 2026
That is a sender with a rule who keeps it. Most people keep the same rule for the first week. Then a reply arrives on one thread, a call fills the afternoon, and the leads from Tuesday are never written to again.
The usual fix is a calendar. Each lead gets a date. The date arrives, nothing has been drafted, and the reminder is snoozed. A week later there are dozens of snoozed reminders and none of them says what to send.
The person on the other end has a rule too. On a follow-up to a message with no way to opt out, one recipient on Hacker News: “I’ll tell gmail to block you” (andrewljohnson). The follow-up that arrives after someone has said no is the one that costs the domain.
What it costs you each week
$59 a month, per user, for one drip campaign on the cheapest Dripify plan. That is the going price for not having to remember. Every other sending tool bundles it, which is why nobody prices the stage on its own.
Source: Dripify pricing page, read 7 September 2026
The sequence is the product in every outreach tool, so its cost usually hides inside a seat you already pay for. Dripify is the one that meters it.
The unpaid cost is the one to count. Open your CRM and find every lead that has been written to once, has not replied, and has no drafted next message waiting. No follow-up statistic is given here; every one found was a vendor’s own send log.
The build
Claude Code: by position, never by date. Each lead carries its messages in order. The next one is the first not yet sent. A reply stops the sequence. Out of office pauses it. Nothing goes out without your yes.
The rule is small. A lead does not carry dates. It carries its sequence from chapter six, in send order, with each step marked sent or not sent. The next step is always the first unsent one. The only setting is the gap: how many days of silence pass before the next step is due.
Open Claude Code in the folder that holds leads.csv, the sequences, sends.log and replies.log from the last three chapters, the last of them the sorter. Type:
Read leads.csv, the sequences folder, sends.log and replies.log. For every
lead, the next step is the first step in its sequence not yet sent. Never
put a date on a lead. Each morning, list every lead whose last step went out
more than the gap in settings.json ago with no reply, with its drafted next
step. Any reply from replies.log stops the sequence, except out of office,
which pauses it until the return date. Flag any lead that is due and has no
draft. When the last step has gone out and the gap has passed, put the lead
on a list for me to close. Hand the due list to the send budget and wait.
What comes back is three lists. Today: each lead, its step, the drafted message, and its days of silence. The problem list: leads due with nothing drafted, which should be empty. And the leads that reached the end of their sequence unanswered, waiting for you to close them.
The due list goes to the send budget from chapter seven, which decides how many go out under each mailbox’s cap. The position is written back to the CRM, so the lead’s page says “step three of four, sent” without anyone typing it. due.json beside the CSV holds today’s list.
One public tool, OpenOutSend, follows up by position, stops on a reply and closes a lead as unresponsive. It does this for email alone, inside a system that needs a paid list source. This build runs from your own CRM, across email and the LinkedIn notes you send by hand.
The pattern is ArkOne’s own CRM rule, at docs/crm-module.md lines 100 to 103: outreach is planned by position, never by date, and a lead carries a sequence[] in send order. Dated follow-ups were tried and removed, because nothing ever wrote one. The reader builds their own version. There is no demo to download.
What it feeds
Logging without typing. Every step sent, every stop and every pause is already an event. The next chapter writes them to the CRM. Proof: leads due for a follow-up with no draft, zero.
Chapter ten makes the CRM true without typing, and it can only do that if every follow-up is an event with a lead, a step and a time attached. A sent step is an event. A stop on a reply is an event.
Two numbers prove this stage worked. Leads awaiting a follow-up whose next step is not drafted, which should be zero every morning. And sequences stopped by a reply against sequences that ran to the end unanswered, the first honest read of whether the messages work.
What stays with a person
The last message, and the giving up. A person writes the line that says this is the last one, and decides when a lead is closed.
The final step in a sequence says it is the final step. That sentence is written by a person, because it is a promise, and the tool keeps it by never sending anything after it.
Closing a lead is the other judgement. The tool lists a lead when the last step has gone out and the gap has passed. Whether it is closed, parked for a quarter, or handed to someone else is a decision about the relationship, and the tool does not make it.
The tools you already pay for
Nothing new to buy.
CRM: the sequence lives on each lead, with each step marked sent or not.
Mailbox: the same seats, under the caps from chapter seven.
A settings file: the gap in days, in one place, for every lead.
LinkedIn: the follow-up note sent by hand, with the tool counting the step.
No sequence tool and no drip plan. A list of messages in order on every lead.
Follow up by position, never by date. Then the CRM can log it without anyone typing.
Ask: How many leads in your CRM are waiting for a follow-up nobody has drafted?
This is chapter nine of twelve, after reading and sorting every reply and before logging everything without typing. 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.