Best for
- PMM teams that want personas updated from real buyer conversations
- B2B companies with regular discovery or demo calls
- Sales-led teams with insight trapped in call recordings
Extract pains, triggers, objections, decision criteria, buyer language, and persona patterns from every qualified sales call so personas evolve continuously.
A living persona intelligence database in Notion or Airtable populated from call transcripts, reviewed by PMM, and converted into updated persona cards.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
6 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Traditional personas go stale because they are built from workshops, anecdotes, and one-time research projects. Sales calls contain fresh buyer language, objections, triggers, and decision criteria, but the signal is buried in unstructured transcripts. This workflow turns qualified calls into reviewed, source-backed persona records, then uses monthly synthesis to update messaging and enablement only when repeated evidence supports the change.
Expected results
Qualified calls processed
20-100 per month
Sales-led B2B teams with regular discovery and demo volume can usually process this range after filtering out internal, support, and low-signal calls.
Research time saved
10-20 hours per month
AI extraction reduces manual transcript review, while PMM review keeps official persona updates tied to evidence instead of raw summaries.
Persona freshness
Monthly evidence-backed updates
The cadence keeps personas current enough to influence campaigns and sales plays without overreacting to individual calls.
GTM impact
Persona insights tied to shipped assets
Each meaningful persona update is connected to landing pages, sales plays, nurture emails, launch messaging, or other downstream GTM assets.
Step-by-step workflow
The first 2 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
1-2 hours
1-2 hours
Before routing any transcripts, define the fields PMM actually needs to analyze. Create the database in Notion or Airtable with fields for buyer role, segment, use case, pain, trigger, current workaround, buying committee role, decision criteria, objections, competitor mentions, exact buyer language, evidence quote, call URL, account name, opportunity stage, confidence score, and review status. Add allowed values where possible so the system does not produce twenty versions of the same persona label. Create views for unreviewed records, approved records, persona themes, and monthly changes. This schema is the difference between a useful research system and a pile of AI summaries.
A persona intelligence database with structured fields, approved values, evidence requirements, and review views.
Keep the first schema focused. Ten consistently populated fields are more valuable than forty fields that only get filled in half the time.
Design a persona intelligence database schema for PMM.
ICP:
{{icp}}
Current persona hypotheses:
{{persona_hypotheses}}
Sales motion:
{{sales_motion}}
Products or use cases sold:
{{product_use_cases}}
Return:
1. Recommended database fields
2. Field type for each field
3. Allowed values where useful
4. Required versus optional fields
5. Evidence rules
6. Confidence scoring rules
7. Review statuses
8. Example filled record
9. Views PMM should create for analysis
Keep the schema practical enough to maintain every month.1 hour
1 hour
Use Gong, Salesforce, and Zapier to route only the calls that can improve persona intelligence. Include discovery calls, demo calls, evaluation calls, late-stage buyer meetings, and win-loss calls with enough buyer participation. Exclude internal meetings, short scheduling calls, customer support calls, implementation calls, and calls where the transcript is mostly the seller talking. Add filters for opportunity stage, call duration, account segment, call type, and whether a transcript is available. Create a rejected-call log so you can later inspect whether the filters are too strict or too loose.
A clean call intake filter that routes qualified buyer conversations and excludes low-signal recordings.
Bad filtering ruins the database faster than bad prompting. Persona research should come from buyer evidence, not every recorded conversation in the sales org.
Pro workflow preview
Previewing 2 of 8 steps
Get the remaining 6 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
A positioning refresh memo with customer language, message pillars, objection themes, and copy recommendations.
A prioritized product education backlog with themes, affected segments, recommended assets, owners, and measurement plan.
A validated messaging recommendation with variants, persona critique, buyer feedback, and a final copy decision.