How to Build a Positioning Statement: Framework + Examples

In a Nutshell

A positioning statement is a two-sentence internal document that names your target customer, the problem they have, the alternative they use today, your product category, the benefit you deliver and the proof behind it. It keeps marketing, sales and product describing the same company, and it never goes on your homepage word for word. The most widely used template comes from Geoffrey Moore's Crossing the Chasm (1991), and the version circulating online has lost two of its most useful lines. This guide gives you six templates for different market situations, a six-step framework for filling each blank with evidence from your CRM and customer calls, six B2B SaaS examples, and before-and-after rewrites of weak statements.

A positioning statement is two sentences long and has still derailed more leadership offsites than the seating chart. Every blank forces a decision someone has been avoiding, like which customers you're willing to disappoint or which competitor you'll finally admit exists. Below are the templates, the framework for filling them in, and enough examples to steal from. If you haven't done the underlying positioning work yet, start with our guide to B2B SaaS positioning and come back with your answers.

Positioning Statement Definition and Purpose

A positioning statement is a short internal document, usually two sentences, that records your positioning decisions in a fixed format. It names who the product is for, what problem they have, what they use today, which category you belong to, what you do better and why anyone should believe you. Teams use it as the reference point for homepage copy, sales decks, agency briefs, ad targeting and even roadmap debates. Customers should never see it in its raw form.

The case for writing it down comes from how B2B buying works now. Gartner surveyed 750 B2B buyers and found they spend only 17% of their buying time meeting with suppliers, and that time is shared across every vendor on the shortlist, so if you're one of three you get roughly 5%. Everything else happens on your website, on review sites, in AI search answers and in internal meetings where your champion tries to explain you to a CFO. A positioning statement makes sure your marketing team, your SDRs and your agency are all writing from the same two sentences, so those conversations you're not in still hear one consistent story.

Positioning statement vs value proposition, tagline and mission statement

These four get mixed up constantly, mostly because they all fit on a sticky note. Here's how they differ, using a made-up finance tool as the example.

The positioning statement comes first because the other three get written from it. Our breakdown of messaging vs positioning covers how the statement turns into homepage copy and sales talk tracks.

Geoffrey Moore's Original Positioning Statement Template

The format nearly every template online borrows from comes from Crossing the Chasm, which Geoffrey Moore wrote after years at Regis McKenna Inc., the Silicon Valley firm behind early marketing for Apple and Intel. Moore called it the elevator test, meaning you should be able to state your claim in the time an elevator takes to reach its floor. In 1991 that was a figure of speech. Today it's roughly how long a buyer gives your homepage before opening a competitor's tab.

Here's the template as it appears in the book.

Compare that with the version on most blogs and strategy decks, which reads "for [target customer] who [need]" and ends with "our product [primary differentiator]." Two details got lost in the copying, and both change how good your statement turns out.

The "beachhead segment only" line

Moore meant one narrow segment you can dominate, chosen on purpose, and he was insistent about picking one and only one. A statement that opens with "For SMBs and enterprises across industries" fails at the first line. In SaaS terms, a beachhead might be "Series B fintechs preparing for their first SOC 2 audit," which is small enough to win and specific enough that a reference from one customer persuades the next one.

The "whole product" line

Moore's last line asks you to list everything the buyer needs for the product to work in their world, including integrations, onboarding, migration help, compliance paperwork and partner support. Mainstream buyers, whom Moore called pragmatists, want proof that your product will work alongside everything they already run. In B2B SaaS, that means SSO, the Salesforce sync, the SOC 2 report and the implementation partner who has done this forty times. If your differentiator line talks only about your AI model, a pragmatist will pick the vendor that looks safer to buy.

One warning before the templates. April Dunford, author of Obviously Awesome, has argued for years that the fill-in-the-blank statement is dangerous as a starting point, because it assumes you already know the answers. She's right. A template records decisions and can't make them for you. Use the six-step framework further down to find each answer, then use a template to write it down.

6 Positioning Statement Templates for B2B SaaS

Each template suits a different market situation. To show how they differ, we'll fill every one in for the same made-up product, Tallybird, a billing reconciliation tool for SaaS finance teams that charge customers based on usage. Same product, six angles.

1. Classic positioning statement template (Moore format)

Best for: internal alignment, onboarding new hires and briefing agencies. If you only write one statement, write this one.

2. Reason-to-believe template (Kellogg format)

For [target customer], [product] is the [frame of reference] that [point of difference] because [reason to believe].

This one comes from the brand positioning model taught at Northwestern's Kellogg School of Management, which builds positioning on four elements: target, frame of reference, point of difference and reason to believe. Their textbook example is Miller Lite, where the target was men aged 21 to 34, the frame of reference was beer, the point of difference was "less filling" and the reason to believe was fewer calories. Beer companies were writing tighter positioning than most SaaS homepages decades before anyone said "AI-native."

