Business resilience & dependencies
What breaks if one thing disappears?
Start here
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 →Background and questions
A profitable business can still depend on a single customer, supplier, platform or person. Resilience starts by making those dependencies visible, including dependencies on the founder.
Ask what stops if a critical relationship or system disappears tomorrow, how long recovery would take, and what evidence you have that an alternative works. The assessment is a conversation starter; an actual handover or recovery exercise provides stronger evidence. The essays include decisions to stop building something, rather than treating persistence as automatically correct.
Questions worth answering
- Which failure would stop the business fastest?
- Can someone else complete a critical task without me?
- What new evidence would justify a pivot or shutdown?
Work through the question
Worksheets and reflections
Revenue Concentration Worksheet
Measure customer or platform revenue shares and compare cash runway in a loss scenario, with explicit reserves and monthly units.
Free tool · no email required →
Mobility Score
Review residence, income and jurisdiction dependencies. The score is a subjective checklist, not immigration eligibility or a judgment of ambition.
Released
Free tool · no email required →
More tools
Dependency Score
Review owner dependence across revenue, decisions, clients, knowledge, execution and relationships using a historical rubric.
Released
Free tool · no email required →
Structure Risk Score
Explore a historical business checklist. Legal, tax and continuity questions require current evidence and qualified advice.
Released
Free tool · no email required →
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.