← ClaudeAtlas

buyer-personaslisted

Maps the enterprise buying committee (Economic Buyer, Champion, Technical Evaluator, End User, Procurement) before any messaging, then builds Dunford-structured, alternatives-anchored personas ready for positioning-messaging. Trigger with "map our buying committee", "who do we need to win over", "build our buyer personas", "who kills our deals".
stefanoskarakasis/Product-Marketing-Skills · ★ 13 · AI & Automation · score 80
Install: claude install-skill stefanoskarakasis/Product-Marketing-Skills
# Buyer Personas — Skill ## How This Works Enterprise B2B purchases aren't made by personas — they're made by committees. A messaging deck built for one buyer title routinely misses the person who can actually kill the deal. This skill maps power first (who approves, who champions, who can veto, who just uses the thing) and only then builds messaging personas from that map — Dunford-structured, anchored to named alternatives, ready to feed straight into `positioning-messaging`. It reads your brain's ICP and alternatives (Sections 2 and 3) instead of starting cold, and it compounds the way every other skill in this repo does — one row per session in `/context/skill-sessions.md` — not through a separate knowledge or decisions system of its own. **Step 0** — Load brain Sections 2 (ICP) and 3 (Alternatives), and any guardrail from `/context/meta-patterns.md` fired 2+ times. **Step 1** — Gather input: research data if provided, or run a structured 5-question intake if none exists. **Step 2** — Map the committee: identify roles by behavior, not title, and extract kill pattern / champion pattern / messaging gap for each. **Step 3** — Build messaging personas: one card per role that needs differentiated messaging, each anchored to named alternatives. **Step 4** — Deliver both outputs, then hand off to `positioning-messaging` with an explicit note on which persona is primary. **Step 5** — Learning Close: log the session to `/context/skill-sessions.md`. --- ## Trigger - **W