creatop-gtm/apollo-operator / .claude/skills/apollo-sequence-builder
apollo-sequence-builder
VerifiedWrite a 3-step, 2-variation cold email sequence matched to the persona (ATL or BTL) and build it in Apollo as an inactive draft. Use to write and create outbound sequences on Apollo.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 23.9 KB |
| references/atl-btl.md | markdown | 2.0 KB |
| references/frameworks.md | markdown | 2.6 KB |
references/atl-btl.md
View on GitHub# ATL vs BTL: write to the person, not the company
> Executives and individual contributors read different emails. Decide which one you are writing to before you write a word. ATL is above the line (VP, C-level, director). BTL is below the line (manager, IC, end user). Pull seniority from the list or `profile.yaml`.
## Above the line (VP, C-level, director)
They think strategically, they skim, and they want validation more than a fix.
- **2 to 3 sentences. Maximum.** Every word earns its place.
- **Strategic language:** revenue impact, risk, competitive position, a board-level priority.
- **Lead with the outcome, not the process.** They care what changes, not how it works.
- **A question often lands well:** "What would it mean for next year's targets if..."
- **Fatal mistake:** talking about daily operations, time saved, or manual workflows. It gets you delegated down to a subordinate, and you lose the thread.
## Below the line (manager, IC, end user)
They think tactically, they want a problem solved now, and they care about their daily work.
- **3 to 4 sentences.** A little more room than ATL, still tight.
- **Operational language:** "stop spending 3 hours on...", "cut reporting time by...", specific time or effort saved.
- **Lead with the daily pain.** Name the frustration they actually deal with.
- **Make them look good to their boss.** BTL buyers care how they are perceived.
- **Fatal mistake:** ROI, strategy, and board-level abstractions. Too far from their day, so it gets ignored.
## How to pick
- The list has seniority. VP and above, or "director," go ATL. Manager and below go BTL.
- When a title is ambiguous (a "Head of X" at a 20-person company is often the strategic buyer and the operator both), write closer to ATL but keep one concrete operational proof point.
- In a buying committee you may run both, a strategic angle to the exec and an operational angle to the champion, as separate sequences. Keep them distinct, not a blend that fits neither. The full method, including timing and the stop rule, is in `account-based-outbound`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |