How to create buyer personas: pull deal and call data, talk to recent buyers, map who can spend, write a one-page story, then test it on the next ten calls. A persona is a decision model, not a cartoon with a hobby list. Gartner's B2B buying research still puts a typical buying group at 6 to 10 people. One "Marketing Mary" slide cannot cover that chain.
This guide is for product marketers, founders, and RevOps leads at B2B SaaS companies. You will get seven steps, TAP Persona (Trigger, Authority, Proof), one worked example, a prompt, and the mistakes that leave teams filing unused PDFs.
In plain terms: say who buys. Say what started the search. Say who holds the budget. Say what proof they need. Then check it against a real deal.
TL;DR
- How to create buyer personas means building a decision model: trigger, authority, and proof, not a demographic sketch with a first name.
- Use CRM wins and losses plus five live conversations. Do not start from a whiteboard.
- Map roles by budget power. A director and a VP do not buy the same way.
- Validate the draft on the next ten discovery calls, or rebuild it.
- Pair the write-up with a buyer persona template and the in-app persona page pattern so sales can act on it.
What is a buyer persona?
A buyer persona is a short model of how one role decides. It records the pain that started the search, who else is in the room, what budget they hold, and what evidence de-risks the close.
A profile is a mugshot. Job title, industry, company size. A persona is the decision. Adele Revella's Buyer Persona Institute treats interviews as the source of truth for that decision, not a form with hobbies.
When you learn how to create buyer personas the useful way, you are writing a mini operating system. Product uses it to pick roadmap. Sales uses it to sequence outreach. Marketing uses it to choose channels and the value proposition that role will believe.
This is not your ICP. ICP is the company you want. A persona is the person inside that company who can move a deal. Do not mash them into one page.
The TAP Persona is the filter we use:
| TAP part | What it answers | Why it matters |
|---|---|---|
| Trigger | What started the search? | Gives outbound a first line that is not a feature dump |
| Authority | Who can spend, and who only recommends? | Stops you pitching a user as if they sign |
| Proof | What evidence de-risks the buy? | Tells you which case study, demo, or metric to show |
If a draft cannot fill those three cells, it is still a sketch.
How to create buyer personas in 7 steps
Marketers search how to create buyer personas because they want a repeatable workflow, not another definition. This is TAP plus a 30-day check for B2B SaaS.
Step 1: Pull signals from deals and calls
Start with revenue data, not guesses. Export closed-won and closed-lost. Keep company size, industry, deal value, cycle length, and buyer-side titles. Add call recordings from Gong, Chorus, or Zoom.
| Signal type | What you get | Where it lives |
|---|---|---|
| Role and company | Title, size, industry | CRM, LinkedIn |
| Company facts | Revenue, stack, stage | ZoomInfo, BuiltWith, G2 |
| Behavior | Pages, emails, events | Product analytics, site analytics |
| Motives | Fears, criteria, triggers | Interviews and call transcripts |
| Talk track | Objections and rival names | Gong, Chorus, manual review |
You need at least three of those five. HubSpot's persona method is a useful form. It is not a substitute for your own deals.
Step 2: Interview five recent buyers
If you can book five 30-minute calls with people who bought or walked away, you have the richest dataset. Ask:
- What was happening in your role when you started looking?
- Who else was in the decision, and what did each person fear?
- What did you try first, and why did it fail?
- What would have gone wrong if you picked the wrong vendor?
- Who held the budget, and how long did approval take?
Record the calls. Transcribe them. Mark repeated phrases, dollar thresholds, and team size. That language belongs in the persona, not a synonym you like better.
Step 3: Map roles and budget authority
Demographics tell you who they are. TAP tells you whether they can buy.
| Role | Typical titles | Budget power | Primary concern |
|---|---|---|---|
| Decision-maker | VP, CTO, CRO, Head of | Signs the deal | ROI, risk, disruption |
| Influencer | Director, Manager | Recommends; may have a sub-budget | Fit, adoption, features |
| End user | Individual contributor | None | Ease of use and support |
| Champion | Often an influencer | Recommends only | Getting the signer to yes |
For a B2B sale you need at least three role-specific personas per buying group. One "IT Manager Ian" that tries to serve all three is why deals go dark.
How to create buyer personas for multi-threaded deals
List every role that touched your last five closed-won deals. Note who started, who influenced, who approved spend, and who signed. Group roles with the same fears. You will usually land on three archetypes even when titles vary. Run competitive analysis on the alternatives those roles named. Those names belong in Proof.
Step 4: Write a one-page story
A bullet list of traits is easy to forget. A short story of their week is not.
Use three blocks:
- Who they are, title, team size, who they report to, company context
- What they are solving, trigger, urgency, cost of waiting
- How they decide, sources, criteria, approval path, timeline
Keep it to one page. If it needs a deck, you have not synthesized.
Step 5: Pressure-test the draft on live calls
A persona is a guess until pipeline data agrees.
- Match the last five closed-won customers. If three of five differ on trigger or authority, revise.
- Take it into the next ten discovery calls. If their language and timeline do not match, change the persona, not the prospect.
- Write an anti-persona for deals you churn, discount too far, or never get past a demo. Knowing who to refuse saves more time than another happy-path slide.
Step 6: Put the persona into outbound and content
A finished page is not the job. Use it.
- Outbound: the trigger becomes the first line. Riley, after two missed quotas, does not get a feature announcement.
- Content: the proof column tells you what to publish next. For Riley that is a peer case study with numbers, not a whitepaper on the future of revenue intel.
- CRM: tag new leads with the closest persona. Measure close rate and LTV by tag.
This is also where a positioning statement should name the same economic buyer. If the statement says "mid-market marketers" and the persona says "Director of RevOps," one of them is lying.
Step 7: Refresh every quarter
How to create buyer personas is not a one-week project. Refresh when a new vertical starts closing, average deal size moves 30% or more, or the rival set changes. Schedule the check. Do not wait for a rebrand. If you skip this step you will keep filing unused PDFs while the live buyer has already changed.
How to create buyer personas: a B2B SaaS worked example
How to create buyer personas gets real when you stop using a stock title and start from five of your own wins. Here is a full pass you can copy. A revenue-intel platform (think a Gong or Chorus rival) sells to B2B SaaS with 100, 500 people. After five closed-won deals, the pattern is Riley, Director of Revenue Operations. Riley is not a cartoon. Riley is the person who opened the deal, wrote the business case, and still cannot sign above $30K. Use this table as the one-pager you hand sales. Then rewrite every cell from your own transcripts. If a cell is a guess, leave it blank until a call fills it. That blank is more honest than a hobby list.
| Dimension | Riley |
|---|---|
| Role | Director of RevOps at a Series B SaaS company |
| Reports to | CRO or VP of Sales |
| Team | 3–5 ops analysts; no dedicated enablement hire |
| Trigger | Missed quota two quarters in a row; CRO wants pipeline visibility |
| Pain | Dirty CRM data; forecasts are gut feel; QBRs have no proof |
| Proof they need | CRM fit, reports with no SQL, time from deploy to first useful view |
| Authority | Recommends; CRO signs deals over $30K ACV |
| Objection | "We tried a recorder. Nobody read the transcripts." |
| Channels | LinkedIn, RevOps Slack groups, Pavilion |
| Content that converts | Benchmarks, peer case studies with metrics, a comparison |
This is not a generic RevOps director. It is your RevOps director. The data came from your deals and your calls. If your wins look different, a VP of Sales who signs alone, or a CS lead who championed the tool, write that person instead. Do not keep Riley because the example felt tidy.
A sales email that uses TAP sounds like this: "Your CRO asked for pipeline visibility after the Q2 miss. Here is how a similar RevOps team got consistent forecasts inside the CRM they already have, without asking reps to change how they work." That line only works because Trigger, Authority, and Proof are filled. How to create buyer personas that sales will send means the first sentence names a real event, not a persona nickname.
What mistakes kill buyer personas?
Most failures are not "bad data." They are no data. Teams sit in a room, name "Marketing Mary," and stop. How to create buyer personas that last means you refuse that shortcut even when a workshop is already on the calendar. The room will feel productive. The PDF will look finished. Sales will still ignore it because nothing in it matches last Tuesday's call.
Watch for three traps. The consensus person is a blend of every stakeholder that describes nobody. The wish-list person is the customer you want, not the one who pays. The flat person is demographics only, no trigger, no authority, no proof. Each trap produces a slide you can present and a tool nobody uses. If you catch yourself writing hobbies, age ranges, or favorite podcasts, you have left TAP and started decorating.
| Mistake | How it shows up | The fix |
|---|---|---|
| Consensus blend | One slide that "covers" VP, director, and user | One TAP sheet per role |
| Wish-list buyer | Persona matches the deck, not closed-won | Rebuild from last five wins |
| Flat sketch | Title, age, hobbies | Fill Trigger, Authority, Proof |
Also write a negative persona. Deals you lose, discount, or churn early are as useful as wins. Put that anti-persona next to Riley so SDRs know who not to chase. The cost of a bad persona is not an ugly slide. It is six months of sequences aimed at a role that never signs.
What's a good buyer persona prompt?
Use a prompt that forces TAP and forbids invented traits. Paste this, then drop in real notes:
> You are a B2B revenue operations analyst. Using only the customer data I paste, write a buyer persona with four parts: (1) role and company facts, (2) trigger events and primary pains, (3) decision criteria and budget authority, (4) channels and content they trust. Keep it specific enough that a sales rep could write a cold email that names the trigger. Use a real-sounding name and title. Do not invent attributes the source material does not support. > > [Paste interview notes, CRM fields, call excerpts, or survey lines here]
Even with AI, you validate. Use the output as a first draft. Then run Step 5.
The failure is not a missing adjective. Teams file the PDF and the sequences keep talking to "marketing leaders." A skill and a workflow keep Trigger, Authority, and Proof next to the outreach you send.
When that context sits next to deal notes, an agent can draft the first line without inventing a hobby. Discovery and execution stay together: the role, the trigger, the signer, and the proof.
Metaflow is built for that handoff, outbound automation for persona-to-sequence work, the buyer persona template as the sheet you fill once, and the persona page pattern when the same profile has to show up on a page.
Frequently Asked Questions
What is a buyer persona example?
A buyer persona is a research-backed profile of one buying role. A B2B example: "Riley, Director of RevOps at a Series B SaaS company, triggered by two missed quotas, who needs pipeline visibility but was burned by a tool that needed too much setup." The trigger and the old-tool objection are what make it usable. In Metaflow that profile belongs in the same template sales uses for the first email.
How can I create my own persona without a big budget?
You do not need a research budget. You need five customer calls, a CRM export, and one hour. Run the interviews yourself. Transcribe with Otter or your meeting tool. Follow the seven steps above, then use the prompt to speed synthesis. Metaflow teams usually start from the template so the TAP fields stay the same from the first draft.
What's a good buyer persona prompt?
The best prompt is the one in the section above: role-specific, structured, and explicit that the model must not invent unsupported traits. Avoid "create a persona for a SaaS buyer." That prompt reprints a generic sketch.
Who should be involved in creating your buyer persona?
At minimum: someone from sales who runs discovery, someone from customer success who hears post-purchase pain, and someone from marketing who owns positioning. Add a product manager if you can. Fit assumptions often show up in interviews that sales and marketing would miss. In Metaflow the same TAP fields should be visible to all three so you are not keeping parallel docs.
How often should buyer personas be updated?
Every quarter, or when your ICP shifts. Refresh when a new industry starts closing, deal size moves 30% or more, or the rival set changes. Treat validation as a recurring operation, not a launch project. That cadence is how to create buyer personas that stay true after the first quarter.
