The job
A prospect has gone quiet. Emails sent two weeks ago. Nothing since. The rep needs the next touch. Without context, that becomes generic: “Just checking in to see if you had a chance to review the proposal.” That kills the deal.
Follow-up sequence drafting reads the entire email thread, the call notes, and the current deal status. It drafts a move that lands differently because it’s grounded. “You mentioned your Q2 launch was dependent on getting the infrastructure sorted. Given what’s happened with AWS pricing in the last month, I wanted to surface three options we’re seeing on the similar path.” That email gets a reply.
Plated well: the rep reads the station’s draft, maybe edits two sentences, and sends it. The prospect replies because the email is specific enough to feel like it was written for them.
The recipe
All seven ingredients still apply. The leverage on this dish is Context (Ingredient #2). The follow-up lands because the station has read the full thread, not a summary.
Training sets what a sharp follow-up sounds like (consultative, specific, signal-aware). Examples show the station what follow-ups work at your company and why they work. Context is the load-bearing ingredient: feed the station the full thread, not the summary. Summaries kill specificity. The station needs the actual emails, call notes, and trigger language to write a move that lands. Output Over Process says: tell the station the destination: “a specific email that addresses what they last said and gives them a reason to move.” Don’t list the steps. Guardrails protect against over-promising or inventing needs. Measurement: did the prospect reply? If yes, the follow-up worked.
How to build it
-
Collect the full email thread. Not a summary. The entire history. From first touch through the most recent silence.
-
Include the call notes. What did the prospect say they were worried about? What timeline did they mention? What would make them move?
-
Write the output destination. One specific sentence: “The follow-up gives them a reason to reply by connecting what they said to something happening now.”
-
Show the house style. Give three follow-ups you are proud of. They should feel consultative, not desperate. Specific, not generic.
-
Set the guardrails. The station never invents a reason they should move. If the prospect said “Q2 launch,” and it’s now Q3, the station acknowledges the timeline changed. The station never promises something without saying “let me confirm with the team.”
-
Set the signal threshold. The station should flag if it’s seeing the same follow-up drafted twice in one month. That’s a signal the deal is actually dead, not stalled.
-
Test on five stalled deals. Station drafts the follow-up. Rep reads it. Does it feel like a specific move or a template? If template, sharpen the examples and context.
What breaks it
-
Context starvation. You give the station the last email and the current deal status. The station doesn’t see the thread. The follow-up is disconnected from what was actually discussed. Feed the full thread, not the headline.
-
Summary substitution. You give the station CRM notes instead of the actual emails. The station reads “prospect is interested but budget is pending.” The follow-up becomes “what about your budget?” That’s a conversation starter you had already in the thread. The prospect saw this already.
-
Over-generalization of house style. Your three examples are all similar (consultative, specific). The station doesn’t see what a more direct follow-up should sound like in your voice. Show variety, not uniformity.
-
Missing escalation logic. The station has drafted the same follow-up once. The deal is still silent. The station drafts it again. By the fourth follow-up, the deal is actually dead, but the station doesn’t know that yet. Set the rule: after the second follow-up with no reply, escalate to a phone call instead of another email.
When it’s working
By week two, the rep is drafting fewer follow-ups manually. By week four, the follow-ups that the station generates are getting replies at a higher rate than the rep’s manual drafts because the station has context the rep is too busy to retrieve.
Measure it: compare reply rates on station-drafted vs. rep-drafted follow-ups. If station is +15%, it’s working.
Monday Move
Pick a stalled deal. Pull the full email thread. Have the station draft the next follow-up. Read it. Does it feel specific to this deal or generic? If generic, the examples or context need sharpening. If specific, send it. Report whether the prospect replied.
Dish 4 of 10 on the Sales Station. Build-note leverage: Context (Ingredient #2).