Negative Personas: Deciding Who Not to Build For
A negative persona describes a type of customer your product is not for: people who cost too much to serve, churn immediately, or pull the roadmap away from your core market. Writing it down stops teams from quietly optimizing for users they should be politely declining.
Why exclusion is a strategy
Every feature, integration, and support policy built for a poor fit segment is taken from the customers who pay and stay. Teams feel the pull as individual requests, each sounding reasonable, until the product is a compromise that serves nobody particularly well.
For more on this, see this related guide and our earlier explainer on the same theme.
A written negative persona turns those moments into a simple check. When a request matches the exclusion profile, the answer is a fast, kind no, and the roadmap hour goes to the audience the business actually depends on.
Finding your poor fit patterns
Look at the customers who churned in the first month, filed the most tickets per dollar of revenue, or demanded refunds at the highest rate. Patterns usually cluster: a company size you cannot support, a use case adjacent to yours, or buyers who needed the cheapest option above all else.
Talk to sales and support before writing anything. They carry the anecdotes that data misses, like the prospect who needs a feature you will never build but buys anyway and spends a year unhappy. Those stories, checked against numbers, become the persona.
Writing it so teams use it
Give the negative persona a name, a short story, and the economic facts: acquisition cost, support load, lifetime value, churn timing. Add the phrases this segment uses in sales calls, so reps can spot the fit problem in the first conversation.
Readers also found this companion piece from our archive useful.
Keep it respectful. This document is about fit, not mockery, and it may be read by anyone in the company. Describe needs you cannot meet well and wish them a better suited product, in writing, without caricature.
Using it in daily decisions
Put the negative persona in the rooms where scope is decided: roadmap reviews, pricing changes, and campaign planning. Marketing uses it to write copy that repels the wrong reader gently, like stating scale requirements and setup effort up front.
Review it twice a year. Markets move, and a segment that was poor fit at one price or product stage can become attractive later. The persona is a decision tool, not a permanent verdict on a group of customers.
Frequently asked questions
What is a negative persona, exactly?
It is a documented profile of a poor fit customer, built from real patterns: high support load, low willingness to pay, needs your product will never meet, or usage that breaks your model. It guides qualification, pricing pages, and roadmap tradeoffs.
Does a negative persona mean refusing customers?
Usually it means not marketing to them, not designing for them, and setting expectations honestly when they arrive. Some businesses do decline sign ups, but most simply stop spending money to attract a segment that loses money.
How do we build one without stereotyping?
Base it on behavior and economics, not demographics. Use support tickets, churn data, refund patterns, and sales notes to describe what the poor fit customer does and needs, rather than who they are.
How many negative personas do we need?
One or two usually cover the expensive patterns. If the list keeps growing, the real problem may be unclear positioning for your positive personas rather than a long list of people to exclude.