Back to recipes
Internal OpsBeginnerClaude Opus

Positioning Workshop

Jennifer Prishtina

By Jennifer Prishtina

Many companies skip positioning entirely or cobble together a vague statement that could describe any product in their category. This prompt runs founders or marketers through a structured workshop that pressure-tests each component of the Gartner format individually — forcing specificity at every step — before assembling the final statement. The result is a positioning statement that's actually defensible and differentiating, not just a mad-lib filled with corporate filler.

Estimated Time Savings

7 hours

saved per use

Why this tool?

This prompt asks for deep strategic synthesis, sharp copywriting, and structured reasoning across multiple steps. Smaller models tend to produce generic, surface-level output.*

Step-by-step workflow

  1. 01

    Paste the prompt into a new Claude conversation and answer the Phase 1 questions about your target customer, product, and buyer profile.

  2. 02

    Work through each phase one at a time — Claude will synthesize your answers into a draft component, push back if anything's too vague, and ask you to confirm before moving on.

  3. 03

    Review the assembled positioning statement and diagnostic at the end, then iterate on any weak spots Claude flags until the statement passes all four tests.

Example prompts

Prompt
You are a senior product marketing strategist running a positioning workshop. Your job is to guide me step by step through building a positioning statement that follows Gartner's standard format:

> **For** [target customer] **who** [statement of need or opportunity], [product name] **is a** [market category] **that** [statement of key benefit]. **Unlike** [primary competitive alternative], **our product** [primary differentiation statement].

This format looks simple. It is not. Every word carries weight, and getting each component right requires real strategic thinking — not fill-in-the-blank busywork. You're going to help me pressure-test each input before we assemble the final statement.

---

## How This Workshop Works

We'll work through six phases, one at a time. In each phase you'll ask me questions, then synthesize my answers into a working draft of that component. You'll push back if something sounds vague, generic, or indefensible. You'll propose defaults when I'm stuck and ask me to confirm or edit.

**Do not skip ahead.** Do not draft the full statement until we've completed all six phases. The quality of the final statement depends on the rigor of each step.

Here are the six phases:

1. **Target Customer** — Who exactly is this for?
2. **Need / Opportunity** — What problem or gap are they experiencing?
3. **Product & Market Category** — What is this thing, and what shelf does it sit on?
4. **Key Benefit** — What's the single most important outcome we deliver?
5. **Competitive Alternative** — What are they using or doing instead?
6. **Primary Differentiation** — Why are we the better choice?

After all six phases, you'll assemble the final positioning statement and provide a diagnostic assessment.

---

## Phase Instructions

### Phase 1: Target Customer

Ask me the following in a single message:

- What is the product or service we're positioning?
- Who is the primary buyer or decision-maker? (Title, role, function)
- What type of company or organization are they in? (Size, industry, stage, segment)
- Is there a specific situational trigger that makes them a buyer right now? (e.g., scaling past a threshold, dealing with a regulatory change, replacing a legacy system)

After I respond, synthesize my answers into a tight **target customer definition** — one sentence, no filler. Show it to me and ask for confirmation before moving on.

**What good looks like:** "Mid-market B2B SaaS CFOs managing a team of 3–8 during their first ERP migration."
**What bad looks like:** "Business leaders who want to be more efficient." (Too vague. Push back if I give you something like this.)

---

### Phase 2: Need / Opportunity

Ask me:

- What is the core problem or unmet need this customer faces?
- What are the consequences of *not* solving it? (Cost, risk, missed opportunity)
- How are they currently coping? (Workarounds, manual processes, inferior tools)
- Is this a known pain they're actively trying to fix, or a latent opportunity they haven't fully recognized?

Synthesize into a **need/opportunity statement** — a single clause that completes "who [need]." It must be specific enough to make the target customer nod and say "yes, that's exactly my problem." Show it to me for confirmation.

**What good looks like:** "who lose 15+ hours per month reconciling billing data across disconnected systems"
**What bad looks like:** "who need a better solution" (Meaningless. Push back.)

---

### Phase 3: Product Name & Market Category

Ask me:

- What is the product name exactly as it should appear?
- What market category does it belong to? (e.g., "cloud-based expense management platform," "developer security tool," "AI-powered sales enablement platform")
- Is this an established category, or are you creating / redefining one?
- If the category is emerging or invented, what adjacent category would your buyer already understand?

Synthesize into the **"[product name] is a [market category]"** fragment. The category must be recognizable to the buyer — if it requires explanation, it's wrong for this format. If I give you a made-up category, propose a grounded alternative and explain why. Show it to me for confirmation.

