Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas Your GTM Team Actually Uses
By Rick Elmore ·
Most B2B personas die in a slide deck. Someone builds "Marketing Mary," gives her a stock photo and a coffee habit, and no rep ever thinks about her again. That's not persona work—that's decoration.
Buyer persona development is the process of building research-backed profiles of the individual people inside a buying committee—their role, goals, objections, and buying triggers—so your GTM team can tailor outreach, content, and sales conversations to how each person actually makes decisions.
Buyer persona vs. ICP: what's the difference?
These get used interchangeably, and that confusion is why so many personas end up useless. They operate at different levels.
Your ICP (ideal customer profile) describes the account: company size, industry, tech stack, revenue band, growth stage. It answers "which companies should we chase?" A persona describes the person inside that account: their job pressures, what makes them look good to their boss, what makes them hesitate. It answers "who do we talk to, and what do we say?"
| Dimension | ICP (account-level) | Buyer persona (individual-level) |
|---|---|---|
| Unit of analysis | The company | The person inside the company |
| Example attributes | Industry, headcount, revenue, tech stack | Role, goals, objections, trigger events |
| Question it answers | Which accounts do we target? | Who do we message, and how? |
| Used most by | Demand gen, ABM, list building | SDRs, AEs, content, lifecycle marketing |
| Changes when | You move upmarket or into a new vertical | You sell to a new department or seniority level |
You need both. The ICP filters your list. Personas shape the conversation once you're in front of the right account. A common failure mode: teams nail the ICP, build a clean target list, then blast every contact the same generic message. The account was right. The person was ignored.
How to research buyer personas without guessing
The reason personas feel fluffy is that most of them are invented in a conference room. A marketer imagines what a VP of Operations probably cares about, writes it down, and calls it research. Real persona development pulls from evidence you already have and evidence you go get.
Mine your existing sales conversations
Your call recordings are the richest persona data you'll ever have, and you're already sitting on them. Pull 15–20 recordings from recent won and lost deals. Listen for the exact language buyers use to describe their problem, the objections that come up in the same spot every time, and the moment someone says "yeah, that's exactly it." That phrasing goes straight into your messaging. You're not summarizing—you're transcribing how buyers actually think.
Interview real buyers, especially the ones who said no
Ten to twelve interviews per persona is usually enough to see patterns. Talk to recent customers, but don't skip the deals you lost. The people who chose a competitor or did nothing will tell you more about your positioning gaps than any happy customer. Ask about the problem before they found you, who else weighed in on the decision, and what nearly stopped them from buying. Avoid leading questions. You want their story, not confirmation of yours.
Pull patterns from your CRM and product data
Which titles close fastest? Which roles show up in deals that stall? What job functions correlate with expansion versus churn? Your CRM already knows things your personas should reflect. Cross-reference that with support tickets and onboarding notes to understand what each persona struggles with after the sale, not just before it.
Watch how they behave, not just what they say
People misreport their own behavior. Layer in observable signals: which content a persona engages with, which pages they visit before booking, what they search. Behavior fills the gaps between what someone claims matters and what actually moves them.
What goes into a persona your GTM team will actually use
Skip the age range and the fictional weekend hobbies. None of that changes a single sentence in an outreach sequence. A working persona is built around what your team needs to make decisions. Here's the structure we use with clients when we build out their revenue engine.
- Role and mandate. What are they responsible for, and how is their performance measured? A VP of Sales measured on pipeline coverage cares about different things than one measured on rep ramp time.
- Primary goals. The two or three outcomes that make this person's quarter. Tie these to metrics they report upward.
- Pain points and frustrations. The specific, concrete problems—phrased in their words, taken from your interviews and call recordings.
- Objections and hesitations. What makes them stall? Budget, risk, past bad experiences with tools like yours, fear of the implementation lift.
- Buying trigger. The event that turns this from a "someday" into a "now." A new hire, a missed number, a funding round, a system that finally broke.
- Role in the buying committee. Are they the economic buyer, the champion, the technical evaluator, or the blocker? This single field changes your entire approach.
- Where they get information. Which communities, newsletters, podcasts, and peers they trust. This tells you where to show up.
- Messaging that lands. The value propositions this persona responds to, and the ones that fall flat.
If a field on your persona template doesn't change what a rep says or what a marketer builds, cut it. Every attribute should earn its place by influencing a real decision.
Why the buying committee breaks single-persona thinking
B2B purchases rarely come down to one person. A typical deal of any size involves a handful of stakeholders, and they don't want the same thing. The champion wants to look smart for bringing you in. The economic buyer wants to protect the budget and hit a number. The technical evaluator wants to know it won't create work or risk. Someone in the room just wants the whole thing to go away so they can get back to their day.
If you build one persona and speak only to the champion, you win the champion and lose the deal in procurement or IT review. This is where persona development earns its keep. Map the full committee for a typical deal:
- Champion: feels the pain daily, advocates internally, needs ammunition to sell you upward.
- Economic buyer: signs the check, thinks in ROI and risk, often enters late and skeptical.
- Technical/functional evaluator: judges whether it works and what it costs to implement.
- End users: live with the tool daily; their resistance can quietly kill adoption.
- Blocker: the status-quo defender or the person whose turf you're stepping on.
Each of these needs its own message and, often, its own content asset. Your champion needs a one-pager they can forward. Your economic buyer needs a business case. Your technical evaluator needs a security doc or integration overview. Build personas for the roles that consistently show up in your deals, then arm your team to speak to all of them in sequence.
How to operationalize personas across outreach and content
A persona that lives in a Google Doc is worthless. The whole point is to change what your GTM engine does day to day. Here's how to push personas into the actual work.
Wire personas into outreach sequences
Build separate sequences per persona, not one sequence you spray at everyone. The champion sequence leads with the operational pain. The economic-buyer sequence leads with the number and the risk of inaction. Same company, same deal, different entry point. When you tag contacts by persona in your CRM, this becomes automatic. AI-driven personalization only works when it has a persona to draw from—feed the model the persona's language, goals, and objections, and your outbound stops sounding like a template.
Map content to persona and buying stage
Take each persona and each stage of their journey, and check whether you have an asset for it. Early-stage champion content looks nothing like late-stage economic-buyer content. Most teams have a pile of top-of-funnel blog posts and nothing for the evaluator who needs a comparison sheet at decision time. The gaps in that grid are your content roadmap.
Give reps a persona cheat sheet
For every persona, hand your reps a single page: top three pain points, the two objections you'll definitely hear and how to handle them, the value props that land, and the questions that surface the buying trigger. This turns a persona from theory into something a rep uses on a live call.
Keep personas alive
Personas decay. Buyers change, markets shift, and your product evolves. Review them quarterly against fresh call data and closed-deal patterns. A persona built once and never revisited slowly drifts back into fiction. When we build integrated revenue systems, we treat persona maintenance as an ongoing input to the engine, not a one-time project. If you want that built and maintained for you, that's part of what our packages cover.
Common mistakes that make personas useless
A few patterns show up again and again when we audit a team's go-to-market setup:
- Confusing personas with ICP. Describing the company instead of the person leaves reps with nothing to say.
- Inventing them from imagination. No interviews, no call data, no CRM analysis—just assumptions dressed up as insight.
- Too many personas. If you have twelve personas, you effectively have zero. Focus on the three or four roles that drive most of your revenue.
- Demographic filler. Details that don't change any decision waste space and dilute the parts that matter.
- Building them and abandoning them. A persona that never touches a sequence, a piece of content, or a sales call was a waste of everyone's afternoon.
Frequently asked questions
How many buyer personas should a B2B company have?
For most teams, three to five is the sweet spot—usually mapped to the core roles in your buying committee, like the champion, the economic buyer, and the technical evaluator. If you're building more than five, you're likely slicing too thin. Start with the roles that appear in your highest-value closed deals and expand only when a distinct new role consistently shows up.
What's the difference between a buyer persona and an ideal customer profile?
An ICP describes the account you want to sell to—industry, size, tech stack, revenue. A buyer persona describes an individual person inside that account—their role, goals, and objections. Use your ICP to build the target list, then use personas to decide who to contact and what to say to them.
How do you research buyer personas with a small team?
Start with what you already have. Pull 15–20 sales call recordings and listen for recurring language and objections, then mine your CRM for which titles close and which stall. Add five to ten short interviews with recent customers and lost deals. You don't need a research department—you need to actually listen to the conversations you're already having.
How often should you update buyer personas?
Review them quarterly against fresh call data and closed-deal patterns, and do a deeper refresh whenever you enter a new market, move upmarket, or ship a major product change. Personas drift back into fiction if you set them once and forget them, so treat maintenance as an ongoing input to your revenue engine.
If your personas are collecting dust while your outreach stays generic, the fix is connecting research to the systems that actually run your GTM. Book a Revenue Systems Audit and we'll show you where your personas should be driving pipeline and aren't.