Positioning Statement: How to Write One for a Startup, With a Template and Examples
A fill-in positioning statement template, before-and-after examples that turn features into outcomes, how to write one before you have customers, and how to test it cheaply.
By Suren, Founder & Growth Strategist at Gufy · Published
A positioning statement is one or two sentences that say who your product is for, what problem it solves, what it is, the outcome it delivers and why it beats what the customer does today. For a startup, its main job is to force a choice: one customer, one problem, one reason to switch.
Think of it as a bridge. On one side is the customer's problem. On the other is your product. The positioning statement describes the bridge between them: why this person should walk across and use what you have built.
This guide gives you a template to fill in, shows how to turn a feature list into an outcome, covers what to do when you have no customers yet, and explains how to test the result before you build a website around it.
The template
The most widely used format comes from Geoffrey Moore's Crossing the Chasm. In plain form:
For [one specific customer] who [has this problem or need], [product name] is a [category the customer already understands] that [delivers this main outcome]. Unlike [what they use today], it [does this one thing differently].
Six blanks, each a decision:
| Blank | The question it answers | Common mistake |
|---|---|---|
| Customer | Who exactly is this for? | "Small businesses", "everyone who…" |
| Problem | What are they trying to get done that is hard today? | Describing your solution instead of their problem |
| Category | What will they compare you with? | Inventing a category nobody searches for |
| Outcome | What is better in their life or business afterwards? | Listing features |
| Alternative | What do they do now? | Naming only direct competitors and forgetting spreadsheets, paper and doing nothing |
| Difference | Why switch? | A difference the customer does not care about |
Positioning statement, value proposition and tagline
These are often mixed up. They are three layers of the same decision.
| Who reads it | Length | Job | |
|---|---|---|---|
| Positioning statement | Your team | One or two sentences | Decide who it is for and why they would switch |
| Value proposition | Customers | A headline and a line or two | Promise the outcome in the customer's words |
| Tagline | Customers | A few words | Be remembered |
Write them in that order. A tagline written before the positioning is settled is a guess with nice wording.
Sell the outcome, not the feature
This is where most early-stage positioning goes wrong. Founders describe what they built. Buyers want to know what changes for them.
A feature is what the product does. An outcome is what the customer gets. The quickest way to move from one to the other is to ask "so that what?" until you reach something the customer would say out loud.
| Feature-led | Outcome-led |
|---|---|
| "All your admin tools in one dashboard" | "Get back 12 hours a week you now spend on admin" |
| "AI-powered quoting module" | "Send a full quote in 20 minutes, not two days" |
| "Automated identity checks" | "Onboard a new client the same day" |
| "Real-time analytics" | "Know by Monday which campaign to stop" |
The outcome also changes how the price reads. A founder we spoke with had a modest monthly price and still found people hesitating. The page listed what the product handled (enquiries, jobs, quotes, invoices), and a visitor could fairly ask how that differed from any other tool. Now do the arithmetic for one specific customer. If the product gives back around 12 hours a week, and that customer's time is worth what they charge per hour, the saving each week is many times the monthly fee. Said that way, the price is a small share of a return. Said as a feature list, it is a cost.
Work out whether your customer wants time or money. For an owner working seven days a week, time is the outcome. For a business already paying for five separate tools, the outcome may be one cheaper bill. The same product needs a different statement for each, which is another reason to choose one customer first.
If you can express the outcome in hours or money, do, as long as the figure is one you can stand behind.
The feature the founder loves and the job the buyer has
Clayton Christensen's milkshake story is the best-known illustration. A fast-food chain trying to sell more milkshakes asked customers what they wanted and changed the product accordingly, with little effect. Watching who actually bought them showed that many were sold in the morning to commuters, who wanted something to make a long drive less dull and keep them full until lunch. The milkshake's job was the commute. Its competition was a banana, a bagel or a doughnut, not only the milkshake across the road.
Jobs to Be Done explains the idea in full, with the interview questions that uncover a job. Founders make the same mistake with features. A founder building an AI tool for lawyers led with a technical claim about accuracy. The features were good. The question we put to him was different: would that sentence make a busy lawyer, who bills by the hour, give up an hour to hear about it? The first job of your positioning is to get the right person into the room. Features are what you sell once they are there.
Two more lessons came out of that conversation:
- Check the feature against what the buyer wants. "Saves time on analysis" only works if the lawyer wants that time saved. Some will tell you the analysis is the part of the job they trained for.
- Watch the words that put up a wall. In a profession that has been burned by AI mistakes, leading with "AI" can lose the reader before you have said what changes for them. Lead with the change.
Where the user and the buyer are different people, write the statement for the one who decides. Our guide to the ideal customer profile covers how to separate the two.
The difficulty test: is it a must-have or a nice-to-have?
People do not switch for a small improvement. Your customer is already getting the job done somehow, without you. Changing costs time, money and the risk of looking wrong, so the new way has to be clearly better than the current one.
Here is the exercise we run with founders. Say someone has to get from A to B. They can walk, cycle, stand at the kerb and hail a cab, or book a ride on their phone. Ask them to rate how hard each option is, from 1 to 10.
They cannot answer until you say who is travelling and how far. For a fit student going a short distance, walking is fine. Make it a long trip for a student who cannot be late for a shift, and walking is a 10, cycling a 7, and hailing a cab perhaps a 4 or 5: they have to find one, hope one stops and pay whatever it costs. Booking from a phone, with the price known and the car coming to them, is a 1.
Three things follow:
- You cannot score a value proposition without a specific customer. The ratings change completely when the person changes.
- Ride-hailing won because it cut the difficulty of the next-best option by three or four points on that scale. That size of drop is what makes a product a must-have. A one-point improvement is a nice-to-have, and people do not switch for it.
- The alternatives set your price. What the customer pays for the current way, in money and effort, is the ceiling on what they will pay you.
Run the same exercise for your product: list what your chosen customer does today, rate each option, and see how far yours drops the number. If you cannot find a drop of three or four points for your whole market, narrow the customer until you can. A product that is slightly better for everyone is usually far better for someone.
How to write yours, step by step
- Pick one customer. The narrowest group you can name and reach. If you are choosing between several, What Is an ICP? has a scoring method.
- List what they do today. Include the unglamorous alternatives: a spreadsheet, an assistant, an agency, nothing at all. These are your real competition.
- List what you have that those alternatives lack. Features and capabilities, plainly.
- Turn each into an outcome. Use "so that what?" and keep the ones the customer would pay for.
- Choose the category. Use the words the customer would type into a search box. April Dunford's work on positioning is worth reading on this point: the category you choose sets what people expect and who they compare you with.
- Fill in the template. Then cut every word that is not doing work.
- Read it to someone in the target group. If they ask "so what does it do?", it is not finished. The reaction you are looking for is "that's me" or "that is exactly my problem".
If you have a few users already, ask each of them to describe the product in one sentence. When they all say the same thing, write that down, because it is your positioning in their words. When they say different things, look for what is common underneath.
Selling to more than one side? A marketplace needs a statement for each side. A site for short stays says one thing to people with a spare room (earn from it) and another to travellers (somewhere better to stay). Write them separately, then check that they describe the same product.
A worked example
Take an imaginary product: admin software aimed at "small businesses".
First draft
For small businesses who need to manage admin, AdminHub is an all-in-one platform that brings invoicing, scheduling and client records together. Unlike other tools, it is simple and affordable.
Every blank is vague. "Small businesses" covers millions of different companies, "manage admin" is not a problem anyone would describe, and "simple and affordable" is what every product says.
After narrowing to the industry the founder knows
For owners of physiotherapy clinics with two to ten staff who lose their evenings to rebooking, invoicing and chasing payments, AdminHub is practice-management software that gives them back about 12 hours a week. Unlike a mix of a booking app, a spreadsheet and an accounting tool, it handles a patient from first booking to paid invoice in one place.
It serves fewer people on paper. It is also the first version a clinic owner would recognise as being about them.
If you have no customers yet
Most guides assume you can ask your customers why they bought. Before launch, treat the statement as a hypothesis and collect evidence in this order:
- Start with the group you know. Founders who have worked in an industry can name its problems and reach its people. That is an unfair advantage. Use it. It has one catch: being close to a problem makes it look obvious, and what is obvious to you is not obvious to a stranger. Step back and describe it as an outsider would hear it.
- Interview five people who do not know you. Friends are polite. Strangers tell you whether the problem is real, what they use now and what words they use for it. Put those words into the template.
- Write two or three versions. Vary one blank at a time: a different customer, or a different outcome.
- Test them (next section).
Until a stranger pays, each version is a hypothesis. That is not a criticism of the idea. It is a reminder of what you know so far.
The SaaS idea validation playbook covers the interviews in detail, and Marketing Strategy for Pre-Seed Startups shows where positioning sits among the first marketing tasks.
How to test a positioning statement
A statement your team likes has not been tested. Three checks, cheapest first:
- The five-second test. Show the headline version to someone in the target group for five seconds, then ask what the product does and who it is for. If they cannot say, rewrite.
- Sales and demo calls. Open with the statement. Watch whether the prospect starts describing their own version of the problem. That is the reaction you want.
- A small ad test. Score your versions first if you have more than you can afford to test (ICE scoring takes minutes). Then run two or three versions as ads to the same audience, each to a matching landing page, and compare sign-ups or enquiries, not clicks. The aim is to learn which message works before you scale, so the spend should be modest and the test should run long enough to give a clear answer. Marketing Budget for a Tech Startup Without Revenue gives realistic ranges.
For Syntrico, a Meta campaign built around guide downloads was used first to find the angle buyers responded to, and only then was that angle taken to direct sign-up ads. The case study sets out the sequence.
Common mistakes
- Trying to cover every customer. A statement that fits everyone persuades no one.
- Shaping the problem to fit the product. It is tempting to build first and then look for a problem the product matches. Learn the shape of the problem, then cut the product to fit it.
- Leading with the feature you are proudest of. Lead with what the buyer gets.
- Ignoring "do nothing". Your most common competitor is the customer carrying on as they are.
- Superlatives. "Best", "leading" and "revolutionary" add no information.
- Treating it as copy. It is a decision. The website copy comes afterwards.
- Never revisiting it. Positioning should follow the evidence as it comes in.
Common questions
What is a positioning statement?
A positioning statement is one or two internal sentences that say who your product is for, what problem it solves for them, what kind of product it is, the main outcome it delivers, and why they should choose it over what they use today. It is a working document for your team, not a slogan for customers.
What is the difference between a positioning statement and a value proposition?
The positioning statement is the internal decision: which customer, which problem, which alternative you are replacing. The value proposition is the customer-facing promise that follows from it, usually the headline and first lines of your website. A tagline is shorter again and exists to be remembered, not to explain.
How do you write a positioning statement for a startup with no customers?
Write it as a hypothesis. Pick the one group you know best, interview five of them who do not know you, and use their words for the problem and the outcome. Fill in the template, then test it with a landing page or a small ad test before you treat it as settled.
How long should a positioning statement be?
One or two sentences, short enough to say aloud without notes. If it needs a paragraph, you are still trying to serve more than one customer or solve more than one problem.
How often should a startup change its positioning?
Review it whenever the evidence changes: after a round of customer interviews, when a different kind of customer starts buying, or when a new competitor changes what you are compared with. Early on that may be every few months. Changing it every week because one prospect said something is too often.
Where Gufy fits
Gufy works with SaaS and mobile-app startups on go-to-market strategy: choosing the first customer, working out the message, and testing it with real buyers through landing pages and paid campaigns before budget is committed. Many founders start with a growth workshop to settle positioning in a few sessions.
If you can describe what your product does but not why someone would switch to it, bring what you have.