How to create a buyer persona that your team will actually use

A buyer persona is a short, research-based profile of a typical customer: who they are, what they are trying to achieve, what gets in their way, what makes them hesitate and where they look for answers. It gives marketing, sales and product one shared picture of the person they are serving. The good ones come from talking to real customers, not from a brainstorm. The marketing persona generator turns your research into a one-page card, and this guide explains how to gather and use it.

What a buyer persona is

Personas came into product design through Alan Cooper, who described them in The Inmates Are Running the Asylum (1999) as a way to design for a specific person rather than a vague average user. Marketing adopted the idea as the buyer persona. A persona is semi-fictional: the name and photo are invented, but the goals, pains and behaviour are drawn from patterns in real customers. Most businesses need two to four, one for each meaningfully different kind of buyer, not a dozen.

Start with research

The difference between a useful persona and a stereotype is evidence. Good sources include:

  • Customer interviews โ€” even six to ten conversations reveal recurring goals and objections. Ask about the last time they bought something like yours, not what they would hypothetically do.
  • Sales and support notes โ€” the questions people ask before buying and the complaints after.
  • Surveys and analytics โ€” useful for checking how common a pattern is once interviews have found it.
  • Lost deals โ€” people who chose not to buy are often the most informative.

Write the sources at the bottom of the persona. The generator has a field for that and reminds you if it is empty, because a persona without sources is easy to dismiss as one person's opinion.

What to include

Keep to fields that change decisions. Demographics such as age range and job title help people picture the persona, but the useful parts are behavioural:

  • Goals โ€” what they are trying to get done.
  • Pain points โ€” what gets in the way today.
  • Objections โ€” why they might not buy, in their words.
  • Channels โ€” where they look for answers and recommendations.
  • Purchase triggers โ€” the events that make them start looking.
  • Role in the decision โ€” do they research, decide, or approve the budget?
  • Key message โ€” the one thing you most need them to understand.

A worked example

Imagine an invented online shop selling hand-dyed yarn. After eight customer interviews and a look through a year of support emails, one persona emerges: Returning Rachel, 35 to 55, who knitted as a teenager and has taken it up again.

  • Goals: finish projects she is proud of; find colours she cannot get in high-street shops.
  • Pains: colours look different on screen; unsure how much yarn a pattern needs.
  • Objections: "What if the dye lots do not match?" "Postage costs more than the yarn."
  • Channels: Instagram, Ravelry pattern pages, knitting podcasts.
  • Triggers: starting a new pattern; a gift to make for a birthday.
  • Key message: real-daylight photos of every colourway, and kits with the exact amount for the pattern.

That persona immediately suggests work: daylight photos on product pages, a yarn-quantity note on each pattern kit, free postage above a threshold. A content calendar can then plan posts around her triggers, and How to write a product description that sells shows how to answer her objections on the product page itself.

Common mistakes and limits

  • Inventing it in a workshop. A persona written from assumptions confirms what the team already believed.
  • Too much irrelevant detail. Favourite films and pet names make a persona vivid but rarely change a decision.
  • Too many personas. If you have eight, you have not decided who you serve.
  • Never updating it. Customers change; revisit personas when sales patterns or feedback shift.

A persona is a summary, not a substitute for talking to customers. When a decision is close, test it with real people, or with an A/B test if you have the traffic. And once the persona is clear, the value proposition generator helps turn their goals and pains into a promise.

Sources and further reading

The claims in this guide rest on these references, which were checked when the guide was last updated. Spotted an error? The contact page says how to report it.

  1. Persona (user experience) โ€” Wikipedia
  2. Personas make users memorable โ€” Nielsen Norman Group
  3. Personas: study guide โ€” Nielsen Norman Group

Try the tool

Frequently asked questions

What is a buyer persona?

A short, research-based profile of a typical customer covering their goals, pain points, objections, channels and buying role.

How many buyer personas do I need?

Most businesses need two to four, one for each meaningfully different type of buyer.

What research do I need for a persona?

Customer interviews are the core, supported by sales and support notes, surveys and analytics.

Who invented personas?

Alan Cooper introduced personas in software design and described them in his 1999 book The Inmates Are Running the Asylum.