follow-upslisted

# Sequence Architecture ## Pipeline contract **Stage 16 of 20.** Reads `14-emails.csv`, `15-linkedin.csv`. Writes `16-sequence.md` (steps, day offsets, channel per step) and `16-followups.csv` (`segment, step, day_offset, channel, subject, body`). - Each follow-up adds something new (proof, angle, resource). A bump that only says "following up" does not ship. - Follow-up copy rules live in [`/cold-email`](../cold-email/SKILL.md) section 7; this skill owns order, timing, and escalation. - Drafts only. Sequence settings are a recommendation for the human's sender. Files live in `runs/<run>/`. Column definitions: [`/prospecting-system`](../prospecting-system/SKILL.md). Standalone use: ignore this block. ## When to Use - Building a new outbound campaign from scratch - Restructuring sequences with poor step-2+ engagement - Designing multi-channel cadences (email + LinkedIn + phone) - Setting up A/B testing frameworks for sequence optimization ## Framework ### Sequence Design Principles 1. **Every step earns the next** — Step 1's job is to get Step 2 opened. Step 2's job is to get a reply. Never front-load everything into Step 1. 2. **New value every touch** — Each step must introduce a new angle, insight, or proof point. "Following up" is not a strategy. 3. **Decay is natural** — Open and reply rates drop with each step. Design for this: your best material goes in Steps 1-2, your boldest ask goes in the final step. 4. **Variants multiply learning** — Run 2-3 subject/body