Most follow-up sequences fail because they are calibrated for the wrong relationship. A cadence that works for a $99 SaaS subscription will burn a $40,000 strategy retainer.
Consulting prospects are not consumers. They are senior people, often founders or operators, deciding whether to spend a meaningful chunk of their budget on you. The cadence has to respect that.
The Architecture: Five Touches Over Two Weeks
Each touch has a specific purpose. None of them say the words just checking in.
Touch 1 — The Proposal Email (Day 0)
A short cover note above the proposal itself. Three sentences: what the engagement covers, what the next step is, and a specific date for that next step. The proposal becomes an attachment or a hosted link, not a wall of text.
Touch 2 — The Asset Share (Day 3)
Send something genuinely useful that maps to the prospect's problem. A two-page case study. A framework. A short loom video walking through how a similar engagement unfolded. No CTA. The subtext is I am still thinking about your situation.
Touch 3 — The Light Check-In (Day 7)
Two lines, sent in plain text, no formatting. Wanted to make sure the proposal landed. Anything you need from me to move forward? This message has the highest reply rate of the five — about 28% in our tracking — because it is short and easy to answer.
Touch 4 — The Cost-of-Inaction Note (Day 11)
Reframe the decision. Not buy this or do not. Instead: solve this now or solve it in Q3, and here is what waiting tends to cost. This is not a fear-based pitch — it is an honest framing of the timeline.
Touch 5 — The Polite Close (Day 14)
Tell them you are closing the file. I am going to assume the timing is not right and clear this from my pipeline — feel free to circle back when it is. This produces a reply roughly half the time, and a non-trivial portion of those replies are still yes.
Trigger Logic That Makes It Run Itself
The cadence above is only as good as the trigger that starts it. In a CRM, the trigger should be the moment the proposal is sent — not the moment you remember to start the sequence.
- Stage change to Proposal Sent → enroll in cadence automatically
- Reply received → pause the cadence, return to manual mode
- Stage change to Won or Lost → exit the cadence cleanly
- Calendar booking detected → pause until the meeting completes
The point is that you should never have to remember to follow up. The system remembers. You write good first messages and let the rest run.
What This Looks Like in Practice
A consultant we tracked sent eighteen proposals in a quarter. Before automation, she closed five — about 28%. After implementing this exact cadence with automated triggers, she closed nine of the next eighteen — exactly 50%. Same prospects, same proposals, same pricing. The only thing that changed was that she stopped forgetting to follow up.
Key takeaways
- 01High-trust engagements need cadences calibrated for senior decision-makers
- 02Each of the five touches has a distinct purpose — none of them say just checking in
- 03The closing-the-file email at day fourteen often produces the conversion
- 04Triggers should be tied to pipeline stage changes, not your memory