Customer discovery
Customer persona for startups: why know your customer
By Boring Marketing Loop · Published
Why startups need to know their customer, and how to build a customer persona from evidence, not guesses. Includes a template with a source for every line.
What is a customer persona?
A customer persona is a short description of one type of customer: what they are trying to do, how they do it today, what gets in the way, and what would make them switch. For a startup, a customer persona is useful only if it is built from what real people said and did. A persona written from imagination looks just as convincing and points you in the wrong direction.
Most customer persona templates ask for a name, an age, a job title, a stock photo, and a list of hobbies. Those fields are easy to fill in without talking to anyone, which is the problem. This article explains why knowing your customer matters so much for a startup, which persona fields matter, and how to build a persona where every line has a source.
Why do startups need to know their customer?
Because the most common way startups fail is building something the customer does not need. In a March 2026 analysis of 431 venture-backed companies that shut down since 2023, CB Insights found that 43% cited poor product-market fit. Running out of money was cited more often, at 70%, but CB Insights describes that as the final cause, not the root problem.
The UK government's service design guidance says it more directly: "If you do not understand who they are or what they need from your service, you cannot build the right thing." The GOV.UK guide to user needs was written for public services, but the reasoning holds for a startup.
Knowing your customer changes concrete decisions:
- What to build first. The feature that removes their biggest cost, not the one you find most interesting.
- What to say. Their words for the problem, which are rarely the words you use.
- Where to find them. The places they already go when the problem comes up.
- What to charge. What the problem costs them today, in money or hours.
A persona is a way to write that knowledge down so you can check it before each of those decisions.
Two kinds of customer persona
The Nielsen Norman Group, a user-experience research firm, separates personas by the research behind them. In a 2020 article on persona types, Page Laubheimer describes proto personas as "created with no new research," built from what a team already believes. He warns that they "can be an echo chamber for the team's incorrect assumptions." Qualitative personas, by contrast, come from interviews and observation, grouped by shared goals, pain points, and expectations. The article recommends the qualitative kind for most teams.
A startup founder almost always starts with a proto persona. That is fine as a starting point. The mistake is treating it as finished. A persona written before you speak to anyone is a list of guesses, and it should say so.
Which fields belong in a startup customer persona?
Keep the fields that change a decision and drop the rest. Here is what we would keep, with the question each field answers.
| Field | What it tells you | Example (hypothetical) |
|---|---|---|
| Who they are | A group you could find and list by name | Independent consultants who send 3+ proposals a month |
| What they are trying to do | The job, in their words | "Win work without chasing people for weeks" |
| What triggers the problem | The moment it costs them something | A proposal goes unanswered for a week |
| What they do today | Your real competitor | A spreadsheet and calendar reminders |
| What it costs them | Why they would pay to change | Lost deals, about one a quarter by their own estimate |
| What would make them switch | The bar your product has to clear | Follow-ups that go out without them remembering |
| Where they ask for help | Your first channel | Two Slack communities and a LinkedIn group |
| Words they use | Your message | "Chasing," "ghosted," "went quiet" |
Age, hobbies, and a stock photo are missing on purpose. They rarely change what you build or say. Add a demographic field only if it changes a decision, for example a region that changes how people pay.
A customer persona template with a source for every line
The column that makes this template work is the last one. Each line says where it came from, so you can see at a glance which parts are guesses.
Field | Answer | Source | Status
Who they are | | | guess / observed
What they are trying to do | | | guess / observed
What triggers the problem | | | guess / observed
What they do today | | | guess / observed
What it costs them | | | guess / observed
What would make them switch| | | guess / observed
Where they ask for help | | | guess / observed
Words they use | | | guess / observed
A source is something you can point to: "interview with a consultant, 2 October," "12 forum questions read on 5 October," "3 of 30 outreach replies mentioned this." "I think" is also a valid source, as long as the status column says "guess."
How to turn a guessed persona into a real one
- Write the proto persona in 15 minutes. Fill in every field from what you already believe and mark them all as guesses.
- Find people who match the first line. Our guide on how to find customers for a startup shows how to build a list of 30 names from something people recently did.
- Talk to them about their last experience. Ask what happened the last time the problem came up, what they did, and what it cost. Our customer discovery interview questions give you a full guide.
- Update one field at a time. When an answer has a source, change its status to observed. When interviews contradict a field, rewrite it and keep the old version so you can see what changed.
- Split the persona when the answers split. If half the people describe one trigger and half another, you probably have two customers. Pick the one you can reach more easily and test that one first.
The persona is never finished. It is the current best record of what you know about one customer, with the guesses labeled.
Customer persona vs ideal customer profile
The terms overlap, and people use them loosely. In the business-to-business sales writing we have read, an ideal customer profile usually describes the company that buys, such as its industry, size, and budget. A customer persona describes the person inside it who has the problem. A solo founder selling to individuals or very small businesses can usually treat them as one document.
Keep each line attached to its evidence
A persona in a document drifts away from the tests that should update it. You run an outreach test, learn that the trigger is wrong, and the persona still says the old thing a month later.
We are building Boring Marketing Loop to keep those connected. The workspace asks nine Customer & offer questions, including who needs your help and what they do today, and each answer is marked as a guess until people respond. When you plan a test, you choose which answers it checks. After you record the result and make a decision, those answers show as tested.
Marketing Loop is in development and not open to the public yet. If you want to hear when it is ready, join the build updates.
FAQ
How many customer personas does a startup need?
Start with one. You need enough focus to find people, write one message, and learn from the replies. Add a second persona when interviews show a clearly different group with a different trigger.
How many interviews do I need to build a persona?
There is no fixed number. Keep talking to people until new interviews mostly repeat what you already heard about the trigger, the current workaround, and the cost. Then test the persona with outreach, which shows whether a larger group responds the same way. Our guide on how many customer interviews you need explains how to tell when answers repeat.
What is the difference between a buyer persona and a user persona?
A buyer persona describes the person who decides to pay. A user persona describes the person who uses the product. For many small products they are the same person. When they are not, for example when a manager buys a tool for a team, write both, because each needs a different message.
Should I use AI to write a customer persona?
An AI tool can draft the proto persona quickly, and that draft is still a set of guesses. Mark every line as a guess and replace it with what real customers say. A persona that no customer has contributed to is a proto persona, however detailed it looks.
Write the persona, then label it
Fill in the template today from what you believe, and mark every line as a guess. Then pick the line you are least sure of, usually the trigger or the cost, and talk to five people about it this week. Change its status to observed only when you can name the source.