Most founders think they have a persona when what they actually have is a vague category of person.
They say things like “small business owners”, “creators”, “consultants”, “accountants”, “coaches”, “busy professionals”, “sales teams”, or “people who want to be more productive”. That may sound like a target market, but it is not specific enough to build a product, write a landing page, create an offer, or run outreach.
A useful persona is not a fictional character with a stock photo, a made-up name, and a random list of hobbies. That kind of persona is corporate theatre. It makes the founder feel like they understand the market without forcing them to confront whether they actually understand the buyer.
A useful persona tells you who the person is, what they already want, what they are already trying to fix, what they are measured against, where they spend attention, what they have already tried, what they can afford, who influences the decision, what language they use, and why they would care now.
That is the difference between a marketing exercise and a business asset.
This matters because a solo-founder has very little room for error. You do not have a large team, a giant sales budget, a brand that can brute-force attention, or unlimited time to test ten different markets. You need to know exactly who you are building for and why they would care.
Sam Ovens has often taught that demand already exists in the market. You do not create demand from nothing. You find existing demand and channel it towards your product or service. That idea closely mirrors Eugene Schwartz’s famous argument in Breakthrough Advertising: copy cannot create desire; it can only take existing desires in the market and direct them towards a product.
That is why personas matter. A persona is not just a profile of a customer. It is your attempt to locate existing desire with enough precision that you can build, sell, and communicate without guessing.
Alex Hormozi makes a similar point from another angle when he talks about picking the right market. In $100M Offers, his market selection criteria are often summarised as massive pain, purchasing power, ease of targeting, and growth. Those are persona questions. Does this person have pain? Can they pay? Can you reach them? Is their market moving in the right direction?
Nick Kozmin’s product-market fit thinking is also useful here. A strong opportunity starts with a clearly defined person and desire. Can you access the person? Do they have money? Is the problem painful and urgent? Is your solution the best or only option for that defined person?
If you cannot answer those questions, you do not have a persona yet. You have a guess.
Why Personas Matter So Much for Solo-Founders
As a solo-founder, a persona reduces wasted motion. It tells you what to build, what not to build, what to say, who to contact, what proof to collect, what objections to handle, and what buying trigger to focus on.
Without a persona, every decision becomes abstract. Should the product be self-serve or sales-led? Should you charge £19/month or £2,000 upfront? Should you build integrations or templates? Should you sell to the user or the manager? Should your landing page lead with saving time, making money, reducing risk, improving status, or simplifying a workflow?
The answer depends on the persona.
A founder selling to broke beginner creators needs a different product, price, message, and sales process than a founder selling to agency owners doing £50k/month. A founder selling to junior staff inside accounting firms needs a different argument than a founder selling to partners. A founder selling to a Head of Sales needs to understand pipeline, conversion rates, booked meetings, activity metrics, and revenue targets. A founder selling to an operations manager needs to understand utilisation, turnaround time, capacity, error rates, and margin.
Personas are not just about demographics. In fact, demographics are often the least useful part. The important questions are behavioural, emotional, economic, and organisational.
What does this person want badly enough to act? What are they already trying to solve? What happens if they fail? Who judges the outcome? What budget exists? What language do they use when describing the problem? Where do they go when they are looking for help? What would make this urgent now?
That is what a useful persona captures.
The Bad Version of Personas
The bad version of persona development looks like this:
“Sarah is 34, lives in London, likes coffee, uses Instagram, and wants to be more productive.”
This is mostly useless.
It may be mildly helpful for brand tone if you are selling a consumer lifestyle product, but for most solo-founders building software, services, courses, templates, or consulting offers, it does not tell you enough.
It does not tell you what Sarah is already trying to achieve. It does not tell you what she has tried. It does not tell you if she has money. It does not tell you if she has authority. It does not tell you whether she has a KPI. It does not tell you what problem is urgent enough to interrupt her day. It does not tell you whether she can buy, whether her manager needs to approve, or whether the company already pays for alternatives.
Bad personas are usually built from imagination. Good personas are built from evidence.
The goal is not to invent a character. The goal is to document a real market pattern.
The Good Version of Personas
A useful persona sounds more like this:
“Operations managers at UK accounting firms with 10–50 staff who are responsible for improving workflow visibility, reducing missed deadlines, and increasing team capacity. They are frustrated because partners keep asking for status updates, staff work is spread across spreadsheets and practice management tools, and they are measured informally on whether the firm feels organised. They are not always the final buyer, but they can strongly influence the founder or managing partner if the product clearly reduces operational chaos, improves turnaround time, or helps the firm recover lost margin.”
That is much more useful.
Now you can build a product. You can write a landing page. You can run outreach. You can design a lead magnet. You can create a demo. You can decide which integrations matter. You can work out who needs to be convinced internally. You can identify the business case.
A strong persona should help you make decisions.
If it does not change what you build, what you say, how you price, or who you contact, it is probably not specific enough.
The Persona Development Checklist
Before building around a persona, I would want to document the following:
- Who exactly is the person?
- What do they already want?
- What painful problem blocks that outcome?
- How urgent is the problem?
- What happens if they do nothing?
- Do they have money or access to budget?
- Are they the buyer, user, influencer, or internal champion?
- Who else influences the decision?
- What KPIs, targets, or responsibilities are attached to their role?
- What existing solutions have they tried?
- What do they dislike about current solutions?
- Where do they gather online or offline?
- Can you identify and reach 100 of them?
- What words do they use to describe the problem?
- What would make this problem urgent now?
- What objections would stop them buying?
- What proof would they need?
- What would make their manager or leadership team prioritise it?
- What manual workaround are they using today?
- What is your advantage in serving them?
That is the level of detail you need if you want the persona to be useful.
A persona is not finished when it looks neat in a Notion page. It is finished when it helps you predict behaviour. If you know what this person will respond to, what they will ignore, what they will object to, what they will pay for, and what they will need to justify internally, then you are getting somewhere.
Step 1: Start With a Narrow Hypothesis
Do not start with “creators”, “founders”, “accountants”, or “business owners”. Start narrower than feels comfortable.
For example:
- Not “creators”, but “fitness creators with 10k–100k followers who want to sell a low-ticket digital product”.
- Not “accountants”, but “UK accounting firm owners with 5–30 staff who are trying to increase fees from legacy clients”.
- Not “consultants”, but “solo consultants who get leads through LinkedIn and lose opportunities because they do not follow up properly”.
- Not “sales teams”, but “B2B sales managers at teams of 5–20 reps who are measured on booked demos and pipeline conversion”.
- Not “operations people”, but “client onboarding managers who are measured on reducing time-to-value and avoiding implementation delays”.
This does not mean you can never expand later. It means you need a sharp starting point. A narrow persona is testable. A broad persona lets you avoid the hard questions.
Use this sentence:
“I believe [specific person] wants [specific outcome] because they are struggling with [specific problem], and this matters because [specific consequence].”
Example:
“I believe UK accounting firm owners with 5–30 staff want to increase fees from underpriced legacy clients because old pricing has not kept up with scope creep, and this matters because it quietly destroys margin and capacity.”
That is a persona hypothesis. Now you can test it.
Step 2: Separate the User, Buyer, Champion, and Decision-Maker
One of the biggest mistakes in persona development is assuming “the customer” is one person.
In B2B, there are often multiple personas involved:
- The user: the person who uses the product day to day.
- The buyer: the person who pays or owns the budget.
- The champion: the person who wants the product internally.
- The decision-maker: the person who can approve or block the purchase.
- The influencer: the person whose opinion affects the decision.
- The admin or implementer: the person who has to set it up.
If you confuse these, your sales process gets messy.
For example, an operations manager may feel the pain deeply, but the managing partner controls the budget. A junior sales rep may use the tool daily, but the Head of Sales decides whether the team adopts it. A marketing manager may want better attribution, but the founder only cares if it increases revenue or reduces wasted ad spend.
This is why KPI alignment matters. If the user can connect your product to a metric their manager already cares about, the internal sale becomes much easier.
A good persona document should say:
- Who feels the pain?
- Who owns the budget?
- Who has authority?
- Who has to implement?
- Who benefits if it works?
- Who gets blamed if nothing changes?
- Who would need to approve this?
For consumer products, this may be simpler. The user and buyer may be the same person. But even then, there may be social influences, status considerations, partners, friends, communities, or platform trends affecting the decision.
Step 3: Identify the Desire Before the Problem
Most founders start with the problem. That is useful, but it is not enough. You also need to understand the desire underneath the problem.
People do not just want fewer admin tasks. They may want more control, more revenue, less stress, more status, fewer embarrassing mistakes, faster progress, better clients, more freedom, or a sense that the business is finally under control.
This is where the Eugene Schwartz idea matters. You are not creating desire. You are finding the existing desire and positioning your product as the route to satisfy it.
For each persona, write down:
- What do they want on the surface?
- What do they really want underneath?
- What are they afraid will happen if they fail?
- What would make them feel successful?
- What would make them look good to their manager, clients, team, audience, or peers?
Example:
Surface desire: “I want better client onboarding.”
Deeper desire: “I want clients to feel confident, I want fewer status-chasing emails, I want the team to stop dropping tasks, and I want leadership to trust that onboarding is under control.”
That deeper desire is much more useful for product and messaging.
Step 4: Map the Persona’s Pain
Once you understand the desire, map the pain blocking it.
Hormozi’s “massive pain” filter is useful here. If the pain is weak, you will struggle to sell. If the pain is strong, specific, and urgent, everything gets easier.
Ask:
- What is frustrating them?
- What is costing them money?
- What is costing them time?
- What is making them look bad?
- What creates stress?
- What creates risk?
- What creates rework?
- What causes lost sales, churn, complaints, delays, or margin loss?
- What does their manager keep asking them about?
- What do they already know needs to be fixed?
Then classify the pain:
- Financial pain: lost revenue, wasted spend, poor margins, underpricing, churn.
- Operational pain: delays, errors, manual work, duplicated effort, poor visibility.
- Status pain: looking disorganised, falling behind competitors, losing authority.
- Emotional pain: stress, overwhelm, embarrassment, uncertainty.
- Compliance or risk pain: deadlines, regulation, security, audit risk, client risk.
- Growth pain: bottlenecks, inability to scale, founder dependency, capacity constraints.
The more categories a problem touches, the stronger the persona may be.
A problem that costs money, creates embarrassment, and affects a KPI is usually more valuable than a problem that merely feels slightly annoying.
Step 5: Document KPIs, Targets, and Internal Priorities
This is a major point that many solo-founders miss.
Some personas have formal KPIs. Others have informal responsibilities. Either way, if your product helps them improve something they are already judged on, it becomes much easier for them to understand, care, and act.
Examples:
- A Head of Sales may care about pipeline, booked meetings, close rate, sales cycle length, revenue per rep, and activity levels.
- A Customer Success Manager may care about churn, renewals, onboarding completion, time-to-value, support tickets, and expansion revenue.
- An Operations Manager may care about turnaround time, utilisation, capacity, error rates, process compliance, and margins.
- A Marketing Manager may care about qualified leads, CAC, conversion rates, attribution, landing page performance, and campaign ROI.
- A founder may care about revenue, profit, cash flow, growth, risk reduction, team capacity, and enterprise value.
If you can attach your product to one of these metrics, you make the persona’s job easier. They do not need to invent a reason to care. The reason already exists in their role.
This also helps with internal prioritisation. A user may personally like a tool, but if they cannot explain why it matters to their manager, it dies. A much stronger message is: “This will help us reduce onboarding time by 30%,” “This will increase booked calls,” “This will reduce missed deadlines,” or “This will help recover fees from underpriced clients.”
A useful persona document should include a section called “What they are measured on”. If you cannot fill that in, you may not understand the persona well enough yet.
Step 6: Find Where They Already Spend Attention
Hormozi’s “easy to target” criterion is not optional. A persona you cannot reach is not a practical persona for a solo-founder.
You need to know where this person already spends attention. Not where you wish they spent attention. Where they actually are.
Document:
- LinkedIn groups and creators they follow.
- Facebook groups they participate in.
- Reddit communities they read.
- YouTube channels they watch.
- Podcasts they listen to.
- Newsletters they subscribe to.
- Events they attend.
- Associations they belong to.
- Software tools they already use.
- Job titles you can search for.
- Keywords they search on Google.
- Competitors they compare.
- Influencers or experts they trust.
Then ask the practical question:
“Can I reach 100 of these people without needing a miracle?”
If the answer is no, the persona may be too vague, too hidden, too senior, too broad, or simply impractical for your current stage.
As a solo-founder, you need accessible markets. A perfect persona on paper is useless if you cannot get conversations.
Step 7: Study Existing Solutions and Workarounds
Good personas are revealed by behaviour.
Do not just ask what people want. Look at what they already do.
For each persona, document:
- What software do they already use?
- What consultants do they hire?
- What courses do they buy?
- What templates do they download?
- What spreadsheets do they maintain?
- What internal roles exist to solve this?
- What manual workarounds have they created?
- What are they complaining about in reviews?
- What alternatives are they comparing?
- What words appear repeatedly in complaints?
This is important because existing spend is evidence. If people are already spending money or time solving the problem, the persona is more likely to be commercially useful.
Competition is not automatically bad. For a solo-founder, competition often proves there is demand. The question is not whether anyone else is solving the problem. The question is whether existing solutions leave a gap for a more specific, simpler, faster, more integrated, more trusted, or more outcome-focused offer.
Step 8: Interview the Persona Without Pitching
Once you have a hypothesis, you need conversations. But you need the right kind of conversations.
Do not pitch your idea at the start. If you pitch too early, the person will react to your idea instead of revealing their reality. They may be polite. They may say it sounds interesting. They may try to help. That is not the same as truth.
The goal is to understand the persona’s world before your solution enters the conversation.
Ask:
- What are you currently trying to improve in this area?
- What is frustrating about the current process?
- How are you solving it today?
- What have you already tried?
- What did you pay for?
- What worked?
- What did not work?
- What happens if this does not improve?
- How often does this problem come up?
- When does it become urgent?
- Who else is involved?
- Who owns the budget?
- Who would need to approve a new solution?
- What metrics are you responsible for?
- Does this affect any KPIs or management priorities?
- What would your manager need to see to care about this?
- What would a perfect solution allow you to do?
You are listening for specifics.
Weak signal:
“Yeah, that sounds like it could be useful.”
Strong signal:
“We lose leads because follow-up is inconsistent. I’m measured on booked demos, and I’ve already tried using HubSpot tasks, a spreadsheet, and Slack reminders. None of it sticks. My manager only cares if booked calls increase.”
That is persona gold.
You now know the pain, the existing workaround, the KPI, the manager’s priority, and the language.
Step 9: Capture Their Exact Language
Your persona document should include the words real people use.
Do not translate everything into founder language. The customer’s language is usually better than yours.
Founder language:
“Revenue operations optimisation platform.”
Customer language:
“Leads are slipping through the cracks after calls.”
Founder language:
“AI-powered workflow intelligence.”
Customer language:
“I don’t know what the team is working on unless I ask.”
Founder language:
“Automated pricing optimisation.”
Customer language:
“We have clients who are still paying 2019 fees for 2026 work.”
The closer your messaging is to the customer’s actual language, the more likely they are to feel understood.
This is also how you avoid vague positioning. “Save time” is weak. “Stop chasing clients manually before every deadline” is stronger. “Improve sales productivity” is vague. “Stop losing warm leads because nobody follows up after the discovery call” is stronger.
Step 10: Build the Persona Document
Once you have research, turn it into a usable document.
I would structure it like this:
1. Persona Name
Use a descriptive name, not a fake one.
Bad: “Marketing Mary”
Better: “Founder-led accounting firm owner with underpriced legacy clients”
2. Persona Summary
Write one paragraph describing who they are, what they want, and what is blocking them.
3. Role and Context
Document their job title, company type, company size, industry, seniority, and daily responsibilities.
4. Desired Outcome
What do they already want? Be specific.
5. Pain and Consequences
What is painful? What happens if they do nothing? What does it cost them financially, operationally, emotionally, or reputationally?
6. KPIs and Priorities
What are they measured on? What does their manager care about? What business outcome would make this urgent?
7. Current Alternatives
What are they using now? Software, spreadsheets, staff, consultants, agencies, courses, templates, or manual processes.
8. Existing Complaints
What do they dislike about current solutions?
9. Buying Role
Are they the user, buyer, champion, decision-maker, influencer, or implementer?
10. Buying Trigger
What makes this problem urgent now? A deadline, growth stage, new hire, lost client, regulation change, churn, cash issue, platform change, or failed process?
11. Objections
Why would they not buy? Price, trust, complexity, switching cost, lack of urgency, internal approval, fear of implementation, or satisfaction with the current workaround?
12. Proof Needed
What would they need to believe before buying? Case studies, ROI calculator, demo, testimonials, sample templates, security documentation, founder credibility, integration proof, or a guarantee?
13. Access Channels
Where can you reach them?
14. Exact Language
Include quotes from calls, reviews, posts, comments, and emails.
15. Product Implications
What does this persona imply for the product? Features, integrations, onboarding, service layer, pricing, support, templates, and positioning.
16. Offer Implications
What offer would make sense? Self-serve software, paid pilot, done-for-you setup, workshop, audit, template pack, consulting package, or hybrid service/software offer.
This document should become a decision-making tool. When you are unsure what to build next, return to the persona. When you are unsure what to say in outreach, return to the persona. When you are unsure how to price, return to the persona. When you are unsure whether to add a feature, return to the persona.
Step 11: Score the Persona
Not every persona is worth pursuing.
Use this 1–5 scoring framework:
1. Clarity
Can you define the person clearly?
1 = vague category
3 = defined segment
5 = specific role, context, company type, and situation
2. Existing Desire
Do they already want the outcome?
1 = you need to educate them
3 = some awareness
5 = they are already actively seeking the outcome
3. Pain
How painful is the problem?
1 = mild annoyance
3 = recurring frustration
5 = costly, urgent, stressful, risky, or embarrassing
4. Urgency
Why now?
1 = no urgency
3 = periodic urgency
5 = clear trigger event or deadline
5. Purchasing Power
Can they pay or access budget?
1 = no money
3 = some budget
5 = clear budget, existing spend, or strong ability to pay
6. Access
Can you reach them?
1 = hard to find
3 = reachable with effort
5 = clear lists, channels, communities, search intent, ads, or network access
7. KPI Alignment
Does this connect to something they are measured on?
1 = no clear KPI
3 = loosely connected
5 = directly connected to a KPI, target, budget priority, or leadership goal
8. Existing Spend
Are they already spending money or time on alternatives?
1 = no evidence
3 = some workarounds
5 = clear spend on tools, services, people, or manual process
9. Dissatisfaction
Are existing solutions failing them?
1 = no clear dissatisfaction
3 = some complaints
5 = repeated complaints, switching behaviour, or obvious gaps
10. Founder Advantage
Do you have an edge with this persona?
1 = no access or insight
3 = some experience
5 = strong domain knowledge, credibility, network, or lived experience
Score out of 50.
- 0–20: Weak persona. Do not build around it yet.
- 21–30: Interesting, but needs more research or narrowing.
- 31–40: Promising. Test with conversations and a manual offer.
- 41–50: Strong persona. Worth serious validation.
The score is not magic. It is a forcing function. It stops you from pretending all personas are equally valuable.
Step 12: Create a Persona Research Sprint
Here is a practical seven-day sprint for developing a useful persona.
Day 1: Create Three Persona Hypotheses
Write three narrow persona hypotheses using this structure:
“I believe [specific person] wants [specific outcome] because [specific problem], and this matters because [specific consequence].”
Do not allow vague categories. Force yourself to define the role, situation, and desired outcome.
Day 2: Research Existing Demand
Look for evidence that each persona already cares about the problem. Search communities, review sites, LinkedIn, Reddit, YouTube comments, podcasts, competitor pages, job descriptions, and Google search terms.
Collect evidence of pain, language, alternatives, spend, and urgency.
Day 3: Map Alternatives and Workarounds
For each persona, document the tools, services, consultants, spreadsheets, employees, templates, and manual processes they already use.
If there are no alternatives or workarounds, be careful. That may mean the problem is not important enough yet.
Day 4: Build a List of 100 Real People
Find actual people or companies that match the persona.
Include names, roles, company websites, LinkedIn profiles, likely pain, likely KPI, and reason they might care.
If you cannot build the list, the persona may not be accessible enough.
Day 5: Send 30 Research Messages
Do not pitch. Ask for insight.
Example:
“I’m researching how [specific role] handles [specific problem]. I’m not selling anything — I’m trying to understand the problem properly. Would you be open to sharing how you currently deal with this?”
The goal is not to validate your ego. The goal is to get conversations.
Day 6: Run Five to Ten Persona Interviews
Ask about the person’s role, responsibilities, goals, pain, existing process, spend, urgency, KPIs, internal approval, and objections.
Do not pitch until the end. If the conversation naturally goes there, you can briefly describe the outcome you are exploring and ask whether it would be worth discussing further.
Day 7: Build and Score the Persona Document
Use the persona template and the 50-point scorecard.
Then make a decision:
- Kill the persona.
- Narrow the persona.
- Research more.
- Test a manual offer.
- Build a small MVP around the strongest persona.
Most persona hypotheses should not survive this process. That is a good thing. You are filtering for signal.
Example Persona Document
Persona Name
Founder-led accounting firm owner with underpriced legacy clients.
Persona Summary
This person runs a UK accounting firm with 5–30 staff. The firm has grown over several years, but many legacy clients are still on old fees. Scope has expanded, staff costs have increased, and partners suspect that some clients are now unprofitable or underpriced. They want to increase fees without damaging client relationships or creating awkward conversations.
Desired Outcome
They want to recover lost margin, increase revenue from existing clients, and create a repeatable process for reviewing fees.
Pain and Consequences
Underpriced clients quietly consume team capacity, reduce profit, and make the firm feel busier than it should be. The founder knows fees need to increase, but the process is emotionally uncomfortable and operationally messy.
KPIs and Priorities
The founder cares about revenue, profit, capacity, recovery rates, staff utilisation, and client retention. The pain connects directly to margin and firm value.
Current Alternatives
Manual fee reviews, spreadsheets, partner judgement, ad hoc conversations, practice management reports, pricing consultants, and annual review meetings.
Existing Complaints
They do not know which clients are genuinely underpriced. They do not have a clean process for reviewing fees. They worry about upsetting long-term clients. They suspect staff are spending too much time on low-margin work.
Buying Role
The founder or managing partner is likely the buyer and decision-maker. Operations managers may influence the process if they are responsible for workflow data or reporting.
Buying Trigger
Capacity pressure, declining margins, hiring costs, partner frustration, annual fee review season, or a realisation that legacy clients are blocking growth.
Objections
Fear of damaging client relationships, lack of clean data, scepticism about whether the process will work, and concern that the team will not implement it properly.
Proof Needed
Examples of fee increases, scripts, templates, ROI calculator, case studies, sample reports, and a clear process for identifying which clients to review first.
Access Channels
LinkedIn, accounting communities, practice management software ecosystems, webinars, accounting podcasts, direct outreach, and referrals.
Exact Language
“We know some clients are underpriced, but we do not know where to start.”
“The team is flat out, but the profit does not reflect the amount of work going through the firm.”
“I do not want to annoy long-standing clients by suddenly increasing their fees.”
Product Implications
The product or service should help identify underpriced clients, quantify the opportunity, prepare fee review conversations, provide scripts and templates, and create a repeatable workflow.
Offer Implications
A strong first offer may be a fee review audit, annual review system, workshop, or done-for-you implementation before building a full SaaS product.
Common Persona Mistakes
Mistake 1: Making the Persona Too Broad
“Small businesses” is not a persona. “Creators” is not a persona. “Consultants” is not a persona. These are broad markets. You need a specific person in a specific situation with a specific desire.
Mistake 2: Inventing Instead of Researching
If the persona is built entirely from your imagination, it is probably wrong. You need evidence from calls, posts, reviews, comments, search behaviour, competitor research, and actual buying behaviour.
Mistake 3: Confusing Interest With Demand
A person can be interested without being willing to act. Demand is shown through behaviour: spend, workarounds, urgency, complaints, searches, conversations, and willingness to commit time or money.
Mistake 4: Ignoring Budget and Authority
A user with no budget can still be valuable as a champion, but you need to understand who pays. If nobody can pay, or nobody owns the problem, the persona may be commercially weak.
Mistake 5: Ignoring KPIs
If your product does not connect to something the persona or their manager already cares about, prioritisation becomes harder. KPI alignment turns a vague benefit into a business case.
Mistake 6: Treating the Persona as Static
Your persona should evolve as you learn. The first version is a hypothesis. The better version is built through evidence.
Mistake 7: Building for Multiple Personas Too Early
Trying to serve five personas at once usually creates a vague product and weak messaging. Pick one sharp persona first. Win there. Expand later.
What a Strong Persona Looks Like
You probably have a strong persona if:
- You can define them clearly.
- You can find 100 real examples.
- You know what they already want.
- You know what pain blocks the outcome.
- You know what they have already tried.
- You know what they spend money or time on today.
- You know where to reach them.
- You know what language they use.
- You know who approves the purchase.
- You know what KPIs or business outcomes matter.
- You know why the problem is urgent.
- You know what proof they need.
- You know what wedge your product or service could own.
You probably do not have a strong persona if:
- The definition could apply to millions of unrelated people.
- You cannot find real people who match it.
- You do not know where they spend attention.
- You do not know what they already use.
- You cannot describe the pain in their words.
- You do not know whether they can pay.
- You do not know whether they are the user or buyer.
- You cannot explain why their manager would care.
- You need to educate them from zero.
- Your main evidence is that you personally think the idea is good.
Final Thought
Personas are not decoration. They are not something you create because a marketing textbook said you should.
For a solo-founder, a persona is a survival tool.
It stops you from building for an imaginary market. It forces you to define the person, the desire, the pain, the buying process, the budget, the access channel, the KPI, and the trigger event. It makes your product sharper, your messaging clearer, your outreach easier, and your offer more believable.
The point is not to create a cute customer avatar. The point is to find a real group of people with existing demand that you can reach and serve better than the current alternatives.
Sam Ovens’ demand principle, Schwartz’s direct response insight, Hormozi’s market selection criteria, and Kozmin’s product-market fit filters all point in the same direction: start with the market. Start with the person. Start with the desire that already exists.
Then build around that.
References
- Eugene Schwartz, Breakthrough Advertising — the principle that copy does not create desire, but channels existing desire in the market.
- Sam Ovens — market demand and niche selection principles from his consulting and business training material.
- Alex Hormozi, $100M Offers — market selection criteria commonly summarised as massive pain, purchasing power, ease of targeting, and growth.
- Nick Kozmin — product-market fit criteria around defining the person, desire, access, money, pain, urgency, and whether your solution is the best option for that person.