Persona Development logo

Persona Development

Community
kenny589
persona-development

Build detailed buyer personas grounded in real data, not assumptions. Pain mapping, motivation frameworks, and messaging architecture for each persona in your ICP.

Overview

Publisherkenny589
Repositorygtm-flywheel
Skill namepersona-development
Stars
71
Forks
26
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by kenny589 on GitHub. Read the source before you install it.

Installation

Install the Persona Development AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/kenny589/gtm-flywheel/tree/main/icp-research/persona-development
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/kenny589/gtm-flywheel.git /tmp/gtm-flywheel
mkdir -p .claude/skills
cp -r /tmp/gtm-flywheel/icp-research/persona-development .claude/skills/persona-development
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Persona Development in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Persona Development on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Persona Development is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Persona Development

When to Use

  • Building outbound campaigns for a new persona or title
  • Copy is getting opens but not replies (persona-message mismatch)
  • Expanding from one buyer persona to multiple within the same account
  • Training AI systems or SDRs on how to speak to specific personas

Framework

Persona vs. ICP: The Difference

ICP = the company you should target (firmographics, technographics, intent signals) Persona = the person within that company you should contact (role, pain, motivation)

You need both. An ICP without personas means you're emailing companies, not people. A persona without an ICP means you're reaching the right person at the wrong company.


The Persona Blueprint: 8 Components

Every actionable persona contains these eight elements:

1. Identity Profile
FieldWhat to CaptureExample
Title patternsAll variations of the title they holdVP of Sales, Vice President Sales, VP Revenue, Head of Sales
Seniority bandTheir level in the orgVP / Director / C-Suite
DepartmentWhere they sitSales, Revenue, Growth
Reports toTheir boss's titleCRO, CEO, COO
Team sizeHow many people they manage5-30 direct reports
TenureHow long they've typically held the role1-3 years (relevant for "new in role" trigger)
LinkedIn keywordsPhrases in their headline or About"building pipeline," "scaling revenue," "B2B growth"

Why title patterns matter: If your email platform matches on exact titles, you'll miss 40-60% of your audience. "VP of Sales" and "Vice President, Revenue" might be the same person. Capture every variant.

2. The Day-in-the-Life Map

Understand what this persona's week actually looks like:

Time BlockActivityFrustrationOpportunity
Monday AMPipeline review, forecastingNumbers never match CRM data"Is your pipeline review still a spreadsheet exercise?"
Monday PMTeam 1:1sReps aren't hitting activity targets"Most VP Sales spend Monday fixing last week's problems"
Tuesday-ThursdayDeals, strategy, internal meetingsNo time for strategic work"When did you last have a full day for strategy?"
FridayReporting to CRO/CEOScrambling to build the narrative"Friday afternoon report assembly shouldn't take 3 hours"

How to use this: Your email should land during a moment of relevant frustration. If you're selling pipeline tools, send Tuesday morning — not Friday afternoon when they're already in reporting mode.

3. Pain Hierarchy (Ranked)

Not all pains are equal. Rank them by urgency and budget authority:

RankPain CategorySpecific PainUrgencyBudget Authority
P1Revenue"We're going to miss our number this quarter"CriticalFull authority
P2Efficiency"My reps spend 60% of their time on non-selling activities"HighNeeds approval
P3Visibility"I can't tell which deals are real and which are happy ears"Medium-HighCan champion
P4Talent"I'm losing good reps to companies with better tools"MediumShared decision
P5Process"We don't have a documented sales playbook"Medium-LowLow priority

Rule: Always lead your outreach with P1 or P2 pains. P3-P5 are follow-up angles for later steps in the sequence.

4. Motivation Map

What drives this persona personally and professionally:

Motivation TypeWhat They WantHow to Reference It
CareerGet promoted to CRO/CEO within 2 years"The VPs who get promoted to CRO are the ones who..."
TeamBuild a winning team they're proud of"Your reps' success reflects directly on you"
RecognitionBe seen as the leader who scaled revenue"When you present the board deck, what story do you want to tell?"
ControlPredictable pipeline, not hope-based forecasting"Replace 'I think we'll hit our number' with 'I know we will'"
EfficiencyMore output with the same headcount"Add $2M pipeline without adding headcount"

Key insight: People buy for personal reasons and justify with business reasons. Your email hook should tap the personal motivation. Your proof points should satisfy the business justification.

5. Buying Behavior Profile
BehaviorDescription
Research styleWhere do they go to evaluate solutions? (G2, peers, LinkedIn, events)
Decision speedFast (days-weeks) or slow (months)? What slows them down?
Risk toleranceEarly adopter or "show me the case study first"?
Champion or buyerDo they sign the check, or do they sell internally to someone who does?
Objection patternWhat they say when they're interested but cautious (see Objection Mining skill)
Preferred communicationEmail, LinkedIn DM, phone call, or in-person?
Meeting format15-min intro, 30-min demo, or 60-min deep dive?
6. Language Profile

The exact words and phrases this persona uses to describe their problems:

CategoryTheir LanguageNOT Your Language
Problem"We can't fill the top of the funnel""Your demand generation needs optimization"
Goal"I need more pipeline, fast""Accelerate revenue acquisition velocity"
Frustration"My reps are guessing""Your team lacks data-driven insights"
Success"We crushed our number""Revenue targets were exceeded"
Evaluation"Does it actually work?""What's the ROI methodology?"

How to build this: Read their LinkedIn posts. Listen to their podcast appearances. Scan sales call transcripts. The phrases they use repeatedly ARE your copy.

7. Anti-Persona Signals (Disqualifiers)

Just as important as knowing who to target is knowing who to skip:

