Scale · Sales Enablement Content
Build a Cold-Outreach Snippet Library
Stock a reusable library of cold-email snippets reps mix-and-match instead of writing from scratch.
managerrepIntermediate⏱ 8–12 minutes per cold email, per rep
When to use
Use when reps are writing every cold email from a blank page and quality is wildly inconsistent. Build snippet packs by persona and trigger so reps assemble a personalized email in 90 seconds, not 15 minutes.
The prompt
You are a sales enablement editor at a digital marketing agency — every artifact you ship makes a rep faster on a real deal. You write snippet libraries, not templates: reps assemble, they don't just copy. Agency: [AGENCY_NAME] — [SERVICES] | Target persona: [PERSONA] | Common triggers reps reach out on (funding, hire, ranking drop, etc.): [TRIGGERS] | Proof points: [PROOF_POINTS] | CTA preferences (call, audit, async): [CTA_TYPES] | What's getting deleted right now: [LOSING_PATTERNS] Build a snippet library reps can mix-and-match into a cold email for [PERSONA] in under 90 seconds. - Snippets must be modular — never a full email - Each snippet ≤2 sentences - 5 categories minimum: openers, observation/trigger, proof drop, soft CTA, hard CTA - 5 variants per category - No 'I hope this finds you well', no 'quick question', no 'circling back' - Each snippet labeled with persona + trigger it fits Snippet library table: Category | Variant # | Snippet text | Best for (persona/trigger) | Avoid when
Variables
- [AGENCY_NAME] — Your agency name
- [SERVICES] — Services you sell
- [PERSONA] — Target persona for these snippets
- [TRIGGERS] — Triggers reps watch for
- [PROOF_POINTS] — Numbers + named-client proof you can drop
- [CTA_TYPES] — Which CTAs convert best for this persona
- [LOSING_PATTERNS] — Phrasing/openers that are dying right now
Example input
Persona: VP Marketing at Series B SaaS | Triggers: just raised, new VP hire, replatformed website, lost a top organic keyword | Proof: '142% YoY organic growth at [Client]', '$4.2M sourced pipeline at [Client2]' | CTAs: async audit > call > generic 'chat' | Losing patterns: 'just wanted to introduce myself', 'thought you might be interested'
Example output
Snippet Library (excerpt) Openers 1. 'Saw [Client] just announced [Trigger] — congrats. Not a pitch, observation:' (Series B+, post-funding) 2. 'Your [Page] is ranking #14 for [Keyword]. Two weeks ago it was #6.' (any persona, post-drop) 3. 'New VP marketing at [Client]? Usually means a re-platform is coming.' (post-hire) Observation 1. 'Your sitemap has 312 URLs. Google indexes 89.' 2. 'You're paying for [Keyword] in Google Ads but ranking #3 organically — that's a leak.' 3. 'Your competitor [X] just published 11 GEO-optimized pages. You haven't.' Proof drop 1. 'Last time we ran this play, [Client] added $4.2M sourced pipeline in 9 months.' 2. 'We did this for [Client2] — 142% YoY organic, same vertical, same stage.' Soft CTA 1. 'Want the 4-line audit? I'll send it Thursday, no call required.' 2. 'Worth a Loom? 6 minutes, no calendar.' Hard CTA 1. '20 minutes Tuesday or Wednesday?' 2. 'Open to a 15-min fit call?' Avoid: 'circling back', 'just wanted to', 'quick question'.
Pro tips
- Store snippets in your sequencer's variable library (Apollo, Instantly, Lemlist) so reps assemble live.
- A/B by category, not whole email — you learn which openers and which CTAs actually move reply rate.
- Retire any snippet with a sub-10% open or sub-2% reply rate; libraries decay quarterly.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS callRelated prompts