SaaS Feature Parity Matrix

Use This Skill When

• The user wants a product-level comparison between software vendors.
• The thesis depends on whether a product lead is real, fading, or already commoditized.
• Feature parity risk may affect win rates, pricing power, retention, or multiple durability.
• The question is whether the company owns a workflow or just matches the category checklist.

Required Inputs

• Target company plus the most relevant 2 to 5 competitors.
• Customer segment being compared: SMB, mid-market, enterprise, vertical, or developer-led.
• Core workflows that matter to buyer decision-making, not just a list of UI features.
• Evidence sources such as product pages, demos, release notes, user reviews, partner docs, or channel checks.
• Optional but helpful: pricing tiers, implementation complexity, ecosystem depth, and recent roadmap changes.

Workflow

1. Set the comparison boundary. Define buyer persona, use case, deployment model, and the jobs the software must accomplish.
2. Build the matrix around workflows. Compare onboarding, daily use, analytics, admin controls, integrations, automation, AI, compliance, and extensibility as relevant.
3. Separate table stakes from true differentiation. Mark features that are required to compete but do not create pricing power.
4. Evaluate depth, not only existence. Ask whether a feature is native, mature, widely adopted, integrated, and proven at scale.
5. Assess direction of travel. Identify where parity is closing, where the gap is widening, and where roadmaps may erase current advantage.
6. Translate product position into economics. Link product differences to pricing, attach rate, churn, expansion, sales efficiency, or moat durability.

Output Requirements

• Use buyer-relevant workflows as the main frame, not marketing categories.
• Clearly distinguish feature presence, feature quality, and feature importance.
• State where evidence is direct, where it is inferred, and where confidence is low.
• End with a verdict on whether the product lead is durable, narrowing, or overstated.
• Include investment implications, not just product commentary.

Output Template

Quality Checks

• The comparison uses the same buyer persona and use case across vendors.
• Table-stakes features are not mistaken for moat.
• The matrix reflects depth and usability, not just check-box existence.
• The conclusion links product position to commercial outcomes.
• Weak or indirect evidence is labeled as such.

Guardrails

• Do not compare across mismatched customer segments and call it parity.
• Do not reward a vendor for announcing roadmap items that are not yet shipped or adopted.
• Avoid huge undifferentiated feature lists; focus on what changes buying behavior.
• Do not assume "AI" equals differentiation without workflow proof and customer value.
• If a competitor has a better feature but weak go-to-market reach, say so explicitly.

Example Prompts

• Build a feature parity matrix for this SaaS company versus its top three competitors.
• Tell me whether this product lead is real or just marketing positioning.
• Compare workflow depth, not just features, and explain the impact on pricing power.