Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas That Actually Shape Messaging and Targeting
By Rick Elmore ·
Most of the buyer personas I inherit when we take over a revenue system are useless. They live in a slide deck somebody built two years ago, they have a stock photo and a cute name like "Marketing Mary," and they list things like "enjoys yoga and reads industry blogs." None of that has ever helped a single rep write a better opening line or helped a media buyer exclude a bad audience.
Here's the thing nobody says out loud: a persona that doesn't change what you say or who you say it to is decoration. If your SDRs, your content team, and your ad platform all behave identically with or without the persona document, you don't have personas. You have a creative writing exercise.
So let me walk you through how we actually do buyer persona development at FullStackCloser—the research-driven version that feeds outreach copy, content angles, and audience targeting instead of sitting in a shared drive.
- Personas are role-level, not account-level. Your ICP describes the companies worth selling to. Personas describe the humans inside those companies who approve, use, or block the purchase.
- Build from conversations, not assumptions. The useful inputs are won/lost call recordings, actual objections, and the language buyers use—not internal guesses.
- Every persona needs four things that drive action: the pain they feel, the trigger that makes them act, the objections that stall them, and the words they use to describe all three.
- The buying committee has conflicting priorities. The economic buyer, the user, and the blocker each need different messaging. One persona can't cover them.
- If a persona doesn't change a subject line or an audience exclusion, delete it. Operationalization is the whole point.
ICP vs buyer persona: why the distinction matters
I see these two used interchangeably constantly, and it causes real damage. Your Ideal Customer Profile is an account-level filter. It answers: which companies should we spend time on? Industry, headcount, revenue band, tech stack, growth stage, regulatory pressure. The ICP tells your SDRs which doors to knock on.
Buyer persona development operates one level down. Once you're inside a qualified account, you're not selling to "a 200-person logistics company." You're selling to a VP of Operations who's being measured on throughput, a CFO who just got burned by a tool that overpromised, and an IT lead who has to integrate whatever gets bought. Same account. Three humans. Three completely different conversations.
Confusing the two is why so much B2B outreach reads like it's addressed to a building instead of a person. The ICP gets the targeting roughly right at the company level, then the message falls flat because it ignores the specific role reading it.
| Dimension | ICP (account-level) | Buyer persona (role-level) |
|---|---|---|
| Unit | The company | The individual in the buying committee |
| Answers | Who should we target? | What do we say to them, and why do they care? |
| Built from | Firmographics, tech stack, growth signals | Pains, triggers, objections, and actual buyer language |
| Drives | List building, account scoring, territory design | Messaging, content angles, ad creative, objection handling |
You need both. The ICP keeps you from wasting time on accounts that will never close. The persona keeps you from wasting the conversation once you're in.
Where real persona research actually comes from
The lazy way to build a persona is to gather your team in a room and brainstorm what you think the buyer cares about. That produces a mirror of your own assumptions. Useful personas come from sources where the buyer's actual words show up unfiltered.
The richest source by far is recorded sales calls—especially the ones you lost and the ones that stalled. Won deals tell you what worked. Lost and stalled deals tell you what the buyer was really worried about, which is the stuff that never makes it into your pitch deck. When I'm rebuilding a client's personas, I spend most of my time in call recordings, and I'm listening for three patterns: the phrase they use to describe their problem, the moment something shifted and they decided to look for a solution, and the specific reason they hesitated.
Beyond calls, I pull from:
Win/loss notes and CRM fields. What reasons do reps log for losses? "Price" is usually a cover story. Dig and you'll often find it was really "couldn't get IT buy-in" or "the champion left."
Support tickets and onboarding friction. The problems customers hit after buying reveal what they actually valued and expected. That's gold for messaging.
The buyer's own public language. How do people in this role describe their challenges on LinkedIn, in community threads, in job descriptions for roles they're hiring? Job postings in particular are a cheat code—they spell out exactly what a department is struggling with.
Short interviews with recent buyers. Ten focused conversations with people who bought in the last quarter will teach you more than any survey. Ask them to walk you through the day they decided to solve this problem.
Notice what's missing from that list: demographics, hobbies, favorite publications. None of that changes what you say. Drop it.
The four things every persona has to capture
When we document a persona, it has to earn its place by driving a decision somewhere in the revenue system. That means four components, and each one maps to something concrete your team does.
The pain. Not a generic category like "inefficiency." The specific, felt version: "I'm manually reconciling three systems every Friday and I don't trust the numbers I hand to my boss." Pain written at that resolution writes your outreach for you. Vague pain produces vague copy that gets ignored.
The trigger. What event moves this person from "aware of the problem" to "actively looking"? A new hire. A funding round. A missed target. A competitor's move. A tool that got sunset. Triggers are the most underused piece of persona work, because they tell your targeting when to reach out, not just who. A VP of Ops always has inefficiency pain. They go looking for a fix right after they inherit a messy team or get handed an aggressive growth number.
The objections. Every role has predictable reasons to say no or "not now." The CFO's objection is risk and ROI proof. The IT lead's objection is integration burden and security. The end user's objection is "one more tool I have to learn." If you know the objection cold, you can preempt it in the message instead of getting ambushed by it on call three.
The language. The exact words this persona uses. If buyers say "revenue leakage" and you say "funnel optimization," you sound like an outsider. Mirroring their vocabulary is the fastest way to earn trust in a cold message. I keep a running swipe file of verbatim phrases pulled from calls, organized by persona, and that file does more for copy quality than any messaging framework.
Map the buying committee, not just the buyer
B2B purchases over a certain size are never made by one person. There's a committee, whether it's formal or not, and the members have conflicting incentives. This is the single biggest reason one-persona thinking fails.
Take a typical mid-market software deal. The economic buyer (often a VP or C-level) cares about outcomes and risk—will this move a number I'm accountable for, and will it embarrass me if it fails? The champion is usually the person who feels the pain daily and wants it gone; they'll fight for you internally if you arm them. The end users care about whether their day gets easier or harder. And there's almost always a blocker—frequently IT, security, finance, or legal—whose job is to find reasons this is a bad idea.
You need a persona for each of these, and the messaging has to flex accordingly. The email to the champion leans into the daily pain and hands them ammunition. The content you send the economic buyer is about outcomes and de-risking. The material that helps your champion get past the blocker is a security overview or an integration one-pager. Same company, same deal, four messages.
When we build out a revenue engine for a client, this mapping directly shapes the sequences. A multi-threaded outreach play isn't just "hit more people at the account"—it's hitting the right people with the message built for their seat at the table.
How to operationalize personas across outreach, content, and ads
Here's where most persona projects die. The document gets built, everyone nods, and nothing downstream changes. Operationalizing means wiring the persona into the three places messaging actually lives.
Outreach. Each persona should produce a distinct opening line, a distinct pain hook, and a pre-written objection handle. Your SDRs shouldn't be guessing what to say to a CFO versus a Head of Ops—the persona hands them the angle. Triggers feed your intent signals and timing, so sequences fire when someone just changed roles or the company just raised.
Content. Every asset you produce should be aimed at a specific persona at a specific stage. Champion-stage content solves the daily pain and is easy to forward. Economic-buyer content proves outcomes and reduces perceived risk. If you can't name which persona a piece of content serves, it's probably serving no one.
Ad targeting. This is where role-level personas pay off directly. Job-title and seniority targeting on LinkedIn, or audience building on other platforms, maps straight to your personas. The creative changes per persona too—the ad a VP of Finance sees should not be the ad a frontline manager sees. And your exclusions matter as much as your inclusions; a clear persona tells you who to keep out of the audience so you stop paying for clicks from people who never influence the purchase.
The test I use: pull up any live sequence, any piece of content, any ad set, and ask "which persona is this for, and what pain, trigger, or objection is it addressing?" If the team can answer instantly, the personas are doing their job. If they shrug, you've got decoration again. This is exactly the kind of connective work we handle when we build an integrated engine—personas feeding outreach, content, and targeting from one source of truth. You can see how that fits together in our packages.
Keep them alive
Personas aren't a one-time deliverable. Markets shift, triggers change, new objections emerge, your product evolves. I treat the persona set as a living document that gets refreshed every quarter against new call recordings and win/loss data. The language file in particular should be updated constantly, because the way buyers talk about their problems moves faster than you'd think.
The ones that go stale are the ones that quietly stop matching reality, and your copy drifts back toward sounding like an outsider. A thirty-minute monthly review of recent calls is enough to keep them sharp.
Frequently asked questions
How many buyer personas do I actually need?
Fewer than you think. Most B2B companies need three to five, mapped to the roles in the buying committee—typically an economic buyer, a champion, an end user, and sometimes a blocker. If you have fifteen personas, you've built segments, not personas, and nobody will use them. Build one per distinct role with distinct pains and objections, and stop there.
What's the difference between a buyer persona and an ICP?
Your ICP is account-level: it defines which companies are worth targeting based on firmographics, tech stack, and growth signals. A buyer persona is role-level: it defines the individual humans inside those accounts and what they personally care about. The ICP tells you which doors to knock on; the persona tells you what to say when someone opens it. You need both working together.
How do I know if my personas are good enough to use?
Run the operational test. Pull up a live email sequence, a content asset, and an ad set, and ask which persona each one serves and which pain, trigger, or objection it addresses. If your team answers immediately, the personas are working. If they can't, the personas aren't driving decisions and need to be rebuilt from real buyer conversations instead of internal assumptions.
If your personas are sitting in a slide deck instead of shaping your outreach, content, and targeting, that's a gap worth closing. Book a Revenue Systems Audit and we'll show you where your messaging is leaking and how to wire your personas into the system that actually sends it.