An earlier tool. Kept here for you to explore, with its original assumptions. It's no longer actively maintained.
Put the result in context
A number is the beginning of the decision.
Map your business dependencies before they become emergencies
A worksheet for examining customer concentration, platforms, suppliers and founder dependency through recovery tests.
Read the guide and use the worksheet →From the field
Personal accounts behind the questions. Each essay reflects when it was written.
The Day I killed our product strategy
Today (on a Sunday) I took our own AI models off our own app and replaced them with a competitor's model. This is the story of how the decision happened in…
Why this reading: Read this decision account when asking what evidence would justify ending a plan. The author's explanation does not isolate the cause of later results.
What You Kill > What You Build
OpenAI killed Sora Chronology and source correction — October 11, 2026: This preserves my March 30 site-removal account. The corporate comparison below was…
Why this reading: Use this perspective to compare the work and obligations created by continuing, stopping or replacing a project.
AWS and Google Cloud Are Designed to Keep You. Here's What We Do Instead.
Historical cost and portability context — October 11, 2026: This April 7 account preserves our reported month-long migration with three developers. The…
Why this reading: Read this while mapping provider dependencies, then require a current export or recovery test rather than assuming portability.
Trust But Verify — What 6 Years of Partnerships Taught Me About People
Weeks after I cut him off, blocked his number, and swallowed a financial loss I couldn't afford — he emailed me asking for referrals.
Why this reading: Use this partnership account to ask which responsibilities and handover steps have evidence, and which depend on trust alone.