.cursor/skills/high-cagr-market-discovery/SKILL.md
Find structurally durable, high-growth markets — not hype cycles. Combines macro structural analysis with micro bottleneck discovery to identify markets with sustainable 10–20 year tailwinds.
npx skillsauth add alexwox/genesis-template high-cagr-market-discoveryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Find structurally durable, high-growth markets — not hype cycles. Combines macro structural analysis with micro bottleneck discovery to identify markets with sustainable 10–20 year tailwinds.
Before any framework, a market must pass all four investor questions:
If yes to all four → high-CAGR candidate. If not → likely a hype cycle.
Identify forces that must push the market forward for 10–20 years regardless of sentiment.
The four strongest structural forces:
| Force | Examples | Markets Created | |---|---|---| | Demographics | aging populations, urbanization, migration | eldercare, longevity biotech, retirement services | | Technology step changes | internet, cloud, AI | SaaS, vertical SaaS, AI tooling | | Regulation | ESG, KYC/AML, cybersecurity compliance | compliance tech, regtech | | Cost curve collapse | solar, genome sequencing, GPUs, cloud storage | new industries appear when costs drop 10-100x |
Rule: Structural forces create guaranteed demand. Demographics are the most reliable because people cannot stop aging.
Ask: "What problems become unavoidable as the world evolves?"
| Trend | Inevitable Problem | |---|---| | AI adoption | AI governance & safety | | Remote work | identity / security | | EV adoption | charging infrastructure | | Data explosion | data management | | Aging population | chronic care |
If the problem must be solved, the market grows.
Simple but powerful. Market must satisfy all three:
| Market | Pain | Budget | Growth | |---|---|---|---| | Cybersecurity | huge | huge | exploding | | Eldercare | huge | large | guaranteed | | Climate risk analytics | rising | rising | fast |
Critical distinction.
High CAGR comes from pull, not push.
The biggest markets often appear in the second or third wave after a primary technology:
Ask: "What secondary layers does this primary technology create?"
Massive growth markets appear when manual industry workflows go digital.
| Industry | Digitization Market | |---|---| | Law | legal tech | | Healthcare | health tech | | Construction | contech | | Insurance | insurtech |
Steps: Industry → Manual workflow → Software replaces it → Vertical SaaS
Large technologies create ecosystems of secondary markets that often grow faster than the primary.
Example (AI):
Constraints in large industries create concentrated growth. Everyone depends on the bottleneck, so it gets funded and scaled.
| Industry | Bottleneck | |---|---| | Semiconductors | lithography | | Shipping | ports | | Construction | permitting | | Healthcare | staffing |
Large market appears when a new technology hits an inefficient incumbent industry.
| Inefficient Industry | Technology Transfer | |---|---| | Finance | fintech | | Healthcare | health tech | | Logistics | supply chain software |
Massive inefficiency + enabling technology = massive growth opportunity.
Problems that occur millions of times per day. Even tiny improvements become billion-dollar markets.
| Activity | Friction | |---|---| | Payments | processing | | Identity | authentication | | Documents | signing | | Support | ticket handling |
Use this sequence to move from trend to specific opportunity:
Macro trend
↓
Structural force (which of the 4 forces is driving this?)
↓
Industry workflow (where does this force hit real work?)
↓
Bottleneck (what is the constraint within that workflow?)
↓
Offer pillar (what specific problem can be solved here?)
Example:
AI adoption
↓
Companies deploying models at scale
↓
Risk of hallucinations and failures
↓
No monitoring/observability tooling
↓
AI observability startups
Use this to calibrate whether a market's growth rate is actually exceptional or just normal.
| Percentile | CAGR | Interpretation | |---|---|---| | 0.1% | -10% | Collapsing industry (fax machines, physical media) | | 1% | -5% | Severe structural decline | | 5% | -2% | Shrinking | | 10% | 0% | Stagnant | | 25% | 2% | Slow, GDP-like growth | | 50% (median) | 5% | Average industry | | 75% | 10% | Solid growth sector | | 90% | 18% | Very strong growth | | 95% | 25% | Elite growth market | | 99% | 40% | Hypergrowth | | 99.9% | 70–100%+ | New platform wave |
How to interpret each zone:
The sweet spot for offer pillar hunting: 12–25% CAGR.
Critical insight: CAGR alone is not enough.
You want: high CAGR + large TAM + structural drivers + unsolved problems.
| Market | CAGR | Outcome | |---|---|---| | NFT marketplaces | 80% | Bubble — collapsed | | Cybersecurity | 15% | Massive durable industry | | Eldercare | 9% | Extremely durable |
Durability beats raw CAGR every time.
The wind metaphor:
The best founders sail where wind + stability coexist.
A market is likely to have durable high CAGR if it has:
When applying this skill to a specific market/sector, produce:
Market: [specific sector] Structural Forces: [which of the 4 forces apply] Pull or Push: [assessment] Inevitable Problems: [what must be solved] Bottlenecks: [where constraints exist] Second-Order Opportunities: [adjacency layers] Verdict: [high/medium/low CAGR confidence + reasoning] Suggested Offer Pillars: [cross-reference offer-pillar-discovery skill]
Slash command: /cagr
Also invoke this skill when the user asks:
tools
Translate role-based organizations into workflow-based organizations by decomposing roles into scored tasks, extracting dark playbooks (proprietary tacit knowledge), formalizing workflows, calculating automation ROI, and producing a sequenced automation roadmap. Use when a company wants to identify what work can be automated, extract undocumented expert knowledge, or build an automation strategy.
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
development
Builds stakeholder-friendly project status updates from markdown sources. Use when asked for progress reports, implementation status, future plans, UI/UX flow summaries, infrastructure/data-flow summaries, risks, code smells, or scout-principle improvement notes.
development
Repeatable playbook for finding and interviewing key stakeholders to validate an offer pillar hypothesis. Produces a pain proximity map, target list, outreach plan, interview protocol, and structured synthesis of findings. Use when a hypothesis needs human validation before building.