Positioning Statement: What It Is and How to Fill In the Template
A positioning statement is a short internal sentence that fixes who your product is for, which category it competes in, what benefit it leads with and how it differs from the closest alternative. You write it for yourself and your team, not for the public. Its value is that every later choice, from features to launch channels to which comparisons to make, can be checked against it.
Is a positioning statement something customers see?
No, and that is what separates it from the pages around it. Customers see a tagline, a headline and a description. The positioning statement is the decision those were written from. It can be blunt in ways public copy cannot, for example by naming the competitor you are really up against or the group you have chosen to ignore.
Think of it as the answer to “what are we, to whom, instead of what?” Once that answer is written down, you stop arguing in circles about a feature request or a post idea, because you can ask whether it fits the statement. If you are a solo maker, the statement is how future-you keeps present-you honest.
What is the fill-in template?
The widely copied template has the shape below. It is usually credited to Geoffrey Moore’s book Crossing the Chasm, and many variations exist, so adapt it rather than guarding the wording. April Dunford’s book Obviously Awesome breaks the same job into related components: the alternatives customers have, your unique attributes, the value they create, the customers who care most and the category you claim.
For [target customer] who [statement of the need or opportunity], [product name] is a [product category] that [key benefit, the reason to buy]. Unlike [primary alternative], our product [primary difference that matters to this customer].
Each blank forces a choice. The target customer comes from your ICP. The category tells people how to file you, and filing you wrongly is expensive. The alternative must be what customers really use today. The difference must be something they care about, not something you are proud of.
What does a filled-in statement look like?
Take an invented tool, a code-review agent that reads a pull request and leaves comments on risky changes. This is an illustration only, written to show the reasoning behind each blank.
- Target customer: small teams of two to eight developers with no dedicated reviewer. They are chosen because large teams already have review habits and tooling.
- Need: pull requests sit unreviewed for days, or get a quick approval nobody trusts.
- Category: a review assistant, not a general coding agent. This keeps comparisons with the assistants developers already know and avoids a promise to write code.
- Benefit: a first pass on every pull request within minutes, flagging the three changes most likely to break something.
- Alternative: waiting for a teammate, or skipping review. Not another assistant. Naming this changes the pitch: the product is better than nothing, fast, not better than a senior engineer.
Read as one sentence: “For small teams with no dedicated reviewer who wait days for pull requests to be looked at, the tool is a review assistant that flags the riskiest changes within minutes. Unlike waiting for a teammate, it is there on every pull request.” The public tagline might become “A first reviewer for every pull request.” To see how other makers phrase an agent’s job in one problem sentence, read the AI agent ideas on the board.
What can a positioning statement settle for you?
| Decision | How the statement answers it |
|---|---|
| Which features come next | Does it serve the target customer’s stated need? If not, it waits |
| Where to launch | Where does the target customer already read? Pick those places first |
| What to compare yourself to | The named alternative, in your own copy and in replies |
| What to leave out of the listing | Anything that appeals to a customer you chose not to serve |
When you launch your product free, the statement tells you which sentence leads the description and which feature goes in the first screenshot. The public wording comes from the value proposition, and the shortest public form is the tagline.
When should you rewrite it?
Rewrite it when evidence contradicts a blank, not when you are bored of it. Three signals deserve a rewrite: your users turn out to be a different group than the one you wrote, people keep comparing you to a different alternative, or the category you claimed makes buyers expect something you do not ship. Keep old versions with dates. A trail of statements shows how your understanding moved, and it is a useful input to a launch retrospective.
The usual error is writing the statement in the abstract and never testing it. Say it aloud to three people in the target group. If they correct the category or the alternative, change the statement before you change the page.
Frequently asked questions
What is the difference between a positioning statement and a value proposition?
The positioning statement is an internal decision about who you serve, what category you are in and what you are better than. The value proposition is the public promise written from it. You write the positioning first, and several different public lines can come out of the same statement.
Does a solo maker need a positioning statement?
Yes, because a solo maker has nobody to catch drift. It takes twenty minutes to fill in and then settles questions about features, channels and comparison pages without a debate. It also makes outsourcing copy or asking for feedback easier, since you can hand over a clear target.
How long should a positioning statement be?
One or two sentences. If it needs a paragraph, you are still deciding what the product is. Long versions hide a missing choice, usually about the customer or the alternative. Cut until each blank holds one specific answer and no list of options.
Should I publish my positioning statement?
Normally no. It can name competitors and customers you decided not to serve, which public copy should not. Publish what comes out of it: the tagline, headline and description. Some makers share a simplified version in a build log, which is fine as long as it is accurate.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.