Positioning Statement Generator: A 4-Step AI Framework

Most failed startups had a real market need. They just couldn’t explain why anyone should pick them over the alternative.

A positioning statement fixes that. One sentence that nails four things: who it’s for, what category it sits in, how it’s different, and why that claim is believable. April Dunford calls positioning “the context that determines how a customer perceives your product.” Without it, marketing, sales, and product tell three different stories about the same thing.

The old way of building positioning takes weeks — workshops, stakeholder interviews, rounds of revisions. AI compresses this to 30 minutes by handling the analytical grunt work that used to require a consultant.

Here’s a 4-step framework with prompts for each stage.

What a Positioning Statement Is and Why You Need One

A positioning statement pins down where your product sits in the customer’s head. Geoffrey Moore laid out the classic structure in Crossing the Chasm:

For [target audience]
who need [key need],
[product] is a [category]
that [key differentiator].
Unlike [alternatives],
our product [proof point].

Six components. Each requires actual research. What happens instead: teams fill in the template from gut feeling and end up with something like “For businesses that need an effective solution, X is a platform that helps them grow faster.” That positioning could describe literally any SaaS product ever built.

Don’t confuse this with a tagline. A tagline talks to customers (“Just Do It”). A positioning statement is an internal document — it drives website copy, the investor pitch, sales scripts, cold outreach personalization, and ad campaigns.

Without it, every department tells a different story. Marketing sells an “AI platform,” sales pitches “process automation,” product builds “an analytics tool.” The customer hears three contradictory messages and trusts none of them.

The Framework: 4 Steps to a Positioning Statement

Step 1. Define the Target Audience Through Competitor Analysis

Most teams start with the product. Wrong move. Positioning starts with the audience — not demographics (“50–200-person SaaS companies”), but behavior. What are these people doing right now to solve the problem? That’s the real starting point.

April Dunford recommends working backwards: find your best existing customers, figure out what alternatives they considered, and build from there.

Prompt for audience analysis:

You are an expert in product positioning (April Dunford framework).

