guia-matthieu/persona-generator
Create research-backed buyer personas that drive real marketing and product decisions. Combine Buyer Personas methodology with Jobs-to-be-Done to build profiles based on actual behavior, not demographics fiction. Use when: **Starting customer discovery** to define who you're validating with; **Marketing campaign planning** to target the right messages to right people; **Content strategy** to create content that resonates with specific audiences; **Product roadmap prioritization** to build fea...
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill persona-generator
> Create research-backed buyer personas that drive real marketing and product decisions. Combine Buyer Personas methodology with Jobs-to-be-Done to build profiles based on actual behavior, not demographics fiction.
| Aspect | Details |
|--------|---------|
| Source | Adele Revella - "Buyer Personas" (2015) + Clayton Christensen - Jobs-to-be-Done |
| Core Principle | "Buyer personas built on real research reveal the thinking behind buying decisions—not just demographics, but motivations, anxieties, and decision criteria." |
| Why This Matters | Most personas are demographic fiction ("Marketing Mary, 35, likes yoga"). Useful personas explain WHY someone buys—their anxieties, trigger events, and decision process. |
| Claude Does | You Decide |
|-------------|------------|
| Structures production workflow | Final creative direction |
| Suggests technical approaches | Equipment and tool choices |
| Creates templates and checklists | Quality standards |
| Identifies best practices | Brand/voice decisions |
| Generates script outlines | Final script approval |
I've completed [X] customer interviews. Here are my notes: [summary]
Generate buyer personas using the Buyer Personas + JTBD methodology.
Focus on buying triggers, decision criteria, and anxieties.
I'm building [product] for [market].
Generate hypothesis personas I should validate through customer discovery.
Include questions to ask to validate each persona.
Here are our current personas: [paste personas]
Analyze them against best practices.
What's missing? What questions should we research to make them useful?
When generating personas, follow this evidence-based methodology:
## The Persona Problem
### BAD Personas (Demographic Fiction)
"Marketing Mary"
- Age: 35
- Income: $80K
- Lives in suburbs
- Likes yoga and organic food
- Uses Instagram
**Why this fails:**
- Describes demographics, not motivations
- Doesn't explain why she would buy
- Can't drive marketing/product decisions
- Could describe millions of people
### GOOD Personas (Behavioral/JTBD-Based)
"The Overwhelmed First-Timer"
- **Trigger:** Just got promoted to manager, now responsible for [task]
- **Job-to-be-Done:** Make me look competent to my boss
- **Current Behavior:** Using spreadsheets, asking colleagues, stressed
- **Decision Criteria:** Easy to learn, makes me look good, won't fail publicly
- **Anxiety:** "What if I choose wrong and look incompetent?"
**Why this works:**
- Explains what triggered the search
- Reveals what they're really hiring the product to do
- Shows how they decide
- Surfaces what might stop them
- Drives specific marketing and product decisions
## Adele Revella's Five Rings
### Ring 1: PRIORITY INITIATIVE
**What event triggered their search?**
Questions to research:
- What was the trigger event?
- Why now vs. 6 months ago?
- What finally made this urgent?
- What was the breaking point?
Example insight:
"They start looking when they get a new boss who asks 'why don't we have...' or when a competitor does something that makes them look behind."
---
### Ring 2: SUCCESS FACTORS
**What outcome are they trying to achieve?**
Questions to research:
- What does success look like?
- How will they measure results?
- What would make them a hero internally?
- What would make them regret the decision?
Example insight:
"They don't actually want [product feature]. They want to be seen as innovative by their CEO while not risking a high-profile failure."
---
### Ring 3: PERCEIVED BARRIERS
**What could stop them from buying?**
Questions to research:
- What concerns came up during evaluation?
- What almost made them walk away?
- What would cause them to delay?
- What do they fear will go wrong?
Example insight:
"Their biggest fear isn't that it won't work—it's that their team won't use it and they'll have wasted budget on something that sits unused."
---
### Ring 4: DECISION CRITERIA
**How do they evaluate options?**
Questions to research:
- What features/capabilities are must-haves?
- How do they compare options?
- Who else influences the decision?
- What trade-offs are they willing to make?
Example insight:
"They create a spreadsheet comparing 3-5 options. Integration with existing stack is #1. If it doesn't connect to Salesforce, they won't consider it."
---
### Ring 5: BUYER'S JOURNEY
**How do they research and decide?**
Questions to research:
- How did they first learn about the category?
- What resources did they use to research?
- Who did they talk to?
- What was the decision timeline?
Example insight:
"They google '[category] vs [category]' then ask for recommendations in a Slack community. Reviews on G2 are the final checkpoint before talking to sales."
## JTBD Analysis Per Persona
### The Job Statement
"When I [situation], I want to [motivation], so I can [expected outcome]."
### Three Types of Jobs
**Functional Job:** What they need to accomplish
- "I need to get this report done faster"
- "I need to track our campaigns across channels"
**Emotional Job:** How they want to feel
- "I want to feel confident presenting to the board"
- "I don't want to worry about this anymore"
**Social Job:** How they want to be perceived
- "I want my team to see me as innovative"
- "I don't want to look like I made a bad decision"
### Forces That Drive Switching
**Push (away from current):**
- Pain points with current solution
- Frustrations with status quo
- External pressures (boss, market, competition)
**Pull (toward new):**
- Desired outcomes
- Attractive features
- Vision of better future
**Anxiety (about switching):**
- Fear of failure
- Implementation concerns
- Uncertainty about claims
**Habit (keeping current):**
- Familiarity with status quo
- Sunk costs
- "Good enough" mentality
For a persona to buy: Push + Pull > Anxiety + Habit
## PERSONA: [Name Based on Behavior, Not Demographics]
### Snapshot
| Aspect | Detail |
|--------|--------|
| **Role** | [Job title / responsibility] |
| **Environment** | [Company size, industry, team structure] |
| **Primary JTBD** | [Job statement] |
| **Current Solution** | [What they use today] |
---
### Ring 1: Priority Initiative (Trigger)
**What triggers the search:**
- [Specific event 1]
- [Specific event 2]
- [Specific event 3]
**Why now (urgency drivers):**
- [What makes them act now vs. later]
**Quotes:**
> "[Verbatim from research]"
---
### Ring 2: Success Factors
**Desired outcomes:**
1. [Functional outcome]
2. [Emotional outcome]
3. [Social outcome]
**How they'll measure success:**
- [Metric or indicator]
**What makes them a hero:**
- [Internal win they're seeking]
**Quotes:**
> "[Verbatim from research]"
---
### Ring 3: Perceived Barriers
**Concerns/anxieties:**
1. [Concern about product/vendor]
2. [Concern about implementation]
3. [Concern about results]
**What almost stops them:**
- [Top barrier]
**Risk they fear most:**
- [What failure looks like]
**Quotes:**
> "[Verbatim from research]"
---
### Ring 4: Decision Criteria
**Must-haves (non-negotiable):**
1. [Feature/capability]
2. [Feature/capability]
3. [Feature/capability]
**Nice-to-haves:**
- [Feature/capability]
**Deal-breakers:**
- [What would eliminate you]
**How they compare:**
- [Their evaluation process]
**Quotes:**
> "[Verbatim from research]"
---
### Ring 5: Buyer's Journey
**Stage 1 - Trigger:** [What happens]
**Stage 2 - Research:** [Where they look]
**Stage 3 - Evaluate:** [How they compare]
**Stage 4 - Decide:** [Who's involved]
**Stage 5 - Buy:** [Process/procurement]
**Information sources:**
- [Channel 1]
- [Channel 2]
- [Influencers]
**Timeline:** [Typical decision timeframe]
---
### Jobs-to-be-Done
**Primary Job:**
"When I [situation], I want to [motivation], so I can [outcome]."
**Functional Job:** [What to accomplish]
**Emotional Job:** [How to feel]
**Social Job:** [How to be seen]
**Forces Analysis:**
| Force | Strength | Specifics |
|-------|----------|-----------|
| Push | High/Med/Low | [Details] |
| Pull | High/Med/Low | [Details] |
| Anxiety | High/Med/Low | [Details] |
| Habit | High/Med/Low | [Details] |
---
### Marketing Implications
**Messaging that resonates:**
- [Message/hook]
- [Message/hook]
**Content they'd engage with:**
- [Content type]
- [Content type]
**Where to reach them:**
- [Channel]
- [Channel]
**What NOT to say:**
- [Anti-message]
---
### Sales Implications
**Objections to expect:**
- [Objection]
- [Objection]
**Questions they'll ask:**
- [Question]
- [Question]
**Proof points they need:**
- [Case study/demo]
**Decision process:**
- [How deals close with this persona]
## Persona Validation Checklist
### Is this persona based on evidence?
- [ ] Minimum 5 interviews with this type
- [ ] Includes verbatim quotes
- [ ] Describes behavior, not just demographics
- [ ] Explains WHY they buy
### Does this persona enable decisions?
- [ ] Marketing team can use it to target campaigns
- [ ] Product team can use it to prioritize features
- [ ] Sales team can use it to tailor conversations
- [ ] Content team can use it to create relevant assets
### Is this persona distinct?
- [ ] Clearly different from other personas
- [ ] Different triggers
- [ ] Different decision criteria
- [ ] Different objections/anxieties
### Red Flags (Persona Needs Work)
- [ ] Based on assumptions, not research
- [ ] All demographics, no behaviors
- [ ] No quotes from real customers
- [ ] Too vague to drive decisions
- [ ] Overlaps significantly with another persona
Input:
> "Generate personas for our marketing analytics dashboard. Target: marketing managers at 100-500 employee B2B companies. Price: $500/month."
Output:
| Aspect | Detail |
|--------|--------|
| Role | Marketing Manager, reports to VP/CMO |
| Environment | B2B SaaS, 100-300 employees, small marketing team (3-5) |
| Primary JTBD | Prove marketing's ROI to justify budget and headcount |
| Current Solution | Spreadsheets + GA + Hubspot reports (manual) |
What triggers the search:
Why now:
Quotes:
> "My CFO asked me last week what our CAC is by channel. I had to spend a full day in spreadsheets to give him a rough estimate."
Desired outcomes:
How they'll measure success:
What makes them a hero:
Concerns:
What almost stops them:
Risk they fear:
Quotes:
> "We tried a dashboard before and the numbers never matched Hubspot. That was a disaster."
Must-haves:
Nice-to-haves:
Deal-breakers:
How they compare:
Timeline: 4-8 weeks from trigger to purchase
Messaging that resonates:
Where to reach them:
What NOT to say:
| Aspect | Detail |
|--------|--------|
| Role | Marketing Coordinator or Specialist, early career |
| Environment | B2B, 150-400 employees, reports to Marketing Manager |
| Primary JTBD | Get data to my boss without spending all week in spreadsheets |
| Current Solution | Export from 5 tools, combine in Excel, format in Slides |
What triggers the search:
Quotes:
> "Every Monday I dread the reporting. I spend half my day in Excel just pulling numbers together."
Desired outcomes:
Concerns:
Must-haves:
How they compare:
Messaging:
Where to reach:
Who they influence:
Input:
> "We're launching a premium meal prep service ($150/week). Create personas based on these 8 customer interviews."
Interview Summary:
Output:
| Aspect | Detail |
|--------|--------|
| Role | Professional, 28-40, demanding job (consulting, finance, tech) |
| Environment | Urban, long hours, high income, limited personal time |
| Primary JTBD | Eat healthy without sacrificing career performance |
| Current Solution | Takeout, occasional HelloFresh (but doesn't cook it) |
Triggers:
Why now:
Quotes:
> "I know I should eat better. I've tried cooking on Sunday but I'm so tired by the weekend I just don't."
Desired outcomes:
What success looks like:
Concerns:
Anxiety:
Quotes:
> "I've tried Blue Apron twice. Both times I ended up with a fridge full of rotting ingredients."
Must-haves:
Nice-to-haves:
Deal-breakers:
Timeline: Same-week decision for trial
Messaging:
Where to reach:
What NOT to say:
(Abbreviated for space)
| Aspect | Burned-Out Professional | Optimized Athlete |
|--------|------------------------|-------------------|
| Primary JTBD | Eat healthy without effort | Hit my macros precisely |
| Trigger | Health concern, guilt | Competition coming, plateau |
| Success Factor | Convenience | Performance/results |
| Decision Criteria | No cooking | Macro transparency |
| Barrier | "Another subscription" | "Will macros be accurate?" |
| Messaging | "Zero effort" | "Fuel your performance" |
## Customer Interview Guide for Persona Development
### Trigger (Priority Initiative)
- "What was happening when you first started looking for [solution]?"
- "Why now? Why not 6 months ago?"
- "What was the trigger event?"
- "What finally pushed you to do something?"
### Success Factors
- "What did you hope would change after buying?"
- "How would you know if this worked?"
- "If this was perfect, what would that look like?"
- "What would success mean for you personally?"
### Barriers (Perceived Risks)
- "What concerns did you have before buying?"
- "What almost made you NOT buy?"
- "What worries did you have about making a change?"
- "What would failure look like?"
### Decision Criteria
- "What was most important to you in evaluating options?"
- "What features were must-haves?"
- "What made you choose us over alternatives?"
- "What would have been a deal-breaker?"
### Buyer's Journey
- "How did you first hear about this category?"
- "What did you research? Where?"
- "Who else was involved in the decision?"
- "How long from first search to purchase?"
## Persona Quality Score
**Persona:** _______________
| Criteria | Score (1-5) | Notes |
|----------|-------------|-------|
| Based on real interviews (not assumptions) | | |
| Includes verbatim quotes | | |
| Explains triggers (why now) | | |
| Explains decision criteria | | |
| Surfaces real anxieties | | |
| Maps buyer's journey | | |
| Includes JTBD statement | | |
| Distinct from other personas | | |
| Marketing team can use it | | |
| Sales team can use it | | |
**Total:** __/50
- 40+: Ready to use
- 30-39: Needs more research
- <30: Start over with customer interviews
## [Persona Name]
**One-liner:** [Job title] who [key behavior] because [primary motivation].
**Trigger:** They start looking when ________________________________
**Job-to-be-Done:** "When I [situation], I want to [motivation], so I can [outcome]."
**Top 3 Decision Criteria:**
1.
2.
3.
**Biggest Anxiety:** ________________________________
**We win by:** ________________________________
name: persona-generator
category: validation
subcategory: customer-research
version: 1.0
author: MKTG Skills
source_expert: Adele Revella, Clayton Christensen
source_work: Buyer Personas, Competing Against Luck
difficulty: intermediate
estimated_value: $3,000 persona research project
tags: [personas, customer-research, JTBD, buyer-personas, segmentation, YC]
created: 2026-01-25
updated: 2026-01-25
Take guia-matthieu/persona-generator from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.