Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas Your Reps Actually Use in Deals
By Rick Elmore ·
Last quarter I watched a rep open a discovery call reading verbatim from a persona doc: "So, as a VP of Operations, you're probably focused on efficiency and scaling your team." The prospect went quiet. Then: "I mean, sure, but that's every VP on the planet." The call never recovered.
That's the problem with most buyer personas. They're built by marketing, laminated, and filed. They describe a demographic, not a human with a budget, a boss, and a reason to say no. If your reps can't use a persona inside a live deal, it isn't a persona. It's decoration.
I've spent years building revenue systems where the persona has to earn its place in the sequence, the call script, and the deal review. Here's how we build buyer personas that survive contact with an actual buyer.
- Personas are not your ICP. ICP describes the account worth selling to. A persona describes the person inside that account you have to convince.
- Demographics are the least useful field. What matters is the trigger, the internal politics, the objection, and the words they actually use.
- If a rep can't quote a line from the persona in an email, it failed. Build for activation, not for the brand deck.
- Research beats imagination. Won/lost call recordings and real objections produce better personas than a brainstorm in a conference room.
- Personas decay. Markets shift, so treat them as living documents tied to your pipeline data.
Buyer persona vs ICP: stop mixing them up
This confusion wrecks more go-to-market motions than any targeting mistake. Your Ideal Customer Profile is firmographic. It answers: which companies should we spend time on? Industry, headcount, revenue band, tech stack, growth stage, a triggering event like a funding round or a new hire in a key seat.
A buyer persona lives one layer down. Inside a company that fits your ICP, there are usually three to six people who touch the decision. The economic buyer who signs. The champion who wants the problem solved. The technical evaluator who can veto you. The skeptic in finance or security who has seen too many tools fail. Each of those is a persona with different fears and different language.
Here's the practical split I use with clients:
| Question | ICP answers | Persona answers |
|---|---|---|
| Who do we target? | The account (company type) | The person inside it |
| What drives it? | Firmographics and triggers | Goals, fears, internal politics |
| Where it's used | List building, routing, scoring | Messaging, discovery, objection handling |
| Owner | RevOps and marketing | Sales and marketing together |
You need both. The ICP gets the right door in front of your reps. The persona gets them through it.
How to do buyer persona development with data, not guesses
Most persona workshops start with the team imagining who the buyer is. That's backwards. You already have the answers sitting in your CRM, your call recordings, and your lost deals. Buyer persona development should be an act of listening, not inventing.
Here's the research process I run. It takes about two weeks of focused work, not a quarter.
Start with the mouths of actual buyers. Pull 15 to 20 recordings of discovery and closing calls, split across won and lost deals. Lost deals are gold because they expose the objections that killed you. Listen for the exact phrases people use to describe their problem. Not how your product solves it. How they name the pain. That language becomes your subject lines and opening sentences later.
Interview your own reps and CSMs. The people who talk to buyers all day already carry a persona in their heads. Get it out. Ask: who's the easiest person to sell to in a deal? Who always stalls things? What question do you dread getting? What makes a champion go cold? You're mining pattern recognition they didn't know they had.
Interview a handful of real customers. Five good conversations beat fifty survey responses. Ask about the moment they decided to look for a solution, who else was in the room, what almost stopped them from buying, and what they told their boss to justify the spend. That last one is critical. The justification story is what your champion needs to repeat internally when you're not there.
Mine the written record. Support tickets, sales email replies, Gong snippets, review sites in your category, the questions people ask in relevant communities. You're building a vocabulary bank of how the market actually talks.
Then cluster. Group what you heard into two or three distinct patterns. Resist the urge to make eight personas. Most B2B teams can run on two or three well-built ones. If a persona doesn't change how you'd write an email or run a call, it doesn't deserve to exist as a separate one.
The persona template fields that actually matter
I'll be blunt about what to cut. Age, hobbies, a stock photo named "Marketing Mary," favorite coffee order. None of that helps a rep close. Here's what we put in a persona doc at FullStackCloser, in rough order of usefulness.
The trigger. What just happened in their world that makes this problem urgent right now? New funding, a missed quarter, a competitor move, a tool that broke, a new hire with a mandate. Timing beats fit. A perfect-fit buyer with no trigger is a slow deal.
The job they're trying to do. Framed as an outcome they're accountable for, not a feature they want. "Hit pipeline targets without adding headcount" is a job. "Wants a CRM" is not.
Their internal pain, in their words. Pull the literal quotes from your research. This is what makes outreach land. When your email mirrors the sentence running through someone's head, they feel understood before you've pitched anything.
What they're measured on. Their number, their boss's number, the metric their bonus hangs on. Tie your value to that metric and you've got a champion who can fight for budget.
Objections and the real fear behind each. "It's too expensive" usually means "I'm afraid this won't work and I'll own that failure." Write down the surface objection and the fear underneath. Your reps need both.
Who they answer to and who they influence. Map the politics. Is this persona the signer, the champion, or the blocker? Who do they need to convince above them? This is what turns a single-threaded deal into a multi-threaded one.
Where they live and who they trust. The communities, podcasts, peers, and sources that shape their thinking. This tells you where to show up and whose name carries weight.
A real quote. One sentence, verbatim from research, that captures how this person sees the world. It anchors the whole persona and keeps it human.
That's the whole template. Eight fields, each of which changes a decision somewhere in the funnel. If a field doesn't change a decision, it's filler.
Activation: how reps actually use personas in deals
Here's where almost everyone drops the ball. The persona gets built, presented in a slide deck, and never touched again. Activation is the entire point, so build it into the places work already happens.
In outbound sequences. Each persona gets its own sequence, not a shared generic one. The opening line references their specific trigger and uses their pain language. The subject line pulls from the vocabulary bank. We tie persona detection to enrichment data so the right person automatically drops into the right sequence. This is where personas and automation meet. If you're routing by title but messaging by persona, your system does the sorting and your reps stay in the right lane.
In discovery calls. Give reps a one-page persona cheat sheet, not the full doc. On it: the three questions that uncover whether the trigger is real, the top two objections with responses, and the metric to tie value to. A rep should glance at it before a call and sound like they've sold to this exact person a hundred times.
In deal reviews. This is the discipline that keeps personas honest. When you review a stuck deal, ask which personas are engaged and which are missing. Single-threaded through one champion with no economic buyer involved? That's a persona gap, and the persona map tells you exactly who to go find.
In marketing content. Each persona should map to the content that answers their specific objection. The finance skeptic needs an ROI breakdown. The technical evaluator needs a security and integration page. When sales hits an objection, there should be an asset ready to send that was built for that exact fear.
The test for whether activation worked is simple. Ask a rep to describe your top persona without the doc in front of them. If they can name the trigger, the pain, and the main objection off the top of their head, the persona is live. If they stare at you, it's dead weight.
Keep personas alive or they lie to you
A persona built 18 months ago is probably wrong now. Buyers change. New roles appear, like the way revenue operations went from a nice-to-have to a budget owner in a few short years. Macro pressure shifts what people are measured on. The objections you heard before a market downturn aren't the objections you hear during one.
Build a quarterly habit: pull ten recent calls, check whether the pain language and objections still match the doc, and update the quotes. Watch which personas your closed-won deals actually came from versus which ones you built. If you keep winning deals from a persona you never formally defined, that's your market telling you something. Listen to it.
We bake this review into the RevOps rhythm for clients because a persona that drifts from reality quietly corrupts everything downstream, from ad targeting to sequence copy to forecast accuracy. If you want to see how this fits into a full build, our packages pair persona development with the sequences and automation that put them to work.
Frequently asked questions
How many buyer personas should a B2B company have?
Fewer than you think. Most teams run well on two or three. The real count is driven by distinct buying behavior, not job titles. If two roles share the same trigger, pain, and objection, they're one persona. Only split them when the difference changes how you'd write an email or run a call.
What's the difference between a buyer persona and a user persona?
A buyer persona is the person who decides to purchase, who cares about ROI, risk, and internal justification. A user persona is whoever uses the product day to day, who cares about whether it's actually good. In B2B they're often different people, and you need to sell to the buyer while making sure the user won't sabotage the rollout. Both belong in your deal map.
Can you build buyer personas without a lot of data?
Yes. Early-stage teams won't have hundreds of calls, but you can interview five customers and five prospects and learn more than most companies ever extract from their CRM. Start lean, write down the patterns, and sharpen the personas as real pipeline data comes in. Imperfect and based on real conversations beats polished and invented.
Personas only pay off when they're wired into the system that touches buyers. If your reps are reading laminated fluff while your sequences run generic copy, you're leaving deals on the table. Book a Revenue Systems Audit and we'll show you where your persona and targeting gaps are costing you.