For finance teams at usage-billed SaaS companies, Tallybird is the billing reconciliation tool that stops revenue leakage before month-end, because it matches every single usage event to an invoice line automatically.

Best for: crowded categories where buyers have heard every claim twice. The "because" clause makes it very hard to sneak a parity claim through.

3. Status quo positioning statement template

For [target customer] who currently [workaround], [product] is a [category] that [outcome]. Unlike [the workaround], [product] [differentiator], so [the cost of staying put] goes away.

Use this when your biggest competitor is a spreadsheet, an agency, a junior hire or the classic "we'll deal with it next year." Spreadsheets have the "this is fine" dog energy of B2B software, and your statement has to make the fire visible.

For SaaS finance teams who reconcile usage billing in spreadsheets every month-end, Tallybird is a billing reconciliation tool that finds unbilled usage automatically. Unlike the spreadsheet only one analyst fully understands, Tallybird checks every event every day, so revenue leakage stops being something you discover during the audit.

Best for: early-stage products, and any team whose lost-deal report is mostly "no decision."

4. Big fish, small pond template

[Product] is the [existing category] built for [specific segment], who need [segment-specific requirement] that general-purpose [category] tools treat as an afterthought.

Dunford describes three positioning styles: head-to-head (win the existing category), big fish in a small pond (win a segment the leader underserves) and create a new game (win a category you invent). This template is the second style, and it's where most B2B startups facing a well-funded leader end up. Linear against Jira, which we covered in our B2B SaaS positioning examples, is this template in action.

Tallybird is the billing reconciliation tool built for SaaS companies on usage-based pricing, who need event-level matching that general-purpose reconciliation tools, designed for fixed monthly subscriptions, treat as an afterthought.

Best for: startups that can't outspend the category leader but can out-specialize it.

5. Category creation template

[Change in the market] means [old approach] no longer works for [target customer]. [Product] is the first [new category], which [benefit] by [mechanism].

This is the "create a new game" style, and it borrows from strategic narrative by opening with a shift in the world before mentioning the product.

Usage-based and AI credit pricing mean month-end reconciliation can no longer keep up with how SaaS companies bill. Tallybird is the first revenue assurance platform for usage-billed SaaS, which stops revenue leakage as it happens by checking every billable event against what the customer was charged.

Best for: products that no existing category can describe without misleading buyers. It's also the most expensive template to live up to, because you're paying to educate a market that doesn't know it needs you yet.

6. Jobs-to-be-done positioning statement template

When [triggering situation], [target customer] hire [product] to [job], so they can [outcome], instead of [current alternative].

When a usage-billed SaaS company's first audit flags revenue it can't explain, finance teams hire Tallybird to reconcile every billable event automatically, so they can close the month without a two-day spreadsheet hunt, instead of hiring another analyst.

Best for: product and growth teams. The trigger in the first line doubles as a targeting signal, which makes this version handy for planning demand generation campaigns around moments when buyers are in-market.

Which positioning statement template to use

Plenty of teams keep a classic Moore statement as the master version and a jobs-to-be-done version for campaign planning. They should say the same thing from different angles. If they contradict each other, one of them is wrong.

How to Write a Positioning Statement in 6 Steps

Templates are the easy part. The work is filling each blank with something you can prove, and this framework maps every slot to a data source you already own.

1. Build an evidence sheet before writing a word

Open a doc and answer each question below from real data, before anyone opens a template.

Write the statement in your customers' words. If interviews keep saying "month-end" and your deck says "financial operations lifecycle," the interviews win.

2. Define the target customer by trigger and situation

"Series A to C SaaS companies with 50 to 500 employees" describes thousands of companies, most of whom will never care about you. Add the situation that makes someone care, like "SaaS companies that just moved to usage-based pricing." That's Moore's beachhead rule applied to a CRM filter.

A quick test is to ask whether a sales rep could use your "for" line to disqualify a lead. If every inbound demo request passes, the line is too broad.

3. Name the alternative buyers use today

"Unlike legacy solutions" is the generic villain of B2B, and no buyer in history has described their current setup as a legacy solution. They say "a spreadsheet," "our agency," or "something we built in-house in 2019 before the person who wrote it left." Search your call transcripts for phrases like "right now we," "currently" and "before this," then rank the alternatives by how often they show up in lost deals.

The answer can surprise the people who should know it best. At a 2026 product conference, Dunford described a workshop where she asked a room what customers would do if the company didn't exist. The CPO said customers would vibe-code a replacement, and the head of sales had never heard of the AI app builders they'd use to do it. If your own leadership team can't agree on the alternative, your statement isn't ready.

