Build signal-triggered multi-channel sequences
outreach-sequence-builderskillsetup L2★40
Othmane-Khadri/gtm-engineer-playbook ↗Causal-lift measurements
outreach-campaigning+13pp vs no-skill baselinewith-skill 80% · baseline 67%
Measured by running the task with and without this artifact, K=5, graded by deterministic checks — no LLM judging.
What it does
Build signal-triggered multi-channel outreach sequences for B2B
Best for
B2B outreach teams building repeatable sequences around specific trigger events (funding, hiring, product launches) where each sequence maps insight → bridge → opener → ask structure.
Inputs
- · ICP definition (personas, company profile, pain points) from docs/icp.md
- · Account-level context from docs/accounts/*.md (optional)
- · Trigger signal selection (post-fundraise, hiring, competitor use, product launch, event, job change)
Outputs
- · Per-trigger sequence with 4 components: insight, bridge, opener, ask
- · Multi-channel sequence (email + LinkedIn)
- · Markdown sequences written to docs/sequences/
Requires
- · File system read (icp.md, accounts/*.md)
Preconditions
- · ICP or 4-question context provided (product/service, target, pain point, differentiator)
- · Trigger signal(s) selected
Failure modes
- · Insight is generic ('Series B raising means they have budget') not specific
- · Bridge feels forced instead of inevitable
- · Opener generic instead of proving specific research
- · Ask is too large (30-min demo vs 10-min look)
Trust signals
- · 7-trigger menu with specific examples (post-fundraise, hiring signal, competitor displacement, product launch, content engagement, event follow-up, job change)
- · Per-trigger development structure: insight (specific from signal), bridge (inevitable connection), opener (proves research), ask (minimum viable CTA)
- · ICP loading from files (personas, pain points, language patterns) vs 4-question fallback if files don't exist