Customer Persona Template
One real buyer, described closely enough that you could write to them.
Details
customer persona templateUploads
Your logo
A photo or picture
Goes on this page only. Drag it anywhere and pull its corner to resize it.
Your signature
Draw it with a finger, a mouse or a trackpad, and it goes on the page like a picture.
Pictures and signatures stay on this device. Nothing is uploaded to a server.
Red highlights mark what is still blank. Click anything on the page to change it. Your draft is kept on this device as you work.
1. Who they are
[their job, their day, how they buy]
2. What they are trying to do
[one goal per line]
3. What gets in the way
[one obstacle per line]
4. Where you reach them
[channels, publications, places, people they listen to]
What is a Customer Persona?
A customer persona describes one buyer in enough detail that you could write directly to them: what they are trying to get done, what makes them hesitate, and where they look for an answer. It matters because copy addressed to everybody reads as though it were addressed to nobody. Without one, feature arguments get settled by whoever in the room is most senior, using the customer they personally happen to imagine.
Marketers use personas when writing web copy and choosing channels; product teams use them to decide which request to build; sales and support use them to recognise who they are talking to inside the first five minutes. Agencies build them in the first weeks of an account to stop guessing. They are also one of the fastest ways to bring a new hire up to speed, because a good persona carries the buyer's own language, which no onboarding deck ever does.
Building a persona from customer records is processing personal data, and the rules differ. The UK and EU GDPR require a lawful basis and data minimisation; India's DPDP Act, Canada's PIPEDA, the Australian Privacy Principles and US state laws such as the CCPA and CPRA each set their own conditions. Aggregate and anonymise rather than pasting a named account's details into a document that circulates widely. Separately, if the persona feeds ad targeting, some categories of advertising — housing, employment and credit in the US in particular — restrict targeting on protected characteristics.
A persona is not a market segment. A segment is a countable group you can size and target; a persona is one illustrative person who helps you write. Confusing the two produces a forecast built on a fictional character. It is also not a substitute for talking to customers — it is a summary of having done so, and it goes stale as soon as the market moves. And a demographic sketch with no buying trigger tells you who they are without telling you when to reach them.
What to put in a Customer Persona
These are the details this template asks for. Anything left blank is marked in red on the preview so you can see what is still missing.
| Field | What goes in it |
|---|---|
| Business name | For example: Barton Supply Co. |
| Your address | For example: Unit 7, Barton Road, Columbus, OH 43212 |
| Persona name | For example: Dave, the one-van builder |
| Who they are | For example: Runs a two-person outfit doing kitchen and bathroom fits. Quotes in the evening, buys in… |
| What they are trying to do | One per line |
| What gets in the way | One per line |
| Where you reach them | For example: Trade counter, local radio in the van, and Facebook groups for regional builders |
| The core message | For example: Stocked for small jobs, not for volume trade — so you are not waiting three days for four… |
How to write a Customer Persona
Build it from interviews, not from the room
Talk to five to ten people who recently bought, recently chose someone else, or recently decided to do nothing at all. Record what they say and keep their phrasing. A persona assembled in a workshop reflects the team's assumptions back at them, flatteringly, and every decision made afterwards inherits that flattery without anyone noticing.
Name the job they are trying to finish
Write the situation that made them start looking, in their terms. 'The auditor asked for evidence we could not produce' is a trigger you can build a campaign around. 'Wants to improve efficiency' is not; nobody wakes up and searches for that. The trigger tells you both what to say and when you need to be visible.
Write their objection in their own words
Capture the sentence that makes them stall — the cost of switching, an internal approval they dread, a past tool that failed, a colleague who will resist. Quote it verbatim from an interview. Objections rewritten in your own marketing vocabulary become straw men that are easy to answer and bear no resemblance to the real hesitation.
Record where they actually look for answers
Name the specific places: a trade publication they read, a professional forum, a supplier they trust, the colleague they ask first, a conference they attend every year. 'Social media' and 'online research' are not answers. This section is what turns a persona into a channel plan, and it is the section most often filled with generalities.
Delete every detail that changes no decision
Run through the finished persona and strike anything that would not alter a headline, a channel choice or a feature priority. Favourite coffee order, stock photograph, invented surname — cut them. What remains should be short enough that people actually read it before writing, which is the only way a persona affects anything at all.
Common mistakes
- Inventing the persona in a workshop with no customer contact produces a portrait that agrees with the product you already built, and every decision it guides inherits that flattery.
- Creating four personas that differ only by job title means nobody can tell which one a given page is for, so pages end up written for all of them at once.
- Filling in age, income and job title but not the buying trigger produces a persona that says who to reach and never when to reach them.
- Pasting a named customer's identifiable details into a widely shared persona document creates a data protection problem far more expensive than the insight was worth.
- Writing personas once and never revisiting them after a pricing change or a new market leaves the team confidently addressing a buyer who has moved on.
Frequently asked questions
How many personas should we have?
Usually two or three, and one is a perfectly respectable answer for a young company. Each additional persona multiplies the copy, the campaigns and the arguments. Add a new one only when you can point to a group whose buying trigger, objection and information sources are genuinely different, not merely a different job title inside the same organisation.
What is the difference between a persona and an ICP?
An ideal customer profile describes the kind of organisation worth selling to: size, sector, geography, technology, budget. A persona describes a person inside it. You use the ICP to build the target list and the persona to write to the people on it. Business-to-business teams generally need both, and they answer different questions.
Do personas need a name and a photo?
A name helps people refer to the persona in conversation, which is genuinely useful. A stock photograph adds nothing and quietly encodes assumptions about age, gender and ethnicity that nobody chose deliberately. If you use one, be aware that everyone who reads the document will remember the picture for longer than the buying trigger underneath it.
How do I build a persona with no research budget?
Interviews cost time, not money. Ten conversations with recent buyers, recent losses and your own support and sales colleagues will get you most of the way. Read your support tickets and the questions asked on sales calls — that is unfiltered customer language. Public forums and review sites for your category supply the objections people voice when you are not listening.
How often should personas be updated?
Review annually, and immediately after anything that changes who buys: a price change, a new market, a product that opens up a different use case. The buying trigger and the objection age fastest. If the persona is quoted in a planning meeting and someone says customers do not think that any more, treat that as the update signal.
This page explains general practice and is not legal advice. Requirements differ between countries and, in some cases, between states — check what applies where the document will be used.