4. Choose a category buyers already understand

The category line sets your comparison set, your price anchor and the feature checklist buyers bring to the demo. If a buyer hears your category and has to ask "so what is that?", you've picked a clever label over a useful one. Dunford's rule of thumb is that it's "always better to be a little boring than completely baffling," and buyers agree with her every time they bounce off a homepage that calls itself an "intelligence fabric."

Check how G2 and Capterra list you and your competitors. If none of the existing categories fits without misleading buyers, go back to template 5 and budget for the education it needs.

5. Turn the differentiator into a benefit with proof

Run every capability through the "so what?" chain until you reach something a buyer would say in a budget meeting. "Event-level matching" leads to "catches every unbilled event," which leads to "recovers revenue you were already owed." The last version is the one that belongs in your statement.

Then attach a reason to believe. Good proof is a number from your product data, an architecture choice competitors can't copy quickly, a certification or a named integration. If the best proof you have is "our team is passionate," keep digging.

6. Stress-test the statement with four checks

Once it passes, cascade it into your homepage, sales deck, content marketing strategy and the rest of your full-funnel marketing plan, in that order.

Positioning Statement Examples from B2B SaaS Companies

Companies rarely publish their internal positioning statements, so the examples below are our reconstructions in Moore's format, based on the positioning each company used while it was breaking out. Each one comes with the detail that made the positioning work.

1. Slack positioning statement example

For teams whose internal communication is buried in email threads, Slack is a team messaging platform that organizes conversations by project in searchable channels. Unlike email, Slack keeps a team's history open to anyone who joins later, so answers stop living in individual inboxes.

On July 31, 2013, two weeks before Slack's preview launch, its CEO sent the team a memo titled "We Don't Sell Saddles Here." The argument was that Slack sold a reduction in information overload and a change in how organizations work, with messaging as the mechanism. The early pitch was equally blunt, promising that teams would know Slack was working when they stopped using email at work. The memo went public in 2014 and is still passed around product marketing teams like a family recipe.

What to take from it: position against the behavior your product replaces, and the category takes care of itself.

2. Figma positioning statement example

For product teams where designers, PMs and engineers all need to work in the same file, Figma is a browser-based interface design tool that lets everyone edit and comment in real time. Unlike desktop design tools that pass files around by email, Figma keeps one live file in the browser that anyone can open on any machine.

Sketch, the category leader when Figma launched in 2016, ran only on macOS, so the PMs and engineers on Windows laptops couldn't even open the design file. Figma's browser-first architecture turned that constraint into the "unlike" line. The positioning worked well enough that Adobe agreed to buy Figma for $20 billion in 2022. Regulators in the UK and EU objected, the deal was abandoned in December 2023, and Adobe paid Figma a $1 billion termination fee for the trouble.

What to take from it: when your architecture removes a constraint buyers have learned to live with, name the constraint.

3. Calendly positioning statement example

For professionals who book meetings with people outside their company, Calendly is a scheduling tool that lets invitees pick an open slot from a single link. Unlike back-and-forth emails, Calendly books the meeting in one step and never double-books your calendar.

Calendly found early traction with teachers scheduling parent-teacher conferences, and it raised just $550,000 before a $350 million round in January 2021 valued it at $3 billion. The positioning did much of the distribution work, since every person who booked through someone's link saw the product solve the problem in real time.

What to take from it: when the alternative is an annoying habit, put the habit in your statement.

4. Vanta positioning statement example

For startups that need a SOC 2 report to close enterprise deals, Vanta is compliance automation software that continuously collects audit evidence from the tools you already use. Unlike consultants and spreadsheets full of screenshots, Vanta monitors your security controls automatically, so the audit becomes a checkpoint instead of a months-long project.

Vanta's founder started the company in 2018 after going through SOC 2 firsthand while leading Dropbox Paper, at a time when plenty of people doubted startups needed SOC 2 at all. Vanta tied the report to the enterprise contract it was blocking, which turned a compliance chore into a revenue problem, and revenue problems get budget.

What to take from it: connect the problem to the deal it's holding up.

5. Loom positioning statement example

For distributed teams that lose hours to status meetings, Loom is an async video messaging tool that records your screen and camera in one click. Unlike live meetings, Loom lets you explain something once and lets everyone else watch on their own schedule.

Atlassian bought Loom for $975 million in 2023, when it had more than 25 million users recording roughly 5 million videos a month. Loom's "unlike" line named an enemy that nobody defends with much conviction, the meeting that could have been an email.

What to take from it: the best alternative to position against is one your buyers already resent.

6. Notion positioning statement example

For teams juggling separate tools for docs, wikis and project tracking, Notion is a connected workspace built from blocks that any team can rearrange into its own tools. Unlike stitching three apps together, Notion keeps notes, knowledge and tasks in one place without writing code.

