A B2B buyer persona is a one-page profile of one buying role, built from what real buyers said rather than from guesswork.

Definition

A B2B buyer persona is a researched profile of one role inside a buying group: what that person is measured on, what they are trying to fix, how they judge vendors, and what makes them say no.

It describes a role, not a company. The company side of targeting belongs in the ideal customer profile. The persona sits underneath it and answers a different question: once you are talking to the right company, who are you talking to, and what do they care about?

The useful part is evidence. In this page's view, buyer personas built from customer interviews and recorded sales calls change what a team writes. Personas built from imagination tend to change nothing, and end up unread in a shared drive.

Tools describe the idea in their own way. The HubSpot Knowledge Base calls personas fictional, generalized characters that encompass the needs, goals and behavior patterns of your customers. This page adds one condition: the generalization should rest on things real buyers said, so a rep can trace each line back to a call.

B2B buyer persona vs ICP vs target audience

The four nest. The target market sizes the opportunity. The ideal customer profile narrows it to the companies that fit best. The B2B target audience turns that into rules for which people a campaign or sequence reaches. The persona then explains what one of those roles cares about.

The practical difference is the unit. An ICP field is "companies with 200 to 1,000 employees that run an in-house support team." A persona field is "the support director, who is judged on first response time and is tired of tools that add work for agents."

In B2B the user and the buyer are often different people, which is the whole reason buyer personas exist. The user persona explains what the product must do. The buyer persona explains why anyone would pay for it, and what would stop them.

This page owns the persona itself: the research, the template, and how to use it in messaging and sales. The company rules live in the ICP and the people rules in the target audience. Keep the three documents separate so each one can be wrong on its own and be fixed on its own.

Why B2B teams create buyer personas

A persona is a shared reference, so that a marketer writing an ad, a rep writing an email and a product manager reading feedback all picture the same buyer. Without one, each person fills the gap with their own guess, and the messages drift apart.

• Understanding the decision: it records why a role starts looking, what it compares and what stops it, which is the part a target list cannot tell you.
• Better marketing content: content built on a persona answers the questions buyers ask before they talk to any vendor, in their own words.
• Sharper sales conversations: reps open with the outcome the role reports, not with a feature, and know which objection is coming.
• Cleaner data: once a persona exists as a CRM field, campaigns, reports and lead routing can use it instead of a free text job title.
• Fewer wasted deals: a written bad fit condition helps a team stop working buyers it cannot win.

LinkedIn's free B2B buyer persona template lists the same uses in its usage guide: tailoring marketing strategies, content creation, product development and sales approaches. The value only appears when the persona is used in those places, so the rest of this page is about making it usable.

What a useful B2B buyer persona contains

Many persona templates ask for age, hobbies and a photo. In our view, in B2B those fields seldom change a sentence you write. The fields below do, because each one has an owner in the sales or marketing process.

LinkedIn's free B2B buyer persona template for marketers is organized into seven sections: basic information, demographics, professional background, company role, personal insights, media consumption and buying behavior. Its company role section asks for decision-making authority, role in the buying process, goals and pain points.

Its buying behavior section asks for buying motivations, criteria for vendor selection, preferred communication channels and past purchasing experiences. Those last two sections are where most of your research time should go, in this page's view, because they are the ones a writer and a rep use every day.

The same template includes an age range, education level, and hobbies and interests. Keep them if your team finds them useful for picturing the buyer, but do not let them take the space that criteria and objections need.

Job pressures, goals and pain points

Every buying decision in B2B is made by someone with a job to keep. The fastest way to make a persona useful is to write down the numbers that person reports upward, and the parts of the job that make those numbers hard.

• The scoreboard: the metrics named in their quarterly review, such as pipeline, uptime, cost per hire, gross margin or audit findings.
• The recurring fire: the thing that interrupts them every week and never gets fixed for longer than a month.
• The project they promised: the initiative they committed to and have not started, often because of headcount or a dependency.
• The invisible work: the reporting, the approvals, the chasing across teams that no one credits them for.
• The career risk: what would make this a bad year for them personally, which is often a visible failure rather than a missed target.

These five lines do more work than a dozen demographic fields. They tell a writer which outcome to lead with, and they tell a rep which discovery question will get a real answer instead of a polite one.

Goals and pain points that are specific enough to be wrong

Every buyer persona template asks for goals and pain points, and many get filled in with sentences that could describe anybody. "Wants to grow the business" is not a goal. "Wants to save time" is not a pain point.

