Deep Competitor Analysis

What Problem It Solves

Generic competitor analysis often stays at the level of SWOT or competitor canvases, relying on vendor pages, press releases, and vague comparisons. This skill targets a practical failure mode for product and engineering teams: unclear analysis target, weak evidence, soft conclusions, and no executable follow-up. It turns competitor analysis into a repeatable workflow that starts by confirming the real competitor, then builds conclusions from primary evidence, and ends with an action plan.

How It Works

The workflow is organized as a deep analysis process:

• Align on the goal: identify the actual product, the perspective, and the strategic objective before gathering evidence.
• Collect primary evidence: prefer source code, installers, CLI artifacts, configuration, real user journeys, and cross-verified public reports over marketing copy.
• Structure the analysis: cover user scenarios, product pipeline, advantage mechanisms, weakness evidence, capability source, internal comparison, and learning directions.
• Produce an action plan: extract prioritized P0/P1/P2 items with diagnosis, response strategy, and rollout cadence.
• Adapt to readers: add context for decision-makers and preserve the user's own wording when refining a draft.

Boundaries

It is useful when the analysis needs evidence-backed judgment, especially when separating technical capability from ecosystem assets. It is not a substitute for market research or PR writing. When source access, real usage paths, or reliable public sources are missing, conclusions should be marked as unverified instead of being presented as hard facts.