In 2015, Notion's founders scrapped their code, laid off their small team and moved from San Francisco to Kyoto, where living costs were less than half, to rebuild the product from scratch. The block-based architecture that came out of that rebuild became the reason to believe behind the "one workspace" claim.

What to take from it: an all-in-one claim needs an architecture that makes it believable, or buyers will assume it does everything badly.

Before and After Positioning Statement Rewrites

Weak statements tend to fail in the same few slots. Here are three common patterns, rewritten using made-up products.

The "everyone is our customer" statement

Before: For businesses of all sizes looking to improve productivity, Flowdesk is an AI-powered platform that helps teams work smarter. Unlike legacy solutions, Flowdesk is intuitive and scalable.

What's broken: there's no segment, no specific problem and no real alternative, "platform" tells the buyer nothing, and "intuitive and scalable" is a claim every competitor already makes.

After: For support teams at B2B SaaS companies whose agents answer the same setup questions all day, Flowdesk is a help desk that drafts replies from your product docs and past tickets. Unlike generic canned responses, Flowdesk's drafts cite the help doc they came from, so agents approve answers in seconds and write only the new ones.

The feature-list statement

Before: For marketing teams, Beacon is an analytics tool with real-time dashboards, 200+ integrations, custom reports and AI insights. Unlike competitors, Beacon offers more features at a lower price.

What's broken: it lists features with no benefit attached, and "more features at a lower price" invites a race to the bottom that the bigger competitor wins.

After: For B2B marketing teams who can't tell which channels create pipeline, Beacon is a marketing attribution tool that connects ad spend to closed revenue in your CRM. Unlike web analytics tools that stop counting at the form fill, Beacon follows each account through to closed-won, so you can defend your budget with revenue numbers instead of lead counts.

The accidental category creation statement

Before: For forward-thinking enterprises, Nexora is the world's first Cognitive Revenue Orchestration Cloud that unlocks the future of growth.

What's broken: buyers can't place it, there's no alternative and no proof, and if your category needs a glossary, buyers will file you under "confusing" and close the tab.

After: For RevOps teams at mid-market SaaS companies who maintain lead routing rules by hand, Nexora is a lead routing tool that assigns every inbound lead to the right rep in seconds. Unlike routing built on CRM workflow rules, Nexora updates itself when territories and headcount change, so RevOps stops rebuilding routing every quarter.

Positioning Statement Do's and Don'ts

Do:

Don't:

Get Help Writing Your Positioning Statement

If your leadership team can't agree on the "unlike" line, that disagreement is the most useful conversation you'll have this quarter. At Keewee, we run positioning work with B2B SaaS teams by digging through won and lost deals, interviewing your best customers and writing the statement your sales, product and marketing teams all sign off on, then building the messaging on top of it.

Talk to us. We can help.

FAQs

1. What is a positioning statement?

A positioning statement is a short internal document, usually two sentences, that defines who your product is for, what problem it solves, what category it belongs to, what alternative it replaces and why it's better. Teams use it to keep marketing, sales and product aligned. It guides external copy but is not published word for word.

2. What are the key elements of a positioning statement?

A positioning statement has six elements: the target customer, the problem or need, the product category, the key benefit, the main competitive alternative and the differentiator or proof that backs up the claim. Geoffrey Moore's template also includes the "whole product" features, such as integrations and support, that make the product safe for mainstream buyers to adopt.

3. How long should a positioning statement be?

A positioning statement should be two sentences and short enough to read aloud in about 30 seconds. If it needs a third sentence, you're usually covering more than one segment or listing features instead of a single benefit. Split it into separate statements per segment rather than stretching one.

4. What is the difference between a positioning statement and a value proposition?

A positioning statement is internal and describes your target customer, category, alternative and differentiation. A value proposition is external and promises a specific outcome to the buyer, such as "close the books three days faster." The value proposition is written from the positioning statement, so the statement has to exist first.

5. Should you publish your positioning statement on your website?

No. The format is built for internal clarity and reads awkwardly as customer-facing copy. Use it as the source for your homepage headline, product pages, sales deck and ads, where the same decisions get expressed in language written for buyers.

6. How often should you update a positioning statement?

Update a positioning statement when something structural changes, such as a new well-funded competitor, a shift in who's buying, a pricing model change or a major product expansion. Many SaaS teams also review it once a year. Avoid changing it just because the team is tired of it, since buyers take much longer to absorb positioning than internal teams do.

7. Can a startup write a positioning statement before product-market fit?

Yes, as long as the team treats it as a hypothesis. Write it from early customer conversations, test it in sales calls and on landing pages, and rewrite it once closed-won data shows which customers get the most value. The first version is rarely the final one, and that's expected.