10x Why Now

1---
2name: 10x-why-now
3description: This skill should be used when the user says "why now", "is the timing right", "what's changed", "why didn't this exist before", "why is this possible now", "what's the tailwind", or needs to formalize whether there is a structural timing advantage for this idea — not just "AI is taking off."
4version: 0.1.0
5---
6 
7# 10x Why Now
8 
9Thiel's "why now" question formalized. What changed in the last 2-3 years — regulatory, technical, behavioral, market — that makes this viable today but not 5 years ago? If the answer is weak, the idea may be too early, too late, or not differentiated by timing.
10 
11## Input Dependencies
12 
13Read from `./founder-outputs/` if available:
14- `pressure-test-output.md` — demand evidence and contrarian truth
15- `battle-cards-output.md` — competitive landscape (why haven't competitors solved this?)
16- `market-size-output.md` — market dynamics
17 
18No files are strictly required — this skill can run standalone.
19 
20## Frameworks
21 
22- *Zero to One* (Thiel) — the "why now" question. The best startups exploit a specific, recent change that makes something newly possible. If the founder cannot name the change, the idea may address a problem that has existed forever and will continue to not be solved — or that someone already solved.
23- *Crossing the Chasm* (Moore) — timing in the adoption curve. Is the technology/behavior mature enough for the early majority, or is this still an innovator toy? Early is not the same as right.
24 
25## Methodology
26 
271. **Ask the "why now" question directly.** "What changed in the last 2-3 years that makes this idea viable today when it was not viable before?" Demand specifics, not vague trends.
28 
292. **Probe across four dimensions:**
30 
31   **Technical shifts:**
32   - New technology that is now mature enough (not just announced — actually usable)
33   - Cost curves that crossed a threshold (compute, storage, bandwidth, devices)
34   - Infrastructure that now exists (APIs, platforms, standards)
35   - Open-source tools or models that remove build cost
36 
37   **Regulatory shifts:**
38   - New regulations that create requirements (compliance, reporting, access)
39   - Deregulation that opens markets previously blocked
40   - Policy changes that create urgency (deadlines, mandates, penalties)
41 
42   **Behavioral shifts:**
43   - Consumer or enterprise behavior that changed recently
44   - Pandemic-accelerated behaviors that stuck
45   - Generational shifts in expectations or tool adoption
46   - New workflows or processes that emerged
47 
48   **Market shifts:**
49   - Incumbent weaknesses newly exposed (platform risk, pricing, trust)
50   - Category creation by adjacent companies (market education done for you)
51   - New funding/budget availability in the target segment
52   - Industry consolidation or fragmentation creating gaps
53 
543. **Challenge weak answers.** Apply these red flag tests:
55   - **"AI is taking off."** Necessary but not sufficient. Every company can say this. What specific AI capability became viable in the last 12 months that enables *this specific product*?
56   - **"Remote work is growing."** This has been true for years. What changed *recently* that your product specifically exploits?
57   - **"The market is big and growing."** Growth is not timing. Name the inflection point.
58   - **No change identified.** If nothing specific changed, this idea could have been built 5 years ago. Why was it not? That question often reveals the real answer.
59 
604. **Assess timing strength.** Rate the timing advantage:
61   - **STRONG** — a specific, recent, irreversible change that directly enables this product. Clear evidence.
62   - **MODERATE** — a real trend, but not unique to this product. Others will see it too.
63   - **WEAK** — generic trends, no specific inflection point, or the change happened too long ago to be a timing advantage.
64   - **TOO EARLY** — the change is real but has not yet reached the tipping point for the target customer.
65 
665. **Write full output** to `./founder-outputs/why-now-output.md`. Display a concise summary in chat: the timing thesis, strength rating, and note that full output is saved to the file.
67 
68## Output
69 
70Write full output to `./founder-outputs/why-now-output.md`. Display concise summary in chat.
71 
72File format:
73 
74```markdown
75# Why Now Output
76**Generated:** [date]
77**Idea:** [one-sentence restatement]
78 
79## Timing Thesis
80[One paragraph: what changed and why it matters for this specific product]
81 
82## Timing Factors
83 
84### Technical
85- [Specific change] — [How it enables this product] — [When it happened]
86 
87### Regulatory
88- [Specific change] — [Impact] — [When]
89 
90### Behavioral
91- [Specific change] — [Impact] — [When]
92 
93### Market
94- [Specific change] — [Impact] — [When]
95 
96## Red Flags Checked
97- [Any generic answers that were challenged and what replaced them]
98 
99## Timing Strength
100**[STRONG / MODERATE / WEAK / TOO EARLY]**
101[2-3 sentences explaining the rating]
102 
103## What Would Strengthen the Timing Case
104[Specific evidence or events that would make the timing stronger]
105 
106## Pipeline Status
107**Timing:** [STRONG / MODERATE / WEAK / TOO EARLY]
108**Recommended Next:** /verdict (if not yet run) or continue pipeline
109```
110