/prd-v09-cold-outreach-tiered
Build Tier 1/2/3 cold outreach sequences differentiated by personalization depth and research signal strength during PRD v0.9 Go-to-Market. Triggers on requests to plan cold outreach, founder-led sales, or when user asks "cold email sequence", "outbound campaign", "founder
$ npx -y skills add mattgierhart/PRD-driven-context-engineering --skill prd-v09-cold-outreach-tiered --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/prd-v09-cold-outreach-tiered
Context preview
The summary Claude sees to decide when to auto-load this skill.
Build Tier 1/2/3 cold outreach sequences differentiated by personalization depth and research signal strength during PRD v0.9 Go-to-Market. Triggers on requests to plan cold outreach, founder-led sales, or when user asks "cold email sequence", "outbound campaign", "founder
SKILL.md
prd-v09-cold-outreach-tiered.SKILL.mdname: prd-v09-cold-outreach-tiered
description: >
Build Tier 1/2/3 cold outreach sequences differentiated by personalization depth and research
signal strength during PRD v0.9 Go-to-Market. Triggers on requests to plan cold outreach,
founder-led sales, or when user asks "cold email sequence", "outbound campaign", "founder
outreach", "LinkedIn outreach", "Tier 1 personalization", "predictable revenue", "sales
cadence", "BDR sequence". Outputs GTM-OUT-* sequence entries and lead-list references.
context: fork
allowed-tools:
- Read
- Write
- Edit
- Glob
- Grep
- WebSearch
- WebFetch
execution_modes:
default: standard
supports: [quick, standard, deep]
Cold Outreach (Tiered: 1:1 / 1:few / 1:many)
Position in workflow: v0.9 Offer Construction → **v0.9 Cold Outreach (Tiered)** → v0.9 Launch Metrics
Execution Mode
Default is **standard**. See [`.claude/rules/08-skill-execution-modes.md`](../../rules/08-skill-execution-modes.md) for selection logic.
| Mode | What this skill produces | |------|--------------------------| | **quick** | One tier (typically Tier 2); 3-touch sequence; lead-list scoring rubric | | **standard** | All three tiers; 3–5 touches each; lead-list scoring + tier-assignment logic; reply-handling guide | | **deep** | All tiers + A/B subject lines per tier; channel mix (email + LinkedIn + voicemail); reply-rate baselines; objection library |
What This Does
Builds three differentiated cold-outreach sequences, each calibrated to a different ratio of research-per-lead:
- **Tier 1 (1:1, founder-led)** — Hand-researched. Highly personalized. Each touch references something specific. Volume: 10–30 contacts.
- **Tier 2 (1:few, semi-automated)** — Segment-personalized. Template with 3–5 dynamic variables per recipient. Volume: 100–500 contacts.
- **Tier 3 (1:many, automated)** — Broad-fit. Template only, minimal personalization. Volume: 1,000–10,000+ contacts.
The tiers are **not "good/better/best"** — each has its place. Tier 3 fills the top of the funnel cheaply. Tier 2 carries the bulk. Tier 1 closes the highest-value targets that templates can never reach.
How It Works
1. **Source lead lists from ICP** — Pull from the Positioning best-fit characteristics. Use enrichment tools (Apollo, Clay, Clearbit) or LinkedIn Sales Nav search anchored on firmographic + behavioral signals from PER-. 2. **Score each lead's signal strength** (1–5):
- **Trigger signal** — Recent funding, hiring, product launch, public pain (5)
- **Fit signal** — Strong firmographic/behavioral match without specific trigger (3–4)
- **Cold signal** — Broad-fit only; no specific signal (1–2)
3. **Tier assignment**:
- Signal 4–5 + opportunity size ≥ threshold → **Tier 1**
- Signal 3–4 → **Tier 2**
- Signal 1–2 → **Tier 3** (or drop if list is large enough)
4. **Build per-tier sequences** — Each tier gets its own template structure (see Output Template). Tier 1 is hand-drafted; Tier 2 is template + variables; Tier 3 is template only. 5. **End every sequence on the guarantee** — The guarantee from [prd-v09-offer-construction-hormozi](../prd-v09-offer-construction-hormozi/SKILL.md) is the reply-friction killer. Don't ask for a meeting cold; ask them to invoke the guarantee. 6. **Plan reply handling** — Define what counts as a reply (positive, ask, objection, unsubscribe), and have a response cadence for each. Tier 1 replies go to founder immediately. Tier 3 replies route through a templatized objection library.
Example
B2B SaaS founder launching, ICP = Series A SaaS PMs.
**Tier 1** (20 hand-picked targets):
- Touch 1 (Day 0, email): Reference specific recent blog post + offer specific insight on their problem
- Touch 2 (Day 4, LinkedIn): Connect with a one-line follow-up referencing the email
- Touch 3 (Day 10, email): Share a relevant case study from a similar company; mention the guarantee
- Touch 4 (Day 18, email): Soft breakup — "want me to circle back in a quarter?"
**Tier 2** (200 mid-signal leads):
- Touch 1 (Day 0, email): Template with 3 variables ({company}, {pain point}, {peer company}). 6–10 sentences max.
- Touch 2 (Day 3, email): One-line bump
- Touch 3 (Day 7, email): Case study + guarantee mention
- Touch 4 (Day 14, email): Breakup
**Tier 3** (2,000 broad-fit leads):
- Touch 1 (Day 0, email): Template only. 4–6 sentences. Lead with category insight, not pitch.
- Touch 2 (Day 5, email): Case study
- Touch 3 (Day 12, email): Breakup ("last note from me")
Expected reply rates: Tier 1 = 30–50%; Tier 2 = 8–15%; Tier 3 = 1–3%.
What You Get Back
- **GTM-OUT-\* entries** (one per tier sequence) — Tier metadata, per-touch templates, channel mix, timing
- **GTM-OUT-touch-\*** entries — Individual touch templates with subject line, body, channel
- **Lead-list scoring rubric** (single GTM-*) — How to assign tier
- **Reply-handling guide** — What counts as a reply; routing rules
When to Use It
| Trigger | Mode | |---------|------| | B2B / founder-led sales motion | standard | | Post-launch acquisition push | standard | | Paid channels too expensive (high CAC) | standard | | Specific ABM-style campaign against named accounts | deep, Tier 1 only | | Mass-market consumer product with no individual-buyer relationship | **do not use** — wrong channel |
Consumes
- **GTM-\* positioning** + **PER-\* best-fit characteristics** — Source for ICP and message anchoring
- **GTM-\* offer card** + **GTM-\* guarantee** (from v0.9 Offer Construction) — Sequences end on the guarantee, not a meeting ask
- **CFD-\* customer stories** (from v0.1–v0.4 + post-launch) — Case studies for touch 3
- **BR-POS-\* constraints** — Tier targeting must honor "not for" rules
- **KPI-\* targets** (from v0.3 + v0.9 Launch Metrics) — Reply rate and meeting-booked targets per tier
Produces
- **GTM-OUT-\* tier entries** — One per tier with sequence metadata
- **GTM-OUT-touch-\* entries** — Per-touch templates (subject, body, channel, timing)
- **GTM-\* lead
Read more
name: prd-v09-cold-outreach-tiered description: > Build Tier 1/2/3 cold outreach sequences differentiated by personalization depth and research signal strength during PRD v0.9 Go-to-Market. Triggers on requests to plan cold outreach, founder-led sales, or when user asks "cold email sequence", "outbound campaign", "founder outreach", "LinkedIn outreach", "Tier 1 personalization", "predictable revenue", "sales cadence", "BDR sequence". Outputs GTM-OUT-* sequence entries and lead-list references. context: fork allowed-tools: - Read - Write - Edit - Glob - Grep - WebSearch - WebFetch execution_modes: default: standard supports: [quick, standard, deep]
Cold Outreach (Tiered: 1:1 / 1:few / 1:many)
Position in workflow: v0.9 Offer Construction → **v0.9 Cold Outreach (Tiered)** → v0.9 Launch Metrics
Execution Mode
Default is **standard**. See [`.claude/rules/08-skill-execution-modes.md`](../../rules/08-skill-execution-modes.md) for selection logic.
| Mode | What this skill produces | |------|--------------------------| | **quick** | One tier (typically Tier 2); 3-touch sequence; lead-list scoring rubric | | **standard** | All three tiers; 3–5 touches each; lead-list scoring + tier-assignment logic; reply-handling guide | | **deep** | All tiers + A/B subject lines per tier; channel mix (email + LinkedIn + voicemail); reply-rate baselines; objection library |
What This Does
Builds three differentiated cold-outreach sequences, each calibrated to a different ratio of research-per-lead:
- **Tier 1 (1:1, founder-led)** — Hand-researched. Highly personalized. Each touch references something specific. Volume: 10–30 contacts.
- **Tier 2 (1:few, semi-automated)** — Segment-personalized. Template with 3–5 dynamic variables per recipient. Volume: 100–500 contacts.
- **Tier 3 (1:many, automated)** — Broad-fit. Template only, minimal personalization. Volume: 1,000–10,000+ contacts.
The tiers are **not "good/better/best"** — each has its place. Tier 3 fills the top of the funnel cheaply. Tier 2 carries the bulk. Tier 1 closes the highest-value targets that templates can never reach.
How It Works
1. **Source lead lists from ICP** — Pull from the Positioning best-fit characteristics. Use enrichment tools (Apollo, Clay, Clearbit) or LinkedIn Sales Nav search anchored on firmographic + behavioral signals from PER-. 2. **Score each lead's signal strength** (1–5):
- **Trigger signal** — Recent funding, hiring, product launch, public pain (5)
- **Fit signal** — Strong firmographic/behavioral match without specific trigger (3–4)
- **Cold signal** — Broad-fit only; no specific signal (1–2)
3. **Tier assignment**:
- Signal 4–5 + opportunity size ≥ threshold → **Tier 1**
- Signal 3–4 → **Tier 2**
- Signal 1–2 → **Tier 3** (or drop if list is large enough)
4. **Build per-tier sequences** — Each tier gets its own template structure (see Output Template). Tier 1 is hand-drafted; Tier 2 is template + variables; Tier 3 is template only. 5. **End every sequence on the guarantee** — The guarantee from [prd-v09-offer-construction-hormozi](../prd-v09-offer-construction-hormozi/SKILL.md) is the reply-friction killer. Don't ask for a meeting cold; ask them to invoke the guarantee. 6. **Plan reply handling** — Define what counts as a reply (positive, ask, objection, unsubscribe), and have a response cadence for each. Tier 1 replies go to founder immediately. Tier 3 replies route through a templatized objection library.
Example
B2B SaaS founder launching, ICP = Series A SaaS PMs.
**Tier 1** (20 hand-picked targets):
- Touch 1 (Day 0, email): Reference specific recent blog post + offer specific insight on their problem
- Touch 2 (Day 4, LinkedIn): Connect with a one-line follow-up referencing the email
- Touch 3 (Day 10, email): Share a relevant case study from a similar company; mention the guarantee
- Touch 4 (Day 18, email): Soft breakup — "want me to circle back in a quarter?"
**Tier 2** (200 mid-signal leads):
- Touch 1 (Day 0, email): Template with 3 variables ({company}, {pain point}, {peer company}). 6–10 sentences max.
- Touch 2 (Day 3, email): One-line bump
- Touch 3 (Day 7, email): Case study + guarantee mention
- Touch 4 (Day 14, email): Breakup
**Tier 3** (2,000 broad-fit leads):
- Touch 1 (Day 0, email): Template only. 4–6 sentences. Lead with category insight, not pitch.
- Touch 2 (Day 5, email): Case study
- Touch 3 (Day 12, email): Breakup ("last note from me")
Expected reply rates: Tier 1 = 30–50%; Tier 2 = 8–15%; Tier 3 = 1–3%.
What You Get Back
- **GTM-OUT-\* entries** (one per tier sequence) — Tier metadata, per-touch templates, channel mix, timing
- **GTM-OUT-touch-\*** entries — Individual touch templates with subject line, body, channel
- **Lead-list scoring rubric** (single GTM-*) — How to assign tier
- **Reply-handling guide** — What counts as a reply; routing rules
When to Use It
| Trigger | Mode | |---------|------| | B2B / founder-led sales motion | standard | | Post-launch acquisition push | standard | | Paid channels too expensive (high CAC) | standard | | Specific ABM-style campaign against named accounts | deep, Tier 1 only | | Mass-market consumer product with no individual-buyer relationship | **do not use** — wrong channel |
Consumes
- **GTM-\* positioning** + **PER-\* best-fit characteristics** — Source for ICP and message anchoring
- **GTM-\* offer card** + **GTM-\* guarantee** (from v0.9 Offer Construction) — Sequences end on the guarantee, not a meeting ask
- **CFD-\* customer stories** (from v0.1–v0.4 + post-launch) — Case studies for touch 3
- **BR-POS-\* constraints** — Tier targeting must honor "not for" rules
- **KPI-\* targets** (from v0.3 + v0.9 Launch Metrics) — Reply rate and meeting-booked targets per tier
Produces
- **GTM-OUT-\* tier entries** — One per tier with sequence metadata
- **GTM-OUT-touch-\* entries** — Per-touch templates (subject, body, channel, timing)
- **GTM-\* lead
PRD-driven Context Engineering: A systematic approach to building AI-powered products using progressive documentation and context-aware development workflows
Repo: mattgierhart/PRD-driven-context-engineering
Other skills on prd-driven-context-engineering.
- /SKILL_TEMPLATE
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
Open skill - /ghm-gate-check
Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py). Returns a graduated PASS / WARN / BLOCK verdict with top blockers and their causal chain. Triggers before advancing from v0.X to v0.Y or explicit
Open skill - /ghm-harvest
Extracts durable insights from temp/ files to SoT during EPIC Phase E. Triggers at EPIC completion or explicit `/ghm-harvest` invocation. Outputs new SoT entries and archive manifest.
Open skill - /ghm-id-register
Validates and registers new SoT IDs with cross-reference integrity. Triggers when creating BR-XXX, UJ-XXX, API-XXX, or CFD-XXX entries. Outputs formatted SoT entry with validated cross-references.
Open skill - /ghm-self-install
Install the PRD-Driven Context Engineering methodology into a fresh OR existing repository — the subscription-native alternative to forking the whole repo. Runs an interactive wizard that seeds the framework (.claude/ hooks, skills, agents, rules, scripts) without clobbering
Open skill - /ghm-sot-builder
Creates new Source of Truth (SoT) files when existing templates don't fit your needs. Triggers on requests to create a new SoT file, add a new artifact type, or when user says "I need to track [X] but there's no SoT for it", "create SoT", "new source of truth". Outputs a
Open skill

