← Vault Index
Source: business/products/consulting-practice-sop-manual/runners/follow-up-sequence-activation-runner-SKILL.md

name: follow-up-sequence-activation-runner description: > Activates a structured follow-up sequence when a prospect goes quiet for 7+ days. Routes to the right follow-up approach based on where the conversation stalled, produces the message, and updates the pipeline record. metadata: author: "Kathryn Brown, Practice Builders" version: "1.0.0" date: "2026-04-28" sop: "Follow-Up Sequence Activation" category: "Business Development" frequency: "Trigger-Based" estimated-time: "15 min" trigger: "When a prospect goes quiet for 7+ days"


Follow-Up Sequence Activation — Runner

You are executing the Follow-Up Sequence Activation SOP for an independent consultant. Prospects go quiet for reasons that have nothing to do with disinterest — competing priorities, internal approvals, calendar chaos. This runner activates a structured follow-up within the right window, before the prospect's context goes cold, so you re-enter the conversation at the same standing where it left off.

Do not skip steps. Do not ask questions across multiple turns — collect everything upfront.


What you'll have when this is done: A follow-up message ready to send (or already sent), the prospect's pipeline record updated with the new contact date, and a follow-up date set 7 days out. The stalled prospect is back in active sequence.

Step 1: Collect Your Inputs

Ask the user for the following (all at once, in a single prompt):

Prospect Record:

Conversation Context:

For Post-Proposal Silence (if applicable):

If the user doesn't have all details, work with what's available and note where more context would strengthen the follow-up.

Step 2: Route to the Right Follow-Up Approach

Based on the inputs, classify the situation:

Path A — Follow-Up Sequence: The prospect went quiet after initial contact or early conversation (before a proposal was sent). Proceed to Step 3.

Path B — Re-Engagement Email: The prospect went quiet after a proposal or substantive conversation and it has been 14+ days. Proceed to Step 4.

Decision logic:

State which path you're taking and why.

Step 3: Follow-Up Sequence (Path A)

Build a timed 4-email follow-up sequence. Each email must add value or new information — if the only thing you're communicating is "just checking in," you're subtracting credibility with every send.

Sequence structure — 4 emails across 14 days:

Email 1 — Value Add (Day 2). Reference a specific point from the conversation and add something not yet discussed — a relevant case example, a data point, a pattern you've seen. 3-4 sentences. No ask. The first follow-up sets the tone for the entire sequence.

Email 2 — Objection Address (Day 5). Name the primary objection or hesitation directly but without defensiveness. Acknowledge the concern, reframe it with evidence or a relevant example, and leave space to respond. 4-5 sentences. If no objection was raised, use the most common objection for the service type (typically timing, budget, or internal buy-in).

Email 3 — Constraint Introduction (Day 9). Introduce a legitimate constraint — your calendar is filling, a relevant deadline is approaching, or an external factor creates urgency. This is not manufactured scarcity. 3-4 sentences. State the constraint factually with no pressure language. If no real constraint exists, use a "what questions remain?" angle instead.

Email 4 — Clean Close (Day 14). Give the prospect a graceful exit. "If the timing isn't right, no hard feelings — I'd rather know than guess." 2-3 sentences. One clear question. Permission to say no. This email converts more often than any other because it removes pressure and triggers reciprocity.

Output each email in this format:

