buyer-personas
Create actionable buyer personas using Adele Revella's 5 Rings of Buying Insight methodology—based on real buyer stories, not demographics. Use when: **Understand why buyers buy** (or don't buy) your solution; **Create personas that drive action** rather than gather dust; **Align marketing and sales** around real buyer insights; **Develop messaging** that resonates with actual decision-makers; **Map content** to the buyer's journey
What this skill does
# Buyer Personas > Create actionable buyer personas using Adele Revella's 5 Rings of Buying Insight methodology—based on real buyer stories, not demographics. ## When to Use This Skill Use this skill when you need to: - **Understand why buyers buy** (or don't buy) your solution - **Create personas that drive action** rather than gather dust - **Align marketing and sales** around real buyer insights - **Develop messaging** that resonates with actual decision-makers - **Map content** to the buyer's journey - **Identify differentiation opportunities** based on buyer concerns - **Improve win rates** by addressing what buyers actually care about This skill is particularly valuable for: - B2B companies with complex buying decisions - Product launches targeting new segments - Companies with misaligned sales and marketing - Teams relying on assumed or outdated buyer knowledge --- ## Methodology Foundation **Source:** Adele Revella - *Buyer Personas: How to Gain Insight into your Customer's Expectations, Align your Marketing Strategies, and Win More Business* (2015) **Core Principle:** Buyer personas should be built on **buying insights**—the actual factors that influence purchase decisions—not demographic profiles or job titles. The 5 Rings of Buying Insight provide a framework for capturing what really matters. > "Buyer personas are examples or archetypes of real buyers that allow marketers to craft strategies to promote products and services to the people who might buy them... based on real stories related by actual buyers." --- ## What Claude Does vs What You Decide | Claude Does | You Decide | |-------------|------------| | Structures video workflow | Final creative vision | | Suggests shot compositions | Equipment selection | | Creates storyboard templates | Brand aesthetics | | Generates script frameworks | Final approval | | Identifies technical requirements | Budget allocation | ## What This Skill Does When invoked, I will guide you through Revella's buyer persona methodology: 1. **Define the buying decision** to focus your research 2. **Identify interview candidates** (recent buyers, won and lost deals) 3. **Conduct insight interviews** using the storytelling approach 4. **Analyze findings** through the 5 Rings framework 5. **Determine persona segmentation** based on meaningful differences 6. **Create actionable persona documents** with buying insights 7. **Apply insights** to messaging, content, and sales enablement --- ## How to Use Provide information about your situation: **Example prompts:** - "Help me create buyer personas for our enterprise HR software" - "I need to understand why we're losing deals to [competitor]" - "Create a buyer persona interview guide for our B2B SaaS product" - "Analyze these interview transcripts and build buyer personas" - "Our personas are outdated—help me refresh them with the 5 Rings framework" **Information that helps:** - Your product/service category - Target market and typical buyer roles - Current understanding of your buyers (even if assumed) - Access to recent buyers for interviews - Won/lost deal information - Competitive context --- ## Instructions ### Phase 1: Define the Buying Decision **Critical first step:** Buyer personas should focus on a specific buying decision, not a general profile. **Define:** 1. **What solution category** are you analyzing? (e.g., "project management software," not "all our products") 2. **What decision** do you want to influence? (e.g., "initial vendor selection," "upgrade decision") 3. **What timeframe** for buyer memories? (ideally last 6-12 months) **Why This Matters:** Vague personas lead to vague insights. A sharp focus on one buying decision yields actionable intelligence. --- ### Phase 2: Plan Buyer Interviews **Who to Interview:** | Category | Why | Target # | |----------|-----|----------| | Recent buyers (won) | Understand what worked | 3-5 | | Recent buyers (lost) | Understand what didn't | 3-5 | | Buyers who chose status quo | Understand barriers | 2-3 | | Buyers from key segments | Ensure coverage | As needed | **Interview Logistics:** - 30-45 minutes per interview - Phone or video (easier to schedule than in-person) - Record with permission (for transcription) - Interviewer should NOT be the salesperson **What NOT to Do:** - Don't interview prospects who haven't completed a decision - Don't use surveys as a substitute - Don't interview internal "experts" about what buyers think --- ### Phase 3: Conduct Insight Interviews **The Opening Question:** > "Take me back to the day when you first decided to evaluate [solution type]. What happened?" This open-ended question triggers storytelling and reveals Priority Initiative naturally. **Follow-Up Probes (use throughout):** - "Tell me more about that..." - "What happened next?" - "Who else was involved at that point?" - "What were you thinking when that happened?" - "How did you go about evaluating that?" - "What concerned you about that?" **Key Interviewing Principles:** 1. **Listen more than talk** - Your job is to capture their story 2. **Follow their lead** - Let the story unfold naturally 3. **Probe for specifics** - "Reliable" means different things to different buyers 4. **Avoid hypotheticals** - "What would you do if..." yields unreliable data 5. **Don't lead** - "Was price important?" biases the response 6. **Capture exact language** - Their words become your messaging **Questions to Ensure Full Coverage:** | Ring | Questions | |------|-----------| | Priority Initiative | "What was happening that made you decide to look for a solution?" | | Success Factors | "What results were you hoping to achieve?" | | Perceived Barriers | "Were there any concerns that almost stopped you? What did you think about vendors you eliminated?" | | Decision Criteria | "What specific questions did you need answered? What capabilities were you evaluating?" | | Buyer's Journey | "Walk me through the steps you took. Who else was involved? What resources did you consult?" | --- ### Phase 4: Analyze Through the 5 Rings After completing interviews, organize findings into the 5 Rings framework. #### Ring 1: Priority Initiative **What triggers buyers to start evaluating NOW?** Extract: - Trigger events (organizational changes, problems, growth) - Personal circumstances (new role, mandate from above) - External factors (market changes, competitive pressure) - Timing factors (budget cycles, planning periods) #### Ring 2: Success Factors **What outcomes do buyers expect to achieve?** Extract: - Business outcomes expected - Personal outcomes expected - Timeline expectations - How they'll measure success #### Ring 3: Perceived Barriers **What fears and concerns cause hesitation or rejection?** Extract: - Concerns about your category/solution type - Concerns about your company specifically - Concerns about change/implementation - Reasons competitors were preferred - Reasons for staying with status quo #### Ring 4: Decision Criteria **What specific attributes do buyers evaluate?** Extract: - Questions buyers asked during evaluation - Features/capabilities compared - Company/vendor attributes compared - Integration/compatibility requirements - Pricing/commercial considerations #### Ring 5: Buyer's Journey **How do buyers navigate from trigger to decision?** Extract: - Steps in the evaluation process - Who's involved at each step - Information sources trusted - Timeline from trigger to decision - How finalists were selected --- ### Phase 5: Determine Persona Segmentation **Key Principle:** You need far fewer personas than you think. **When to Create Separate Personas:** Only segment when there are **meaningful differences in buying behavior:** | Ring | Segmentation Trigger | |------|---------------------| | Priority Initiative | Different triggers/problems drive the search | | Success Factors | Different outcomes are expected | | Perceived Barriers | Different concerns block progress
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.