Skip to content
cccskills
FreePublished on GitHub

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 outreach", "LinkedIn outreach", "Tier 1 personalization", "predictable revenue", "sales cadence", "BDR sequence". Outputs GTM-OUT-* sequence entries and lead-list references.

The English summary is being prepared. Showing the original description.

Works withLinkedIn
See how to install

Files included (1)

  • SKILL.md9.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 for selection logic.

ModeWhat this skill produces
quickOne tier (typically Tier 2); 3-touch sequence; lead-list scoring rubric
standardAll three tiers; 3–5 touches each; lead-list scoring + tier-assignment logic; reply-handling guide
deepAll 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 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

TriggerMode
B2B / founder-led sales motionstandard
Post-launch acquisition pushstandard
Paid channels too expensive (high CAC)standard
Specific ABM-style campaign against named accountsdeep, Tier 1 only
Mass-market consumer product with no individual-buyer relationshipdo 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-list scoring rubric
  • CFD-* gaps — When sequences reveal objections we can't answer, log as CFD- research gaps

Output Template

GTM-OUT-XXX: Tier [1 | 2 | 3] Sequence
Type: Outreach
Tier: [1 | 2 | 3]
Volume: [target lead count]
Owner: [Person / role]
Status: [Planned | Active | Paused]

Lead profile:
  Signal strength: [4–5 | 3–4 | 1–2]
  Source: [Apollo | LinkedIn Sales Nav | Clay | Manual]
  Best-fit criteria: [Anchored in PER- characteristics]

Sequence:
  Touch 1: GTM-OUT-touch-AAA — Day 0, [channel]
  Touch 2: GTM-OUT-touch-BBB — Day [N], [channel]
  Touch 3: GTM-OUT-touch-CCC — Day [N], [channel]
  Touch 4: GTM-OUT-touch-DDD — Day [N], [channel]

Reply handling:
  Positive: [Routing]
  Ask: [Routing]
  Objection: [Routing — point to objection library]
  Unsubscribe: [Action]

KPI targets:
  Reply rate: [Tier 1: 30–50% | Tier 2: 8–15% | Tier 3: 1–3%]
  Meeting-booked rate: [varies]

Linked IDs: PER-XXX, GTM-YYY (positioning), GTM-ZZZ (offer), GTM-AAA (guarantee), KPI-BBB
GTM-OUT-touch-XXX: Touch [N] — Tier [1|2|3]
Channel: [Email | LinkedIn | Voicemail | SMS]
Subject: "[Subject line — A/B variants for deep mode]"

Body:
  [Template body, with {variable} markers for tiers 2 and 3]

Personalization tier:
  Tier 1: Hand-drafted; each touch references something specific
  Tier 2: Template + 3–5 variables — {company}, {pain_point}, {peer_company}
  Tier 3: Template only

Ends on: [Guarantee mention | Case study | Soft ask | Breakup]

Linked IDs: GTM-OUT-XXX (parent sequence), GTM-AAA (guarantee)

Anti-Patterns

PatternSignalFix
Same template for all tiersTier 1 reply rate < 10%Tier 1 must be hand-drafted; templates are the floor, not the ceiling
Fake personalization"{first_name}, I love what {company} is doing"Either personalize for real (Tier 1) or stop pretending (Tier 3)
Ask for meeting cold"Got 15 min next week?" in touch 1Lead with value; ask for guarantee invocation or content engagement instead
No breakupSequence runs forever, hurting deliverabilityAlways include a final-touch breakup
No tier assignment logicAll leads in same tierBuild the scoring rubric before sending anything
Outreach without offerSequence runs before Offer Construction is completeWait — without the guarantee, the sequence ends on weak CTAs
Outreach without positioningGeneric value claimsReply rates die; honor the Dunford positioning

Quality Gates

Before launching:

  • All three tiers defined (or quick-mode single tier with documented reason)
  • Per-touch templates exist and respect BR-POS-* constraints
  • Sequences end on the guarantee (or explicit reason why not)
  • Reply-handling rules documented
  • KPI- targets set per tier (reply rate + meeting-booked rate)
  • Unsubscribe path is one-click and honored
  • Spam-compliance check (CAN-SPAM, GDPR if applicable) done

Downstream Connections

ConsumerWhat it usesExample
Launch Channels (ORB)Cold outreach is a Borrowed channel; rolls into mix matrixTier 1 = Borrowed-time; Tier 2/3 = Borrowed-volume
Launch MetricsPer-tier reply rates become KPI- entriesKPI-tier1-reply-rate
Feedback Loop SetupReply objections feed CFD-"Why we passed" replies → CFD- pattern
v1.0 Continuous DiscoveryHigh-engagement Tier 1 replies = founder interviewsReply → CFD- interview with confidence ≥ 3/5

Detailed References

  • Aaron Ross, Predictable Revenue (2011) — Tier 2/3 outbound structure
  • Aaron Ross, From Impossible to Inevitable (2016) — Sequencing
  • BrianRWagner's cold-outreach-sequence skill (ai-marketing-claude-code-skills)
  • (No bundled references/ — sequences are templates, not theory)

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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 `/ghm-gate-check`.

The English summary is being prepared. Showing the original description.

mattgierhart/PRD-driven-context-engineering181Updated Aug 31, 2026

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.

The English summary is being prepared. Showing the original description.

mattgierhart/PRD-driven-context-engineering181Updated Aug 31, 2026

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.

The English summary is being prepared. Showing the original description.

mattgierhart/PRD-driven-context-engineering181Updated Aug 31, 2026

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 product content. Triggers on "install the methodology", "adopt this into my repo", "self-install", "set up PRD lifecycle here", "onboard existing project". Outputs an installed framework + a verification report.

The English summary is being prepared. Showing the original description.

mattgierhart/PRD-driven-context-engineering181Updated Aug 31, 2026

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 properly structured SoT.*.md file with ID prefix, frontmatter, and update protocol.

The English summary is being prepared. Showing the original description.

mattgierhart/PRD-driven-context-engineering181Updated Aug 31, 2026

Synchronizes README.md Command Center with current project state. Triggers on gate changes, EPIC status changes, or explicit `/ghm-status-sync` invocation. Outputs updated README.md dashboard with current lifecycle stage, blockers, and metrics.

The English summary is being prepared. Showing the original description.

mattgierhart/PRD-driven-context-engineering181Updated Aug 31, 2026

See all skills by mattgierhart

Report a problem with this skill