Start with a buying decision, not a fictional profile
A useful B2B buyer persona summarizes what a particular person needs to accomplish, what makes them consider a change, and how they evaluate options.¹² Build it from customer evidence, not a stock character assembled from job-title stereotypes.
Choose one product or buying decision before interviewing anyone. A persona for a small-team purchase may not describe the people involved in a company-wide rollout. Keep company-level fit, often described by an ideal customer profile, separate from the individual roles and evidence you collect.
Choose interviewees who can explain the decision
Talk with people who recently bought, chose another option, or decided to keep their current process. Including different outcomes helps you avoid building a persona that explains only successful customers. With few interviews, treat your notes as early hypotheses, not a representative picture of every buyer.³
Ask about a specific past decision rather than what someone might do in theory.²³
- What was happening when you first considered changing the current approach?
- What did you try before looking for a new solution?
- Who else took part, and what did each person need to know?
- What made an option seem risky or unsuitable?
- What evidence helped you decide, and what remained uncertain?
- What nearly stopped the decision?
Ask what happened next and when. Avoid steering people toward benefits your product already claims to provide.
Keep observations separate from interpretations
For each interview, record a short paraphrase, the decision stage it relates to, and whether it is a direct statement or your interpretation.³ A vivid comment from one person is a useful lead, not proof of a broad pattern. Compare notes across interviews and leave disagreements visible.
A simple evidence sheet can include:
- Interview ID and date
- Outcome: bought, chose another option, or made no change
- Situation or trigger described
- Desired business outcome
- Concern or decision criterion
- Other roles involved and their contributions
- Evidence note
- Direct statement or interpretation
- Number of interviews where the theme appeared
That count describes only the interviews you conducted. It does not estimate how common the theme is among all buyers. Keep outliers and contradictory accounts rather than deleting them to make the summary look consistent.
Use anonymized IDs unless retaining names is necessary and appropriate. Limit access to interview notes and follow your organization’s consent and retention practices.
Turn repeated evidence into a cautious persona
Look for themes across separate interviews, while preserving meaningful differences.¹³ If users and budget owners describe different needs, do not force them into one profile just because they work at the same company.
For example, imagine three interviews about replacing a manual reporting process. Two operations managers describe spending time reconciling inconsistent spreadsheets before weekly reviews; one says the main difficulty is getting approval for a new tool. A cautious summary might say, “Both operations managers in these interviews mentioned spreadsheet reconciliation.” Keep the approval concern as a separate observation. Three interviews do not establish how common either issue is across the market.
A usable persona page can capture:
- Role in the decision, stated narrowly
- Situation that prompts evaluation
- Work the person is trying to get done
- Outcomes they value
- Concerns or criteria they use to assess options
- People they consult or need approval from
- Supporting evidence and contradictory examples
- Open questions to investigate next
If the interviews do not establish a typical title, budget authority, preferred channel, or buying timeline, mark it unknown. A persona summarizes evidence; it does not claim that everyone with a matching title behaves alike.
Turn role evidence into a search hypothesis
Use supported role patterns as a starting point for prospect research, not as hard rules. If interviews repeatedly point to operations managers who own reporting workflows, that gives you a role hypothesis to test. It does not prove every operations manager has the problem or buying authority.
RadarLeads lets you search B2B contacts by job title, seniority, company, location, industry and more. Search is free to preview, and selected leads can be exported as CSV. Create a free account to see whether a role hypothesis returns contacts relevant to your target companies. Coverage varies, and a database match alone does not confirm buying intent or authority.
Record whether the search examples fit the interview-backed role, then use gaps to frame the next research question. Do not broaden to unrelated senior titles simply to produce more matches.
Revisit the persona when evidence changes
Update the summary when new interviews challenge it, the product or buying process changes, or a customer segment behaves differently. Keep dates and supporting notes for important changes so the persona remains a working document rather than an unexamined label.
For a separate workflow on assembling prospect records, see the B2B contact list guide.