By 
Shreyas M V · Published · 14 min read
Positioning for Early-Stage SaaS: A Practical Method With Worked Examples
SaaS positioning comes down to four decisions in order: which alternatives the buyer uses today, what only you can do, what that is worth to them, and which customer group cares most. This page turns those decisions into a method, then works two invented companies through it to a finished positioning statement. The method is Kanso's assembly of two published frameworks, and the examples are illustrations, not results.
- Positioning is four decisions in order: the alternatives buyers use now, the attributes only you have, the value those create, and the segment that values it most.
- Start with alternatives, because “different” only means something against what the buyer would do otherwise, and that is often a spreadsheet.
- The positioning statement is the output, two or three sentences long, and it should pass a three-question test before it reaches a homepage.
- Both worked examples are invented to show the method. They are not results, and no source here measures whether any positioning framework improves growth.
What is SaaS positioning?
SaaS positioning is the choice of which alternative your product replaces, what it does that the alternative cannot, what that is worth to the buyer and which customers care most.
Market 8, a SaaS growth agency, separates it from brand positioning and clever communication. In its account, positioning is the strategic step that comes before straplines and web copy.
Powered by Search, another agency, says a tagline, a slogan or a unique value proposition is not positioning but comes out of it. That ordering is why the statement is written last on this page, even though it is the part people want first.
The reason it matters early is that a positioning gap can pass for a product gap. Powered by Search reports that startups often mistake one for the other and pivot the product or market when the real trouble was explaining what they do and who it is for. That is one agency's observation, not a measured rate.
What are the four steps of the method?
The method has four steps in a fixed order, alternatives, unique attributes, value and segment, and it ends in a positioning statement. The table gives the question each step answers, what it needs and where the step comes from.
| Step | The question | Input | Output | Draws on |
|---|---|---|---|---|
| 1. Alternatives | What does the buyer do today instead of buying you? | Buyer interviews, sales and support notes | A short list of real alternatives, with what each does well | Market 8: competitors and alternatives. Powered by Search: steps 2 and 7 |
| 2. Unique attributes | What can you do that those alternatives cannot, and show? | Product facts, engineers, customers' reasons for choosing you | Two to four attributes that are true today | Market 8: relievers and uniques. Powered by Search: step 4 |
| 3. Value | What does that give the buyer, and is it a top-two priority for them? | The buyer's priorities and blockers | One outcome in the buyer's words | Market 8: priorities, blockers, impact. Powered by Search: steps 1 and 2 |
| 4. Segment | Which customers feel that priority most and are cheapest to win and serve? | Your customer data, a four-question screen | One customer group to build the position for | Market 8: the customer and market-alignment check |
| Output | Can all of it be said in two or three sentences? | Steps 1 to 4 | A positioning statement, tested | Powered by Search: step 6 |
How the table was put together: Kanso read the Market 8 framework and the Powered by Search canvas, kept the steps that both ask for, and reordered them. Market 8 starts from the customer and Powered by Search starts from the buyer's desires, but this page starts with alternatives because the other three answers are judged against them.
alternatives → unique attributes → value → segment → positioning statement → test with the team
How do you know whether you have a positioning problem?
Ask everyone on the team three questions, who do you help, what problem do you solve and how does the product work, and read the gaps between the answers as the signal. Powered by Search uses these questions to diagnose its prospects and suggests sending them as a form to people in different roles, then comparing their answers with yours.
Two answers are warning signs in its account. A “who” that is too broad suggests a positioning problem, and a “problem” answer that jumps straight to describing the solution misses the point. The brevity of the answers is the tell.
- The team disagrees about the positioning, and the disagreement stalls any change.
- Prospects say they did not know your product could do something that is core to it.
- The answer to “who do you help” changes depending on who is asked.
The first two signs come from Powered by Search and the third is Kanso's reading of its test. None of this has been validated against outcomes, so treat the questions as a fast screen before you decide to rebuild the product.
Step 1: Which alternatives are you really replacing?
You are replacing whatever the buyer does today, which is often a spreadsheet, a manual routine or doing nothing, and not only the product that looks most like yours. Market 8 makes the point with a project management tool, where Excel counts as a competitor because it serves the user's need even though it was never positioned for it.
Powered by Search says the same about SaaS in general: most products offer a more elegant, efficient or effective way to do something that could be done in Excel or Google Docs. Market 8 gives the questions that surface the alternatives: how are you solving this today, how did you solve it before buying, and which alternatives did you consider?
Before launch you have no customers to ask, so put the same questions to prospects. That adaptation is Kanso's inference, since both sources assume you already have customers to talk to.
Powered by Search also tells you to open the homepages of your top five competitors and write down their taglines and value propositions. That shows how crowded the claim you are about to make already is. SaaSBoomi adds an optional chart: plot you and the alternatives on two axes that matter to buyers, such as price and quality, and look for empty areas.
The output is three to five alternatives, with one line each on what the alternative does well. The line on strengths is not politeness. A claim that ignores why the buyer still uses the alternative will fail the first time a prospect objects.
Step 2: What can you do that those alternatives cannot?
Your unique attributes are the few things your product does that the buyer's alternatives do not, that are true today and that you can show. Market 8 asks you to be realistic about what the product does, and says that honesty exposes gaps you can put on the roadmap instead of in the copy.
Powered by Search says the differences should be rooted in fact and recommends asking product owners and engineers how the product achieves its results differently. Its prompts cover strategy, structure, systems, shared values and style. Market 8 adds the customer's side: ask what they weighed when they chose you, and what they think you do better.
Kanso turns those into a filter. Keep an attribute only if it passes all three tests.
- True today. If it is on the roadmap, it is a plan, not an attribute.
- Absent from the named alternative. If the spreadsheet or the closest tool does it too, it is not a difference.
- Provable. You can show it in a demo, a document or a customer's own words.
Market 8's fictitious example, a tool called DATASYNC that logs sales reps' emails and meetings into a CRM, ends up with two: reliable access to enriched prospect data and transparent, bug-free data capture. Short lists like that are the point. Four proven differences beat ten claimed ones.
Step 3: What is the attribute worth to the buyer?
An attribute becomes value only when it relieves a blocker on something the buyer ranks as a first or second priority. Market 8 argues that if the problem you solve is not in the buyer's top two, the product gets ignored, and illustrates it with its soy sauce and letter-size paper test.
In that test, soy sauce is critical in a Chinese restaurant and trivial in a high school, while paper is the reverse. The same people can sit in either place, so context sets the priority. This is also the answer to the question “does my SaaS really matter to my users”: ask them to rank their priorities, then see where your problem lands.
Market 8 also ranks the reasons businesses buy SaaS. Cost reduction sits lowest, then efficiency and growth, which it calls user-led problems, and risk mitigation and entering new markets sit higher, which it says appeal to strategic buyers. Its Zoom example is a repositioning from efficiency toward risk and business continuity during the COVID-19 lockdowns.
State the value as an outcome in the buyer's words and trace it back. This is the chain to write down for each attribute you kept.
attribute → blocker it removes → priority it serves → outcome in the buyer's words
Powered by Search adds a cost to the chain, in steps 1 and 7 of its canvas: what staying put costs the buyer now, and what that cost becomes if they wait. Use it when the alternative is free, as a spreadsheet is, because the price of switching has to be set against something.
Step 4: Which customer group should the position be built for?
Build the position for the one customer group that feels the priority most and is cheapest to win and keep. Market 8 gives four screening questions: which group has the highest profits, which has the shortest sales cycle, which adopts the product fastest, and which costs least to serve.
Its answer to how to find out is plain: go back through your data and talk to the sales and customer success teams. Its fictitious DATASYNC ends up with a specific profile, sales reps in organizations of 20 salespeople who use LinkedIn and Salesforce and have a complex email setup. The specificity is what makes the position recognizable to the person it is for.
A segment that is too broad is the failure Powered by Search flags in the diagnosis test. It is also the easiest to commit, because every extra group sounds like extra revenue. The cost is a statement that no group recognizes as its own.
Pick one group now. If the product later serves several levels of buyer, Market 8 says to keep a through line between what users, managers and leaders each hear, and that work belongs after the first group is won.
How do you write the positioning statement and test it?
Write the statement in two or three sentences that name the segment, the problem, the alternative you replace and the attribute that makes the difference, then test it. Powered by Search caps it at two or three sentences and frames it as the answer to “that's why we…” after the earlier building blocks. SaaSBoomi asks for the unique value to be summarized in one clear sentence.
For [segment] who [problem], [product] is [what it is] that [value]. Unlike [alternative], it [unique attribute].
The template is Kanso's, built from the four steps. It is the same logic as the positioning field of Kanso's one-page marketing strategy, which is where this statement goes once it passes the tests below.
| Test | A pass looks like | Source |
|---|---|---|
| Three questions | Everyone on the team answers who you help, what problem you solve and how the product works in one sentence each, and the answers match | Powered by Search |
| Real alternative | The alternative named in the statement is one that buyers said they use, in their own interviews | Market 8 (interview questions) |
| Priority | The value is a first or second priority for the chosen segment, not a nice extra | Market 8 |
| Not a tagline | The statement explains the choice. The tagline comes afterwards and is shorter | Powered by Search |
| Segment recognition | Someone in the segment could read it and tell in ten seconds whether it is for them | Kanso's addition, not from a source |
This page does not list positioning statements from named real companies. The sources read for it do not supply any that could be checked, and an unchecked quotation would be worse than none. Powered by Search shows a filled-in statement for BoardOnTrack, a school board management platform for charter schools, and the full canvas is at its page.
Worked example 1: how does a vague draft become a specific statement?
It becomes specific by passing through all four steps, and Tallyboard shows how. Tallyboard is an invented product: a tool that reads a subscription business's billing export and flags the accounts likely to cancel. Every interview, ranking and number below is invented by Kanso for this page.
The first draft reads: “Tallyboard is the analytics platform for modern SaaS teams.” It fails the three-question test, because “SaaS teams” is too broad and no problem is named. The table runs the four steps.
| Step | Decision | Working |
|---|---|---|
| 1. Alternatives | Four alternatives: a monthly spreadsheet review of the billing export, the billing tool's built-in reports, a customer-success platform, and waiting for cancellation emails. | In the invented interviews, founders scan the export by eye once a month. The built-in reports show totals but not which account is at risk. The customer-success platform is the closest product, but it needs a CRM and a person to run it. |
| 2. Unique attributes | Keep two of four candidates: it works from the billing export alone, and it ranks accounts by cancellation risk each week. | Dropped: modern dashboards, because a buyer using a spreadsheet did not ask for one. Dropped: integrations with 40 tools, because only two exist today and the test is true now. |
| 3. Value | The founder sees which paying accounts to contact this week, before they cancel. | The priority is protecting recurring revenue. The blocker is learning about a cancellation after it happens. In the invented interviews, retention ranks first or second, behind shipping. |
| 4. Segment | Seed-stage subscription software with no customer success hire. | The screen below rejects the two neighboring groups, one for low profit and one for a long sales cycle and slow adoption. |
The segment decision rests on Market 8's four questions. No group wins all four, so the rule is to choose the one that is never the worst.
| Segment | Profit | Sales cycle | Adoption | Cost to serve |
|---|---|---|---|---|
| Solo founders, under 100 paying accounts | Low | Short | Fast | Low |
| Seed-stage teams, no customer success hire | Medium | Short | Fast | Low |
| Companies with a customer success team | High | Long | Slow | High |
The seed-stage group is medium on profit and strong on the other three. Solo founders are weak on profit, and companies with a customer success team are long, slow and costly.
The final statement: “For founders of subscription software with no customer success hire, Tallyboard is a weekly list of the paying accounts most likely to cancel, built from the billing export alone. Unlike a monthly spreadsheet review or a full customer-success platform, it needs no CRM and no setup project.”
Run the three questions on it. Who it helps: founders of subscription software without a customer success hire. The problem: not knowing which paying accounts are about to cancel. How it works: it ranks accounts from the billing export each week.
Worked example 2: what changes when the alternative is a spreadsheet?
Two things change: the interviews become the only source for the alternative, and the cost of staying put does more of the persuading. Rotawise is an invented rota tool for clinics, and as with Tallyboard every detail is made up to show the method.
| Step | Decision | Working |
|---|---|---|
| 1. Alternatives | A shared spreadsheet plus a group chat, a paper rota on the staff-room wall, and the rota module in an HR suite the clinic group already pays for. | No competitor homepage would have surfaced the spreadsheet. The invented interviews did. It is free, everyone can edit it and nobody has to learn anything, so the demo has to beat it honestly. |
| 2. Unique attributes | Keep two: it lists who is qualified and free to cover a sick day, and staff accept a shift in one tap. | Dropped: payroll integration, because it is not built. Dropped: shift-swap marketplace across clinics, because no interviewee asked for it. |
| 3. Value | The practice manager gets a sick day covered without a round of phone calls. | The priority is every chair covered on the day. The blocker is that a sick call at the start of the morning triggers calls to staff one by one. Left alone, the same morning repeats on every sick day. |
| 4. Segment | Independent dental clinics with one practice manager. | The first draft said small healthcare clinics. That fails the who-do-you-help question, because a dental practice manager and a physiotherapy clinic owner describe the problem differently. |
Rotawise's first draft claimed too much, so the statement went through three versions. Each failed a different test until the last.
| Version | Statement | Result |
|---|---|---|
| Draft 1 | Rotawise is the all-in-one workforce platform for healthcare. | Fails the segment test (healthcare is too broad), names no alternative and states no problem. |
| Draft 2 | Rotawise is a scheduling tool for clinics. | Names a category, not a problem. Any rota app could say the same. |
| Final | For practice managers at independent dental clinics who spend the start of the day phoning round to cover a sick call, Rotawise is a rota tool that lists who is qualified and free and lets staff accept the shift in one tap. Unlike a shared spreadsheet and a group chat, it finds the cover for you. | Passes all five tests in the table above, on the invented interview material. |
Observed in this walkthrough: the final draft names the person, the problem, the alternative and the difference, and it can be read in one breath. Inferred, not shown: that real clinics would respond to it. Only a test with buyers could say.
What do real cases show, and what is only our reading?
The published cases show that positioning shifts with the market and can fail by running ahead of it, but none of them measures the method on this page. The two lists keep what the sources document apart from what Kanso infers.
Documented, with the source in each line:
- SaaSBoomi, in an article titled for 2024, describes Dropbox's product as positioned on simplicity, automatic syncing and collaboration, and its company positioning as moving from consumer cloud storage to a workspace platform for individuals and enterprises.
- Market 8 reports that Zoom began with an efficiency proposition and repositioned during the COVID-19 lockdowns as a risk and continuity solution, followed by an 80% stock rise between January and April 2020. Market 8 states the figure, and this page has not verified it or tied it to positioning.
- The SaaS Club episode summary says Templafy's co-founder identified roughly 800 people mature enough for the conversation, sold a point of view before the product existed, and closed a Big Four accounting firm as first customer. The same summary says he is candid that the messaging got ahead of the market, and that being eighty percent ahead rather than fifteen percent cost conversations the company needed.
- Olivine describes a positioning engagement for TrueNorth with three workshops that produced personas and value propositions, a fourth on product naming, and a new homepage and two product pages. The case text reports no outcome figures.
- Powered by Search describes filling in its canvas for BoardOnTrack and reports no results.
Kanso's analysis:
- The Templafy account suggests that a position can sit too far from how buyers describe their own problem. Step 3, with its top-two priority check, is meant to catch that, although no source tests whether it does.
- The order of the four steps is Kanso's choice. Neither framework prescribes it.
- Four of the six sources are agencies that sell positioning, marketing or go-to-market services, so their view of how much positioning matters carries that interest.
- No source measures whether using a positioning framework improves pipeline or growth. The method is a structured way to make four decisions, not a proven growth lever.
- Both worked examples are invented, so they demonstrate the steps and nothing else.
When should an early-stage team revisit positioning?
Revisit it when something material changes, and bring in outside help only once you can say what you need decided. Olivine lists a product launch, a new market, more competition and slow growth from unclear differentiation as the triggers, and SaaSBoomi suggests a regular check such as quarterly.
SaaSHero, an agency whose page was last updated on 24 July 2026, describes the pre-seed and seed stage as one where the founder runs go-to-market, the first ten customers typically come from warm introductions, and the priority is validating the ideal customer and message. It lists boutique positioning consultants, fractional product marketers and single-channel paid specialists as fitting partners at that stage. It also sells month-to-month retainers, so read that as one agency's view.
The method needs one person and a couple of weeks. The schedule below is Kanso's suggestion and is not a sourced benchmark.
| When | Work | Output |
|---|---|---|
| Days 1 to 3 | Interview buyers or, before launch, prospects. Pull the segment data. Ask how they solve the problem today and what they considered. | A list of real alternatives and a ranked list of priorities and blockers |
| Day 4 | List every attribute you could claim. Cross out any that is not true today or that the named alternative also has. | Two to four attributes, each with its proof |
| Day 5 | Connect each attribute to a blocker and a priority. Cross out any that serve a priority outside the top two. | One outcome in the buyer's words |
| Days 6 and 7 | Run the four-question segment screen and write the first statement. | A draft statement |
| Week 2 | Send the three questions to everyone who talks to customers, compare the answers, then edit the statement until they match. | A tested statement on one page |
Set one stop rule before you start. If the chosen segment does not rank your problem in its top two priorities, change the segment or the problem before you change any copy, because better wording will not fix a position nobody prioritizes.
Once the statement stands, check that the homepage can back it up. Kanso's read of ten AI startup homepages scores each claim on how much evidence sits beside it, which is a fair test for a new statement. For a sourced company case in which positioning is one thread among several, there is Kanso's Zoho growth story.
SaaS positioning: frequently asked questions
What is SaaS positioning?
SaaS positioning is the choice of where a software product sits in a buyer's mind compared with the other ways they could solve the same problem. Market 8 describes it as the strategic step that comes before straplines and web copy, and SaaSBoomi defines product positioning as defining and communicating how a product fits the market and differs from competitors.
What is a positioning statement example?
A positioning statement is two or three sentences that name the segment, the problem, the alternative being replaced and the difference. This page's invented example reads: "For founders of subscription software with no customer success hire, Tallyboard is a weekly list of the paying accounts most likely to cancel, built from the billing export alone. Unlike a monthly spreadsheet review or a full customer-success platform, it needs no CRM and no setup project." Tallyboard is not a real product.
Why does positioning matter for an early-stage SaaS?
It matters because unclear positioning can look like a product problem. Powered by Search, an agency, says startups often mistake a positioning problem for a product-market fit problem and pivot when the real trouble is explaining what they do and for whom. Olivine, also an agency, says clear positioning helps buyers shortlist a product earlier and cuts objections, and neither claim is measured in the sources read here.
How do you differentiate your SaaS?
Differentiate by naming a difference that is true today, that the buyer's current alternative lacks, and that serves a first or second priority for a specific customer group. Market 8 adds that a product-led company stuck on a low-value problem such as cost reduction needs either a more dramatic difference from competitors or a move to a higher-value problem, such as risk, as its Zoom example shows.
Does my SaaS really matter to my users?
It matters if the problem it solves is a first or second priority for them in their own context. Market 8's soy sauce and letter-size paper test makes the point: soy sauce ranks high in a Chinese restaurant and low in a high school, and paper is the reverse, so the same product can be vital or ignored depending on the buyer.
Is a positioning statement the same as a tagline or value proposition?
No. Powered by Search says taglines, slogans and unique value propositions are not positioning but come from it, and Olivine describes a value proposition as a core component of positioning. Write the statement first, for internal use, then derive the shorter public lines from it.
What is the difference between product positioning and market positioning?
Product positioning is about one product and market positioning is about the company as a whole. SaaSBoomi's example is Dropbox, whose file storage and sharing product is positioned on simplicity and syncing, while the company's market positioning moved from consumer cloud storage to a workspace platform for individuals and enterprises.
How do I tell a positioning problem from a product-market fit problem?
Ask everyone on the team who you help, what problem you solve and how the product works, and compare the answers. Powered by Search uses those three questions as a diagnostic and treats an answer that is too broad, or a description of the solution instead of the problem, as a sign of a positioning problem. It is a quick check, not a proof, and a test with buyers is still needed.
How is B2B SaaS positioning different when several people buy?
It differs because users, managers and senior leaders care about different outcomes from the same product. Market 8 says to keep a through line between the groups and gives Slack as its example: an email replacement for users, better teamwork for managers and organizational performance at scale for leaders. For an early-stage team, pick the person who buys first and write the position for them.
Do I need a SaaS positioning agency?
Not necessarily, and the sources here are agencies, so weigh their view accordingly. SaaSHero says that at pre-seed and seed the founder still runs go-to-market and the job is validating the ideal customer and message, and that lightweight help such as a boutique consultant or fractional product marketer fits that stage. This page's method can be run without outside help, and the interviews it needs are yours to do.
How often should I revisit my positioning?
Revisit it when something material changes and on a regular schedule. Olivine lists launching a product, entering a new market, facing more competition and slow growth from unclear differentiation as triggers, and SaaSBoomi suggests a regular check such as quarterly.
Sources
- SaaS Positioning, Market 8
- B2B SaaS Positioning Canvas: Clarify Positioning with This Tool, Powered by Search
- Product Positioning Strategies in SaaS: What you should be doing in 2024!, SaaSBoomi (now AIBoomi)
- SaaS Positioning Strategy, SaaS Club podcast
- Brand Positioning Agency for B2B SaaS, Olivine
- Best B2B SaaS GTM Positioning Agencies for 2026, SaaSHero
Note: Facts are attributed to the six pages named in Sources, all written by companies, agencies or practitioners, and were checked on 19 October 2026. Tallyboard and Rotawise are invented, and every interview, ranking and figure about them is made up to show the method. Kanso has not tested these statements with buyers and has no affiliation with the companies cited.
Playbooks