Sales Enablement Aside—Buyer Personas: How to Build B2B Personas Reps Actually Use in Deals
By Rick Elmore ·
Last quarter I sat in on a deal review where a rep pulled up a "buyer persona" the marketing team had built. It had a stock photo, a name ("Marketing Mary"), a list of hobbies, and a bullet that said she "values innovation." The rep had never opened it. Not once. And I didn't blame him. Nothing on that page helped him win the deal in front of him.
That's the problem with most B2B personas. They're written by people who don't take sales calls, and they get used by exactly nobody. Meanwhile the reps build their own mental models from scar tissue—which objections kill deals, which titles ghost, what the economic buyer actually asks. That knowledge lives in their heads and leaves when they do.
A good b2b buyer persona isn't a character study. It's a compressed summary of patterns pulled from real deals—what this type of buyer cares about, what they're skeptical of, and the exact language that moves them. Built right, it shows up in sequences, discovery prep, and objection handling. Built wrong, it's a poster nobody reads.
- Personas are individual-level (the human in the deal). ICP is account-level (which companies to pursue). You need both, and they do different jobs.
- Evidence beats imagination. Build from win-loss interviews and recorded calls, not whiteboard sessions.
- If a persona field doesn't change what a rep says or does, cut it. Hobbies don't close deals.
- Personas only stick when you embed them into the tools reps already use—sequences, discovery scripts, battlecards.
- Tie each persona to measurable signals: win rate by role, objection frequency, cycle length. Update quarterly.
Persona vs ICP: stop conflating them
These two get mashed together constantly, and the confusion wastes effort. Your ICP answers "which accounts should we spend time on?" It's firmographic and situational: company size, industry, tech stack, trigger events, revenue band. It tells your SDRs where to aim.
Your persona answers a different question: "who inside that account do I need to win, and how do I talk to them?" A single target account might contain four personas—the VP who feels the pain, the director who'll run the evaluation, the finance lead who controls budget, and the IT gatekeeper who can veto on security grounds. Each one hears your pitch differently. Each one has a different reason to say no.
Here's the practical split I use on every engagement.
| Dimension | ICP (account-level) | Buyer persona (individual-level) |
|---|---|---|
| Core question | Which companies do we go after? | Who inside them do we win, and how? |
| Typical attributes | Industry, headcount, revenue, tech stack, trigger events | Role, goals, objections, decision criteria, language |
| Used by | SDRs for targeting, marketing for list building | AEs for discovery, sequencing, objection handling |
| Primary metric | Account-to-opportunity conversion | Win rate and cycle length by role |
When teams skip the ICP work and jump straight to personas, they end up with beautifully detailed profiles of buyers at companies that will never buy. When they skip the persona work, every outbound message sounds the same regardless of who opens it. You need the pair working together.
Where real persona evidence comes from
The fastest way to build a persona reps ignore is to invent it. The fastest way to build one they use is to pull it straight out of deals that already happened. You already own the data. It's sitting in three places.
Win-loss interviews. Nothing beats asking people who just bought (or didn't) why. I like to interview a handful of recent closed-won and closed-lost buyers per persona each quarter. Ask what problem made them start looking, what almost stopped them from buying, who else was in the room, and what nearly sent them to a competitor. The closed-lost conversations are gold—they tell you the exact objections your current messaging fails to answer.
Recorded calls. Your Gong, Fathom, or call recorder is a goldmine of unfiltered buyer language. Pull ten to fifteen discovery calls for a given role and read the transcripts. Pay attention to the words buyers use to describe their pain, because those words belong in your sequences verbatim. If a VP of Ops keeps saying "we're drowning in manual handoffs," that phrase will outperform anything your copywriter dreams up.
CRM and deal data. Segment your win rate by job title. Look at which roles, when they're the champion, correlate with faster cycles and higher close rates. Look at where deals stall. If opportunities consistently die after the security review, your persona set is missing the IT gatekeeper, and your reps are getting blindsided.
Three sources, triangulated. The interviews tell you why, the calls tell you how they talk, and the CRM tells you whether it's actually true at scale. A persona built on all three is defensible. One built on a brainstorm is fiction with a headshot.
What actually belongs on the page
Once you've gathered evidence, the temptation is to dump everything into a long document. Resist it. The test for every field is simple: does this change what a rep says or does in the next call? If not, delete it.
Here's what survives that test. Start with the role and its real goals—not the job description, but what this person is personally measured on and judged by. A RevOps leader isn't buying your tool because they love software; they're buying because their forecast accuracy is getting questioned in board meetings. That's the goal that matters.
Next, the pain in their own words. Pull the three or four phrases that came up repeatedly in calls and interviews. These become the hooks in your subject lines and the mirrors in your discovery questions.
Then the objections, ranked by frequency. For each one, write the response that's actually worked. This is the single most-used part of any persona I've built, because it's the thing reps reach for mid-deal when they're under pressure.
Add their decision criteria and who else they answer to. Does this person sign, or do they have to sell your solution internally to a CFO? If they're a champion rather than an economic buyer, your job is to arm them for the internal conversation, and the persona should say so explicitly.
Finally, where they live and how they prefer to engage. Not "social media"—specifically whether a cold call lands better than email for this role, which communities they trust, what content format they'll actually consume. Keep the whole thing to one page. If a rep can't scan it in ninety seconds before a call, it's too long.
How to embed personas so reps actually use them
This is where most persona projects die. The document gets built, presented in an all-hands, saved to a shared drive, and never opened again. The problem isn't the content. It's that you're asking reps to go somewhere extra to get value, and they won't. You have to put the persona inside the work.
Into sequences. Build a separate outbound sequence per persona, not one generic one. The VP of Sales and the RevOps Manager get different first lines, different pain hooks, different proof points—all drawn straight from the persona's language. When the persona informs the sequence, the sequence becomes the persona in action.
Into discovery. Turn each persona's goals and objections into a short pre-call prep: the three questions to ask this role, the two objections to pre-empt, the one proof point that resonates. We drop this right into the CRM opportunity record so it surfaces when the rep opens the deal, not in a folder they have to remember exists.
Into enablement content. Battlecards, one-pagers, and case studies should be tagged by persona so a rep can pull exactly the right asset for the exact buyer they're talking to. The finance persona gets the ROI breakdown; the technical gatekeeper gets the security and integration sheet.
This is the connective tissue work that separates a persona exercise from a revenue system. In our builds we wire personas into the sequencing engine, the CRM, and the AI agents that draft rep-facing call prep, so the evidence actually reaches the point of decision. If you want that infrastructure set up end to end, that's part of what our packages cover.
Proving the persona earned its keep
A persona is a hypothesis about how to win a type of buyer. Treat it like one. The whole point of building from evidence is that you can measure whether it's working and sharpen it over time.
The signals I watch: win rate segmented by persona, average cycle length when that persona is the champion, reply and meeting-booked rates on persona-specific sequences versus generic ones, and objection frequency over time. If you've nailed a persona's objections and baked the responses into enablement, you should see that objection stop killing deals. If win rate for a given role stays flat after you've rebuilt its persona, the persona is wrong and you go back to the call data.
Review on a quarterly cadence. Markets shift, new objections appear, competitors change their pitch. A persona built eighteen months ago describing a buyer who no longer exists is worse than no persona, because reps trust it and get burned. Fresh win-loss interviews each quarter keep the whole thing honest.
One more operator note: let reps edit the personas. The best insight about what a buyer actually cares about comes from the person who just spent six weeks in a deal with them. Build a feedback loop where reps flag what's wrong, and your personas stop being a marketing artifact and start being shared, living intelligence the whole team trusts.
Frequently asked questions
How many buyer personas should a B2B company have?
Fewer than you think. Most B2B teams need three to five personas covering the roles that actually show up in deals—typically the economic buyer, the champion, and one or two influencers or gatekeepers. If you have twelve personas, you've built a filing cabinet nobody reads. Start with the two or three that appear in most of your closed-won deals and expand only when the data shows a distinct role driving outcomes.
What's the difference between a buyer persona and an ICP?
An ICP describes the ideal account—company size, industry, tech stack, trigger events—and tells you which organizations to pursue. A buyer persona describes an individual inside that account—their goals, objections, and decision criteria—and tells your reps how to win that specific human. You target with the ICP and you sell with the persona. Confusing the two leads to reps using the same pitch on every person in the building.
How often should buyer personas be updated?
Review them quarterly against fresh win-loss interviews and recent call data. Buyer priorities, objections, and competitive pressure shift faster than most teams expect. A persona that hasn't been touched in a year is probably describing a buyer who no longer exists, and reps who trust it will get caught flat in deals.
If your personas are posters nobody reads and your reps are running on gut instinct, the fix isn't a prettier template—it's a system that turns real deal data into intelligence reps actually use mid-call. Book a Revenue Systems Audit and we'll show you how to build it.