Redirecting to interactive showcase…
Executive Summary (Plain Text)
Scenario: DataVault ($18M ARR, 340 mid-market customers) needs a strategy one-pager recommending a $2M investment in an AI API platform. Audience: VP of Product. Three competitors launched developer API products in the last 9 months; 6 of 14 lost deals cited “no API access” as the deciding factor.
What the skill produced: A 487-word strategy one-pager with Minto Pyramid structure (answer first), VP-calibrated framing (competitive positioning lens, not CFO-style ROI), three structurally different options (Full AI API, Basic REST API, Do Nothing), explicit decision ask with deadline, and a 12/12 quality gate score.
Frameworks applied:
- Context Gate (Step -1): Verified artifact fit, analysis readiness, decision authority, and timing before writing.
- Format Routing (Step 0): Selected Strategy One-Pager over Board Memo or Decision Brief based on audience and decision complexity.
- Minto Pyramid / SCR: Situation-Complication-Resolution structure with recommendation in the first paragraph.
- Audience Calibration: Framed for VP of Product (competitive positioning lens). Showed how same investment would be framed differently for CFO, CTO, and CEO.
- Decision Architecture: Classified as Type 1 (one-way door — API contracts are commitments). Three options with full tradeoff matrix including “do nothing” with quantified cost of inaction.
- Evidence Cascade: L1 evidence in body (headline stats), L2 in selected body elements, L3 in appendix. 14 evidence points: 5 at T1, 4 at T2, 4 at T3, 1 at T4.
- Quality Gate: 12/12 on the skill’s quality checklist (10-second test, ask present, audience calibrated, SCR structure, genuine options, jargon clean, honest risks, evidence leveled, word count, reversibility stated, assumptions surfaced, “so what” complete).
- Assumption Registry: 5 load-bearing assumptions with confidence levels and invalidation signals.
- Adversarial Self-Critique: 3 genuine weaknesses — “no API” may be a proxy for price sensitivity; AI premium pricing is untested; may be solving a sales problem with a product investment.
Key numbers in the document:
- $18M ARR, 340 customers, 87% gross retention (T1)
- 2.3 billion events/day processed (T1)
- 6 of 14 lost deals cited “no API access” (T1)
- Amplitude API = 22% of new bookings (T2)
- $6.2M incremental ARR projected in 18 months (T3)
- $2M investment: $1.4M engineering + $600K GTM
- Decision deadline: March 28 (Q2 planning starts April 1)