SignalWhy It's a DQ
"We handle this in-house" (in LinkedIn bio)Not looking to outsource
Title includes "Interim" or "Fractional"Temporary, won't start new vendor relationships
Company is in hiring freezeNo budget for new tools
LinkedIn activity shows they just implemented a competitorWrong timing — wait 12-18 months
Title is too senior for your product (CEO at 10K+ company)Won't personally evaluate, delegates too many layers down
Title is too junior (SDR, BDR, Account Executive)Can't champion, can't buy
8. Competitive Landscape (Per Persona)

What other solutions does this persona consider?

CategoryCompetitorsHow to Position Against
Direct competitorsTools/services that do what you do"Unlike {{competitor}}, we..." (use sparingly)
Indirect competitorsDifferent approaches to the same problem"You could hire 3 more reps OR..."
Status quoDoing nothing / current manual process"The spreadsheet approach works until it doesn't"
Internal buildBuilding their own solution"Most teams that build it themselves spend 6 months and end up with 60% of what they need"

Multi-Persona Account Strategy

For B2B deals, you rarely sell to one person. Map the buying committee:

Account: {{companyName}}
├── Economic Buyer (signs the check)
│   └── CRO / VP Sales — lead with ROI and revenue impact
│
├── Champion (sells internally for you)
│   └── Director of Sales / RevOps Lead — lead with ease and efficiency
│
├── Influencer (shapes the evaluation)
│   └── Sales Manager / Team Lead — lead with day-to-day pain relief
│
├── Blocker (can kill the deal)
│   └── IT / Security / Finance — lead with compliance and risk reduction
│
└── End User (will use the product daily)
    └── SDR / AE — lead with "this makes your job easier"

Sequencing strategy:

  1. Start with the Champion (most responsive, lowest risk)
  2. Get the Champion to introduce you to the Economic Buyer
  3. Address the Blocker proactively (send them the security doc before they ask)
  4. Never cold-email the End User in enterprise deals — they can't buy

Building Personas from Data (Not Assumptions)

Most persona docs are fiction. Here's how to build from evidence:

Source 1: Win/Loss Analysis
  • Interview 5-10 customers who bought: Why did they buy? What almost stopped them?
  • Interview 5-10 prospects who didn't buy: What would have changed their mind?
  • Look for the patterns in both sets
Source 2: Sales Call Transcripts
  • Pull 20+ discovery call transcripts
  • Extract: pain points mentioned, language used, questions asked, objections raised
  • Frequency analysis: which pains come up in 70%+ of calls?
Source 3: LinkedIn and Content Analysis
  • Read 50+ LinkedIn posts from people with your target title
  • What topics do they engage with? What do they complain about? What do they celebrate?
  • The intersection of "what they post about" and "what you solve" = your opening angle
Source 4: CRM Data
  • Which titles have the highest close rate?
  • Which titles have the shortest sales cycle?
  • Which titles generate the highest deal value?
  • This tells you WHO to prioritize, not just WHO to contact
Source 5: Customer Support and Success
  • What do existing customers of this persona type ask for most?
  • What features do they use/not use?
  • What language do they use in support tickets?

Persona Validation Checklist

Before launching campaigns against a new persona, verify:

  • You can name 5+ specific companies where this persona exists and matches your ICP
  • You have at least 500 contacts with this persona available for outreach
  • You've identified at least 3 unique pain points from real data (not assumptions)
  • You can write the opening line of a cold email in their language, not yours
  • You know where they spend time online (LinkedIn, specific communities, events)
  • You've identified the anti-persona signals that disqualify lookalikes
  • Your sales team has closed at least 2 deals with this persona (or you've validated with interview data)

Templates

Persona Document Template

# Persona: {{persona_name}}
# Segment: {{icp_segment}}
# Last Updated: {{date}}

## Identity
- Title patterns: ___
- Seniority: ___
- Department: ___
- Reports to: ___
- Team size: ___

## Top 3 Pains (Ranked)
1. ___
2. ___
3. ___

## Motivations
- Career goal: ___
- Team goal: ___
- Personal driver: ___

## Language Bank
- How they describe the problem: "___"
- How they describe success: "___"
- Phrases to use: ___
- Phrases to avoid: ___

## Buying Behavior
- Research style: ___
- Decision speed: ___
- Role in buying committee: ___
- Common objections: ___

## Disqualifiers
- Skip if: ___

## Best Outreach Channels
- Primary: ___
- Secondary: ___

## Proof Points That Resonate
- Case study: ___
- Metric: ___
- Social proof: ___

Tips

  • Interview at least 5 real humans with this title before finalizing the persona. Reading LinkedIn posts is research. Talking to them is validation.
  • The best persona insight usually comes from the question: "What did you try before us?" Their previous failed solution reveals the real pain better than any survey.
  • Personas decay. A VP Sales persona from 2023 is different from 2026 — the market has shifted, priorities change, new tools emerge. Refresh annually.
  • Don't over-segment. 2-3 well-researched personas beat 8 shallow ones. You need enough depth to write copy that resonates, not just enough categories to feel organized.
  • If your persona and your anti-persona look similar on paper, your persona isn't specific enough. Keep narrowing until a stranger could tell them apart from the description alone.

Progressive disclosure: load role-specific persona deep dives and industry benchmarks only when developing personas for a specific campaign.

Frequently asked questions

What does the Persona Development AI skill do?

Build detailed buyer personas grounded in real data, not assumptions. Pain mapping, motivation frameworks, and messaging architecture for each persona in your ICP.

Why use Persona Development on TypingMind?

Because you install it once and use it with any model. Persona Development is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Persona Development in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/kenny589/gtm-flywheel/tree/main/icp-research/persona-development. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Persona Development?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Persona Development?

As many as you like. As long as a model supports skills, you can use Persona Development with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Persona Development AI skill free?

Yes. It is published on GitHub by kenny589 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