Audience research
Part of Researching B2B buyers with account frames, interviews and surveys that hold up
A B2B buyer persona is a hypothesis with receipts, not a stereotype
Build evidence-based B2B buyer personas for England around buying work, triggers and proof needs, without turning platform profiles into stereotypes.
B2B social selling buyer personas should describe recurring work in a buying decision, supported by research. They should not be fictional biographies with a stock photograph, favourite coffee and guessed temperament. In England-focused work, each persona also needs a clear relationship to the English account or operating site.
What to take away
- A persona is a hypothesis with receipts, not a fictional biography.
- Model the buying group by involvement, not by seniority alone.
- Make England an operational field, not a profile filter.
- Keep only fields that change action and have evidence.
- Use personas as a decision test and update after planned research.
A persona is a hypothesis with receipts
Begin with an evidence card rather than a name. Record the buying task, trigger, constraints, information sought, people involved and point at which social content or contact appeared. Attach source identifiers from interviews, opportunity records or observed behaviour. If a field has no support, label it as an assumption.
Evidence card fields
- Buying task and trigger
- Constraints and information sought
- People involved
- Social content or contact point
- Source identifiers
- Label unsupported fields as assumptions
The Government Digital Service's guidance on learning about users and their needs says needs should come from research rather than assumptions and describes personas as groups with similar behaviour and needs. The context is public-service design, so it does not validate a sales model. Its useful boundary is that a persona must remain traceable to evidence.
Model the buying group, not one hero
For a particular offer, examine four kinds of involvement: experiencing the problem, specifying a response, authorising resources and checking implementation or risk. These are analytical functions, not universal job titles. One managing director may cover all four in a small company; several departments may divide them in a larger account.
Do not assign authority from seniority alone. Ask who initiated the last comparable purchase, whose evidence changed the decision, who could stop it and who lived with the result. Preserve disagreements. A practitioner can be highly influential without signing the contract, while a budget holder may join late.
LinkedIn's first-party Personas in Sales Navigator page describes filters for function, seniority, job title and geography. This can translate a researched role into a search configuration. It cannot verify decision rights, motivation or need. A platform persona is a discovery shortcut, not the research record itself.
Make England an operational field
Add the relevant geographic relationship to each card. The person may work at an English site, support several English regions, or sit elsewhere while approving work delivered here. Do not replace these distinctions with an England profile filter.
Companies House lets researchers check registered names, status, officers, filing history and stated business activity. That record can verify the legal entity behind an account. It does not show where every employee works or who controls a particular purchase. Record the location evidence separately from the role inference.
Keep only fields that change action
A useful card can fit on one page:
- buying task and recent trigger;
- evidence the role seeks before a conversation;
- colleagues who contribute, approve or block;
- terms the participant actually uses for the problem;
- observed discovery or contact route;
- England rule, exclusions and contradictory cases;
- source dates, confidence and next research question.
Age, hobbies, family status and personality labels should not be defaults. The ICO says under its data-minimisation principle that personal information must have a rational link to the stated purpose and be limited to what is needed. A public profile does not make every visible attribute relevant to sales research.
Use personas as a decision test
Put each proposed post, proof asset or contact route against the card. Which documented question does it answer? At what buying stage? What would make the role reject it? If the team cannot point to evidence, the content choice remains an assumption.
Update cards after a planned research round, not after every memorable comment. The GDS analysis method separates observations, findings and actions and recommends involving observers in interpretation. Keep that separation in the persona log. One forceful interview should not erase quieter contrary cases.
Retire a persona when the account frame, offer or buying process changes enough that its evidence no longer fits. The next version should show what changed and why. This turns the document into a reviewable model of purchasing work rather than a permanent story about a type of person.
Before you act
- Start with an evidence card, not a name.
- Label unsupported fields as assumptions.
- Record location evidence separately from role inference.
- Exclude age, hobbies and personality labels by default.
- Test each content choice against the card.
- Retire personas when the account frame changes.
Common questions
What should a persona card contain instead of a name and photo?
A persona card should record the buying task, trigger, constraints, information sought, people involved and the point at which social content or contact appeared. It should attach source identifiers from interviews, opportunity records or observed behaviour. If a field has no support, label it as an assumption.
How can Companies House data be used in persona research?
Companies House lets researchers check registered names, status, officers, filing history and stated business activity. That record can verify the legal entity behind an account. It does not show where every employee works or who controls a particular purchase. Record location evidence separately from the role inference.
Why should age and hobbies not be default persona fields?
The ICO says under its data-minimisation principle that personal information must have a rational link to the stated purpose and be limited to what is needed. A public profile does not make every visible attribute relevant to sales research. Age, hobbies, family status and personality labels should not be defaults.
