Audience research
Part of Plan subscription commerce audience research before you size the market
Before you build subscription commerce buyer personas, check the data
Build subscription commerce buyer personas from the data you already hold, with UK GDPR compliance, a worked pound example and a review cycle.
What to take away
- The common mistake is inventing personas from assumptions instead of building them from data you already hold.
- ICO children's information guidance applies if your subscription service could be used by under-18s, so plan age assurance and consent early.
- Employment contracts for subscription operations staff should be agreed before you hire the team that acts on persona insight.
- A worked example shows how a small English subscription box can segment customers without collecting unnecessary personal data.
Start with data you already hold
Most teams begin with a workshop and a whiteboard. They sketch a name, an age and a job title, then treat that sketch as evidence. The result is a persona that tells you more about the workshop than the market.
Workshop guesses vs observed data
Workshop persona
- Source
- Whiteboard sketch
- Evidence
- Name, age, job
- Cancellations
- Assumed
- Pre-buy questions
- Guessed
- Tells you about
- The workshop
Data-led persona
- Source
- Platform records
- Evidence
- Plan mix, renewals
- Cancellations
- Observed reasons
- Pre-buy questions
- Support data
- Tells you about
- The market
A stronger starting point is the transaction and support data already in your subscription platform: plan mix, renewal rates, cancellation reasons and the questions customers ask before they buy. These are observed behaviours, not guesses.
For a fuller method covering sizing, segmentation and testing, see the subscription commerce audience research guide for England.
What UK GDPR means for persona data
Personas are usually aggregated, but the data feeding them is personal data. Under the UK GDPR you need a lawful basis for processing it, and you must not keep identifiers longer than necessary.
UK GDPR persona data checks
- Lawful basis for processing personal data
- Do not keep identifiers longer than necessary
- Read ICO children's information guidance if under-18s
- Separate persona layer from identity layer
- Store segments and behavioural tags, not names
If your subscription could appeal to under-18s, the ICO's children's information guidance explains how to design age-appropriate services and handle consent. Read it before building personas that include younger users.
Separate the persona layer from the identity layer. Store segments and behavioural tags, not names or email addresses. That keeps the output useful while reducing risk.
Compliance before you hire
Personas often drive operational changes, such as new retention roles or a larger customer service team. Before those roles are filled, check the legislation and regulation guidance for businesses so your contracts and policies match current rules.
For the staff themselves, Acas explains the basics of employment contracts, including written statements and the terms you must put in writing.
Compliance is not a reason to delay audience work.
Run interviews to test the segments
Data tells you what customers did. Interviews tell you why. Once you have draft segments, speak to a small number of people in each and ask about the moments that led to a decision.
A structured approach is covered in the guide to subscription commerce customer interviews, which explains how to recruit, question and record without leading the participant.
Keep the sample small and deliberate. Five to eight interviews per segment is often enough to challenge assumptions.
Worked example with labelled pound figures
Consider a fictional English subscription box for pet supplies. The team has 1,200 active subscribers and wants three personas.
They export twelve months of billing data and find that 55 per cent of cancellations happen in month two. Support tickets show delivery timing is the most common complaint.
Using illustrative figures, suppose the average plan is £25 a month. A cohort of 100 subscribers who cancel in month two represents £2,500 in lost first-year revenue at that rate. That number reframes the persona work around onboarding and delivery expectations rather than price.
The team builds three segments: gift buyers who never intended to renew, trial users who wanted faster delivery, and long-term subscribers who buy add-ONS. Each persona is defined by observed behaviour, not by a fictional biography.
Document and review
Write down what each persona is based on, the date of the data and the size of the sample. A persona without a source note is an opinion with a name attached.
Review the set every six months or after a major pricing change. Subscription behaviour shifts with the economy and with your own product changes.
Share the personas with the people who will use them. A retention agent, a copywriter and a product manager read the same document for different reasons.
Common questions
How many buyer personas should a subscription business have?
Most small and mid-sized subscription businesses can work with three to five. More than that becomes hard to remember and act on.
Can I build personas from survey data alone?
Surveys are useful for attitudes and intent, but weaker for behaviour. Pair survey answers with billing and support data so the persona reflects what people did.
Do I need consent to create personas?
If the data is fully anonymised, consent may not be the relevant basis. If individuals can still be identified, you need a lawful basis under the UK GDPR and a clear retention period.
How often should personas be updated?
Review them at least every six months, and sooner if you change pricing, packaging or the sign-up journey. Outdated personas quietly misdirect retention spend.
