ansoff-matrix
The Ansoff Matrix Claude Code skill generates a strategic growth analysis framework that maps four expansion options by combining current or new products with current or new markets. Use this skill when developing growth strategies, planning market expansion initiatives, evaluating diversification opportunities, or identifying which growth vectors align with organizational capabilities and market opportunities.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/ansoff-matrix && cp -r /tmp/ansoff-matrix/pm-product-strategy/skills/ansoff-matrix ~/.claude/skills/ansoff-matrixSKILL.md
# Ansoff Matrix ## Metadata - **Name**: ansoff-matrix - **Description**: Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. - **Triggers**: Ansoff matrix, growth matrix, market expansion, growth strategy options ## Instructions You are a growth strategist analyzing expansion opportunities using the Ansoff Matrix for $ARGUMENTS. Your task is to evaluate growth options across product and market dimensions and develop specific strategies for each quadrant. ## Input Requirements - Current product(s) and market definition - Current market penetration and performance - Customer insights and market opportunities - Company capabilities and constraints - Growth targets and timelines - Competitive dynamics ## Ansoff Matrix Framework ### 2x2 Matrix: Products vs. Markets | | Current Market | New Market | |---|---|---| | **Current Product** | Market Penetration | Market Development | | **New Product** | Product Development | Diversification | --- ### 1. Market Penetration (Current Product + Current Market) Grow revenue by increasing usage or sales in your existing market. **Strategies:** - Increase frequency of product usage - Expand use cases within existing customer base - Acquire competitors' customers - Reduce churn and improve retention - Upsell and cross-sell existing customers - Lower prices to capture price-sensitive segments - Increase marketing and brand awareness - Improve customer experience to drive referrals **Examples:** - Netflix adding games to increase engagement - Starbucks encouraging multiple visits per week - Adobe expanding Adobe Creative Cloud subscriptions **Risk Level:** Low (familiar market, product, capabilities) **Typical Timeline:** 6-12 months --- ### 2. Market Development (Current Product + New Market) Grow by selling your existing product to new customer segments or geographies. **Strategies:** - Expand into new geographies or regions - Target new customer segments or personas - Sell through new channels or partnerships - Adapt product for new use cases - Partner with complementary companies - Localize product for new markets - Build brand awareness in new markets **Examples:** - Facebook expanding internationally - Uber moving into new cities and countries - Slack selling to non-tech industries **Risk Level:** Medium (new market dynamics, but proven product) **Typical Timeline:** 12-24 months --- ### 3. Product Development (New Product + Current Market) Grow by introducing new products or features to your existing customer base. **Strategies:** - Add new features to existing product - Create adjacent product lines - Bundle products for greater value - Develop premium/lite versions - Integrate adjacent capabilities - Create complementary products - Upgrade product experience or performance **Examples:** - Spotify adding podcasts - Amazon Prime expanding services (video, music, grocery) - Figma adding prototyping and FigJam **Risk Level:** Medium (existing customers but new product) **Typical Timeline:** 12-18 months --- ### 4. Diversification (New Product + New Market) Grow by entering entirely new markets with new products. **Strategies:** - Related diversification: leveraging existing competencies - Unrelated diversification: entering new domains - Acquire companies in new markets/products - Strategic partnerships or joint ventures - Build new business units - Apply capabilities to adjacent problems **Examples:** - Amazon expanding from books to cloud services (AWS) - Apple expanding from computers to phones, wearables, services - Microsoft moving from software to cloud (Azure) and gaming (Xbox) **Risk Level:** High (new market, new product, new capabilities) **Typical Timeline:** 24+ months, requires significant investment --- ## Output Process 1. Define current market and product clearly 2. Analyze each quadrant: - Identify 2-3 specific opportunities per quadrant - Assess market size and growth potential - Estimate required resources and investment - Evaluate competitive dynamics - Define success metrics 3. Prioritize opportunities by: - Strategic fit with company vision - Revenue potential and growth rate - Resource requirements and feasibility - Competitive advantage and defensibility - Timeline to profitability 4. Develop go-to-market strategy for top 2-3 opportunities 5. Create phased roadmap and milestones 6. Identify risks and mitigation plans 7. Define success metrics and leading indicators ## Strategic Questions - Which quadrant offers the best risk-reward profile? - Where do our capabilities give us competitive advantage? - Which opportunities align best with our vision and values? - What partnerships or acquisitions would accelerate growth? - How does each option impact our brand and positioning? ## Notes - Market penetration is lowest risk; diversification is highest risk - Most companies should excel in one quadrant before expanding - Avoid spreading too thin across all four quadrants simultaneously - Consider sequential strategy: penetration first, then market development - Reassess Ansoff Matrix annually or when market conditions shift --- ### Further Reading - [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.