outreach-sequence-builder
Use when creating outreach sequences, writing cold email campaigns, building multi-channel cadences, designing follow-up flows, or crafting signal-triggered messages. Triggers: 'build an outreach sequence', 'write a cold email sequence', 'create a cadence', 'outreach for [signal]', 'email sequence', 'follow-up sequence', 'multi-channel outreach'.
git clone --depth 1 https://github.com/Othmane-Khadri/gtm-engineer-playbook /tmp/outreach-sequence-builder && cp -r /tmp/outreach-sequence-builder/.claude/skills/gtm-playbook/outreach-sequence-builder ~/.claude/skills/outreach-sequence-builderSKILL.md
# Outreach Sequence Builder Build signal-triggered, multi-channel outreach sequences that convert. Maps **Signal --> Angle --> Channel --> Message --> Objection Pre-emption**. Produces ready-to-use sequences in markdown, written to `docs/sequences/`. Can reference `docs/icp.md` for persona and pain-point data, and `docs/accounts/*.md` for account-level personalization. Works for any B2B product or service. --- ## Methodology Follow these steps in order. Do not skip steps. Do not produce output until Step 7. ### Step 1 -- Context Loading Check for existing files before asking questions. 1. **Read `docs/icp.md`** if it exists. Extract: - Target personas (titles, seniority, department) - Company profile (size, industry, stage) - Pain points (ranked by severity) - Language patterns (how prospects describe their problems in their own words) - Key differentiators of the product/service 2. **Glob `docs/accounts/*.md`** if any exist. Extract: - Account names and context - Known tech stack, recent news, or specific pain points - Any existing relationship context 3. **If neither file exists**, gather the minimum viable context by asking the user these four questions (all four are required before proceeding): - What does your product/service do? (one paragraph) - Who are you targeting? (job title, company size, industry) - What is the main problem you solve? (from the buyer's perspective) - What is your key differentiator? (why you over the alternative) Do not proceed to Step 2 until context is loaded or gathered. --- ### Step 2 -- Trigger Selection Present the trigger signal menu and ask the user to select one or more: | # | Trigger Signal | Example | |---|---------------|---------| | 1 | **Post-Fundraise** | Company just raised a round -- they have budget and a mandate to grow | | 2 | **Hiring Signal** | Company posting SDR, GTM, growth, or ops roles -- they are scaling a function you serve | | 3 | **Competitor Displacement** | Prospect is using a competitor and showing frustration -- switching cost feels low | | 4 | **Product Launch** | Company released a new product or feature -- adjacent needs surface | | 5 | **Content Engagement** | Prospect liked, commented, or shared content relevant to your space | | 6 | **Event Follow-up** | Met at a conference, attended the same webinar, or appeared on the same panel | | 7 | **Job Change** | Contact moved to a new company -- fresh mandate, open to new vendors | The user may select multiple triggers or describe a custom trigger. For custom triggers, map them into the same structure (signal, what it reveals, why it matters now). --- ### Step 3 -- Angle Development For **each** selected trigger, develop four components: 1. **The Insight** -- What does this signal tell you about the prospect's current situation? Be specific. "They raised a Series B" is not an insight. "They raised a Series B and are hiring 4 SDRs, which means they are building outbound from scratch and will hit tooling decisions within 60 days" is an insight. 2. **The Bridge** -- How does your product connect to what this signal reveals? The bridge must feel inevitable, not forced. The prospect should think "that makes sense" not "nice try." 3. **The Opener** -- One sentence that proves you did your research. It must reference the specific signal. No generic openers. No "I came across your company and was impressed." The opener must contain a concrete detail only someone paying attention would know. 4. **The Ask** -- The minimum viable CTA. Not "book a 30-minute demo." Something the prospect can say yes to in under 10 seconds: - "Worth a 10-minute look?" - "Want me to send the comparison?" - "Happy to share how [similar company] handled this -- interested?" - "Mind if I send a 2-minute walkthrough?" --- ### Step 4 -- Channel Strategy For each sequence, define the channel mix from these three channels: - **Email** -- Best for: first touch with unknown contacts, detailed value propositions, case study sharing, async communication with busy executives. Strength: space for context. Weakness: crowded inbox. - **LinkedIn** -- Best for: warm connections, social proof via mutual connections, content engagement before outreach, connection requests that build familiarity. Strength: profile visibility. Weakness: character limits, connection-gated. - **Phone** -- Best for: hot leads where timing matters, time-sensitive signals (fundraise announced today), executives who ignore email, and as a pattern interrupt after email/LinkedIn touches. Strength: real-time conversation. Weakness: hard to reach, requires research on direct dials. **Default cadence guidelines:** - 3 to 5 touchpoints per sequence - Never exceed 6 touchpoints - Spread across 2 to 3 channels - Total sequence duration: 10 to 14 days - Minimum 2 days between touchpoints (no back-to-back days) - Vary the channel -- never send the same channel type twice in a row --- ### Step 5 -- Message Writing For each touchpoint in the sequence, write the complete message. **Per-touchpoint deliverables:** For **email** touchpoints: - Subject line (primary) - Subject line (A/B variant) - Body (under 100 words -- hard cap) - CTA (one clear ask) - Tone note (one sentence on how to deliver this) For **LinkedIn** touchpoints: - Connection note or DM (under 300 characters -- hard cap) - Tone note For **phone** touchpoints: - Opening line (under 20 words) - Talk track (3 to 4 bullet points, not a script) - Voicemail script (under 30 seconds when read aloud) - Tone note **Writing rules -- apply to every message, no exceptions:** 1. The first sentence must be about THEM. Not your company, not your product, not your excitement about reaching out. Them. 2. Reference the specific trigger signal. If the signal is a fundraise, mention the round. If it is a job posting, mention the role. Generic messages fail. 3. No buzzwords. Banned list: synergy, leverage, touch base, circle back,
Use when preparing to engage a target account, researching a company before outreach, or building pre-call intelligence. Triggers: 'research this company', 'account brief for [company]', 'company research', 'what do I need to know about [company]', 'pre-outreach research'.
Use when designing an autonomous agent, planning agent architecture, building a scheduled automation, or creating a Claude Code agent workflow. Triggers: 'design an agent', 'build an automation', 'agent architecture', 'automate this workflow', 'create a scheduled agent', 'shell script agent'.
Use when analyzing competitors, creating sales battlecards, building competitive positioning, preparing for competitive deals, or updating competitive intelligence. Triggers: 'battlecard for [competitor]', 'competitive analysis of [competitor]', 'how do we beat [competitor]', 'compare us to [competitor]', 'competitive intel', 'win against [competitor]'.
Use when auditing CRM data quality, finding duplicate records, identifying stale leads, cleaning pipeline data, or improving data hygiene. Triggers: 'clean my CRM', 'audit CRM data', 'find duplicates', 'CRM hygiene', 'data quality check', 'stale leads', 'pipeline cleanup'.
Use when building or refining an Ideal Customer Profile (ICP), defining target personas, mapping buyer psychographics, or discovering where prospects gather online. Triggers: 'build my ICP', 'define target customer', 'who should I sell to', 'refine ICP', 'persona mapping'.
Use when preparing for a sales meeting, discovery call, demo, or customer check-in. Triggers: 'prep me for a meeting with [company]', 'meeting brief for [company]', 'pre-call prep', 'I have a call with [contact] at [company]', 'meeting prep', 'call prep'.
Use when scoring leads, qualifying prospects, prioritizing pipeline, deciding which accounts to pursue, or building a lead scoring model. Triggers: 'score this lead', 'qualify this prospect', 'is this a good lead', 'lead scoring', 'prioritize my pipeline', 'qualification framework'.
Use when searching for buying signals, detecting intent data, scoring prospect readiness, or monitoring accounts for trigger events. Triggers: 'scan for signals', 'find buying signals', 'who is ready to buy', 'intent signals', 'signal scoring', 'account signals'.