Buyer persona

How a buyer persona works

A buyer persona compresses research about real buyers into a profile a team can act on. TechTarget calls it a composite representation of a specific type of customer in a market segment 1. The original B2B definition is strict about the research. Zambito describes personas as research-based archetypal models of who buyers are, what they are trying to accomplish, what goals drive them, how they think, how they buy and why they decide 2. He adds that a buyer persona cannot be defined unless it is research-based 2.

The research usually mixes several inputs. TechTarget lists existing data from CRM systems and website analytics, interviews and surveys, competitor analysis and social media tools 1. Interviews matter most for understanding why buyers decide. CRM fields record what happened, and only a conversation shows how the decision was made.

A finished B2B persona tends to cover the same blocks.

• The role and the job titles that hold it.
• Responsibilities and how the person is measured.
• Goals and current initiatives.
• Problems, fears and objections.
• Decision criteria and the sources the person trusts.
• The person's place in the buying committee, from daily user to final signer.

Personas sit downstream of the ideal customer profile. The ICP picks the companies. The persona picks the people inside them and shapes what each one hears. One account often holds several personas, and Zambito notes that buying teams include influencer personas as well as buyer personas 2. Each needs a different message.

Personas also go stale. TechTarget advises revising them continuously as markets and buyers change 1. A persona last updated before a market shift will steer copy toward problems buyers no longer have.

Buyer persona vs job title

Teams often shrink a persona to a list of job titles. That helps targeting and hurts messaging. A title tells a search tool who to return. It says nothing about the problem keeping that person busy this quarter.

Titles also drift across companies. A head of revenue operations at one company does the job a sales operations manager does at another, so a persona should list several titles for the same role. Search filters approximate the rest with seniority level and job function. RichAPI's people_search takes job_title as an array, so one request can carry every title variant for a persona 4. Pair it with industry, location, employee_size_start and employee_size_end to keep the results inside the ICP 4.

The opposite failure is the fictional persona. A team names a persona, gives it a stock photo and a hobby, and never talks to a buyer. Zambito argues that personas have nothing to do with profiling and everything to do with buying behavior 2. Critics of personas in design argue that personas can become reductive or stereotyped and leave a team with false confidence about its users 3.

A working persona keeps two layers. The targeting layer holds titles, seniority, function and company filters, and it feeds people search. The messaging layer holds goals, triggers and objections, and it feeds copy, sequences and sales talk tracks. Both layers describe the same person, but they change at different speeds. Titles change when the market renames a job. Objections change when a competitor or a budget cycle moves.

Example of a B2B buyer persona

A data tool for revenue teams writes this persona card after a round of buyer interviews.

Persona: The RevOps owner
Titles: Head of Revenue Operations, RevOps Manager, Sales Operations Manager
Company: B2B software, 51 to 200 employees, Germany
Goal: Clean CRM data and a list process that does not depend on one person
Trigger: A sequence with a high bounce rate or a failed data audit
Decision criteria: Cost per usable record, API access, clear billing
Objection: Another tool to maintain

The targeting lines become a search request. This body follows the documented people_search shape 4.

{
  "job_title": ["Head of Revenue Operations", "RevOps Manager", "Sales Operations Manager"],
  "industry": ["Computer Software"],
  "location": ["Germany"],
  "employee_size_start": 51,
  "employee_size_end": 200,
  "limit": 25,
  "page": 0
}

A page with limit 25 returns up to 25 profiles and bills 0.1 credits per result, so a full page costs 2.5 credits 4. The response field totalElements reports total matches for the filter set 4. That shows how many people fit the persona inside the index before the team pays for more pages.

Coverage is the next check. A small count usually means the title list is too narrow or the role goes by names the team did not expect. Pull one page, read the headline field on each profile in the content array, and add the real titles people use to the job_title array 4. A headline such as Revenue Systems Lead points to a variant the card missed. Repeat until a fresh page shows few new variants, then freeze the list for the campaign.

The rest of the card goes into the message. The goal and the trigger set the first line of the email. The objection gets an answer before the prospect raises it. The decision criteria decide which proof point goes in the follow-up. A buyer who measures cost per usable record gets a worked cost example, not a feature list.

Buyer persona vs buying committee

A persona is a reusable model of one role. A buying committee is the actual group of people involved in one specific purchase. Zambito notes that buying teams can include several archetypes, influencer personas as well as buyer personas 2.