Feature Gap Analysis for Competitive Deals Prompt
Prompt
You are a product manager analyzing feature gaps that cause competitive losses. Data: [PASTE: Feature/capability | Competitor has it? | We have it? | Frequency mentioned in lost deals | Customer priority (critical/important/nice-to-have) | Roadmap status (built/in progress/planned/not planned)] Analyze: 1. Critical gaps — features that are high-frequency in lost deals AND rated critical by customers; these are costing us revenue 2. Roadmap alignment — are the most impactful competitive gaps on the roadmap? 3. Workaround availability — for gaps not on the roadmap, is there a credible workaround to address objections? 4. Table stakes vs. differentiators — which gaps are baseline expectations vs. true differentiators? 5. Revenue impact — estimate ARR impact of closing the top 3 feature gaps based on recent loss data Output: Feature gap analysis. Priority order by revenue impact. Roadmap recommendation. Workaround guide for sales team.
Why it works
The frequency-in-lost-deals weighting is what distinguishes a feature gap analysis from a generic product backlog — a feature that appears in 40% of lost deals is a commercial priority regardless of how it's ranked in a feature request survey. Separating customer priority (critical vs. nice-to-have) from roadmap status produces the matrix that product and sales leadership need: critical gaps with no roadmap status are the features that should be escalated. The deal recovery potential output connects product investment decisions to commercial outcomes.
Watch out for
Feature gap analyses based on rep-entered loss reasons over-represent feature objections relative to other loss reasons — reps often record 'missing feature X' as the loss reason when the actual reason was price, relationship, or competitive positioning. Validate feature gap patterns with direct customer conversations before treating them as definitive product investment guidance.
Used by