ansoff-matrix skill
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Is the ansoff-matrix skill safe?
Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.
No findings.
Install the ansoff-matrix skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills mkdir -p ~/.claude/skills cp -r /tmp/pm-skills/pm-product-strategy/skills/ansoff-matrix ~/.claude/skills/ansoff-matrix
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
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
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
- Define current market and product clearly
- 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
- Prioritize opportunities by:
- Strategic fit with company vision
- Revenue potential and growth rate
- Resource requirements and feasibility
- Competitive advantage and defensibility
- Timeline to profitability
- Develop go-to-market strategy for top 2-3 opportunities
- Create phased roadmap and milestones
- Identify risks and mitigation plans
- 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
More skills from phuryn/pm-skills
- Aab-test-analysisAnalyze 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.
- Aanalyze-feature-requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
- Abeachhead-segmentIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
- Abrainstorm-experiments-existingDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
- Abrainstorm-experiments-newDesign lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
- Abrainstorm-ideas-existingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
- Abrainstorm-ideas-newBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
- Abrainstorm-okrsBrainstorm 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.
- Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
- Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
- Acohort-analysisPerform 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.
- Acompetitive-battlecardCreate sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'