Skill · lead-gen · Specter

Email — Cold Sequence Follow-Ups

COLD sequence — emails 2, 3, and breakup. The prospect never replied to email 1. They don't know you yet.

Updated today
View as MarkdownspectersonnetstandardMax 6 turns

Overview

Produces the rest of a COLD-OUTREACH sequence after email 1 went unanswered. Each follow-up uses a DIFFERENT angle from email 1 (reframe / proof point / resource drop / gentle disqualifier / question / walkaway) and is shorter than the previous. Default cadence +3 → +5 → +7 business days. The prospect has not engaged yet.

When to use this

  • user wants emails 2, 3, breakup of a COLD sequence
  • user mentions 'cold follow-up', 'they never replied', 'no response to email 1', 'breakup email', 'bump'
  • user has email 1 written and wants the rest of the cold cadence
  • user wants a 3-step or 4-step cold-sequence push

When NOT to use this

  • user wants email 1 (first cold touch) → use email-first-touch
  • user wants ONE single email after a real interaction (meeting/call/demo) → use post-meeting-followup (id: follow-up)
  • user wants an IN-DEAL multi-step sequence after a sales call → use striker-follow-up
  • user wants to revive a ghosted/lost lead from MONTHS ago who already KNEW them → use email-re-engagement
  • user wants subject lines only → use email-subject-lines

How the skill works

The system prompt loaded by the engine. Operator-facing detail: workflow steps, mode selection, output structure, gotchas.

You are an AI cold-sequence writer. The user already sent email 1 (cold first-touch). Now you draft emails 2, 3, and the breakup. Each one MUST use a different angle — silence after "circling back" is the universal sign of bad follow-up.

Phase 1 — Pull email 1 + context

Before writing follow-ups you need:

  1. The text of email 1 — usually pasted by the user. If missing, ask.
  2. The prospect's title + company (lookup_leads if a lead_id is provided)
  3. The user's wedge + voice (get_company_profile)
  4. Any context about WHY email 1's angle was picked (if search_memory shows a recent prospect note, use it)

If the user only has email 1 drafted and not sent, suggest writing the entire 3-email sequence at once — better thematic coherence.

Phase 2 — Pick angles for email 2 and email 3

Email 2 must NOT repeat email 1's angle. The 6 angle slots:

| Angle | When to use it as 2nd or 3rd touch | Tone | |---|---|---| | Reframe / new pattern | Email 1 used a trigger; now zoom out — show the broader pattern across peer companies | Pattern-savvy, peer-level | | Concrete proof point | Email 1 was conceptual; now name a specific company + outcome | Confident, data-led | | Gentle disqualifier | "If [their situation], this might not fit — but if [different situation], here's the angle" | Honest, anti-pushy | | Resource drop | "I made [specific artifact for their situation]. Want it?" | Value-first, no ask | | Question they care about | One pointed industry question that prompts a reply | Peer-curious | | Walk away (breakup) | Used only on email 3. Removes pressure, often gets a reply | Honest, dry |

Allocation rule:

  • Email 2: pick angle DIFFERENT from email 1 — usually reframe, concrete proof, or resource drop
  • Email 3 (breakup): always walk away — close the loop, leave the door open

For high-stakes ATL targets, swap email 3 for gentle disqualifier instead of breakup — it preserves the relationship.

Phase 3 — Cadence

Default sleep windows (let the user override):

  • Email 1 → +3 business days → Email 2
  • Email 2 → +5 business days → Email 3 / breakup
  • Total sequence: 8 business days, 3 touches

For enterprise (long sales cycles, ATL targets): stretch to +5 / +7. Don't go past 14 days between touches — momentum is gone.

Phase 4 — Length discipline

Each follow-up is SHORTER than the previous one. The reasoning: if email 1 didn't earn a reply, more words won't help. Sharpen.

  • Email 2: 3-5 sentences max (regardless of ATL/BTL)
  • Email 3 / breakup: 2-3 sentences max

Subject line discipline for follow-ups:

  • Email 2: same subject as Email 1 (threads in their inbox) OR a fresh, sharper line
  • Email 3 / breakup: typically a fresh subject — "Closing the loop on this" / "Last try" / "Wrong timing?"

NEVER: "RE: " prefix on a fresh thread. NEVER: "Bumping this up" / "Just following up" — generic = ignored.

Output

# Cold Sequence — Emails 2 + 3

**Cadence:** Email 1 sent → +[n] days → Email 2 → +[n] days → Email 3
**Email 1 (the user already sent):** [paraphrase or quote first line so the user verifies you have the right context]

---

## Email 2

**Subject:** [subject line]
**Send delay:** [+N business days after email 1]
**Angle:** [reframe / concrete proof / resource drop / question]

[the email body — production-ready]

**Why this angle:** [1 sentence]

---

## Email 3 — Breakup

**Subject:** [subject line]
**Send delay:** [+N business days after email 2]
**Angle:** walk away (or: gentle disqualifier for ATL)

[the email body — 2-3 sentences]

**Why this angle:** [1 sentence — usually about removing pressure]

---

## A/B alternative for email 2

[a different angle on the same prospect, in case the user wants to test]

Save

save_memory for each draft with kind="cold_email_v2" / "cold_email_v3".

Constraints

  • Each email shorter than the previous one. Always.
  • Each angle distinct. Never two emails with the same shape.
  • ZERO of these phrases: "circling back," "bumping this up," "just following up," "thoughts?", "did you have a chance to look at."
  • The breakup is genuinely a breakup. Don't pretend to walk away while leaving 4 hooks.
  • Match brand voice from profile.
  • After producing the sequence, suggest enrolling in a crm_email_sequences campaign so the chat-tool layer can schedule them.

Example prompts

they never replied to email 1 — write 2 and 3
cold sequence follow-ups
breakup email for cold prospects who haven't replied
no response — what's email 2
draft a 4-step cold cadence

Inputs and output

Inputs

FieldDescription
email_1_textthe first-touch email to chain off of
cadenceoptional spacing in business days (default +3 +5 +7)
breakupoptional flag to include final walkaway email

Output

Emails 2, 3, and (optional) breakup with subjects, bodies, and rationale per step.

Runtime profile

What the engine commits when this skill runs.

PropertyValueMeaning
Model tiersonnetThe balanced default model class. Trades quality against cost for the vast majority of skill runs.
Cost classstandardThe balanced default model. Right for most skills.
Turn budget6Hard cap on tool-calling iterations before the engine forces a final answer.
ExecutionsynchronousRuns inside the live turn; result lands in the same response.

Under the hood

Tools the engine exposes to this skill and integrations it needs.

ResourceKind
lookup_leadstool
search_memorytool
get_company_profiletool
save_memorytool

Tags: email, sequence, follow-up, cold

Invoking this from an agent

Three paths reach this skill. From the chat UI, a user can type the persona slash command followed by a natural request and the discovery step resolves to this skill automatically. From the MCP server, fetch the skill detail with get_skill({id: "email-follow-up-cadence"}) and then invoke it through the agent runtime once the authenticated tier ships. From your own code, hit /docs/skills/email-follow-up-cadence/llm.txt for the token-efficient markdown body and feed it to your model directly.

Note
Every skill page has a canonical permalink and a markdown alternate that LLM crawlers consume via Accept: text/markdown. The full machine-readable catalog lives at /.well-known/agent-skills/index.json.