Audience research
Part of Run B2B demand generation audience research: a practical guide
How to build B2B buyer personas that reflect real buying decisions
Guide to building B2B buyer personas from real deals, with five steps, lawful data checks under UK GDPR and practical ways to use them in campaigns.
What to take away
- A persona built from three sales call notes and a hunch will be ignored by the sales team within a fortnight.
- Personas work when they name the buyer, the problem they own, and the evidence behind each claim.
- You need a lawful basis before you store named contact data, and the ICO publishes a step-by-step guide to direct marketing for your small business.
- Five to seven personas is usually enough for a UK mid-market campaign; more fragments your message.
- Review them every two quarters, because job titles and buying committees move.
A sales director at a Manchester software firm keeps a persona deck that nobody opens. The deck describes a fictional marketing manager called Emma, with hobbies and a commute. It says nothing about who signs the contract or what triggers a purchase. That is the failure mode this article fixes.
Personas start with a buying decision
A useful persona describes a decision, not a person. Start with a purchase your business actually won or lost in the last year. Write down who asked the questions, who blocked progress, and who signed.
Four buying roles in the room
Technical evaluator
- What they check
- Fit
- Own persona
- Yes
- If grouped
- Sales stops reading
Finance contact
- What they check
- Budget line
- Own persona
- Yes
- If grouped
- Sales stops reading
Operational lead
- What they check
- Daily problem
- Own persona
- Yes
- If grouped
- Sales stops reading
Director or board
- What they check
- Spend approval
- Own persona
- Yes
- If grouped
- Sales stops reading
Each role needs its own persona. Grouping them into one document is why sales teams stop reading them. The wider research process is set out in our audience research guide for England, which covers sampling and question design before you write anything down.
Collect evidence before writing
A persona is a claim about a group of buyers, so it needs evidence behind it. Three sources are realistic for a small or mid-sized team.
Three evidence sources
- Pull closed-won and closed-lost CRM records
- Interview people who took the calls
- Run a short survey of existing customers
- Keep the survey to ten questions
- Ask about the trigger event, not preferences
If you are choosing a survey platform, our notes on demand generation survey tools in England compare what each type handles well. Keep the survey to ten questions and ask about the trigger event, not about preferences.
Keep the data lawful
You are handling personal data the moment a persona includes a named contact or a job title tied to a company. Under UK GDPR you need a lawful basis, and legitimate interests is the usual one for B2B marketing. Record that assessment.
A data management platform helps you keep consent flags, source and suppression lists in one place, which is what HubSpot's data management software is built for. If your records sit in several spreadsheets, fix that before you build personas on top of them.
Build the persona in five steps
- Pick the deal type. Choose one product and one average contract value band, for example deals between £10,000 and £40,000 a year.
- List the roles. Name every person who influenced the last ten deals in that band.
- Interview six to ten people. Ask what triggered the search, what they compared, and what nearly stopped the purchase.
- Write the evidence line. Every claim in the persona gets a source, such as "seven of ten interviewees, Q2 2026".
- Test it with sales. Ask two account executives whether they recognise the buyer described. If not, rewrite.
A persona that survives step five is one you can hand to a new starter on their first morning.
Wire personas into campaigns
Personas only earn their keep when they change something. Use them to pick the subject line, the proof point and the call to action for each sequence.
A finance persona wants payback period and total cost. An operational lead wants implementation effort and who owns the rollout. Same product, different email.
This is where marketing automation earns its place, because the platform can hold separate sequences and route replies to the right owner. Salesforce's B2B marketing automation platform is one example of the category, and the same routing logic applies whichever tool you run.
Common questions
How many buyer personas should a B2B team have?
Five to seven covers most English mid-market campaigns. Fewer than three usually means you have merged distinct buying roles. More than ten means the team cannot remember them, so the deck goes unread.
Do personas need named individuals?
No. Named examples help a sales team picture the buyer, but they also create data protection duties. You can describe the role, the pressures and the objections without naming anyone, and stay outside UK GDPR's personal data rules.
How often should personas be reviewed?
Every two quarters is a workable rhythm. Job titles change, buying committees shrink, and budget owners move. A short review of the trigger events and objections is enough unless your product has changed.
What if sales disagrees with the persona?
Treat it as a research gap, not an argument. Ask which recent deal contradicts it, then add that deal to your interview list. The persona is only as good as the evidence you can point to.
