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

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

At a glanceShiftly vs RosterPro: key feature rowsFrom a three-way comparison that also covers CrewClock
ItemShiftlyRosterPro
Price per location$49/mo$89/mo
Shift swap approval on mobileYesYes
POS sales-based schedulingYes, Toast and SquareYes, 6 POS systems
Tip poolingNoYes
Payroll exportCSV onlyGusto, ADP native
Setup timeUnder 1 day1-2 weeks

Example for: Shiftly, a staff scheduling app for independent restaurants, compared with RosterPro and CrewClock; audience is the sales team.

1. Comparison table

FeatureShiftlyRosterProCrewClockWhy buyers care
Price per location$49/mo (U)$89/mo (U)$35/mo (V)Owners run thin margins
Shift swap approval on mobileYes (U)Yes (U)Partial, web only (U)Managers are rarely at a desk
POS sales-based schedulingYes, Toast and Square (U)Yes, 6 POS systems (U)No (V)Cuts overstaffing on slow nights
Tip poolingNo (U)Yes (U)Yes (V)Required in many full-service venues
Payroll exportCSV only (U)Gusto, ADP native (U)Gusto native (V)Saves 2-3 hours per pay run
Setup timeUnder 1 day (U)1-2 weeks, sales says (U)Unknown (V)Small teams cannot pause operations

2. Where we win

  • Price vs. depth: Shiftly includes POS-based scheduling at $49, while RosterPro charges $89 for the same core capability (rows: Price, POS scheduling).
  • Speed to value: Same-day setup vs. RosterPro's 1-2 weeks matters to owners without an ops manager (row: Setup time).
  • Mobile-first managers: Full mobile swap approval beats CrewClock's web-only flow (row: Shift swap).

3. Where we lose or tie

  • Tip pooling: Both competitors offer it; we do not. Expect losses in full-service restaurants (row: Tip pooling).
  • Payroll: CSV export is weaker than native integrations at both rivals (row: Payroll export).
  • Shift swaps vs. RosterPro: Tie; do not lead with this feature against them.

4. Positioning statement

For independent restaurants with 1-5 locations, Shiftly is the scheduling app that matches staff to real sales data and goes live in a day. Unlike RosterPro, you get POS-driven scheduling without enterprise pricing or a two-week rollout.

5. Verification checklist

ItemWhere to confirm
CrewClock price $35/moCrewClock public pricing page
CrewClock POS integration: NoCrewClock integrations directory or a trial account
CrewClock tip poolingProduct docs or help center
CrewClock Gusto integrationGusto app marketplace
CrewClock setup timeAsk 2-3 lost-deal prospects who chose them

Biggest gap: You have no win/loss data, so we cannot tell which of these rows actually decides deals.

Written by AI from this prompt. Your results will vary.

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 in Product Management