Audience research
Part of Before you brief a prospecting software audience research project
Prospecting software buyer personas need evidence, not guesswork
How to build defensible prospecting software buyer personas for England using ONS population data, LinkedIn dynamic ads and ICO accountability duties.
What to take away
- A usable persona names the buyer's sector, headcount band, territory and the trigger that starts a search, not just a job title.
- England-wide personas need checking against regional population and business density before budget is committed.
- Personalised targeting on LinkedIn can only follow a persona you have documented and can defend under UK GDPR.
Personas start with a decision
You are choosing where to point a fixed prospecting budget next quarter. That choice needs a persona specific enough to exclude most of the market.
A job title is not a persona. A persona says who signs, who blocks and what event makes them look. For example, a ten-person agency in Manchester replacing a spreadsheet after losing a pitch is a different buyer from a 200-person software firm adding a second sourcing tool.
Budget authority and existing contracts narrow the list faster than firmographics alone.
Anchor personas in regional data
England is not one market. Population estimates from the Office for National Statistics give you a defensible baseline for how many potential buyers sit in each region.
Use that baseline to sanity-check any persona that claims a dense cluster of operations managers in one county. If your persona cannot be placed on a map with a rough count attached, it is a mood board rather than a target.
Who actually feels the pain
Prospecting software is bought by people whose week is damaged by manual list building. That is usually a sales manager or a founder, not a marketing director.
The economic buyer cares about pipeline coverage. The daily user cares about how long a list takes to build. Champions care about whether the tool fits the CRM they already pay for.
Document each role separately. A persona that merges all three produces messaging nobody recognises as their own problem.
Our guide to prospecting software audience research sets out how these roles sit inside a full research programme.
Personalisation needs a paper trail
LinkedIn dynamic ads let you vary creative by job title, industry and seniority, which is useful once personas are written down.
Personalisation at that level is data-driven marketing, and the Information Commissioner's Office expects documented decisions about it. The ICO guide to accountability and governance covers the records, risk assessments and governance duties that apply.
In practice, that means writing down why a persona exists, what data supports it and how long you keep it. A persona file with no source notes is a compliance liability as well as a weak target.
A worked example
A Leeds-based seller of prospecting software sets a quarterly outbound budget of £9,000 and splits it across two personas.
Persona A is a sales manager at a 20 to 50 person professional services firm in West Yorkshire. Persona B is a revenue operations lead at a 200 to 500 person software company in Greater London.
The team allocates £3,000 to Persona A and £6,000 to Persona B, where deal values are higher but competition is heavier. After four weeks Persona A returns 40 booked meetings against Persona B's 18, so the next quarter shifts £2,000 towards Persona A. Every figure here is illustrative.
Personas exist to move money, not to decorate a slide.
Interviews beat assumptions
Secondary data tells you the size of a segment, not why someone switches tools.
Run five to eight short interviews per persona before committing serious spend. Ask what they used before, what broke and who had to approve the change. Our notes on prospecting software customer interviews cover how to structure those conversations without leading the witness.
Record the answers against the persona file. If three of eight interviewees describe a trigger you had not listed, the persona is wrong and the budget should wait.
Common questions
How many personas does a prospecting software team need?
Two or three is usually enough for a small sales team. More than that and the outbound list becomes too thin to test properly.
Should personas cover Scotland, Wales and Northern Ireland?
Only if you sell there. Buying behaviour and population mix differ, so build separate notes rather than stretching an England persona across the UK.
What is the minimum evidence for a persona?
A named role, a headcount band, a region, a trigger event and at least three interview or data sources. Anything less is a hypothesis.
