Published: Last updated:
Our guides
Create customer personas from real buyers – step by step, with interview questions and a template

What do you gain from doing the job properly? The difference shows straight away in your content: copy that answers the questions potential customers actually ask, in their own words. Below we take you through the whole job in order: the interview questions, the data sources, the template fields, how many personas is a sensible number, and how to turn the answers into SEO and AEO content.
What is a customer persona – and what is it not?
A customer persona (also called a buyer persona, or simply a persona) is a documented description of a typical buyer: what made them start looking for a solution, what they want to achieve and what decides their choice of supplier. It is based on interviews and data, not on an invented name with a stock photo. We have explained how personas relate to target groups and customer segments in target group, customer group and personas – what is the difference, so we will leave the definition there.
Just as important is what a persona is not: a demographic profile. "Anna, 42, marketing manager, lives in Uppsala" says nothing about why Anna buys. The rest of this guide is about the things that do.
How to build a persona from real customers – the interview questions
One of the most established interview methods comes from Adele Revella and the Buyer Persona Institute. Her framework, the "5 Rings of Buying Insight", structures the interview around five areas: the trigger moment, the success criteria, perceived barriers, the buyer's journey and the decision criteria. The basic principle is to interview people who have recently made a real purchasing decision: customers who chose you and, ideally, someone who decided against you. After-the-fact rationalisations are weaker data than fresh memories.
The interview questions – copy the list
The questions below cover the five areas. Ask them as open questions and follow up with "tell me more"; the best answers often come in the asides.
- Trigger: What happened that made you start looking for a solution at that particular time?
- Trigger: How did you handle the problem before – and why was that no longer enough?
- Success: What needs to have happened in six months for you to see the purchase as a success?
- Success: How will you judge whether it was a good investment?
- Barriers: What made you hesitate during the process?
- Barriers: Was there anything you worried about with this type of solution?
- Buyer's journey: Who was involved in the decision – and who had the final say?
- Buyer's journey: Where did you look for information? Search engines, colleagues, AI tools, industry networks?
- Decision: Which suppliers did you compare – and how did you make the comparison?
- Decision: What decided it in the end?
Where do you find data when you cannot interview?
Interviews are the primary source, but you can supplement them, and while you wait for interviews, these sources beat guesswork:
- The CRM – won and lost deals, the sales team's notes on objections.
- Sales calls – recorded demos and meetings, with the exact phrases potential customers use.
- Support and customer service – recurring questions and friction after the purchase.
- Analytics – which pages buyers visit before they get in touch.
- Search data – keyword research shows which questions the market asks and with what search intent.
The persona is also one of the cornerstones of a broader SEO strategy: research and plan go together.
How many interviews are enough?
Industry practice points to eight to ten interviews per persona. The Buyer Persona Institute, whose framework we use above, has itself tested whether an eleventh interview added new information, and it did not. If the target group is mixed, you may need more; if it is very homogeneous, fewer are often enough. It is not an exact science: the figure is based on the observation that answers tend to start repeating at around that point. A practical stopping rule: when you hear the same trigger and the same objections for the third time, you have probably captured the core. Five completed interviews beat ten scheduled ones.
How many personas does your company need?
At an early stage, it is often best to have one or two high-quality personas. Growing companies usually end up with three to five. Having more personas than the team actively uses is paperwork, not insight.
A better test than counting segments: only add a new persona if that buyer group has its own triggers, its own objections or its own decision criteria. A different title or industry is not enough. Two roles that buy for the same reasons, hesitate for the same reasons and decide on the same grounds are one persona, not two. It is better to start with one persona the whole team knows by heart and add the next when the data calls for it.
Customer persona template: the fields that actually drive decisions
A good persona template is short enough to be used and specific enough to drive decisions. Every field below is there for a reason – and demographics are deliberately played down. Goals, objections and decision criteria steer copy far more than age and location do.
- Name & role – makes the persona easy to refer to in day-to-day work: "would Malin understand this headline?"
- Company context (size/industry) – decides tone of voice, price expectations and how complex the buying process is.
- Trigger moment – the event that starts the buyer's journey; decides which content should reach the person early on.
- Goals/success criteria – what the purchase should lead to; decides how you phrase value and results.
- Barriers & objections – what makes deals stall; drives objection handling in both copy and sales calls.
- Decision criteria – what actually decides the choice; drives comparison pages, quotes and pricing pages.
- Information sources & AI questions – where the person looks and what they ask AI tools; drives channel choice and AEO work.
- Quote from a real customer – a verbatim quote that keeps the persona honest and stops it sliding back towards assumptions.
Build your persona
Fill in the fields right here – from interview answers and data, not guesses. Nothing is saved or sent; copy or download the result when you are done.
Preview the draft (0 of 8 fields filled in)
PERSONA — draft NAME & ROLE — COMPANY CONTEXT — TRIGGER MOMENT — GOALS & SUCCESS CRITERIA — OBSTACLES & OBJECTIONS — DECISION CRITERIA — INFORMATION SOURCES & AI QUESTIONS — QUOTE FROM A REAL CUSTOMER — Template: SEOS Design — seosdesign.se/en/blog/buyer-persona
The template follows the interview method in the article above. Everything you write stays in your browser.
More free toolsFill in the template above and export the result for the team. Leave a field empty rather than guess: empty fields remind you which research is still missing.
Example: what a completed persona can look like
A short example of how the fields fit together (fictional, but based on a common B2B pattern): Malin, marketing manager at a SaaS company with 40 employees. Trigger: the website is stopping the company from winning larger customers. Success criterion: more qualified leads within six months. Barrier: a bad experience with a previous agency that delivered something that looked good but could not be measured. Decision criteria: proven results and a partner who understands the business, not just the design. AI question: "which web agencies in Stockholm have experience of B2B SaaS?" Notice how every field points straight to a content or sales decision.
Are personas outdated? The critique from jobs-to-be-done
The critique is fair, but it targets the wrong kind of persona. The jobs-to-be-done school (JTBD) argues that you should study which "job" the customer hires the product to do, not who the customer is. Nielsen Norman Group describes the two as complementary rather than competing: a thoroughly researched persona already has the depth JTBD asks for, since triggers, goals and barriers are the customer's "job". What the JTBD critique rightly dismisses is the shallow demographic persona. The problem is the execution, not the concept.
One more honest note: persona statistics in the industry are often recycled third- or fourth-hand with no traceable primary source. The only traceable study we have found is a frequently cited, but ten-year-old, benchmark study from Cintell (2016), in which 71 per cent of the companies that beat their revenue targets had documented personas, compared with 26 per cent of those that missed them (Tony Zambito). That is correlation, not causation, and ten years is a long time in marketing. Treat the figure as an indication, not proof.
From persona to content: how it is used in SEO and AEO
This is where the interview work pays off. The answers are not just research; they are raw material for content:
- The trigger answers become topics for early content – guides and blog posts that reach the buyer when the problem first arises, before they start comparing suppliers.
- The objections become FAQ content and objection handling on service pages – answered before the visitor has had time to think of them.
- The decision criteria become comparison pages and content that helps the buyer choose on the right grounds.
- The information sources and AI questions decide where the content needs to be – and exactly what it has to answer.
Our guide to writing SEO-optimised content covers how to turn that raw material into publishable copy.
The AEO link is the one most often missed. The questions your customers asked in the interview are the same questions the next buyer asks ChatGPT, Gemini or Perplexity before contacting you. The "Information sources & AI questions" field in the template is therefore a ready-made brief for AEO content: phrase every question as an H2 or an FAQ entry, and write the answer as a self-contained, citable paragraph. If the information is missing, AI tends to answer "no" rather than "I don't know", and the buyer moves on to a competitor whose answers are documented. First-hand insight from real customer conversations is also exactly the kind of experience that E-E-A-T rewards. Covering the persona's questions systematically builds topical authority, which shows in both classic search results and AI Overviews. We have written more about how the AEO shift affects the whole organic channel in our guide to organic marketing.
Common mistakes when creating personas
Most failed personas fall down on the same five points:
- Gut-feeling personas – built in a workshop without a single customer interview. The result simply mirrors the team's assumptions.
- Never updated – the market changes. A persona more than a year or two old should be checked against new customer conversations.
- Too many – six personas nobody uses are worse than two that steer every campaign.
- Demographic fixation – age and location fill the document while the reasons to buy are missing.
- The PowerPoint deliverable – presented once and never opened again. A persona should live where the work happens: in the brief, in the CRM, in content planning.
Avoid those five and you are already on firmer ground than most competitors. Want help turning your personas into search strategy and content? Get in touch and we will look at it together.
Common questions about customer personas
How many personas does a company need?
Most companies need fewer personas than they think. At an early stage, one is enough – your most important buyer. Growing companies usually end up with three to five. Create a new persona only when a buyer group has its own triggers, objections and decision criteria, not just a different title or industry. Personas that nobody on the team uses day to day are paperwork, not insight.
Do small businesses need personas?
Yes, but a lighter version. A small business rarely needs more than one documented persona, and it can be based on a handful of customer conversations plus patterns from the CRM and support. The value is the same as for large companies: everyone who writes, sells and builds works from the same picture of the customer. Cut back on detail rather than research: three completed interviews are a better foundation than ten assumptions.
Are personas outdated?
No, but shallow demographic personas are. The criticism from the jobs-to-be-done camp applies to personas that describe age and interests instead of reasons to buy. Nielsen Norman Group sees personas and JTBD as complementary: a persona built on proper research already contains the customer's "job", goals and barriers. Base personas on interviews about real purchasing decisions and the conflict disappears.
What should a customer persona include?
The fields that drive decisions: role and company context, the trigger moment that started the buyer's journey, goals and success criteria, barriers and objections, decision criteria, information sources (including what the person asks AI tools) and a verbatim quote from a real customer. Demographics matter least: age and location rarely affect how you should shape copy, offers or objection handling.
How many interviews do you need for a persona?
Around eight to ten interviews per persona is common industry practice, according to Adele Revella of the Buyer Persona Institute among others. The figure is not an exact science; it is based on the observation that answers tend to start repeating at about that point. A practical stopping rule: when you hear the same trigger and the same objections for the third time, you have probably captured the core. Prioritise recent purchasing decisions, and ideally also interview someone who chose a competitor.
What is the difference between a buyer persona and a user persona?
A buyer persona describes the person who makes the purchasing decision (triggers, objections and decision criteria) and is used by marketing and sales. A user persona describes the person who uses the product day to day (tasks, context and friction) and is used in UX and product design. In B2B they are often different people: the finance director buys the system, the finance assistant uses it. Many companies need both, but should keep them in separate documents.



