Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas That Actually Drive Messaging and Targeting
By Rick Elmore ·
Last month I sat in on a discovery call where the rep delivered a flawless pitch to the wrong person. The prospect was an operations lead who cared about implementation risk and team adoption. The rep spent twenty minutes on ROI projections and pipeline math — language built for a VP of Sales. The deal stalled. Not because the product was wrong, but because the message was aimed at a persona who wasn't in the room.
That gap is what buyer persona development is supposed to close. And most of what passes for persona work doesn't. It's a slide deck with a stock photo named "Marketing Mary," a fabricated age range, and a list of generic goals anyone could guess. It sits in a shared drive. Nobody uses it. The reps keep pitching the wrong person.
Real personas aren't demographic profiles. They're working documents that tell your team exactly what each member of the buying committee cares about, what makes them act, and what stops them from saying yes. Built right, they change the words in your emails and the questions on your calls. Here's how we build them at FullStackCloser.
- Personas operate at the individual level — distinct from your ICP, which scores account-level fit. You need both, but they answer different questions.
- The buying committee has 5–8 people. Build personas for the roles that influence, block, or sign — not just the economic buyer.
- Your best source material already exists: CRM notes, won/lost reasons, and call recordings. Mine those before you run a single interview.
- Map four things per persona: their role in the deal, their real pains, the triggers that make them look for a solution, and the objections they raise.
- A persona that doesn't change your messaging or targeting is decoration. Operationalize it or skip it.
Why most B2B personas are useless
The standard persona template was borrowed from consumer marketing, where a single shopper makes the call. B2B doesn't work that way. In a mid-market or enterprise deal, you're selling to a committee. The person with the pain isn't always the person with the budget, and the person with the budget rarely uses the product.
So when a persona document tells me "Mary is 42, has two kids, and enjoys yoga," I know it was built by someone who never listened to a sales call. None of that moves a deal. What moves a deal is knowing that Mary's team has been blamed twice this quarter for missed SLAs, that she's terrified of another failed rollout, and that she'll quietly kill any tool she can't get her team to adopt in the first week.
The difference between those two profiles is the difference between persona work that drives revenue and persona work that wastes an afternoon. We care about psychology and context inside the deal, not biography.
Personas vs. ICP: what's the difference?
People use these interchangeably, and it causes real confusion on go-to-market teams. They're not the same layer.
| Dimension | ICP (Ideal Customer Profile) | Buyer Persona |
|---|---|---|
| Level | The account / company | The individual inside the account |
| Question it answers | Which companies should we sell to? | Who do we talk to, and what do we say? |
| Built from | Firmographics, tech stack, revenue band, trigger events | Roles, pains, motivations, objections |
| Drives | Targeting and list building | Messaging and conversation |
Your ICP gets you to the right door. Your personas tell you who's going to answer it and how to talk to each of them once you're inside. If you only do ICP work, you'll have great lists and flat response rates. If you only do personas, you'll craft beautiful messages aimed at companies that were never going to buy. You need both, working together.
Where to find the raw material (hint: you already have it)
The mistake teams make is treating persona development as a research project that starts from scratch. It isn't. If you've been selling for even six months, you're sitting on more persona data than any survey could give you. Three sources, in order of value.
Call recordings. This is the gold mine. Pull 15–20 recordings — a mix of closed-won, closed-lost, and stalled deals. Listen for the exact language people use to describe their problem. Not how your marketing describes it. How they describe it. When a prospect says "we're drowning in manual handoffs," that phrase goes straight into your outreach. You're not guessing at pain. You're transcribing it.
CRM data and won/lost reasons. Your CRM tells you which titles actually show up in deals that close versus deals that die. If you notice that every won deal had a finance stakeholder looped in by stage two, that's a persona you've been underserving. Look at the notes field, the deal stages where things stall, and the reasons logged on lost opportunities. Patterns emerge fast.
Direct interviews. Once you've mined recordings and CRM, you'll have hypotheses. Interviews confirm or kill them. Talk to recent customers and, if you can, recent losses. Ask what the day looked like when they decided to fix the problem. Ask who else was involved in the decision and what each of them pushed back on. Fifteen minutes with a real buyer beats a month of internal brainstorming.
One rule: never build personas in a conference room by committee consensus. The personas your team imagines are always cleaner and more rational than the humans who actually buy. Go to the source.
The four things every persona must map
Strip away the template fluff and a useful persona comes down to four questions. Answer these for each role in the buying committee and you have something your team will actually use.
Role in the deal. Are they the champion, the economic buyer, the technical evaluator, the end user, or the blocker? The same person can shift roles across deals, but the function matters. Your champion needs ammunition to sell internally. Your economic buyer needs a business case. Your technical evaluator needs proof it won't break. Same product, three different conversations.
Pains. Not the pain your product solves in the abstract — the specific, personal friction this role feels. An operations lead fears a messy rollout that lands on their desk. A VP of Sales fears missing the number and explaining it to the board. A RevOps manager fears being the one who picked a tool that didn't integrate. Pain is personal, and it's usually tied to how someone gets judged by their own boss.
Triggers. What event makes this person start looking? New funding, a leadership change, a tool that just failed, a growth target that doubled. Triggers are what connect personas back to timing. A persona with a known trigger lets you reach out at the moment the pain is loudest instead of hoping you catch them on a good day.
Objections. Every role has a default reason to say no. "We don't have the bandwidth to implement." "We already have something that half-works." "I need to see how this plays with our existing stack." Write these down. When your reps can name an objection before the prospect does, trust goes up and cycles shorten.
That's it. Role, pain, trigger, objection. If a persona doc has those four locked for each committee member, you can throw away the age and the yoga.
How to operationalize personas across sales and marketing
This is where most persona projects die. The document gets built, applauded, and forgotten. A persona only earns its keep when it changes what people actually do. Here's how we wire it into the revenue engine.
Outreach sequences get split by persona. One generic sequence for "decision makers" is lazy. The champion gets messaging about looking good internally and hitting their goals. The economic buyer gets the business case and risk reduction. Same campaign, different tracks, because the pains are different. This alone usually lifts reply rates more than any subject-line tweak.
Call frameworks map discovery questions to persona. When a rep knows they're talking to a technical evaluator, the discovery script surfaces integration and security concerns early. Talking to a champion? Dig into internal politics and who else needs to be convinced. The persona tells the rep where to dig.
Marketing content gets assigned to personas and funnel stages. Your case studies, one-pagers, and landing pages should each have a named persona they serve. If you can't name the persona a piece of content is for, it's probably serving no one.
AI agents and automation get persona logic baked in. This is where it compounds. When your inbound qualification and follow-up run through AI agents, the personas become routing rules. An inbound lead with a RevOps title gets different qualifying questions and a different nurture track than a VP of Sales. The persona stops being a PDF and becomes operational logic that runs on every lead, automatically. That's the integration we build for clients — personas that live inside the system instead of a slide deck. If you want to see how that maps across lead gen, outreach, and RevOps, our packages lay out the full build.
Personas aren't a one-time deliverable. Markets shift, new competitors change the objections, a new trigger emerges. We revisit them quarterly against fresh call recordings. The ones that stop matching reality get cut. The ones that sharpen get sharper.
A quick word on how many personas you need
Teams tend to overbuild here. You don't need twelve personas. You need the three or four roles that actually decide your deals. Start with the champion, the economic buyer, and whichever evaluator most often blocks you. Add more only when the data shows a distinct role you're consistently failing to address. More personas than your team can remember is the same as having none — they stop being a tool and become a filing exercise.
Frequently asked questions
How many buyer personas should a B2B company have?
Usually three to four. Build for the roles that materially influence or decide your deals — typically the champion, the economic buyer, and the key evaluator or blocker. If a role doesn't change how you sell, it doesn't need its own persona. Too many personas defeats the purpose, because your team can't hold them all in their heads during a call.
What's the difference between a buyer persona and an ICP?
Your ICP operates at the account level and answers "which companies should we pursue?" using firmographics, tech stack, and trigger events. A buyer persona operates at the individual level and answers "who do we talk to inside that company, and what do we say?" ICP drives targeting; personas drive messaging. You need both, and they should be built to work together rather than in isolation.
How often should I update my buyer personas?
Revisit them quarterly against recent call recordings and won/lost data. Personas drift as your market shifts, new competitors reframe the problem, and new buying triggers emerge. The fastest way to keep them honest is to pull a handful of fresh recordings each quarter and check whether the pains, triggers, and objections still match what buyers are actually saying.
If your personas are a dusty slide deck and your outreach still speaks to "decision makers" in general, that's a fixable gap — and usually a fast one. We'll audit how your personas, targeting, and messaging line up across the whole revenue system and show you where the leaks are. Book a Revenue Systems Audit.