cold-outreach-sequence
Generate complete multi-touch cold outreach sequences. Not one email — a full campaign where each touch has a different angle, a specific send day, and a clear job to do. Use /cold-email for single emails. Use this when one email isn't enough.
Before Writing Anything
Gather this information — ask for anything missing:
- Target — Role, company type, industry. The more specific, the better the hook.
- Offer — What you're proposing. One sentence.
- Credibility — Social proof. Numbers, notable clients, results. Be specific.
- Goal — Meeting, demo, partnership, intro, advice?
- Unique asset — Demo link, one-pager, case study, free tool? (goes in Email 3)
- Sequence length — 3 touches (light, 7 days) or 5 touches (standard, 12 days)?
If the user says "make it for [target] offering [thing]", extract the rest from context before asking.
The Two Sequence Structures
5-Touch Standard (12 days)
| Touch | Day | Job | Max Length |
|---|---|---|---|
| Email 1 | 1 | Problem + Credibility + Ask | 4 sentences |
| Email 2 | 3 | Bump — low pressure | 2 sentences |
| Email 3 | 5 | Give value, ask nothing | 3 sentences |
| Email 4 | 8 | Social proof — name-drop a real result | 3 sentences |
| Email 5 | 12 | Breakup — clean exit | 2 sentences |
3-Touch Light (7 days)
| Touch | Day | Job | Max Length |
|---|---|---|---|
| Email 1 | 1 | Problem + Credibility + Ask | 4 sentences |
| Email 2 | 3 | Value-add with asset | 3 sentences |
| Email 3 | 7 | Breakup | 2 sentences |
The Rules That Don't Move
Subject lines:
- Email 1: Short, specific. References something real about them.
- Emails 2-5: Always "Re: [original subject]" — stay in the same thread. Do not break the thread.
- Never use: "Following up", "Checking in", "Touching base", "Just wanted to"
Length:
- No email exceeds 60 words in the body
- Emails 2 and 5 should be under 30 words
- If you can remove a word, remove it
Tone escalation:
| Touch | Tone |
|---|---|
| 1 | Confident, direct, problem-aware |
| 2 | Casual, brief, zero pressure |
| 3 | Generous — give something, ask nothing |
| 4 | Social proof — "others are doing this" |
| 5 | Clean exit — door stays open |
What each touch must NOT do:
- Email 1: Must not be generic. If you removed the recipient's name, it should fall apart.
- Email 2: Must not re-pitch. Just nudge.
- Email 3: Must not ask for a call, meeting, or response. Only give.
- Email 4: Must not fabricate social proof. Real clients or skip this touch entirely.
- Email 5: Must not guilt-trip. Clean, warm, final.
The Templates
Email 1
Subject: [specific observation — recent post, job change, company news, product launch]
Hey [Name],
[One sentence: something specific you noticed about them. This sentence must be about them, not you.]
[One sentence: what you do + your strongest proof point.]
[One sentence: specific ask with a time — "15 minutes this week?"]
[Your name]
Email 2
Subject: Re: [original subject]
Hey [Name],
Bumping this in case it got buried.
[Your name]
Email 3
Subject: Re: [original subject]
Hey [Name],
[One sentence: share something genuinely useful — demo, relevant case study, insight about their industry, or a tool they'd care about.]
No pressure on a call — thought this might be relevant.
[Your name]
Email 4
Subject: Re: [original subject]
Hey [Name],
[One sentence: name a real client or result — be specific.] [One sentence: why that's relevant to their situation.]
Happy to show you how — [specific time ask].
[Your name]
Email 5
Subject: Re: [original subject]
Hey [Name],
Last note on this. If the timing's off, completely understand — happy to revisit whenever it makes sense.
[Your name]
Research First
Before drafting Email 1, find a hook. A generic opener makes the whole sequence waste of time. Spend 3 minutes looking at:
- Their LinkedIn: recent post, new role, company milestone
- Their Twitter/X: recent tweet about a problem your offer solves
- Their company: recent funding, launch, press mention
- Job postings: what they're hiring tells you what they're building
The hook in Email 1 must be recent (last 30-60 days) and specific. "I love your work" is not a hook.
Workflow
- Gather target, offer, credibility, goal, asset, sequence length
- Research one specific hook for Email 1
- Draft all emails in sequence order
- Check: is every email under 60 words?
- Check: does Email 1 only work if you know who the recipient is?
- Check: does each touch have a distinct job (no "following up" repeats)?
- Output complete sequence with send days labeled
Verify
[ ] Every email under 60 words
[ ] Email 1 has a specific, researched hook — not generic
[ ] Emails 2-5 thread on same subject line with "Re:"
[ ] Each touch has a different angle — no repeated pitch
[ ] Email 3 gives value with no ask
[ ] Email 4 uses real social proof — or touch is skipped
[ ] Email 5 is clean — no guilt, door stays open
[ ] Send days use business days (no weekends)
[ ] Asset (if exists) is in Email 3, not Email 1
See references/guide.md for full sequence examples across industries and subject line variations.
More from tushaarmehtaa/tushar-skills
ship-credits
Scaffold a complete credits/token metering system for any app — database schema, backend middleware, payment webhooks, frontend state, and UI components. Goes from zero to "users can buy and spend credits" in one session.
17deploy-check
Pre-flight check before pushing to production. Catches TypeScript errors, accidentally staged secrets, pending migrations, and hygiene gaps before they hit live users.
6ship-email
Scaffold transactional and campaign email infrastructure end-to-end — provider setup, templates, user segmentation, and admin send UI. Use when the user wants to add email to their app — welcome emails, notifications, re-engagement, or bulk campaigns. Triggers on requests like "add email", "set up Resend", "email campaigns", "transactional email", "send emails to users", "welcome email", "notification emails", or any mention of email sending in an app context.
6make-skill
Turn any workflow into a properly structured Claude Code skill — YAML frontmatter, phase-based instructions, real code blocks, and a verify checklist. Use when the user wants to package a repeated workflow, create a new skill, turn a process into a slash command, or publish to the skills directory. Triggers on requests like "make a skill", "create a skill", "turn this into a skill", "new skill for...", "package this as a skill", "build a skill", "I want to publish a skill", "help me write a skill", or any request to create a reusable Claude Code skill.
6mvp-spec
Turn a rough product idea into a structured MVP spec — problem statement, personas, core loop, feature split, data model, API routes, page list, and tech stack recommendation. Write this before touching any code. Triggers on requests like "spec this out", "MVP spec", "plan this product", "what should I build first", "scope this idea", "PRD", "product spec", "write a spec for...", "help me plan this", "what do I build in v1", "product requirements", or any request to structure a product idea before writing code.
6og-image
Set up dynamic Open Graph image generation and all required meta tags so links look professional when shared on Twitter/X, LinkedIn, Slack, or anywhere that renders link previews. Triggers on requests like "OG image", "open graph", "social preview", "link preview", "Twitter card", "meta tags for sharing", "my links look broken when I share them", or any mention of how links appear when shared on social media.
6