competitive-teardown
Systematic competitor analysis covering product teardowns, 12-dimension scoring rubric, feature comparison matrices, SWOT analysis, pricing model deconstruction, UX audits, and strategic action plans with stakeholder presentation templates.
What this skill does
# Competitive Teardown Production-grade competitor analysis framework covering systematic data collection across 6 intelligence sources, a 12-dimension scoring rubric, feature comparison matrices, SWOT analysis, pricing model deconstruction, UX audit methodology, and strategic action plans. Produces battle-card-ready output and stakeholder presentation templates. --- ## Table of Contents - [When to Use](#when-to-use) - [Teardown Workflow](#teardown-workflow) - [Data Collection Framework](#data-collection-framework) - [12-Dimension Scoring Rubric](#12-dimension-scoring-rubric) - [Feature Comparison Matrix](#feature-comparison-matrix) - [Pricing Analysis Framework](#pricing-analysis-framework) - [SWOT Analysis Template](#swot-analysis-template) - [UX Audit Methodology](#ux-audit-methodology) - [Positioning Map](#positioning-map) - [Action Plan Framework](#action-plan-framework) - [Battle Card Template](#battle-card-template) - [Stakeholder Presentation](#stakeholder-presentation) - [Output Artifacts](#output-artifacts) - [Related Skills](#related-skills) --- ## When to Use | Trigger | Teardown Scope | |---------|---------------| | Before product strategy or roadmap session | Full teardown (2-4 competitors) | | Competitor launches major feature or pricing change | Focused teardown (1 competitor, updated dimensions only) | | Quarterly competitive review | Update existing teardowns + trend analysis | | Before a sales pitch (battle card needed) | Single-competitor battle card | | Entering a new market segment | Full teardown of segment incumbents | --- ## Teardown Workflow ### Step-by-Step Process 1. **Define competitors** -- List 2-4 competitors. Confirm which is the primary focus. 2. **Collect data** -- Gather intelligence from at least 3 of the 6 sources per competitor. 3. **Score using rubric** -- Apply the 12-dimension rubric to produce a numeric scorecard. 4. **Generate comparison outputs** -- Feature matrix, pricing analysis, SWOT, positioning map. 5. **Build action plan** -- Translate findings into quick wins, medium-term, and strategic priorities. 6. **Package for stakeholders** -- Assemble the presentation or battle card. ### Validation Checkpoints - Before scoring: Confirm you have pricing data, 20+ user reviews, and recent product data - Before action plan: Every dimension should have a score and supporting evidence - Before presentation: Every recommendation should tie back to a data point --- ## Data Collection Framework ### Source 1: Website and Product Analysis | Data Point | Where to Find | What It Signals | |-----------|--------------|-----------------| | Pricing tiers and price points | Pricing page | Market positioning, target segment | | Feature lists per tier | Pricing + feature pages | Packaging strategy | | Primary CTA and messaging | Homepage hero | Positioning and ICP | | Case studies and customer logos | Case study page, homepage | Target segments, social proof | | Integration partnerships | Integrations page | Ecosystem strategy | | Trust signals | Footer, security page | Enterprise readiness | | Job postings | Careers page, LinkedIn | Growth direction, tech stack | ### Source 2: User Reviews **Platforms:** G2, Capterra, TrustRadius, App Store, Product Hunt | Category | What to Track | Strategic Value | |----------|-------------|-----------------| | Praise themes | What users love (top 5 themes) | Their defensible strengths | | Complaint themes | What users hate (top 5 themes) | Your opportunities | | Feature requests | What users want but do not have | Product roadmap gaps | | Switching mentions | Why users left competitors | Competitive migration paths | | Rating trends | Quarter-over-quarter rating change | Improving or declining | **Sample size target:** 50+ reviews per competitor for reliable themes. ### Source 3: Job Postings | Signal | What It Means | |--------|--------------| | High engineering hiring | Product investment, scaling | | AI/ML roles | AI features coming | | Sales team expansion | Moving upmarket or expanding geographically | | Customer success roles | Retention focus, enterprise motion | | Compliance/legal roles | Regulatory expansion | | Reduced postings | Cost cutting, potential contraction | ### Source 4: SEO and Content Analysis | Metric | Tool | Strategic Value | |--------|------|-----------------| | Top 20 organic keywords | Ahrefs, SEMrush, GSC | Content strategy and targeting | | Domain authority | Ahrefs, Moz | Brand strength | | Blog publishing cadence | Manual check | Content investment level | | Ranking pages (product vs blog vs docs) | Ahrefs | Traffic composition | ### Source 5: Social Media and Community | Platform | What to Track | |----------|-------------| | Twitter/X | Product announcements, customer praise, complaints | | Reddit | Honest reviews, comparison threads | | LinkedIn | Thought leadership, hiring signals, employee count | | Community forums | Feature requests, workarounds, power user patterns | | Discord/Slack | Community size, engagement level | ### Source 6: Financial and Market Data | Source | Data Available | |-------|---------------| | Crunchbase | Funding, valuation, investors, employee count | | LinkedIn | Employee count trend (growth proxy) | | Public filings (if public) | Revenue, growth rate, churn | | Industry reports | Market share estimates | --- ## 12-Dimension Scoring Rubric Score each competitor (and your own product) on a 1-5 scale with evidence notes. | # | Dimension | 1 (Weak) | 3 (Average) | 5 (Best-in-class) | |---|-----------|----------|-------------|-------------------| | 1 | Features | Core only, many gaps | Solid coverage | Comprehensive + unique capabilities | | 2 | Pricing | Confusing or overpriced | Market-rate, clear | Transparent, flexible, fair | | 3 | UX / Design | Confusing, high friction | Functional, adequate | Delightful, minimal friction | | 4 | Performance | Slow, unreliable | Acceptable | Fast, high uptime, responsive | | 5 | Documentation | Sparse, outdated | Decent coverage | Comprehensive, searchable, with examples | | 6 | Support | Email only, slow response | Chat + email, reasonable SLA | 24/7, multiple channels, fast | | 7 | Integrations | 0-5 native integrations | 6-25 integrations | 26+ or deep ecosystem (API + marketplace) | | 8 | Security | No mentions | SOC2 claimed | SOC2 Type II + ISO 27001 + GDPR | | 9 | Scalability | No enterprise tier | Mid-market ready | Enterprise-grade (SSO, SCIM, SLA) | | 10 | Brand | Generic, unmemorable | Decent positioning | Strong, differentiated, recognized | | 11 | Community | None | Forum or Slack exists | Active, vibrant, user-generated content | | 12 | Innovation | No releases in 6+ months | Quarterly releases | Frequent, meaningful, well-communicated | ### Scoring Output Format | Dimension | Your Product | Competitor A | Competitor B | Competitor C | |-----------|-------------|-------------|-------------|-------------| | Features | 4 | 3 | 5 | 3 | | Pricing | 3 | 4 | 3 | 4 | | ... | ... | ... | ... | ... | | **Total (/60)** | **38** | **35** | **42** | **33** | --- ## Feature Comparison Matrix ### Matrix Structure | Feature Category | Your Product | Competitor A | Competitor B | Notes | |-----------------|-------------|-------------|-------------|-------| | **Core Features** | | | | | | Feature 1 | Full | Full | Partial | Comp B lacks [specific capability] | | Feature 2 | Full | Missing | Full | Our differentiator | | Feature 3 | Partial | Full | Full | Gap to close | | **Platform** | | | | | | Web app | Yes | Yes | Yes | | | iOS app | Yes | No | Yes | Comp A gap | | API access | Full | Limited | Full | | | **Enterprise** | | | | | | SSO | Yes | No | Yes | | | Audit logs | Yes | Yes | No | | | Custom SLA | Yes | Yes | Yes | | **Score per cell:** Full = 5, Partial = 3, Basic = 2, Missing = 0 --- ## Pricing Analysis Framework ### Pricing Model Comparison | Attribute | Your Product | Competitor A | Competitor B | |-----------|-------------|-----------
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.