The fix is to make both specific enough to be wrong. A goal is useful when it names a number and a deadline. A pain point is useful when it names a task, how often it happens, and who it lands on. See customer pain points for collecting them.

Understanding goals and pain points at this level is what separates a persona that helps a writer from one that reassures a manager. Pull both straight from transcripts, and keep the sentence the buyer used.

One more test. If a competitor could copy your goals and pain points into their own persona without changing a word, you have written a category description, not research.

One persona per buying committee role

Many B2B purchases involve more than one person, and the people in the group want different things. A persona set that ignores the group produces messaging that only ever lands with one of them. The table below is the role model this page uses.

CRM tools use similar labels. HubSpot's default Buying role property gives Decision Maker, Budget Holder and Blocker as example values, and its account-based marketing setup includes default segments for contacts labeled Champion, Budget Holder and Decision Maker.

In our view the blocker is the role easiest to leave out of a persona set. A blocker is not always hostile. Often they own the tool you would replace, or the process you would change, and nobody has given them a version of the story where they come out well.

Write a short persona for each role you actually meet in deals, and one for the role you keep discovering too late. Reaching each of those people inside one open deal is a separate skill, covered in multithreading in sales. The persona tells you what to say once you reach them.

Buying criteria: how this persona decides

Buying criteria are not a feature list. They are the things a buyer compares, in the order they compare them, and the order can differ by role. A champion may rank speed to value first and price fourth. The economic buyer may reverse that.

Write the criteria in the buyer's words, with the order they used. That order is what your value proposition has to respect, and it is the difference between a deck that answers the buyer's questions and one that answers yours.

Public role data can seed this field for roles you rarely interview. The U.S. Bureau of Labor Statistics, describing buyers and purchasing agents, lists evaluating suppliers on the basis of the price, quality, and speed of delivery among their duties. That is a starting order to test in calls, not a finding about your market.

Objections, perceived barriers and the buyer's language

Buyer Persona Institute, a firm whose method rests on interviews with recent buyers, names five areas on its template page, which it calls the 5 Rings of Buying Insight: priority initiatives, success factors, perceived barriers, decision criteria and the buyer's journey.

It describes perceived barriers as the fears and concerns that lead buyers to keep the status quo or prefer a competitor.

A barrier is not always a stated objection. It is whatever makes the buyer quietly prefer the status quo: a bad experience with a similar vendor, a rumor about your category, a colleague who will resist, or a belief that the project will take longer than anyone admits.

• Write the objection verbatim. "We tried something like this two years ago and it died in rollout" is usable. "Price" is not.
• Record who raises it. The same objection from a user and from finance needs two different answers.
• Record when it appears. An objection in the first call is a filter. The same objection in week six is a warning.
• Record what actually resolved it. Often a reference, a pilot scope or a contract term, rather than a rebuttal.

Objections collected this way feed straight into qualification. If a persona reliably raises a barrier you cannot answer, that is a disqualification rule, and it belongs in how you qualify sales leads rather than in a longer sequence.

The language this persona actually uses

Buyers do not always use the category name you use. A finance leader may say "close the books faster" where a vendor says "financial close automation." A support director may say "tickets bouncing between teams" where a vendor says "omnichannel routing."

Collect the buyer's phrasing from transcripts and their own writing, then keep a short two-column list: what we say, what they say. Use their column in subject lines, ad copy and the first line of a call, and your column only once they are already interested.

This is also the cheapest place to catch a persona that is out of date. When new words appear in calls that are not on your list, something in the market moved before your messaging did.

How to create B2B buyer personas from real calls

Buyer persona research is not a brainstorm. It is a small study with a sample you can name. The steps below, written for this page, create one persona from customer data you already have plus a handful of conversations.

1. Pick one decision, not one job title

   Personas are built around a buying decision. Choose the decision you want to influence, then find the role that leads it. One decision keeps the research bounded and the output usable.

2. Mine the calls you already recorded

   Pull a set of recent discovery and closed-lost calls with that role; ten is the sample this page suggests. Note the trigger, the words used for the problem, the objections and who else joined the call.

3. Interview recent buyers

   Talk to people who made this decision recently, including ones who chose a competitor or did nothing. Buyer Persona Institute gives a rule of thumb of at least 10 interviews before you compile and aggregate the findings, and suggests recording and transcribing them.

4. Ask your own reps and support team

   Reps hear the objection that stalls deals. Support and customer success hear what the role complains about after the contract is signed, which is where renewal risk hides.

