Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas That Actually Shape Messaging and Targeting
By Rick Elmore ·
Most B2B personas are useless. They're one-page PDFs with a stock photo of "Marketing Mary," her age, her favorite apps, and a vague note that she "values efficiency." Nobody on the sales team has ever opened the file twice, and it certainly never changed a single line of outbound copy.
Done right, buyer persona development does something specific: it tells you exactly what a real human is trying to accomplish, what's blocking them, what event made them start looking, and the precise words they'd use to describe the problem. That's what shapes messaging and channel choice. Here's how to build personas that actually earn their place in your go-to-market.
The short answer: Build personas from real buyer conversations and behavioral data—anchored to jobs-to-be-done, pains, and buying triggers—then wire each one directly into your messaging, targeting filters, and sequence logic.
Persona vs ICP: what's the difference?
These get conflated constantly, and the confusion wrecks both. Your ICP describes the account: industry, headcount, revenue, tech stack, growth stage. It answers "which companies should we go after?" Your buyer persona describes the person inside that account: their role, what they're responsible for, what they fear, and what triggers them to act.
| Dimension | ICP (account-level) | Buyer persona (person-level) |
|---|---|---|
| Unit of analysis | The company | The individual decision-maker or influencer |
| Core attributes | Industry, size, revenue, geography, stack | Role, goals, pains, buying triggers, language |
| Drives | Targeting and list building | Messaging, offer framing, channel choice |
| Question it answers | "Who do we sell to?" | "What do we say, and why would they care?" |
You need both. The ICP builds your list. The persona decides what hits their inbox. A single account often holds three or four personas—an economic buyer, a technical evaluator, a user-level champion—each needing a different message. Skip the persona work and every one of them gets the same generic pitch.
How to build B2B buyer personas that shape messaging
-
Start with the jobs-to-be-done, not demographics
Forget age and "preferred social platform." The thing that predicts buying behavior is the job the person is hired to get done. A VP of Sales is "hired" by their CEO to hit a number predictably. A RevOps lead is hired to make the pipeline trustworthy and the forecast accurate. Write the job as an outcome the person is accountable for, in their own terms. When you understand the job, the pain and the trigger fall out of it naturally—and so does the message.
-
Mine real conversations before you write a word
The best persona input already exists in your organization. Pull it from: recorded sales calls (especially discovery and lost-deal debriefs), support tickets, won-deal interviews, and the raw language in reply emails. Read how buyers describe their own problem. You're listening for the exact phrasing—"my reps spend all day on admin instead of selling" is a usable line; "operational inefficiency" is not. If you're early and don't have call volume yet, book five conversations with people who match the role and just ask about their last six months.
-
Document pains at three levels
Surface pain is the symptom they'll mention first ("our reply rates dropped"). Underneath it sits the business pain (pipeline is shrinking) and underneath that, the personal pain (the person looks bad in the Monday forecast meeting). Great messaging connects all three. You lead with the symptom they recognize, tie it to the business cost that justifies budget, and acknowledge the personal stake that creates urgency. Document all three for every persona.
-
Identify the buying triggers
Nobody buys because of a feature. They buy because something changed. Buying triggers are the events that flip a persona from "aware of the problem" to "actively looking." Common ones in B2B: a new leader in the seat (first 90 days, wants a win), a missed quarter, a funding round, a tool that got sunset or repriced, a sudden scaling mandate, a competitor pulling ahead. List the three or four triggers that most reliably precede a purchase for each persona. These become your targeting signals and your opening lines.
-
Map the information diet and channel behavior
Where does this person actually learn and get persuaded? A technical evaluator might live in community Slack groups and documentation. An economic buyer might only read a peer referral or a tight LinkedIn post. This isn't about "which platform they use"—it's about which channel carries credibility for this decision. The answer tells you where to show up and in what format. Cold email, LinkedIn, paid, partner intros, and content all have different fit by persona.
-
Capture their objections and decision criteria
Every persona has a predictable set of reasons to say no and a scorecard they use to evaluate. Write down the top objections ("we tried outbound and it didn't work," "my team won't adopt another tool") and the criteria they weigh (speed to value, integration with current stack, risk to their reputation). Your messaging and sales sequences should preempt the objections and speak to the criteria before they're even raised.
-
Write the persona as a messaging brief, not a biography
Collapse everything into a one-page working document a copywriter or SDR can act on. The format we use: the job, the three-level pain, the top triggers, the buyer's own language (verbatim quotes), the objections, the decision criteria, and the channel. If a field doesn't change what you'd write or where you'd send it, cut it. A persona that doesn't drive a decision is decoration.
-
Wire personas into targeting, messaging, and sequences
This is the step most teams skip, and it's the only one that produces revenue. Each persona needs:
- Targeting: Translate triggers into filters. "New VP of Sales in the last 90 days" becomes a job-change signal in your data provider. "Recently funded" becomes a funding filter.
- Messaging: One core angle per persona, built on their primary pain and trigger, using their verbatim language in the subject and opening line.
- Sequences: Channel order and cadence matched to the persona's information diet—email-first for one, LinkedIn-first for another, with follow-ups that cycle through the objections.
When personas are wired in like this, your whole engine gets sharper. We build this layer directly into the systems we run for clients, so persona insight isn't a slide—it's the logic behind every send. If you'd rather have it built for you, that's what our packages are designed around.
-
Validate and revise against real response data
Personas are hypotheses until the market replies. Watch which angles get replies, which triggers correlate with booked meetings, and which personas convert to revenue versus just opening emails. The persona that looked most important on paper is often not the one that closes. Revisit the documents quarterly and rewrite them based on what actually performed. A persona built once and never touched is already decaying.
Common mistakes in buyer persona development
- Inventing personas in a conference room. If the persona came from a brainstorm instead of real buyer input, it's fiction. Fiction doesn't convert.
- Padding with demographics that don't change anything. Age, hobbies, and a made-up name feel thorough but never alter a single word of copy or a targeting filter.
- Building one persona per account. Deals have multiple humans. The champion who loves you can't sign; the economic buyer who signs has never heard of you. Build for the committee.
- Confusing persona with ICP. Targeting the right company with the wrong message to the wrong person still loses. You need account fit and person-level resonance.
- Treating triggers as optional. Without triggers you're guessing at timing, and timing is most of why cold outreach works or fails.
- Letting personas rot. Markets move, leaders change, tools get repriced. A two-year-old persona is describing a buyer who no longer exists.
- Never connecting them to the system. A beautiful persona document that lives in a folder has zero revenue impact. The value is in the wiring.
Frequently asked questions
How many buyer personas do I actually need?
For most B2B companies, three to five active personas is the right range—usually an economic buyer, a technical or operational evaluator, and a user-level champion, sometimes split by segment. If you have more than five you're probably slicing too thin; fewer than three and you're likely ignoring members of the buying committee who can kill the deal.
What data should buyer persona development be based on?
Primary sources beat everything: recorded sales calls, won and lost deal interviews, support conversations, and reply-email language. Supplement with behavioral data from your CRM and outreach tools—which angles got replies, which triggers preceded meetings. Avoid building personas purely from third-party demographic reports; they describe populations, not the specific people in your pipeline.
How is a buyer persona different from an ICP?
An ICP is account-level—it defines which companies to target based on firmographics like industry, size, and stack. A buyer persona is person-level—it defines what an individual inside that account is trying to accomplish, what pains and triggers drive them, and how to message them. The ICP builds your list; the persona decides what you say to each human on it.
How often should I update my personas?
Review them quarterly against real response and conversion data, and trigger an immediate revision whenever something structural shifts—a new competitor, a market downturn, a pricing change in an adjacent tool, or a clear pattern of new objections showing up in calls. Personas are living documents. The ones that stop getting updated quietly stop being accurate.
If your messaging feels generic and your targeting is spraying the same pitch at every contact, the fix usually isn't more volume—it's persona-level insight wired into the system. Book a Revenue Systems Audit and we'll show you where your personas and your pipeline are out of sync.