Startup Positioning: A 60-Minute Framework
Stop being compared to the wrong thing. Frame the category you own.
If prospects keep comparing you to the wrong product, you do not have a sales problem. You have a positioning problem.
A job-management app for plumbers that gets compared to a general to-do list will always lose on price. The same app compared to "the paper job cards and three phone calls it takes to close out a job" wins easily. Nothing about the product changed. Only the frame did.
Positioning is deciding that frame on purpose. This post walks through a one-hour working session, built on April Dunford's approach from her book Obviously Awesome, which treats positioning as a set of connected decisions rather than a slogan.
The five components
Dunford's framework breaks positioning into five parts, worked through in a specific order:
- Competitive alternatives. What customers would do if your product did not exist.
- Unique attributes. What you have that those alternatives do not.
- Value. What those attributes let customers achieve, with proof.
- Target customers. The characteristics of the people who care most about that value.
- Market category. The context you present yourself in, so the value is obvious.
The order matters. Most founders start with the category ("we are a CRM") and work backwards. Starting from alternatives forces you to see the product the way a buyer does.
The 60-minute session
Get the founders, and anyone who talks to customers, in a room or on a call. Bring notes from recent sales conversations and support tickets. Set a timer for each block.
Minutes 0–10: List the real alternatives. Not just competitors. Include spreadsheets, paper, a part-time admin person, "do nothing", and a general tool stretched to fit. For a chauffeur business looking at booking software, the true alternatives might be a shared calendar, WhatsApp messages with clients, and a whiteboard in the office. Write every one down.
Minutes 10–20: List your unique attributes. For each alternative, what can you do that it cannot? Be concrete: "drivers see the job, the flight number and the pickup sign name on their phone" rather than "better driver experience". Cross off anything a customer could get from an alternative without much effort.
Minutes 20–30: Turn attributes into value. For each remaining attribute, ask "so what?" until you reach something a business owner would care about. Drivers seeing flight details means fewer calls to dispatch, which means the owner stops being on the phone at 5am. Then note the proof: something a customer said, something you measured, something you can demonstrate in a two-minute demo.
Minutes 30–40: Describe who cares most. Look at the value list and ask which customers feel it most. Not a persona with a name and a coffee order; a set of characteristics you could screen for. "Operators running three to ten cars, doing airport transfers, with the owner still driving some jobs." These are the people for whom the value is obvious.
Minutes 40–50: Choose the category. Now pick the frame that makes that value obvious to that customer. You have three broad options:
| Option | When it fits | Risk | | --- | --- | --- | | Existing category, as-is | Buyers already search for it and your strengths match what they expect | You get compared on the category's standard checklist | | Existing category, with a twist ("booking software for chauffeur fleets") | Your strengths are real for a sub-segment | The sub-segment must be big enough | | New category | Nothing existing describes the value at all | You have to teach the market, which is slow and expensive |
For most early-stage small-business software, the middle option is the safe default. It borrows buyers' existing understanding and narrows it to where you win.
Minutes 50–60: Write it down and test it. Write a short positioning statement using the components in order:
"For [target customers] who currently [alternative], [product] is a [category] that [key value], because [unique attribute]."
For the chauffeur example: "For small chauffeur operators who run bookings through a shared calendar and messages, this is booking and dispatch software built for fleets under ten cars. Drivers get every job, flight detail and sign name on their phone, so the owner stops fielding calls from the road."
Then decide what you will test before your next session.
Testing positioning without guessing
A positioning statement is an internal document. What you test is how it shows up: your homepage headline, the first line of your listing, the opening of a sales call.
Good tests are ones where people have to do something:
- Swap the headline on your homepage or listing and watch whether the right people sign up or apply.
- Open sales calls with the alternative. "Most operators we speak to are running bookings through a shared calendar. Is that you?" If they say yes and lean in, the frame fits.
- Listen for who you are compared to. After a demo, ask "what would you use if you did not use this?" If the answer is still the wrong product, the frame is not landing.
A worked example for operators
Positioning is not only a builder's concern. If you run a small business and are choosing software, the same lens helps you read vendor pages. Ask what the vendor thinks you would use instead. A rostering tool that compares itself to enterprise workforce suites is aimed at a different buyer from one that compares itself to a paper roster on the fridge. The second one is more likely to fit a café with eight staff, whatever the feature lists say.
Common positioning mistakes
- Positioning for everyone. Broad positioning feels safer and sells worse. It makes you look like a weaker version of the market leader.
- Leading with features. Features are attributes. Customers buy value.
- Borrowing a category because it is popular. Calling a simple invoicing tool an "AI finance platform" invites comparison with products that do far more.
- Never revisiting it. Positioning should change when your product, your market or your best customers change.
Where early feedback sharpens positioning
The hardest part of the session is minutes 20–40, because proof and "who cares most" both need real customer input. If you do not have many customers yet, you are guessing.
LetsBeta gives you a way to get that input. You list your build, a person reviews it, and businesses apply to try it. Because you accept or decline each application, you can deliberately recruit the target customers from your positioning statement and see whether they respond the way you expect. Their end-of-trial reports tell you what worked, what broke, whether they would pay and at what price. Builder Max also shows demand per category and lets you request introductions to businesses that have opted in to being contacted; see pricing.
For the tools that feed this session, see Value Proposition Canvas and Beachhead Market. For positioning distilled into a single line, read How to Explain Your Startup in One Sentence.
Recap
Start with what customers would do without you. Find what only you can do, translate it into value, find who cares most, and pick a frame that makes it obvious. One focused hour gets you a first draft; real customers tell you whether it holds.