5. Read what the role writes in public

   Job posts, O*NET task lists, conference talks, community threads and their own posts. Public sources will not give you the trigger, but they give you vocabulary and priorities for free.

6. Look for patterns, not averages

   Group quotes into the fields from the table above and count how many buyers said each thing. Buyer Persona Institute draws the same line between an insight cited by several buyers and an outlier from a single buyer.

7. Write it on one page and circulate it

   One page per role, with a headline for each finding and the quotes under it. Show it to two reps and ask what is wrong. Anything nobody recognizes is a guess you inherited, so cut it.

Buyer interview questions that produce a persona

Ask about the last real decision, not about preferences in general. This page works on the assumption that people describe what they did more reliably than what they say they would do.

• Take me back to the day you decided to look. What happened that week that made this worth your time?
• What had you been living with before that? Why was that tolerable until then?
• Who else got involved, and at what point? Who had to agree, and who could have stopped it?
• What did you compare? Including doing nothing, building it internally, or hiring a person instead.
• What almost stopped you? What were you worried would go wrong?
• What did you have to promise internally? What number or date did you attach to it?
• Where did you look for information? Who did you ask that does not work at a vendor?
• What surprised you after the decision? What do you wish someone had told you earlier?

Record with permission, transcribe, and keep the quotes. Ask no leading questions about your product. The moment the call turns into a pitch, the answers turn polite and stop being evidence.

Data sources when you cannot get an interview

A new team may not have ten customers to call. You can still create a first draft from public and internal data, as long as you label it a draft and replace each guess as real calls come in.

Account data helps here too, and technographics tell you which tools an account runs. They describe the account, not the person, so treat them as a reason to research rather than as a finished persona.

Drafting a persona from O*NET and BLS role data

O*NET OnLine, published by the U.S. Department of Labor, Employment and Training Administration, has a profile for each standard occupation: a summary, a sample of reported job titles, a task list, work activities, work context and the software used.

For a role you have never interviewed, that profile is a free, neutral first draft of the role and scope field.

Take procurement, a role that, in this page's view, often joins B2B deals late. O*NET's Purchasing Managers profile (11-3061.00) summarizes the job as planning, directing or coordinating the activities of buyers, purchasing officers and related workers involved in purchasing materials, products and services.

The Bureau of Labor Statistics adds a line that belongs in the objections field: purchasing managers develop their organization's procurement policies and procedures to help ensure that workers who handle procurement meet ethical standards and avoid potential conflicts of interest. A vendor that pushes around that process creates its own blocker.

The same method works for the technical reviewer. O*NET's Computer and Information Systems Managers profile (11-3021.00) lists IT Director and IT Manager among reported titles, and includes tasks such as consulting with users, management, vendors and technicians to assess computing needs and system requirements, and evaluating data processing proposals to assess feasibility.

Two limits keep this honest. Occupation data describes a job across every industry, not the person at your target accounts, and it says nothing about your category. Use it for scope, titles and vocabulary, mark every line "draft, not yet heard in a call," and replace it as interviews come in.

A B2B buyer persona template

The buyer persona template below was written for this page. Fill it in for one buying role at a time, keep it to a single page, and delete any line you cannot support with a quote, a recording or a data source.

PERSONA: {{personaName}} ({{roleLabel}})
Typical titles: {{titles}}
Sits in: {{department}} | Reports to: {{reportsTo}}
Company context: {{icpSummary}}

MEASURED ON
1. {{metricOne}}
2. {{metricTwo}}

JOB PRESSURES
Recurring fire: {{weeklyFire}}
Postponed project: {{stalledProject}}
Career risk: {{visibleFailure}}

TRIGGER TO LOOK
{{triggerEvent}}

ROLE IN THE DECISION
Decides / approves / uses / can veto: {{decisionRole}}
Also involved: {{otherRoles}}

BUYING CRITERIA, IN THEIR ORDER
1. {{criterionOne}}
2. {{criterionTwo}}
3. {{criterionThree}}

OBJECTIONS, VERBATIM
"{{objectionQuote}}"
Resolved by: {{whatResolvedIt}}

LANGUAGE
They say: {{buyerPhrase}}
We say: {{vendorPhrase}}

WHERE THEY LOOK
{{channelsAndPeers}}

DISQUALIFY WHEN
{{badFitCondition}}

LIST FILTERS
Function: {{function}} | Seniority: {{seniority}} | Titles: {{titles}} | Geography: {{geography}}

