Build a Competitor Feature Comparison and Positioning Summary
Get a feature comparison table with every cell tagged as user-provided or needing verification, plus win/lose points, a positioning statement and a fact-check list.
You getComparison table, where we win and where we lose or tie
Prompt
Act as a senior product manager who builds competitive analyses for sales and leadership teams.
Your job: build a feature comparison and a short positioning summary for my product against its competitors.
First, ask me these questions in one message and wait for my answers:
1. What is my product, and who buys it?
2. Which 2-4 competitors should we compare, and which features matter most to buyers?
3. What do I already know about each competitor (pricing, features, strengths, weaknesses)? I may paste notes or sales feedback.
4. Who will read this?
Rules:
- Use only what I tell you. Do not invent features, prices, customer counts or quotes.
- Tag every table cell: (U) user-provided or (V) needs verification. Anything from your general knowledge is (V).
- Keep cells short: Yes, No, Partial, or a fact under 8 words.
- Every positioning point must reference a specific table row.
- Include where we lose or tie, not only where we win.
Output format:
1. Comparison table: Feature | My product | one column per competitor | Why buyers care
2. Where we win (3 bullets)
3. Where we lose or tie (2-3 bullets)
4. Positioning statement (2 sentences: for whom, and why us over the main alternative)
5. Verification checklist: each (V) item and where to confirm it
End with one line naming the biggest gap in the information I gave you.Example output
Tips and common edits
Why this works
- Asking for competitors and existing notes first keeps the table grounded in your real knowledge instead of generic guesses.
- The (U)/(V) tag on every cell shows at a glance which claims are safe to share and which need checking.
- Forcing each positioning point to cite a table row and listing losses keeps the summary honest and usable by sales.
Use before a sales enablement update, board deck or roadmap review. Have competitor names, pricing pages, win/loss notes and sales feedback ready to paste. Works in ChatGPT, Claude and Gemini.
Common edits
- Add a pricing tier comparison section if buyers often compare plans side by side.
- Ask for a one-paragraph battlecard version for each competitor that sales reps can read in a minute.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Prioritize Your Feature Backlog with RICE Scoring and Flagged Weak Assumptions
Get a ranked RICE scoring table for your pasted backlog, with the math shown, weak assumptions flagged, and a short list of what to build next.
Draft an Internal Launch FAQ and Enablement Brief for Sales and Support
Turns your launch notes into a sales and support brief with talk tracks, a plain-answer FAQ, objection handling, and flags for claims that need legal or engineering sign-off.
Analyze Your Product Funnel and Find the Biggest Drop-Off to Fix First
Paste your funnel step counts and get a conversion table, the largest leak flagged with reasoning, and one testable fix per step with an expected lift range.
Diagnose a Sudden Metric Drop with a Ranked List of Likely Causes
Get a ranked table of likely causes for a metric drop, covering tracking, segments, platforms, releases, seasonality and external factors, each with an exact check.
Interpret A/B Test Results and Decide Whether to Ship, Iterate or Kill
Paste your A/B test numbers and get a Ship, Iterate or Kill verdict backed by significance, sample ratio, guardrail checks and a list of what the data cannot prove.
Run a Post-Launch Retrospective Comparing Goals to Actual Results
Get a blameless launch retrospective with a goal-versus-actual table, facts kept apart from causes, and lessons that each carry an owner and a change for the next launch.