**Email [#] — [Type] (Day [#])**
Subject: [Specific reference — not generic]

[Email body]

**Signal:** [What triggered this angle] → **Do This:** [When to send, what to do if they reply]

Sequence quality checks (run before presenting):

#CheckFix
1Does each email have a distinct angle, or do two make the same argument?Rewrite the duplicate to serve a different purpose.
2Does any email contain "just checking in" or equivalent filler?Replace with a specific value-add or question.
3Does email 2 name and address a real objection?Sharpen to a specific concern with a specific response.
4Is the constraint in email 3 legitimate, not manufactured?Switch to "what questions remain?" if it feels artificial.
5Does email 4 genuinely offer a clean exit, or does it hedge?Remove any "but I hope we can still..." language.

Identify the weakest email. Rewrite it. Verify the rewrite improved the sequence before presenting.

After completing the sequence, skip to Step 5.

Step 4: Re-Engagement Email (Path B)

Produce a single email that gives the silent prospect a genuine reason to respond — without pressure, guilt, or desperation.

4A. Classify the relationship and silence:

This classification drives tone. State it before drafting.

4B. Identify the best trigger — in order of strength:

  1. External trigger — News about their company, industry shift, regulatory change (strongest — it's about them)
  2. Shared reference — Something connecting to a conversation you had
  3. Value offer — A resource or insight genuinely useful to them (not a disguised pitch)
  4. Milestone reference — "It's been six months since we discussed [X]. Curious how that's going."
  5. No trigger — Be direct: "I've been thinking about [specific problem we discussed]. Worth a quick conversation?"

Never fabricate a trigger. An honest "no particular reason" is better than a forced reference.

4C. Draft the email:

  1. Subject line: Short, specific, curiosity-provoking. Not "Checking in" or "Following up."
  2. Opening line: The trigger or reference. No "Hope you're well" or "It's been a while." Start with the thing.
  3. Connection: One sentence linking the trigger to their situation.
  4. Low-friction ask: Something that takes less than 60 seconds to respond to. Not "let's schedule a 30-minute call." Something like "worth a quick 10-minute catch-up?" or "curious if [specific question] — no rush."
  5. Sign-off: Brief, warm, no pressure.

Total length: 4-6 sentences.

Output format:

**Subject:** [Short, specific, curiosity-provoking]

Hi [Name],

[Trigger/reference — start with the thing.] [Connection to their situation.] [Low-friction ask.]

[Warm sign-off]

Re-engagement quality checks (run before presenting):

CheckQuestion
No guiltDoes the email avoid language that makes the recipient feel bad for not responding?
Real triggerIs the reason for reaching out genuine, not manufactured?
Low frictionCould they respond in under 60 seconds?
Right toneDoes the tone match the relationship depth?
No desperationWould you feel comfortable if this email were forwarded to someone else?

Identify the weakest section. Rewrite it. Verify improvement before presenting.

Step 5: Review and Edit

Review the output from Step 3 or Step 4. Check for:

Present the edited output to the user.

Step 6: Assemble Final Output and Pipeline Update

Combine the follow-up content with a pipeline update record:

# Follow-Up Sequence Activation
## [Prospect Name] — [Date]

### Situation
- **Stage:** [Current pipeline stage]
- **Last contact:** [Date]
- **Days silent:** [#]
- **Silence followed:** [Proposal / Discovery call / Initial contact]
- **Approach used:** [Follow-Up Sequence / Re-Engagement Email]

### Follow-Up Content
[Full email sequence from Step 3 OR single email from Step 4]

### Pipeline Update
- **New contact date:** [Today's date — when the first message is sent]
- **Next follow-up date:** [7 days from today]
- **Action:** Update prospect record in pipeline tracker with new contact date and follow-up date

### SOPs to Trigger
- [ ] Weekly Pipeline Review — prospect will reappear if no response by next review
- [ ] Re-Engagement Email Writer — if using Path A and full 4-email sequence completes with no response, wait 2 weeks, then re-engage with a completely different angle

Quality Check (Internal — never shown to the user)

Before presenting the final output, verify:

CheckRequirement
Routing correctPath A vs. Path B matches the decision logic in Step 2
No apology languageZero instances of "just checking in," "sorry to bother," "I know you're busy," "circling back," "touching base"
Distinct anglesEach email in a sequence serves a different strategic purpose
SpecificityEvery email references something specific to this prospect — no generic templates
Constraint is realIf email 3 uses a constraint, it's legitimate and based on user input
Clean exit is cleanEmail 4 (if applicable) genuinely offers permission to say no
Trigger is genuineRe-engagement email (if applicable) uses a real trigger, not a fabricated one
Low frictionEvery call to action can be responded to in under 60 seconds
Under 100 words eachEach email in a follow-up sequence stays under 100 words
Pipeline update completeContact date and follow-up date are set

Identify the weakest element. Rewrite it. Verify the rewrite before presenting.

Rules

From the SOP:

  1. Follow up at 7 days, not 21. At 7 days you're a relevant follow-up. At 21 days you're a cold email they don't remember.
  2. Never open with an apology. "Just checking in" and "Sorry to bother you" signal low confidence and reset the relationship at a lower status than where it ended.
  3. Route correctly — pre-proposal silence gets a follow-up sequence; post-proposal silence past 14 days gets a re-engagement email. Using the wrong tool for the situation either overwhelms or underwhelms.
  4. Send the message within 15 minutes of triggering this SOP. Don't batch follow-ups to a separate session. The longer you wait, the less relevant the follow-up becomes.

From the Follow-Up Sequence Writer:

  1. Never use "just checking in," "circling back," or "touching base" — these are credibility-destroyers.
  2. Each email must stand alone — the prospect may not have read the previous ones.
  3. No discounting or revising terms unless explicitly asked.
  4. Keep each email under 100 words. Shorter emails get read; long ones get archived.
  5. Space the sequence across 14 days: Day 2, Day 5, Day 9, Day 14.
  6. Never send more than 4 emails in a sequence. After 4, switch to a different channel or wait 30 days.

From the Re-Engagement Email Writer:

  1. Never reference how long it's been. "It's been three months since we last spoke" makes the recipient feel guilty, not motivated.
  2. Never pitch in a re-engagement email. The goal is to re-open the conversation, not close a sale.
  3. Maximum one follow-up after no response to a re-engagement email. Two attempts, spaced 3-4 weeks apart. After that, stop.
  4. Always include a specific trigger or reference. If you can't find one, be honest about it rather than fabricating one.

Output format:

  1. Escape dollar signs as \$ for Notion compatibility.
  2. Present as a single unified document, not separate skill outputs.

Copyright (c) 2026 Kathryn Brown, Practice Builders Licensed under the Practice Builders Skill License v1.0 See https://practicebuilders.ai/license for terms.

This skill is part of the Consulting Practice SOP Manual, a Practice Builders product. Redistribution, resale, or derivative use without written permission is prohibited.