EVIDENCE
{{interviewCount}} interviews, {{callCount}} call recordings, last reviewed {{reviewDate}}
Draft lines not yet heard in a call: {{draftLines}}

LinkedIn's template suggests giving each persona a fictitious name to make it more relatable. A name tied to the role works well for that, because nobody mistakes it for a real contact in the CRM.

Two example B2B buyer personas

Both example personas below were written for this page. Their names are invented role labels, not real people, and no real company is described. They show the shape of a filled-in template, not facts about any market.

Example 1: "Support Sam," the champion (invented)

Example 2: "Procurement Pat," the late reviewer (invented)

This second persona starts from the O*NET draft above and shows what changes once calls fill it in. Lines marked "draft" came from occupation data; the rest are invented interview findings written for this page.

Notice what neither example contains: age, hobbies, a photo or a personality type. None of them would change a subject line, a discovery question, an ad or a page on the website.

How many B2B buyer personas you need

Fewer than you think. Buyer personas cost research to create and attention to maintain, so each one has to earn its place by changing what a marketing or sales team actually does.

• Start with one: the role that leads the decision you most want to win, researched properly.
• Add a second only when the message must change: a different problem, a different scoreboard, a different set of objections.
• Do not split by seniority alone: a manager and a director with the same scoreboard are one persona with two levels of detail.
• Do not split by industry unless the buying criteria differ: otherwise you have one persona with an industry field.
• Keep the set small enough to own: every persona needs a named owner and a review date, so the right number is the number your team will actually keep current.

Published advice varies. LinkedIn's template guidance says to create multiple personas if your product or service caters to different types of buyers. Buyer Persona Institute's rule of thumb is one buyer persona for each distinct product or service where you need buying insights. Both start from the decision, not from the org chart.

Primary, secondary and negative personas

A primary persona leads the decision you want to win, and gets the deepest research. Secondary personas are the other committee roles: they get shorter documents focused on criteria and objections. Both labels are this page's working terms, not a standard.

A negative persona describes the buyer who wastes the most time: the one who books demos, asks detailed questions and never becomes a customer, or becomes a customer and churns in the first year.

Write it with the same discipline as the others. The role, the situation, the words they use, and the specific reason the deal does not close: no budget line of their own, a requirement you cannot meet, or a project that was never funded.

Named clearly, a negative persona gives your team permission to end a call early.

Mapping buyer personas to the buyer journey

A persona answers who. The buyer journey answers when. Together they decide what information a person needs at each stage, and which roles are even in the room at that point. The map below is this page's working model; check it against your own deals.

Two things follow from this map. Early-stage content should speak to the champion in the buyer's own words, because nobody else is reading yet. Late-stage material exists for roles the champion has to convince, and in this page's view it is the part marketing teams tend to underbuild.

The journey also tells you where each persona joins the process, which belongs in your B2B sales process. A blocker who appears at validation is manageable. The same blocker discovered after the contract goes to legal can cost a quarter.

Using B2B buyer personas in messaging and sales outreach

Buyer personas earn their keep in the first two sentences of an email or a call. Every row below comes from a field in the template, which is the test of whether the research was worth doing.

Different roles in one account should get different messages on the same deal. Coordinating those messages across marketing and sales, account by account, is what an ABM strategy does; the persona supplies the words for each role.

A quick test before any send: point to the persona line each sentence came from. A sentence that comes from nowhere is your opinion of the buyer, and the buyer can tell.

Turning a persona into a prospect list and an ad audience

A persona becomes a list when a few of its fields are turned into search filters. In LinkedIn Sales Navigator, LinkedIn Help says you can define a persona by function, seniority level, current job title and geography, with a persona name of up to 35 characters.

The same help pages set the limits. You can have up to five personas at a time, two of which, Director+ and CXO, are there by default. The Personas filter applies only to lead searches, and personas do not support keyword search, so non-standardized titles cannot be used in one.

That is a much narrower thing than the persona document. Function, seniority and title find candidates; the rest of the persona tells you whether to write to them and what to say. Keep both, and do not let the filter fields quietly become the whole persona.

LinkedIn's Campaign Manager uses related facets for ads. Its help page defines Job Function as common tasks or activities undertaken within a job position, and Job Seniority as the rank or level of influence of a member's current role, both mapped from job titles using LinkedIn's own taxonomy.

So the persona's titles field matters twice: once for search and once for the function and seniority it maps to. Audience size, required facets and list uploads belong to the target audience, which the B2B target audience entry linked above covers in detail.