Product context:
- Name: [name]
- Description: [what the product does, 2–3 sentences]
- Current customers: [who's already using it, if any]
- Problem it solves: [the specific problem]

Task: identify 3 target audience segments that get the maximum value from this product.

For each segment, specify:
1. Role and context (not demographics, but situation and responsibility)
2. What they are doing NOW to solve this problem (specific alternatives: manual process, competitor, Excel, outsourcing)
3. Why their current solution isn't working (friction points)
4. What trigger will make them look for a new solution
5. How they would describe the ideal solution in their own words (verbatim style)

Format: structured analysis. Avoid marketing clichés. Use the language real people use to describe their problems.

Example: before and after

Before (intuitive): “Our audience is small and medium businesses that need marketing automation.”

After (with AI analysis): “Head of Growth at B2B SaaS companies with $1–10M ARR, who manually assembles reports from 5 tools every Monday and spends 6 hours a week on dashboards instead of running acquisition experiments.”

The difference is night and day. The second version gives you a real person with a real problem doing a real thing every Monday. You can write a landing page from that. You can’t write anything useful from “small and medium businesses.”

Choosing a segment. AI will suggest 3 options. Pick the primary one based on: (1) who’s already buying or showing the most interest, (2) who has the sharpest pain, (3) who’s willing to pay. No customer data yet? Go with whoever’s pain is most acute.

Step 2. Define the Category and Competitive Context

Category is the answer to “what is this?” It sets a baseline of customer expectations. CRM means there are contacts, deals, a pipeline. Project management tool means tasks, deadlines, a kanban board.

The category you choose determines your competitors. “AI marketing platform” competes with HubSpot and Jasper. “Marketing analytics tool” competes with Mixpanel and Amplitude. Different categories, different competitors, different expectations.

Three category positioning strategies:

1. Head-to-head. Enter an existing category and win on a specific parameter. “CRM for startups” — like Salesforce, but simpler.
2. Subcategory. Create a subcategory within an existing one. “AI-first CRM” — narrow focus, clear context.
3. New category. Create a new category. The riskiest path: you have to explain not just “why us,” but “why this exists at all.”

Prompt for category analysis:

You are a product positioning strategist.

Product: [name]
Description: [what it does]
Target audience: [result from Step 1 — paste the chosen segment]

Task: analyze category options for positioning.

For each option (suggest 3–4):
1. Category name
2. Strategy (head-to-head / subcategory / new category)
3. What expectations this category sets for the customer
4. Top-3 competitors in this category
5. Main advantage of this positioning
6. Main risk

Then give a recommendation: which category is optimal for the current stage of the product and why.

Criteria:
- The customer should instantly understand what this product is
- The category should highlight, not obscure, the key differentiator
- The competitive field should be favorable for the product

Example: before and after

Before: “We’re an AI platform.”

After: “We position ourselves in the ‘revenue intelligence platform’ category (a subcategory of BI tools), competing with Gong and Clari, and winning through integration with product analytics.”

Calling yourself an “AI platform” in 2026 is like calling yourself a “website” in 2010. It says nothing. “Revenue intelligence platform” tells the customer exactly what to expect and exactly who you’re competing with.

Step 3. Articulate the Differentiator

The differentiator answers one question: “why you and not the alternative?” Most claimed differentiators fall apart the moment you push on them.

Run every differentiator through three tests:

1. Uniqueness test. Can a competitor claim the same thing? “We’re easier to use” — anyone can say that. “The only tool with native integration into both Figma and Jira simultaneously” — no one else can.
2. Value test. Does the customer actually care? “Written in Rust” — technically unique, but irrelevant to customers. “Runs 10x faster on datasets over 1M records” — that matters.
3. Provability test. Can it be verified? “Best UX” — subjective. “NPS 72, category average is 34” — a fact.

Prompt for finding a differentiator:

You are an expert in competitive analysis and positioning.

Product: [name]
Category: [result from Step 2]
Target audience: [result from Step 1]
Competitors: [top 3 from Step 2]

Product capabilities (list everything the product does):
- [capability 1]
- [capability 2]
- [...]

Task: find 3–5 potential differentiators.

For each:
1. Differentiator statement (one sentence)
2. Uniqueness test: can competitors [list] claim the same? (yes/no + explanation)
3. Value test: how important is this to the target audience? (critical / important / nice-to-have)
4. Provability test: how to prove it? (metric, case study, demo)
5. Overall strength rating: strong / medium / weak

At the end: recommendation for primary and backup differentiator.

Rules:
- Don't suggest "better UX" or "easier to use" without specifics
- Focus on measurable differences
- Consider that customers compare not just with direct competitors, but with "doing nothing" / "solving manually"

Example: before and after

Before: “Our advantage is simplicity and power.”

After: “The only tool in the category that automatically connects revenue data from CRM with product usage data without configuring ETL pipelines. Average time to first insight: 15 minutes vs. 2 weeks with Gong/Clari (which require separate ETL configuration for product usage data).”

The first version is a subjective claim anyone could slap on their homepage. The second is a measurable differentiator with a number and a direct comparison.

Step 4. Assemble the Positioning Statement and Proof Points

Proof points are evidence that the differentiator is real, not a marketing claim. Three categories of evidence:

• Quantitative. Metrics, benchmarks, tests. “Processes 10M records in 3 seconds.”
• Social. Customers, case studies, testimonials. “Used by Stripe, Notion, Linear.”
• Demonstrable. Can be shown in a live demo. “Setup takes 5 minutes — start a trial and see for yourself.”

Prompt for final assembly:

You are a strategic copywriter specializing in product positioning.

Source data (results from previous steps):

AUDIENCE: [paste result from Step 1 — chosen segment]
CATEGORY: [paste result from Step 2 — chosen category and strategy]
DIFFERENTIATOR: [paste result from Step 3 — primary differentiator]
COMPETITORS: [top 3]
PROOF POINTS (if any): [metrics, case studies, facts]

Task 1: Create a positioning statement using the Geoffrey Moore template:

"For [target audience] who need [key need], [product] is a [category] that [key differentiator]. Unlike [alternative], our product [proof point]."

Requirements:
- Maximum 2 sentences
- Concrete words, zero abstractions ("efficient," "innovative," "powerful" are forbidden)
- The differentiator must be measurable or demonstrable

Task 2: Create 3 positioning statement variants with different focuses:
a) Focus on audience pain
b) Focus on competitive advantage
c) Focus on customer outcome

Task 3: For each variant, suggest 3 proof points (quantitative, social, demonstrable).

Task 4: Rate each variant on:
- Clarity (is it clear in 5 seconds?)
- Distinctiveness (does it stand out from competitors?)
- Credibility (is it believable without additional explanation?)

Full walkthrough: from zero to positioning statement

Here’s the entire framework applied to one product — a reporting automation tool for marketing teams.

Step 1 (audience). AI identified three segments. Chosen: “Head of Growth at B2B SaaS companies with $2–15M ARR, spending 8+ hours per week pulling data from Google Analytics, HubSpot, and Mixpanel into Google Sheets for weekly leadership reports. Current solution: manual CSV export + pivot tables.”

Step 2 (category). Of four options, the subcategory “automated marketing reporting” within BI tools was selected. Competitors: Databox, Supermetrics, Whatagraph. Positioning advantage: focus on marketing (vs. general business analytics) narrows the competitive field.

Step 3 (differentiator). Primary: “Automatically generates narrative reports with insights and recommendations, not just dashboards with charts.” Passed the uniqueness test: Databox and Supermetrics display data but don’t interpret it. Value test: critical — leadership needs conclusions, not charts. Provability test: live demo, time-to-insight metric.

Step 4 (assembly). Final positioning statement:

For marketing leaders at B2B SaaS companies who spend hours manually assembling weekly reports, MetricStory is automated marketing reporting that doesn’t just aggregate data from all channels — it generates written insights with recommended actions. Unlike Databox and Supermetrics, which show dashboards, MetricStory produces a complete report with data interpretation in 2 minutes instead of 8 hours of manual work.

