Scale · Sales Enablement Content
Build a Buyer Persona Enablement Doc
Turn a fluffy marketing persona into a rep-ready doc with real questions, objections, and language.
managerrepIntermediate⏱ 5–8 hours per persona
When to use
Use when reps keep treating every persona the same and discovery calls sound generic. Build one per top-3 persona. Especially useful for new-hire ramp and when expanding into a new vertical.
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 persona docs reps actually open, not the 12-slide marketing kind. Agency: [AGENCY_NAME] — [SERVICES] | Persona: [PERSONA] (title + company stage) | Where we meet them: [SOURCING_CHANNELS] | What they actually buy us for: [JTBD] | What they fear/get burned by: [PAINS] | Real quotes from past calls: [VERBATIMS] Write a one-page sales enablement persona doc for [PERSONA] that a rep can read 5 minutes before a discovery call and immediately sound informed. - One page, skimmable - Use this persona's actual vocabulary — not marketing's - Every section must be call-actionable (not background context) - Include 5 discovery questions and 3 phrases this persona reacts well to - No demographics fluff unless it changes how the rep sells Persona doc: 1) Snapshot (role, what they're measured on) 2) What they're really buying 3) Top 3 fears 4) 5 discovery questions in their language 5) 3 phrases that land + 3 to avoid 6) Common objection + best rebuttal
Variables
- [AGENCY_NAME] — Your agency name
- [SERVICES] — Services you sell to this persona
- [PERSONA] — Title + company context (e.g., VP Marketing, Series B SaaS)
- [SOURCING_CHANNELS] — Where you typically engage this persona
- [JTBD] — The job they hire your agency to do
- [PAINS] — What's gone wrong for them before
- [VERBATIMS] — Direct quotes from past discovery/sales calls
Example input
Persona: VP Marketing at Series B B2B SaaS ($10–30M ARR) | Channels: LinkedIn outbound, podcast guesting, referrals from VCs | JTBD: 'prove paid + content can hit pipeline number my CEO already promised the board' | Pains: last agency hid behind impressions, churned through 3 ABM tools in 18 months | Verbatims: 'I don't need another dashboard, I need a number I can defend.' / 'My CRO doesn't believe marketing-sourced pipeline is real.'
Example output
Persona: VP Marketing, Series B SaaS Snapshot: Reports to CEO. Measured on marketing-sourced pipeline + CAC payback. 18-month average tenure — clock is ticking. What they're really buying: Defensible pipeline number, not 'awareness'. Top 3 fears: Board asking where the spend went. CRO discrediting marketing-sourced. Getting fired before the strategy compounds. Discovery questions: - 'What number did you commit to the board this year?' - 'How does your CRO define marketing-sourced pipeline today?' - 'What did the last agency promise vs. what shipped?' - 'Where in the funnel are you losing the most defensibility?' - 'Walk me through the QBR slide you dread.' Phrases that land: 'pipeline you can defend', 'CRO-credible attribution', 'compounding asset'. Avoid: 'brand lift', 'engagement', 'holistic'. Common objection + rebuttal: 'I've been burned by agencies' → 'Then let's not start with a retainer. Let's start with a 60-day proof.'
Pro tips
- Pull the verbatims from Gong/Fathom recordings — invented language always sounds invented.
- Have one current customer matching the persona review it; their edits are the doc.
- Re-run this prompt quarterly; persona language drifts faster than buying behavior.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS callRelated prompts