How to build SAAS marketing buyer personas with evidence

What to take away

A SAAS marketing buyer persona is a written profile of one buying role, built from evidence about the job they do, the triggers that start a search and the objections that stall a deal.

Personas work when each one names a role, a trigger and an objection, not a fictional character with a hobby.
Use three inputsyour own win and loss notes, public labour market data, and interviews with people who hold the role.
Consent rules apply before you collect any behavioural data on a B2B website, so sort tracking before you build the profile.
Keep each persona under one page and review it every six months.

Start with the role, not the person

Most weak personas fail at the first step. They describe a personality type rather than a job. A finance director at a 40-person software firm buys differently from a finance director at a 4,000-person group, even if both enjoy the same podcasts.

Role fields to write first

Job title
Company size band
Reporting line
Budget they can approve alone

Write the role first. Job title, company size band, reporting line, and the budget they can approve alone. That last point decides whether your persona is a buyer or an influencer, and it changes the whole page.

If the role sits inside a wider audience map, build that map before you write individual personas. Our guide to audience research for England sets out the order of work, including how to segment by sector and company size without over-splitting.

Gather evidence from three sources

First, your own pipeline. Pull closed-won and closed-lost notes for the last four quarters. Look for the sentence where the deal changed direction. That sentence is usually the objection you need to name.

Three evidence sources

Pull closed-won and closed-lost notes for four quarters
Find the sentence where the deal changed direction
Check Bank of England rate decisions and commentary
Run six to ten calls with people in the role
Ask what they searched, who agreed, what they feared

Second, public data. The Bank of England publishes rate decisions and economic commentary that shape how finance teams treat new software spend, which is useful context when you write the budget section of a persona.

Third, conversations. Six to ten calls with people who hold the role will beat any amount of desk research. Ask what they searched for, who else had to agree, and what they feared would go wrong after signing.

Sort consent before you track

The Information Commissioner's Office sets the rules for cookies and similar technologies on UK websites. Its guidance on storage and access technologies explains what counts as consent and when it is needed. Read it before you add any analytics tag to a persona-driven landing page.

Once tracking is compliant, check that pageview measurement is configured correctly, because pageviews remain the basic unit for judging which persona pages attract attention. Google's documentation on measuring pageviews covers how views are recorded in the current analytics platform.

Build the before and after page

The table below shows the same persona at two stages. The left column is what most teams write first. The right column is what survives contact with a sales call.

Before

Name: Marketing Mike, 38, likes cycling
Trigger: Wants more leads
Objection: Price
Proof needed: Case study
Budget: Unknown

After

Name: Head of Demand Generation, 200 to 500 staff
Trigger: Board asked for pipeline attribution by quarter end
Objection: Cannot justify a 12-month term before the next funding round
Proof needed: Reference call with a peer at a similar headcount
Budget: Approves up to £15,000 a year, above that needs finance sign-off

Rebuild one persona this way before you touch the others. The change in the objection row alone usually redirects the whole content plan.

Test personas against competitor research

A persona is only useful if it explains why a buyer picks someone else. Map each persona against the two or three vendors they shortlist, and note where your product loses on a specific criterion.

This is where persona work overlaps with market analysis, and our piece on competitor research in England shows how to record rival positioning in a form you can reuse in sales conversations.

Keep the output short. One page per role, one paragraph per section, reviewed every six months or after any major pricing change.

Common questions

How many personas should a SAAS company have?

Most B2B software firms need two to four. Start with the role that signs the contract and the role that uses the product daily. Add more only when a new role changes the sales conversation.

Can I build personas without customer interviews?

You can draft them from pipeline notes and public data, but the draft will miss the language buyers actually use. Six short calls close most of that gap.

How often should personas be updated?

Review each one every six months, and sooner if you change pricing, packaging or the sectors you target. A stale persona quietly misdirects budget.

Do I need consent to track persona pages?

Yes, where cookies or similar technologies are used. The ICO guidance linked above explains the consent standard that applies to UK visitors.