Anti Personas: Defining Who Your Product Is Not For
An anti persona describes the customer you deliberately do not serve: the one whose needs would distort the product, whose support costs eat the margin, or whose expectations your model cannot meet. Writing it down stops the slow drift of saying yes to everyone and building for no one.
What an anti persona actually decides
Every roadmap argument has a hidden customer. Teams invoke the user who needs the enterprise feature, the bargain hunter who needs the discount tier, the power user who needs total configurability. An anti persona names the customers whose requests get a respectful no, with reasons agreed before the argument starts.
For more on this, see this related guide and our earlier explainer on the same theme.
That clarity saves real money. Sales stops chasing accounts that will churn. Marketing stops attracting signups the product will disappoint. Support stops being the place where a positioning problem is paid for, ticket by ticket, by the hour.
Build it from churn and support data
Your anti persona already exists in your records: the churned accounts with the shortest lives, the support tickets with the worst ratios, the deals sales lost money winning. Interview a few if you can. The pattern usually resolves into one or two recognisable profiles with specific mismatches, not bad people.
Describe the mismatch, not a villain. The anti persona is a good customer for somebody: a business needing deep customisation in a product built for speed, a hobbyist in a tool priced for professionals. Framing it as fit keeps the exercise honest and the language usable in public.
Where the anti persona does work
In positioning, it sharpens the promise: built for teams like this, not for that. In pricing, it justifies floors and edition boundaries. In product reviews, it gives teams a shared citation for declining work, which ends debates faster than taste ever does.
Readers also found this companion piece from our archive useful.
Sales enablement may be the biggest win. A short guide to recognising the anti persona early, with kind disqualification language and a competitor suggestion where one genuinely fits better, returns hours every week and produces former prospects who speak well of you anyway.
Keep it current and keep it kind
Review anti personas when strategy shifts. A segment you could not serve at one scale may become attractive at another, and yesterday's exclusion can harden into a blind spot. Date the document, name its owner, and revisit it like any other positioning asset.
Never let it leak into contempt. The moment internal language mocks the excluded customer, it starts leaking into calls and copy. The anti persona is a boundary, and boundaries stated respectfully are a sign of a confident product, not a hostile one.
Frequently asked questions
How is an anti persona different from just having an ICP?
An ideal customer profile says who you target. An anti persona says who you actively exclude and why, including customers who can pay and want in. The exclusion is the useful part, because those are the decisions teams actually struggle with.
Should we publish our anti persona?
Publish the positioning version: who the product is built for and the use cases it does not cover. Keep the detailed internal version, with churn economics and support data, inside the company. Customers respect clear fit statements.
Can a startup afford to exclude customers?
Startups exclude by necessity already: limited support hours and roadmap space see to that. The anti persona makes the exclusion deliberate instead of accidental, which usually means excluding the expensive mismatches earlier and keeping more runway.
What if sales keeps selling to the anti persona?
That is a compensation and qualification problem, not a document problem. Align incentives so disqualifying early is rewarded, share churn cost data openly, and review anti persona deals in pipeline meetings until the pattern changes.