---

name: startup-trend-prediction description: "Analyze 2-3 year historical trends in technology, market, and business models to predict 1-2 years ahead. Uses pattern recognition, adoption curves, and cycle analysis to identify timing windows and emerging opportunities. History is cyclical - products and markets follow predictable patterns." metadata: globs: | **/*.md /research/ /trends/ /analysis/

Startup Trend Prediction

Systematic framework for analyzing historical trends to predict future opportunities. Look back 2-3 years to predict 1-2 years ahead.

Modern Best Practices (Jan 2026):

• Triangulate: require 3+ independent signals, including at least 1 primary source (standards, regulators, platform docs).
• Separate leading vs lagging indicators; don’t overfit to social/media noise.
• Add hype-cycle defenses: falsification, base rates, and adoption constraints (distribution, budgets, compliance).
• Tie trends to a decision (enter / wait / avoid) with explicit assumptions and a review cadence.

---

When to Use This Skill

---

Quick Reference: Building a Trend View (Dec 2025)

1) Define the Decision

• What decision are we supporting: enter / wait / avoid?
• Horizon: {{HORIZON}}
• Buyer and market: {{BUYER}} / {{MARKET}}

2) Collect Signals (Leading vs Lagging)

3) Hype-Cycle Defenses

• Falsification: what evidence would prove the trend is not real?
• Base rates: how often do similar trends reach mass adoption?
• Adoption constraints: distribution, budget, switching costs, compliance, implementation complexity.

4) Market Sizing Sanity Checks

• Bottom-up first: #customers × willingness-to-pay × realistic penetration.
• Explicit assumptions: who pays, how much, and why you can reach them.

---

Adoption Curve Framework

Rogers Diffusion Model

Copy                    ADOPTION CURVE
    │
    │                          ╭────────╮
    │                      ╭───╯Late    │
    │                  ╭───╯Majority    │
    │              ╭───╯Early          │
    │          ╭───╯Majority           │
    │      ╭───╯Early                  │
    │  ╭───╯Adopters                   │
    │──╯Innovators                     ╰──────
    │     │      │      │      │      │
    │   2.5%   13.5%   34%    34%    16%
    └─────────────────────────────────────────▶
                     TIME

Bass Diffusion Model (Quantitative)

Mathematical model for predicting adoption timing:

CopyF(t) = [1 - e^(-(p+q)*t)] / [1 + (q/p) * e^(-(p+q)*t)]

Where:
  F(t) = Fraction of market adopted by time t
  p    = Coefficient of innovation (external influence)
  q    = Coefficient of imitation (internal/word-of-mouth)
  t    = Time since introduction

Typical values:
  Consumer products: p=0.03, q=0.38
  B2B software:      p=0.01, q=0.25
  Enterprise tech:   p=0.005, q=0.15

Position Identification

Gartner Hype Cycle Mapping

Copy                    HYPE CYCLE
    │
    │        Peak of
    │     Inflated        ╭─────────────
    │   Expectations  ╭───╯ Plateau of
    │            ╭────╯   Productivity
    │       ╭────╯
    │  ╭────╯         Slope of
    │──╯              Enlightenment
    │  Technology    ╲_____╱
    │   Trigger     Trough of
    │              Disillusionment
    └─────────────────────────────────────▶
                     TIME

---

Cycle Pattern Library

Technology Cycles (7-10 years)

Market Cycles (5-7 years)

Business Model Cycles (3-5 years)

---

Signal vs Noise Framework

Strong Signals (High Confidence)

Moderate Signals (Validate)

Weak Signals (Monitor)

Noise Filters

Exclude from prediction:

• Single viral tweet without follow-up
• PR-driven announcements without product
• Predictions from parties with financial interest
• Old data recycled as "new trend"

---

Prediction Methodology

Step 1: Define Scope

CopyDomain: [Technology / Market / Business Model]
Lookback Period: [2-3 years]
Prediction Horizon: [1-2 years]
Geography: [Global / Region-specific]
Industry: [Horizontal / Specific vertical]

Step 2: Gather Historical Data

Step 3: Identify Patterns

• Linear growth/decline
• Exponential growth/decline
• Cyclical pattern
• S-curve adoption
• Plateau reached
• Disruption event

Step 4: Generate Prediction

Copy## Prediction: [TOPIC]

**Thesis**: [1-2 sentence prediction]
**Confidence**: High / Medium / Low
**Timing**: [When this will happen]
**Evidence**: [3-5 supporting data points]
**Counter-evidence**: [What could invalidate]

Step 5: Identify Opportunities

---

Navigation

Resources (Deep Dives)

Templates (Outputs)

Data

---

Key Principles

History Rhymes

Past patterns repeat with new technology:

• Client-server → Web apps → Mobile → On-device
• Mainframe → PC → Cloud → Distributed
• Manual → Scripted → Automated → Autonomous

Timing Beats Being Right

Being right about a trend but wrong about timing = failure:

• Too early: Market not ready, burn runway
• Too late: Established players, commoditized
• Just right: Ride the wave

Multiple Signals Required

Never bet on single signal:

• Funding + Hiring + GitHub activity = Strong signal
• Just media coverage = Hype, validate further
• Just VC interest = May be speculative

Update Predictions

Predictions are living documents:

• Revisit quarterly
• Track accuracy over time
• Adjust for new data
• Document what changed and why

---

Do / Avoid (Dec 2025)

Do

• Use a decision horizon (enter/wait/avoid) and revisit quarterly.
• Track leading indicators and adoption constraints, not just hype.
• Write assumptions explicitly and update them when data changes.

Avoid

• Extrapolating from a single platform, influencer, or funding headline.
• Treating “attention” as “adoption”.
• Market sizing without assumptions and bottom-up checks.

What Good Looks Like

• Decision: one clear enter/wait/avoid call with horizon and owner.
• Evidence: 3+ independent signal types (not just media) and explicit confidence (strong/medium/weak).
• Assumptions: TAM/SAM/SOM with assumptions + sensitivity ranges; falsification criteria documented.
• Constraints: adoption blockers listed (distribution, budget, switching, compliance, implementation) with mitigations.
• Pragmatic scalability: capital efficiency and break-even path documented (2026 investor priority).
• TAM validation: both bottom-up and top-down calculations cross-checked.
• Cadence: quarterly refresh with "what changed" and accuracy notes.

Optional: AI / Automation

Use only when explicitly requested and policy-compliant.

AI Trend Forecasting Tools (2026)

Automation Guidelines

• Topic modeling/clustering for large corpora; validate with primary sources and spot-checks.
• Summarization of reports; keep links and dates to avoid stale claims.
• Use AI for signal aggregation, not signal interpretation — human judgment required for decisions.
• 73% of researchers report AI hallucination concerns; always verify critical insights.

---

Trend Awareness Protocol

IMPORTANT: When users ask about market trends or timing, you MUST use WebSearch to check current trends before answering.

Trigger Conditions

• "What's trending in [market/technology]?"
• "Is [technology/market] growing or declining?"
• "When should I enter [market]?"
• "What's the adoption curve for [technology]?"
• "Is [trend] real or hype?"
• "What comes after [current trend]?"
• "Market timing for [startup idea]?"

Required Searches

1. Search: "[technology/market] trends 2026"
2. Search: "[technology] adoption curve 2026"
3. Search: "[market] market size forecast 2026"
4. Search: "[technology] vs alternatives 2026"

What to Report

After searching, provide:

• Current state: Where is the technology/market NOW on adoption curve
• Trajectory: Growing, peaking, or declining based on data
• Timing window: Is now early, optimal, or late to enter
• Evidence quality: Distinguish hype from real adoption signals

Example Topics (verify with fresh search)

• AI/ML adoption across industries
• Climate tech and sustainability markets
• Vertical SaaS opportunities
• Developer tools ecosystem
• Consumer app categories
• Emerging technology cycles

---

Integration Points

Feeds Into

• startup-idea-validation - Market timing score
• router-startup - Trend context for analysis
• product-management - Roadmap prioritization

Receives From

• startup-review-mining - Pain point trends over time
• startup-competitive-analysis - Competitor movement patterns