メニュー
Build detailed buyer personas grounded in real data, not assumptions. Pain mapping, motivation frameworks, and messaging architecture for each persona in your ICP.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Benchmark your outbound campaigns against internal baselines, industry standards, and cross-portfolio performance data. Know if your campaigns are actually good — not just whether they feel good.
Analyze outbound campaign performance across every meaningful metric. Diagnose what's working, what's broken, and exactly where to optimize for higher conversion.
Extract, analyze, and replicate the patterns behind your highest-performing email copy. Turn individual campaign wins into repeatable copy frameworks your team can deploy across every campaign.
Battle-tested cold email copy frameworks that earn replies. Structures, formulas, and templates for writing emails that convert strangers into conversations.
Turn raw prospect data into compelling personalized email elements. Signal detection, personalization layers, and variable frameworks that make cold emails feel warm.
Design multi-step outbound sequences that convert. Timing, channel mix, variant strategy, and escalation logic for cold email campaigns.
| name | persona-development |
| description | Build detailed buyer personas grounded in real data, not assumptions. Pain mapping, motivation frameworks, and messaging architecture for each persona in your ICP. |
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.
Every actionable persona contains these eight elements:
| Field | What to Capture | Example |
|---|---|---|
| Title patterns | All variations of the title they hold | VP of Sales, Vice President Sales, VP Revenue, Head of Sales |
| Seniority band | Their level in the org | VP / Director / C-Suite |
| Department | Where they sit | Sales, Revenue, Growth |
| Reports to | Their boss's title | CRO, CEO, COO |
| Team size | How many people they manage | 5-30 direct reports |
| Tenure | How long they've typically held the role | 1-3 years (relevant for "new in role" trigger) |
| LinkedIn keywords | Phrases 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.
Understand what this persona's week actually looks like:
| Time Block | Activity | Frustration | Opportunity |
|---|---|---|---|
| Monday AM | Pipeline review, forecasting | Numbers never match CRM data | "Is your pipeline review still a spreadsheet exercise?" |
| Monday PM | Team 1:1s | Reps aren't hitting activity targets | "Most VP Sales spend Monday fixing last week's problems" |
| Tuesday-Thursday | Deals, strategy, internal meetings | No time for strategic work | "When did you last have a full day for strategy?" |
| Friday | Reporting to CRO/CEO | Scrambling 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.
Not all pains are equal. Rank them by urgency and budget authority:
| Rank | Pain Category | Specific Pain | Urgency | Budget Authority |
|---|---|---|---|---|
| P1 | Revenue | "We're going to miss our number this quarter" | Critical | Full authority |
| P2 | Efficiency | "My reps spend 60% of their time on non-selling activities" | High | Needs approval |
| P3 | Visibility | "I can't tell which deals are real and which are happy ears" | Medium-High | Can champion |
| P4 | Talent | "I'm losing good reps to companies with better tools" | Medium | Shared decision |
| P5 | Process | "We don't have a documented sales playbook" | Medium-Low | Low priority |
Rule: Always lead your outreach with P1 or P2 pains. P3-P5 are follow-up angles for later steps in the sequence.
What drives this persona personally and professionally:
| Motivation Type | What They Want | How to Reference It |
|---|---|---|
| Career | Get promoted to CRO/CEO within 2 years | "The VPs who get promoted to CRO are the ones who..." |
| Team | Build a winning team they're proud of | "Your reps' success reflects directly on you" |
| Recognition | Be seen as the leader who scaled revenue | "When you present the board deck, what story do you want to tell?" |
| Control | Predictable pipeline, not hope-based forecasting | "Replace 'I think we'll hit our number' with 'I know we will'" |
| Efficiency | More 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.
| Behavior | Description |
|---|---|
| Research style | Where do they go to evaluate solutions? (G2, peers, LinkedIn, events) |
| Decision speed | Fast (days-weeks) or slow (months)? What slows them down? |
| Risk tolerance | Early adopter or "show me the case study first"? |
| Champion or buyer | Do they sign the check, or do they sell internally to someone who does? |
| Objection pattern | What they say when they're interested but cautious (see Objection Mining skill) |
| Preferred communication | Email, LinkedIn DM, phone call, or in-person? |
| Meeting format | 15-min intro, 30-min demo, or 60-min deep dive? |
The exact words and phrases this persona uses to describe their problems:
| Category | Their Language | NOT 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.
Just as important as knowing who to target is knowing who to skip:
| Signal | Why 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 freeze | No budget for new tools |
| LinkedIn activity shows they just implemented a competitor | Wrong 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 |
What other solutions does this persona consider?
| Category | Competitors | How to Position Against |
|---|---|---|
| Direct competitors | Tools/services that do what you do | "Unlike {{competitor}}, we..." (use sparingly) |
| Indirect competitors | Different approaches to the same problem | "You could hire 3 more reps OR..." |
| Status quo | Doing nothing / current manual process | "The spreadsheet approach works until it doesn't" |
| Internal build | Building their own solution | "Most teams that build it themselves spend 6 months and end up with 60% of what they need" |
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:
Most persona docs are fiction. Here's how to build from evidence:
Before launching campaigns against a new persona, verify:
# 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: ___
Progressive disclosure: load role-specific persona deep dives and industry benchmarks only when developing personas for a specific campaign.