Now compare that with a typical gut-feel version: “MetricStory is an AI-powered analytics platform that helps marketers make better decisions.”

No audience. No category. No measurable differentiator. No reason to believe it. The framework-built version has all four.

Positioning Statement Template

POSITIONING STATEMENT

For: [role + context + company size]
Who: [specific problem / current behavior]
[Product] is: [category]
That: [differentiator — measurable or demonstrable]
Unlike: [top 2 alternatives]
Our product: [proof point — metric or fact]

---

PROOF POINTS
1. Quantitative: [metric / benchmark]
2. Social: [customers / case studies / testimonials]
3. Demonstrable: [what can be shown in demo / trial]

---

MESSAGING DERIVATIVES
- Website headline (10 words max): ___
- Elevator pitch (30 seconds): ___
- One sentence for investors: ___
- One sentence for customers: ___

5 mistakes the framework prevents

Positioning from features, not from the problem. “We have AI, integrations, and dashboards” is a feature list, not positioning. The framework starts with the audience and their pain — the product comes later.

A blurry audience. “For businesses of all sizes” means “for no one in particular.” Step 1 forces you to narrow down to a real segment with observable behavior.

Unprovable differentiators. “Best UX,” “most intuitive,” “innovative approach.” The triple test in Step 3 kills subjective claims on contact.

Wrong category. “AI platform” in 2026 differentiates nothing. Step 2 makes you pick a category that sets the right expectations and puts you in a winnable competitive field.

No proof points. A claim without evidence is just an opinion. Step 4 demands three types of backing for each variant.

How to Use the Positioning Statement After Creating It

The positioning statement isn’t the end product. It’s the input that generates everything else:

Messaging matrix. A table where rows are audience segments and columns are channels (website, email, sales call). Each cell is an adapted version of the positioning for that context.

Homepage hero. The headline and subheadline of the website. The positioning statement is too long for a hero section, but it contains all the components needed to compress it. “Marketing reports with insights in 2 minutes” is the differentiator from the positioning statement, compressed to 7 words.

Sales narrative. A script for the first call. Structure: problem (from audience description) → category (what it is) → differentiator (why us) → proof point (why to believe it). Same information, different format.

Investor pitch. One sentence for the deck: “[Category] for [audience] that [differentiator]. [Proof point].” Example: “Automated marketing reporting for B2B SaaS that generates reports with data interpretation. A pilot with 15 companies showed reporting time reduced from 8 hours to 12 minutes per week.”

Iteration and validation

A positioning statement isn’t something you write once and laminate. Three signals that it’s time to revisit:

Your customer segment shifted. You started with marketers, but product managers are buying. Go back to Step 1.

A competitor claimed your differentiator. Databox added AI insights? Step 3 restarts with updated competitor data.

The category evolved. “Marketing reporting” got absorbed into “marketing ops platform.” Step 2 needs a fresh look.

AI makes each iteration fast. The first pass takes 30 minutes. After that, 10–15 minutes — the product context is already captured, you’re only updating the inputs.

This works at any stage. Pre-launch, you’re filling in hypotheses instead of real customer data, and expected outcomes instead of metrics. As real data comes in, the positioning sharpens. The framework stays the same — only the quality of what you feed it changes.

---

Need help with positioning and product strategy? I help startups build AI products and automate processes — belov.works.

FAQ

How is a positioning statement different from a value proposition?

A value proposition answers “what value does this deliver?” for the customer. A positioning statement answers “where does this product live in the market?” for the team. The value proposition is customer-facing: “Save 8 hours per week on reporting.” The positioning statement is internal: it specifies the audience segment, the category you’re competing in, the differentiator that makes you the right choice, and the proof point that makes the claim credible. The positioning statement is the strategic input; the value proposition is one of the outputs derived from it. You can’t write a good value proposition without having the positioning statement first.

Can I have more than one positioning statement for different segments?

Technically yes, but practically it’s a sign that you haven’t made a choice yet. A single product with two competing positioning statements creates the exact problem the framework is designed to solve: different parts of the organization tell different stories. The right approach is to pick the primary segment and build one canonical positioning statement from it, then create a messaging matrix where each row adapts that core positioning for a different audience context. The statement stays stable; the language adapts. If the gap between your segments is so large that a shared positioning statement becomes meaningless, you likely have two separate products — or you need to pick which segment is the real beachhead.

How do I know if my differentiator passes the triple test if I don’t have competitor data?

Use AI to simulate the test rather than skip it. Run the differentiator prompt with publicly available competitor descriptions, product pages, and G2 category overviews — Claude can synthesize what competitors claim and surface whether your stated differentiator is genuinely unique or widely claimed. For the value test, look at the top complaints and feature requests in competitor reviews on G2 and Capterra: if customers are asking for exactly what you offer, that’s strong evidence the value is real. For the provability test, the minimum viable proof point at launch is a live demo or a concrete setup time claim — something a skeptical buyer could verify in 15 minutes without trusting your word.