Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas Your Reps Actually Use to Sell
By Rick Elmore ·
Last quarter I sat in on a discovery call where a rep was pitching automation ROI to a VP of Sales. The VP kept nodding politely and going nowhere. Turns out the real buyer was two seats away — a RevOps lead who cared about data hygiene and hated ripping out tools her team just learned. The rep had the account right. He had the human completely wrong.
That gap is what buyer persona development is supposed to close, and it's the piece most B2B teams skip or fake. They copy a persona template off the internet, fill in "Marketing Mary, age 42, likes coffee and efficiency," and never look at it again. Meanwhile their reps improvise in every call because the persona doc tells them nothing about how this specific human actually decides to spend money.
- ICP tells you which accounts to target. Personas tell you which humans inside those accounts to persuade — and how.
- A useful persona is built from real conversations and won/lost data, not demographics and guesses.
- Focus on pains, triggers, and buying role. Age, hobbies, and "favorite tools" are noise.
- Map every deal by its buying committee: economic buyer, champion, technical evaluator, blocker.
- If a rep can't use the persona to write a better opening line, the persona failed.
ICP vs. persona: stop conflating the account and the human
We've written before about building an ICP. Quick reminder of the difference because teams blur it constantly. Your ideal customer profile describes the company: industry, headcount, revenue band, tech stack, growth stage, the conditions that make an account a good fit. It's a filter for your pipeline.
A buyer persona describes a person inside that company. It answers a different question entirely — not "should we sell to this account" but "what does this specific human need to believe to say yes." One is targeting. The other is messaging and persuasion. You need both, and they operate at different layers of your revenue engine.
Here's why the distinction matters in practice. A single ICP-fit account might contain four or five people who all touch the buying decision, and they don't share the same pains. The economic buyer worries about payback period. The end user worries about their day getting worse. The IT gatekeeper worries about security review. If your persona work stops at the account level, your reps walk into every meeting with one generic pitch and hope it lands on whoever happens to be in the room.
| Dimension | ICP (the account) | Buyer persona (the human) |
|---|---|---|
| Question it answers | Should we spend time here? | How do I move this person to yes? |
| Built from | Firmographics, tech stack, deal history by account | Interviews, call recordings, won/lost reasons by role |
| Used for | List building, routing, disqualification | Messaging, outreach copy, discovery questions |
| Owned by | RevOps and marketing | Marketing and sales, together |
Where the real research comes from
Most persona documents are fiction because they're built from imagination in a conference room. Real persona development starts with sources you already have and rarely mine.
Won and lost deal reviews. Your CRM notes and closed-lost reasons are gold. Pull the last 20 to 30 deals and read them for patterns. Who championed the winners? What objection killed the losers? What was happening in the business when they decided to buy? You're looking for the recurring human story underneath the transactions.
Call recordings. If you use Gong, Fathom, or even plain Zoom recordings, you have a library of your buyers explaining their own pain in their own words. This is the single best source and almost nobody systematically mines it. Listen for the phrases buyers repeat. Those exact words belong in your outreach because they're the language your prospects already use in their own heads.
Direct interviews. Call five to ten recent customers and ask what problem they were trying to solve, who else was involved in the decision, and what almost stopped them from buying. Ask what they typed into Google before they found you. Twenty minutes on the phone beats a month of brainstorming.
Sales team debriefs. Your reps hear objections all day. Get them in a room and ask: "When a deal stalls, who's the person blocking it and what are they afraid of?" That question surfaces the blocker persona faster than any survey.
Notice what's missing from that list: demographics, LinkedIn scraping for age, and personality quizzes. None of it moves a deal. I don't care that your buyer is a millennial who prefers Slack over email. I care what wakes them up at 3 a.m. about their number.
The four things a persona has to capture
Strip away the template bloat and a persona your reps will actually open needs to nail four elements.
1. The pain that has a budget behind it
Not every pain gets funded. Plenty of buyers are mildly annoyed by things they'll never pay to fix. The persona has to distinguish nice-to-have irritation from the pain that's already showing up in a board deck or a performance review. When a VP of Sales is missing quota three quarters running, that pain has a budget. When they'd "like better reporting someday," it doesn't. Write down the funded pain specifically, in the buyer's language.
2. The trigger that starts the buying window
People don't buy on a random Tuesday. Something changes. A new VP comes in with a mandate. A funding round adds a growth target nobody knows how to hit. A competitor lands a customer they should have won. Layoffs mean the same output has to come from fewer people. These triggers are the moments your outreach should key off, because timing beats persuasion most of the time. A mediocre message at the right moment outperforms a brilliant one sent to someone who's fine as they are.
3. The buying role they play
This is the piece ICP work can't give you. In any real B2B deal, several people play distinct roles, and each needs a different conversation:
The economic buyer signs off and cares about outcome and payback. The champion feels the pain daily and will sell internally on your behalf if you arm them well. The technical or functional evaluator pressure-tests whether it actually works. The blocker — often finance, IT, or someone protecting the status quo — looks for reasons to say no. You need a persona for each of these, because a message that lands with a champion often spooks a blocker. Selling ROI to the person worried about a messy migration is how you lose deals you should win.
4. The objection that shows up every time
Each persona carries a predictable fear. The economic buyer's is "what if this doesn't pay back." The end user's is "what if this makes my job harder." Document the objection per role, along with the honest answer, and suddenly your reps can defuse it before it derails a call.
How to document it so reps actually use it
The best persona I've seen fit on one page. The worst was a 14-slide deck that lived in a shared drive nobody opened. Length is inversely correlated with use.
My rule: a persona should be usable as a writing prompt. If a rep can look at it and immediately draft a better first line of an email, it works. That means it needs the funded pain, the trigger, the buyer's actual words, and the top objection — on one screen, scannable in thirty seconds.
Keep it living. A persona built once and frozen goes stale as your market shifts. We treat personas as a quarterly refresh tied to the same call-recording and won/lost review that feeds everything else. When the market changes — a new competitor, an economic squeeze, a shift in what triggers buying — the persona changes with it, and so does the outreach layered on top.
The payoff shows up when personas plug into the rest of the engine. Once you know the trigger, your data providers can watch for it. Once you know the buying role, your sequences branch by persona instead of blasting one message to everyone. Once you know the funded pain, your AI agents can qualify against it on the first touch. Personas aren't a marketing deliverable that dies in a folder. They're the input layer for how the whole system talks to humans. That's the logic behind how we structure our build packages — research feeds messaging, messaging feeds automation.
The mistake that makes personas useless
Building for the buyer you wish you had instead of the one you keep closing. Teams design a persona around the sophisticated, forward-thinking executive who instantly gets their value. Then they wonder why outreach flops. Real buyers are busy, skeptical, and mid-way through fixing three other fires. The persona has to reflect that reality, not the aspirational version. Write the persona who's overwhelmed and unsure, because that's who reads your email.
The second mistake is treating personas as marketing's private project. If your reps didn't help build it and don't see themselves in it, they'll ignore it and keep improvising. Build it together. The rep who told you about the RevOps blocker two seats down from the VP just handed you a persona you'd never have written alone.
Frequently asked questions
How many buyer personas should a B2B company have?
Usually three to five active ones, mapped to the roles in your buying committee rather than to job titles. If you find yourself with a dozen, you're probably describing job variations, not distinct buying behaviors. Start with your economic buyer, your champion, and your most common blocker, then add only when a role genuinely changes how you'd sell.
Do buyer personas replace an ICP?
No, they work at different layers. Your ICP filters which accounts deserve attention. Your personas shape how you persuade the humans inside those accounts. Skip the ICP and you waste effort on bad-fit companies. Skip personas and you win the right accounts far less often because your messaging is generic. You need both.
How often should personas be updated?
Review them quarterly against fresh call recordings and won/lost data. Markets shift, triggers change, and new objections surface. A persona built two years ago and never touched is describing a buyer who may no longer exist. Tie the refresh to the same deal-review rhythm your team already runs.
If your personas are guesses on a slide and your outreach shows it, we can fix the input layer and the automation built on top of it. Book a Revenue Systems Audit and we'll pressure-test the personas your reps are actually selling with.