Positioning
Statement Examples.
Ten worked positioning statements from B2B SaaS companies (Stripe, Linear, Figma, Datadog, HubSpot, Notion, Slack, Vercel, Airtable, Loom), each analyzed against April Dunford's positioning framework: what they say, what makes them work, what to copy.
By Daria Dovzhikova · Updated May 2026
Each example below has been reconstructed from the company's public positioning (homepage hero copy, sales decks, and analyst briefings as of mid-2026). The exact wording each company uses externally may differ; the underlying positioning is what matters. Use these as templates; don't copy verbatim. See the positioning framework for the methodology that produces these statements.
Stripe
Payments infrastructureFor developers who need to accept payments online, Stripe is the payments platform that lets you start with a few lines of code. Unlike legacy gateways that require enterprise contracts, Stripe is developer-first and self-serve.
Specific buyer (developers). Specific category (payments infrastructure). Specific differentiator (few lines of code). Direct contrast with alternatives (legacy gateways).
Linear
Product managementFor modern software teams, Linear is the issue tracker built for the next generation of software development. Unlike Jira's complexity, Linear is fast, focused, and beautiful.
Specific buyer (modern software teams). Specific category (issue tracker). Specific differentiator (speed + focus + design). Named competitor (Jira) without disparagement.
Figma
DesignFor design teams that collaborate, Figma is the collaborative design platform that runs in the browser. Unlike Sketch, which requires installation per-user, Figma is real-time multiplayer.
Specific buyer (design teams). Specific differentiator (real-time multiplayer in browser). Named competitor (Sketch) with specific weakness (installation friction).
Datadog
ObservabilityFor DevOps teams running cloud-native applications, Datadog is the observability platform that unifies metrics, traces, and logs in one product. Unlike point solutions (New Relic for APM, Splunk for logs), Datadog has the full stack.
Specific buyer (DevOps teams running cloud-native). Category-level differentiator (unification). Named competitors with their narrower scope.
HubSpot
Marketing automation / CRMFor small and mid-size businesses, HubSpot is the all-in-one growth platform that combines CRM, marketing, sales, and service. Unlike Salesforce, which requires expensive customization, HubSpot works out of the box.
Specific buyer (SMB). Bundle positioning (all-in-one). Direct contrast with Salesforce (cost + complexity). Speed-to-value claim.
Notion
Productivity / workspacesFor knowledge workers and teams, Notion is the connected workspace that combines notes, docs, wikis, and project management. Unlike Confluence, Notion is flexible and modular.
Broad buyer but bounded (knowledge workers). Unification position. Named competitor (Confluence) with its rigid-structure weakness.
Slack
Team communicationFor team-based companies, Slack is the messaging platform that replaces email for internal communication. Unlike email, Slack is real-time, searchable, and channel-based.
Specific buyer (team-based companies). Direct alternative (email) rather than a competitor — positioning as a category-creator.
Vercel
Frontend hostingFor frontend developers building Next.js, React, or Vue applications, Vercel is the deployment platform optimized for the modern frontend stack. Unlike AWS, Vercel ships in seconds without DevOps overhead.
Narrow buyer (frontend devs on specific frameworks). Specific differentiator (deployment speed). Named competitor (AWS) with specific friction (DevOps overhead).
Airtable
Database / spreadsheetsFor teams that outgrow spreadsheets but don't want a database, Airtable is the relational database that looks like a spreadsheet. Unlike Excel, Airtable handles relationships; unlike Postgres, Airtable doesn't require SQL.
Specific buyer (teams in the gap between Excel and Postgres). Dual alternative positioning. Specific differentiator (no SQL required).
Loom
Async videoFor distributed teams, Loom is the async video messaging tool that replaces meetings. Unlike Zoom, Loom is asynchronous; unlike email, Loom captures tone and screen context.
Specific buyer (distributed teams). Specific category (async video messaging). Dual alternative positioning against Zoom + email.
Four positioning frameworks compared
Every statement above reverse-engineers to one of four canonical frameworks. Pick the framework first; the statement falls out of the structure. Five axes that distinguish the four:
| Axis | Dunford | Moore | R. Martin | Trout & Ries |
|---|---|---|---|---|
| Structure | Competitive alternatives → unique attributes → value → best-fit customer → category | For (target) who (need), our product is a (category) that (key benefit). Unlike (alternative), our product (differentiator). | Where to play + how to win (5-question integrated cascade) | Own a single word/position in the prospect's mind |
| Signature exercise | List all competitive alternatives; find the unique attributes | Fill the elevator-pitch template; pick the right category bowling-pin | Run the 5-question Strategy Choice Cascade | Find what the category leader can't say; own the opposite |
| Output example | Master messaging doc + sales-narrative deck | One-paragraph elevator pitch in the template structure | 5-page strategy doc with linked choices | One-word brand position + supporting proof points |
| When it works best | Established product needing repositioning against new alternatives | Crossing the chasm from early adopters to mainstream | Multi-product companies needing aligned strategic choices | Category-creator or challenger brand with one big idea |
| Fail mode | Skipping customer interviews; positioning from internal hypotheses | Picking the wrong bowling pin (target segment) | Filling the cascade but never killing alternatives | Over-simplifying complex B2B products into one word |
Frameworks summarized from Dunford's Obviously Awesome, Geoffrey Moore's Crossing the Chasm, Roger Martin's Playing to Win, and Trout & Ries' Positioning: The Battle for Your Mind. Distinctions sharpened against 12 years of in-house positioning work at JetBrains, Lightrun, and Odigos.
By the numbers
One reference point that anchors why the examples above lean on a single methodology — modern B2B positioning is overwhelmingly downstream of one practitioner's framework.
Years of B2B positioning practice behind April Dunford's methodology — the most-cited modern positioning framework, applied across 100+ B2B SaaS engagements and the source of the structure most of the examples on this page reverse-engineer to.
April Dunford · 2026 →FAQ
What is a positioning statement?
A positioning statement is the one-paragraph distillation of a product's positioning. Standard format: 'For [target customer] who [need], [product] is the [category] that [unique value]. Unlike [alternative], we [differentiator].' The statement is the artifact produced by the positioning framework; it gets used as the master messaging doc that all external copy cascades from.
What makes a positioning statement effective?
Four traits. (1) Specific buyer: 'B2B SaaS companies' is not a buyer; 'small-team SaaS founders using Stripe' is. (2) Named alternatives: vague 'competitive products' gets ignored; named alternatives with specific weaknesses ground the differentiation. (3) One clear differentiator: trying to differentiate on 3-5 axes dilutes the message; pick one and lead with it. (4) Category clarity: a positioning statement that doesn't tell the reader what category the product is in fails the first test.
How do you write a positioning statement?
Run the positioning framework first (see /positioning-framework). The framework's outputs feed directly into the statement: competitive alternatives → 'Unlike...'; unique attributes + value → 'the [category] that [unique value]'; best-fit customers → 'For [target customer]'; market category → 'is the [category]'. The framework is the work; the statement is the output. Skip the framework and you'll write a positioning statement that sounds good but doesn't withstand sales conversations.
Should we name competitors in the positioning statement?
Yes, when the competitor is a real alternative the buyer is considering. Naming competitors gives the differentiation specificity and grounds the buyer's mental model. The risk is appearing to disparage; mitigate by being factual about the competitor's actual constraint (Sketch requires per-user installation; Salesforce requires customization; Jira is complex). Avoid negative editorializing; let the facts position you against them.
How often should we revisit our positioning statement?
Quarterly at minimum, plus after every product launch, every funding round, and every major competitive shift. Positioning drifts as the product evolves and the market matures. The most common dysfunction is treating positioning as a one-time exercise; quarterly retros catch positioning that's gone stale before it shows up in lost deals.
Writing yours?
Run the positioning framework first.
GTM Clarity ($5,000–$8,000) runs the full Dunford framework over 2-4 weeks, including discovery interviews and a master messaging doc. See services.
Take the diagnosticReady when you are.
Discovery calls are 20 minutes. First one's on me.