Every company already has a position. It just accumulated.
A bit from the first pitch deck. A bit from the three customers who happened to say yes early. A bit from whatever you said in the last investor meeting because it landed well that day. None of it was wrong exactly. It just wasn't decided by anyone.
The cost is quiet and constant. Two people describe the company differently in the same week. A buyer files you in the wrong category and starts comparing you to companies you'd never worry about. A designer asks what makes you different and gets a feature list back.
Five decisions, in order
This is April Dunford's sequence, from Obviously Awesome. We use it because it's the clearest version anyone has written down, and because working out of order is the single most common way positioning falls apart.
- Competitive alternatives. What your buyer would genuinely do if you didn't exist.
- Unique attributes. What you have that those alternatives don't. Provable, not stylistic.
- Value. What those attributes let a buyer do that they couldn't before.
- Best-fit customer. Who cares disproportionately, and what situation they're in when they care.
- Category. The frame that makes all of the above obvious.
Each depends on the one before it. Then compress it with Neumeier's onlyness statement: we are the only ___ that ___. If a competitor's name fits in the blank, you haven't finished.
"We're the only AI-native platform built for modern revenue teams."
Three vague words doing the work. AI-native describes a technology choice. Modern means nothing. Revenue teams is everyone. A competitor could sign this.
"We're the only close-management tool that works without a controller on staff."
Narrow, checkable, and it excludes people. That last part is the point. It will feel too small when you write it. Write it anyway.
Start with what they'd do without you
The first decision is the one people get wrong most often, and getting it wrong throws off everything downstream.
Your competitive alternative usually isn't another vendor. It's a spreadsheet someone maintains. An internal tool built by an engineer who has since left. A manual process nobody loves. Most often, doing nothing and living with the problem.
Write those down even when they're unflattering. "They keep using the spreadsheet" is a real answer, and it tells you your actual job is beating inertia rather than beating a competitor.
Then list every capability the alternatives lack. Go long first, twenty items is fine. Turn each into value by asking "so what?" until you reach something a buyer cares about. Real-time sync becomes your team stops arguing over stale numbers becomes your Monday meeting gets shorter. Somewhere in that chain is the sentence worth keeping.
Pick your category last
This is the highest-leverage decision in the exercise and the one everyone reaches for first, because it's the fun one.
Category is the frame that makes your value obvious. Get it right and your strengths look inevitable. Get it wrong and you spend every sales call explaining why the usual comparison doesn't apply.
You can't choose it well until the other four are settled, because the right category is the one that puts your specific value at the centre. Choose early and you lock yourself into a frame built around whichever strength you happened to think of first.
When all five are done, write it as one page. Not a slogan. A document your team can argue with, because they will, and the arguing is where it gets good.
Teardown
Linear
Linear entered a category with Jira in it. That's a bad fight on features.
So they didn't take it. Karri Saarinen has described starting with quality and then discovering people noticed, because it's rare for startups to lead with that. The positioning wasn't "a better issue tracker." It was closer to "the tool for teams who care how software gets built."
Look at what that does to the five decisions. The alternative isn't just Jira, it's Jira plus the resignation of teams who assumed all tools are joyless. The unique attribute is craft, which is provable the moment you open the app. The value is a team that doesn't dread its own workflow. The best-fit customer is a specific kind of engineering culture. And the category shifts from issue tracking to something about how good teams work.
Same product category. Completely different frame. That's what choosing the category last buys you.
What you leave with
What you now have. A one-page positioning document and an onlyness statement that a competitor's name doesn't fit into.
The test. Tell it to someone outside your company. Wait a week. Ask them to describe what you do. What comes back is your actual positioning, regardless of what you wrote down.
Where this usually goes wrong. Filling in a template and calling it done. Dunford is blunt that a positioning statement is a way to write positioning down, not a substitute for the thinking. A confident sentence with nothing underneath is worse than no sentence, because it stops the conversation.
What it takes. A week of focused work. Three to five people helps, ideally someone from sales and someone from product. If you're alone, write the strongest case against each decision and see if it survives.