The company filters come from the ICP, so build the account list first and apply persona filters inside it. That order is how to make a prospect list without a spreadsheet full of the right titles at the wrong companies.

Storing personas in the CRM: persona vs buying role

A persona that lives only in a slide deck cannot drive a report or a workflow. CRM tools give it a field. In HubSpot, the Knowledge Base describes a Persona contact property that helps you target certain groups and categorize your contacts.

You create personas inside that property, from Settings, then Properties, then the Persona property, adding a name, goals and demographics for each. Once they exist, HubSpot says you can filter contacts by Persona in saved views or segments, and use the property in forms or reports.

One detail matters for forms: when the Persona property is used as a form field, HubSpot displays each persona's description rather than its name. Write descriptions a visitor can recognize themselves in, or leave the field off public forms.

Persona and buying role are different fields, and keeping them apart is useful. The persona says what kind of buyer this contact is. HubSpot's Buying role property identifies the role a contact plays during the sales process, and a contact can hold more than one role or share one with another contact.

A procurement persona can be the Decision Maker on a small renewal and a Blocker on a new purchase. Storing both lets lead nurturing follow the persona while the deal team follows the role.

How marketing teams use B2B buyer personas

Sales uses buyer personas one conversation at a time. The marketing team uses the same research to decide what content to create, which audience to buy, and what a page has to say before a buyer will fill in a form.

• Content marketing: each persona's triggers and objections become article topics, because those are the questions a buyer searches before talking to any vendor.
• Ad targeting and copy: role and company filters set who sees the ad, and the "measured on" line sets the promise in it.
• Website pages: in this page's view, a page per customer problem, in the buyer's words, serves a persona better than a page per product feature in yours.
• Sales enablement: one objection sheet per persona, with the verbatim objection and what actually resolved it.
• Product feedback: barriers that keep appearing across interviews are a product roadmap input, not only a messaging problem.
• Lead scoring: persona fit becomes a scoring field alongside company fit and behavior data.
• Customer marketing: the same personas describe existing customers at renewal, where the economic buyer reappears.

The habit worth building is simple. When a marketer or a rep proposes a campaign, a page or a sequence, ask which persona it is for and which line of that persona it uses. Anything that cannot answer is guesswork with a budget.

A quality check for your buyer personas

These pass marks were written for this page. They are a working standard, not an industry benchmark.

Keeping B2B buyer personas current

Buyer personas go stale quietly. Titles change, products change, and a trigger that mattered two years ago stops appearing in customer calls. Nothing breaks, so nobody notices until the marketing underperforms.

LinkedIn's template guidance says to regularly update personas with new insights and as your product or services evolve. Put a review date on the document and attach the review to something that already happens, such as a quarterly pipeline review or the meeting where you revisit the ICP.

Three signals mean a persona needs work now. New words appear in calls that are not on your language list. An objection you have never logged starts repeating. Or a role you do not have a persona for keeps joining deals late.

If the persona is also saved as filters in a prospecting tool, update those too. LinkedIn Help notes that editing a Sales Navigator persona does not update a saved search that already uses it; the saved search keeps the original persona filters.

Mistakes that make B2B buyer personas useless

• Inventing buyer personas in a workshop, then treating the output as research because someone wrote it down.
• Filling in age, hobbies and a stock photo, and leaving triggers, criteria and objections empty.
• Confusing the persona with the ideal customer profile, so company fit and role fit get scored as one thing.
• Building a persona for the user and never for the person who signs, then losing deals at the budget stage.
• Creating one persona per job title, which produces a pile of documents, no decisions and no owner.
• Copying occupation data or job posts into the persona and never replacing the draft lines with what buyers said.
• Summarizing away the quotes, which removes the only part that survives an internal argument.
• Never updating the document, so it describes customers and a market that have both moved on.
• Using the persona to write flattery instead of relevance. A message that names their role but not their problem still reads as a mail merge.

In a sequence

The template below turns persona fields into a first email: the trigger as the reason for writing, the metric as the outcome, and one question that a person in that role can answer in a sentence.

Subject: {{buyerPhrase}} after {{triggerEvent}}

Hi {{firstName}},

When {{triggerEvent}} happens, {{roleLabel}} teams I talk to often get pulled into {{buyerPhrase}}, and it lands on a number you report: {{metricOne}}.

The part people tell me is hardest is {{weeklyFire}}. We handle that piece for teams your size.

Worth a short conversation, or is someone else looking at {{metricOne}} this quarter?

{{senderName}}

Frequently asked questions