Create Competitive Analysis Grids
Skill for building competitive-analysis grids using the PACE framework - scoring, feature gaps, and strategic actions.
Why it matters
Generate comprehensive competitive analysis grids to inform strategic product positioning and identify market opportunities.
Outcomes
What it gets done
Structure competitive landscapes using the PACE methodology.
Create feature comparison matrices and market positioning maps.
Integrate SWOT analysis and provide strategic recommendations.
Analyze competitor positioning, advantages, capabilities, and execution.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-competitive-analysis-grid | bash Overview
Competitive Analysis Grid Creator Agent
A skill for competitive analysis using the PACE framework - a weighted scoring grid, a feature-gap matrix, a positioning map, competitive SWOT, and a phased (immediate/medium-term/long-term) strategic-recommendations plan. Use it for a structured, recurring competitive-analysis framework, not a one-off competitor mention or single-sales-call battlecard.
What it does
This skill covers competitive analysis and strategic product positioning - building comprehensive competitive-analysis grids that drive actionable business decisions, structuring complex competitive landscapes into clear, comparable frameworks that reveal market opportunities and strategic advantages. The core framework uses the PACE methodology: Positioning (how competitors position themselves in the market), Advantages (unique value propositions and competitive moats), Capabilities (feature sets, technical capabilities, resources), and Execution (go-to-market strategy, pricing, customer success). Core dimensions always covered: market positioning and target segments, core features and functionality gaps, pricing strategy and value proposition, go-to-market approach and distribution channels, technical architecture and scalability, customer-base size and growth trajectory, funding status and financial health, and key partnerships and integrations.
A standardized scoring grid quantifies comparison across weighted criteria - market position, feature completeness, price competitiveness, technical scalability, customer satisfaction, innovation speed - each weighted and scored 1-5 with qualitative labels like "Leader", "Challenger", or "Niche", rolled up into a weighted score per competitor. A feature-gap-analysis matrix maps specific features by category (for example API rate limiting, webhooks, real-time dashboard, SSO/SAML, native mobile apps) against your product and named competitors, using a status legend (full/advanced capability, limited/basic capability, unavailable) plus a priority rating. A positioning map plots competitors on key strategic dimensions such as price versus feature completeness as a quadrant chart, with target-market analysis noting which segment each competitor dominates - enterprise, mid-market, or small business.
SWOT integration ties competitive insight to strategic implications: strengths against the competition (named technical-speed or onboarding-time advantages with specific multiples or percentages), weaknesses against the competition (brand-awareness or sales-team-size gaps), market opportunities (underserved segments with a growth-potential estimate, an API-first trend alignment, compliance features creating switching costs), and competitive threats (a named competitor's feature-parity timeline, a well-funded new entrant, platform consolidation reducing integration needs). A strategic-recommendations framework translates analysis into action across three horizons: immediate actions (0-3 months - close critical feature gaps, develop competitive messaging, adjust pricing), medium-term initiatives (3-12 months - roadmap adjustments, partnership strategies, go-to-market expansion into underserved segments), and long-term strategic moves (12+ months - platform differentiation, category creation or expansion, potential acquisition targets).
Validation and update guidance covers data sources (primary research like customer interviews and sales feedback, secondary research like analyst reports and public data, and direct product testing), update cadence (quarterly comprehensive reviews, monthly tactical updates for key competitors), stakeholder review (validating findings with sales, customer success, and engineering teams), and competitive intelligence (automated monitoring of competitor product releases, pricing changes, and funding announcements). Every analysis should close with specific, measurable recommendations tied to business goals, including a confidence level per recommendation based on data quality and market volatility.
When to use - and when NOT to
Use it when building a competitive-analysis grid to inform product, pricing, or go-to-market strategy - scoring competitors on a weighted grid, mapping feature gaps, plotting market positioning, or translating competitive insight into a phased strategic-action plan. It is not a one-off competitor mention or a battlecard for a single sales call - it is a structured, recurring analysis framework meant to be validated and updated on a cadence.
Inputs and outputs
Given a set of named competitors and your own product, it produces a weighted scoring grid, a feature-gap matrix, a positioning map, a competitive SWOT, and a phased immediate/medium-term/long-term strategic-recommendations plan.
Who it's for
Product marketing, product management, and strategy teams building or maintaining competitive-analysis grids to inform positioning and roadmap decisions.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.