Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas Reps Actually Use in Deals
By Rick Elmore ·
Most B2B buyer personas are useless. They tell you Marketing Mary is 42, drinks oat milk lattes, and "values efficiency" — and then they sit in a Google Doc nobody opens. Meanwhile your reps are on live calls trying to figure out why the champion went quiet, with zero help from the persona deck. A real b2b buyer persona isn't a demographic sketch. It's a working tool that tells a rep what this specific role cares about, what triggered them to look, and what they'll say to kill the deal.
Here's how to build personas that actually get used, built around the buying committee instead of a single fictional buyer.
1. Separate your persona from your ICP (they are not the same thing)
Your ICP describes the account: company size, industry, tech stack, revenue band, growth stage. Your buyer persona describes a person inside that account. Conflating the two is the most common mistake I see, and it's why so many personas feel generic — they're just ICP traits glued to a stock photo.
One ICP contains multiple personas. A mid-market SaaS company (ICP) might have a VP of Sales who feels the pain, a RevOps lead who evaluates the fix, a CFO who signs, and an SDR manager who has to live with whatever you sell. Same account, four completely different conversations. Build the ICP first, then map the humans inside it.
2. Map the whole buying committee, not just the champion
B2B deals aren't closed by one person. They're approved by a group, and every member can slow or stop you. If your persona work only covers the enthusiastic champion, you're flying blind on the people who actually control the budget.
For a typical mid-market deal, map at least these roles:
- Champion — feels the pain daily and wants it solved. Sells internally on your behalf.
- Economic buyer — controls budget. Cares about ROI and risk, not features.
- Technical/operational evaluator — will own implementation. Cares about integration, effort, and whether this breaks their stack.
- End user — has to use the thing. Cares about whether it makes their day easier or harder.
- Blocker — often security, legal, or procurement. Their job is to find reasons not to buy.
You don't need a 40-field profile for each. You need to know what each one is trying to protect and what each one is afraid of.
3. Build every persona on pain, not demographics
Age, job title, and "favorite tools" don't change how you pitch. Pain does. The core of each persona should answer one question: what is this person struggling with that we can credibly fix?
Get specific. "Wants to grow revenue" is useless — everyone wants that. "Spends six hours a week pulling pipeline reports by hand because the CRM data is a mess" is something a rep can actually speak to. Write pains in the person's own language, pulled from real conversations, not from your marketing brochure.
For each persona, capture:
- The functional problem (what's broken in their workflow)
- The emotional cost (what makes them look bad or feel stuck)
- The business consequence (what it costs the company if it stays broken)
4. Identify the buying triggers that start the clock
People don't wake up and decide to evaluate software. Something changes. A trigger is the event that moves a persona from "this is annoying" to "I need to fix this now." If you know the triggers, your marketing can catch buyers at the moment they're actually in motion, and your reps can ask the right qualifying questions.
Common triggers by persona type:
- New leader in seat — a new VP wants a quick win and will rip out old systems to get it.
- A number got missed — a blown quarter forces the economic buyer to look for answers.
- Headcount froze — suddenly the team needs to do more with the same people, which opens the door to automation.
- A painful manual process hit a breaking point — the spreadsheet finally fell over.
- A competitor moved — the board starts asking why they're behind.
Tie each persona to its two or three most likely triggers. That's what turns a static profile into something your SDRs can use to prioritize outreach.
5. Document the real objections each role will raise
Every persona has a predictable set of objections, and they're different per role. The CFO's objection ("how do I know this pays back?") is not the technical evaluator's objection ("this won't integrate with our stack"). If your reps hear an objection for the first time on a live call, your persona work failed.
For each persona, list the top three to five objections and the strongest honest response to each. Write the response the way a good rep would actually say it, not as a canned rebuttal. The goal is that a new rep can read the persona and walk into a call already knowing what's coming.
6. Pull the content from real data, not a brainstorm
The fastest way to build a persona nobody trusts is to invent it in a conference room. Build them from evidence instead. You already have more than you think:
- Call recordings — Gong, Fathom, or even raw Zoom transcripts. The exact words buyers use are gold.
- Win/loss interviews — ask why people bought and why they walked.
- Your CRM — which titles actually close, how long each role takes, where deals stall.
- Sales and CS teams — the people who talk to buyers all day know the real objections.
- Support tickets and onboarding notes — these reveal what end users actually struggle with.
Mine the language. When you phrase a persona's pain in the buyer's exact words, your messaging stops sounding like marketing and starts sounding like someone who gets it.
7. Write one message angle per persona
A persona you can't act on is just trivia. The output of each profile should be a clear through-line: given this role's pain, trigger, and objections, here's the one thing we lead with. For the champion, you lead with the day-to-day relief. For the economic buyer, you lead with payback and risk reduction. For the technical evaluator, you lead with how little this disrupts their stack.
This is where personas connect to the rest of your revenue engine. The same persona map that guides a cold email sequence should guide your sales talk tracks, your demo flow, and your proposal framing. When those stay consistent, buyers feel like your whole team is reading from the same understanding of their world — because they are.
8. Keep personas short enough to actually read
A persona that runs four pages will never get opened before a call. Fit each one on a single screen. A usable format:
- Role and what they're responsible for (one line)
- Top three pains in their words
- Two to three buying triggers
- Top objections and the response
- The one message angle we lead with
If a rep can scan it in 90 seconds before a discovery call, you built it right. If they have to study it, you built a document, not a tool.
9. Put personas where reps already work
The best persona in the world dies in a shared drive. Surface it where the work happens. Drop a persona snippet into the CRM record. Add it to the deal stage checklist. Reference the persona by name in your sequence templates so reps know which version to send. When you're running AI agents for outreach or qualification, feed the persona definitions directly into the system so messaging adapts by role automatically.
This is the difference between a marketing artifact and an operational asset. We build personas into the actual revenue engine — the sequences, the routing, the agent prompts — so they shape every touch instead of sitting on a shelf. That's part of how our packages tie messaging to the system that delivers it.
10. Review them quarterly, kill the ones that don't close
Personas drift. Markets shift, your product changes, and the buyer who mattered last year may not be the one signing today. Review your set every quarter against closed-won and closed-lost data. If a persona never shows up in winning deals, cut it. If a title keeps appearing in your pipeline but isn't on your map, add it. Personas are living assumptions about your buyers, and the only way to keep them useful is to keep testing them against reality.
Frequently asked questions
What is the difference between a B2B buyer persona and an ICP?
An ICP (ideal customer profile) describes the type of account worth selling to — things like company size, industry, and tech stack. A b2b buyer persona describes an individual person inside that account, including their role, pains, triggers, and objections. One ICP usually contains several personas, because B2B deals are decided by a committee, not one buyer.
How many buyer personas does a B2B company need?
Fewer than you think. Most teams are well served by three to five personas that cover the core buying committee roles: the champion, the economic buyer, the technical or operational evaluator, and sometimes a key end user or blocker. More than that and nobody maintains them. Start with the roles that actually appear in your closed-won deals and expand only when the data demands it.
How do you build buyer personas without a big research budget?
You don't need a research firm. Pull call recordings, run a handful of win/loss conversations, mine your CRM for which titles actually close, and interview your own sales and CS teams. The goal is to capture real pains, triggers, and objections in the buyer's own words. That beats an expensive survey that produces demographic fluff every time.
If your personas are collecting dust while your reps wing it on calls, the fix is to wire buyer intelligence into the system that runs your outreach and sales motion. Book a Revenue Systems Audit and we'll show you where your messaging and your buying committee are out of sync.