The Competitive Positioning Teardown: Turn Your Product and 3 Rivals Into a Differentiation Map
Why this prompt matters
Stale positioning doesn’t just look dated — it actively loses deals. Sales reps improvise differentiation on calls because the official messaging no longer matches what competitors ship, prospects evaluate you against criteria you no longer lead on, and marketing keeps running ads built on a value proposition the product team quietly deprioritized. Rebuilding positioning from scratch takes a strategist days; this prompt produces a defensible first draft in minutes.
What we use it for
Your VP of Marketing asks you to refresh the competitive comparison page on the website before next week’s board meeting, and the positioning language hasn’t been touched since the Series A pitch deck eighteen months ago — competitors have since repriced, rebranded, and shipped features that made half your bullet points stale.
Prompt
Role: Act as a senior competitive-intelligence analyst who has spent a decade building positioning strategy for B2B software companies and has sat in on hundreds of lost-deal debriefs. Context: [YOUR PRODUCT NAME] competes against [COMPETITOR 1], [COMPETITOR 2], and [COMPETITOR 3] in the [MARKET CATEGORY] space. Our product: [PRODUCT DESCRIPTION — KEY FEATURES, PRICING, TARGET CUSTOMER] Competitor 1 — [COMPETITOR 1]: [WHAT YOU KNOW — FEATURES, PRICING, POSITIONING, RECENT CHANGES] Competitor 2 — [COMPETITOR 2]: [SAME] Competitor 3 — [COMPETITOR 3]: [SAME] Our current tagline/value proposition: [PASTE CURRENT MESSAGING] Task: Using only the facts given above, produce: 1. A positioning map described in text — choose the two axes that matter most to a buyer in this category, and place all four products on it with a one-line justification for each placement. 2. A differentiation analysis for each competitor: one specific area where we are genuinely stronger (tied to a stated fact, not an opinion), and one specific area where we are at risk of looking weaker. 3. Three messaging angles that no competitor has convincingly claimed, each with a one-sentence rationale. 4. One rewritten value proposition, no longer than 20 words, that we could A/B test against our current tagline. Constraints: - Do not invent features, pricing, or claims that were not stated above. If you need a fact that was not provided, write “[NEEDS INPUT: ...]” instead of guessing. - Never use unsupported superlatives like “best-in-class” or “easiest to use” — every claim must trace back to a specific stated fact. - If two products are essentially identical on an axis, say so explicitly instead of forcing a difference. - Flag anything you are inferring rather than quoting directly as “(inferred)”. Output Format: ## Positioning Map [two chosen axes, and where each of the 4 products sits, with one-line justification each] ## Differentiation Gaps [one subsection per competitor: Our Edge / Our Risk] ## Unclaimed Messaging Angles [3 numbered angles, one sentence of rationale each] ## Value Proposition to Test [one sentence, ≤20 words]
Result
Positioning Map
Axes: implementation speed (fast ↔ slow) vs. depth of customization (shallow ↔ deep).
- TaskFlow (us): fast implementation, moderate customization — our onboarding wizard gets teams live in under a day, but we deliberately cap workflow customization (stated fact: 14 workflow templates, no custom field scripting).
- Asana: moderate implementation, moderate customization — a strong rules engine, but a multi-week rollout for mid-size teams (stated: their own case studies cite 3–4 weeks for enterprise onboarding).
- Monday.com: fast implementation, deep customization — templates plus a visual automation builder let teams heavily tailor boards within days.
- ClickUp: slow implementation, deepest customization — the most configurable of the four, but reviewers consistently cite a steep learning curve (stated: G2 reviews average 3.6/5 on ease-of-use vs. 4.4+ for the other three).
Differentiation Gaps
Asana — Our Edge: our 1-day onboarding beats their stated 3–4 week enterprise rollout for teams that need to move fast. Our Risk: Asana's rules engine supports more conditional logic than our 14 fixed templates, which could matter for complex approval chains.
Monday.com — Our Edge: we're priced lower per seat at the tier most of our customers buy ($9 vs. $12). Our Risk: their visual automation builder is more flexible than our template-only approach — a prospect who wants custom automations has a real reason to prefer them.
ClickUp — Our Edge: ease-of-use is a stated, measurable gap (4.4 vs. 3.6 on G2) that directly offsets their deeper feature set for teams without a dedicated ops person. Our Risk: power users who've outgrown simple templates may see our customization cap as a ceiling they'll hit within a year.
Unclaimed Messaging Angles
- “Live in a day, not a quarter” — none of the three competitors lead with implementation speed as a headline claim, even though it's a stated differentiator for us.
- “Built for teams without an ops person” — ClickUp's and Monday.com's messaging targets power users and admins; no competitor speaks directly to teams without anyone whose job is configuring the tool.
- “Fewer settings, more shipped work” — reframes our lower customization ceiling as a feature (less setup overhead) rather than defending it as a limitation.
Value Proposition to Test
“TaskFlow: project management live in a day, built for teams without a tools person.”
The problem this solves
Positioning docs rot quietly. A company writes a sharp comparison page during a funding round and ships it, then nobody revisits it as competitors reprice, rebrand, or launch features that quietly undercut half the original claims. By the time someone notices — usually because a sales rep gets outmaneuvered on a call, or a board member asks why the comparison table looks dated — rebuilding the whole analysis from scratch feels like a multi-day project nobody has time for. This prompt turns scattered notes on your product and three rivals into a first-draft positioning map in minutes, so updating it becomes a 20-minute task instead of a strategy offsite.
Why four fixed outputs beat a free-form comparison
A loose “compare these products” prompt tends to produce safe, symmetrical praise — every product gets a paragraph of balanced strengths and weaknesses, which is useless for making a messaging decision. Forcing a positioning map, a per-competitor edge/risk pair, unclaimed messaging angles, and one testable value proposition gives you four different decisions you can actually act on: what to say, where you're exposed, what nobody else is saying, and what to test next.
Why the constraints matter more than the structure
The real risk with this kind of prompt isn't a bad structure — it's the model inventing a competitor's pricing or feature set to fill a gap, then that fabricated detail ending up on a live comparison page. The constraint to write “[NEEDS INPUT: ...]” instead of guessing, and to flag inferences explicitly, keeps the output auditable. You can hand the result to a colleague and point to exactly which lines are sourced fact versus interpretation.
Where it's weakest
This prompt is only as good as what you feed it. If your notes on a competitor are two years old, the output will confidently misposition them — the model has no way to know your information is stale. Re-run it whenever a competitor ships a major release, reprices, or rebrands, not just once a year.