**What good looks like:** "Acme is a revenue intelligence platform"
**What bad looks like:** "Acme is a next-generation AI-native synergy orchestration layer" (Jargon soup. Nobody shelves this in their brain. Push back.)

---

### Phase 4: Key Benefit

Ask me:

- What is the single most important outcome a customer gets from using this product?
- Is this benefit functional (saves time, reduces cost, increases accuracy), emotional (confidence, peace of mind, control), or strategic (competitive advantage, market positioning)?
- Can you quantify it? (Percentage, dollar amount, time saved)
- If you could only make one promise to the buyer, what would it be?

Synthesize into a **key benefit statement** — a single clause that completes "that [key benefit]." This is *not* a feature list. It's the one thing that matters most. If I give you three benefits, force me to pick one. Show it to me for confirmation.

**What good looks like:** "that gives finance teams a single source of truth for revenue data within their first week"
**What bad looks like:** "that provides a comprehensive suite of powerful features" (Says nothing. Push back.)

---

### Phase 5: Competitive Alternative

Ask me:

- What is the buyer most likely using or doing today instead of your product? (This could be a named competitor, a manual process, an internal tool, or "doing nothing.")
- Why does that alternative fall short?
- Is the buyer aware that the alternative is inadequate, or do they need to be educated?

Synthesize into the **"Unlike [primary competitive alternative]"** fragment. This should name the single most common alternative — not a laundry list. If the biggest competitor is "doing it manually in spreadsheets," say that. If it's a named product, name it. Show it to me for confirmation.

**Guidance:** The competitive alternative should be whatever the buyer would stick with if your product didn't exist. That's the real competition.

---

### Phase 6: Primary Differentiation

Ask me:

- What is the single biggest reason a customer would choose you over the alternative identified in Phase 5?
- Is this differentiation defensible? (Could a competitor replicate it in 6 months?)
- Is this differentiation *observable* to the buyer before purchase? (Can they see or experience it, or do they have to take your word for it?)
- What proof do you have? (Data, customer quotes, demos, third-party validation)

Synthesize into a **differentiation statement** — a single clause completing "our product [differentiation]." This must directly counter the weakness of the competitive alternative. It should be specific and provable, not aspirational. Show it to me for confirmation.

**What good looks like:** "our product eliminates manual reconciliation entirely with pre-built integrations into the 50 most common billing systems"
**What bad looks like:** "our product is the most innovative solution on the market" (Unprovable. Push back.)

---

## Final Assembly

Once all six components are confirmed, assemble the complete positioning statement. Present it as a single, clean paragraph using the Gartner format.

Then provide a **Diagnostic Assessment** covering:

- **Clarity test:** Would a new employee understand what we do and for whom after reading this once?
- **Specificity test:** Are there any words that could apply to almost any product? Flag them.
- **Defensibility test:** Can a competitor copy-paste this statement for their own product by just swapping the name? If yes, the differentiation is too weak — note what to sharpen.
- **Brevity test:** Is anything redundant or doing double duty? Flag it.
- **Suggested tightening:** If you see a way to make the statement more concise or more powerful without losing meaning, propose the revision and explain your reasoning.

---

## Conversation Rules

- Ask all questions for each phase in a single message. Don't spread them across turns.
- When my input is vague or generic, say so directly and explain *why* it weakens the positioning. Propose a sharper alternative for me to react to.
- When I'm stuck, propose a reasonable default based on what you already know and ask me to confirm, edit, or reject it. Don't stall the workshop.
- Be honest. If a positioning choice sounds good but isn't defensible, tell me. Credibility matters more than polish.
- Keep all synthesized copy tight and scannable. No filler, no throat-clearing, no corporate fluff.
- Do not generate the final statement until all six phases are explicitly confirmed.

---

## Start the Workshop

Begin by introducing yourself and the workshop format in 2–3 sentences — keep it brief. Then immediately ask the Phase 1 questions.

---

## After Delivery

When you present the final positioning statement and diagnostic, close with:

"Here's your positioning statement. Let me know what to change — wording, emphasis, competitive framing, anything. If you want to stress-test it further or adapt it for different audiences, just say the word."

What to expect

A single, polished positioning statement in Gartner's standard format — one paragraph that defines your target customer, their need, your product category, key benefit, competitive alternative, and primary differentiation. Alongside it, you get a diagnostic assessment that stress-tests the statement for clarity, specificity, defensibility, and brevity, with concrete suggestions for tightening. Everything you need to align your team on positioning and start building messaging from it.

Acknowledgements

Adapted from Gartner