Skip to content
← All free resources

You are away for a day.

Can someone else send the invoices?

Fictional example · not George's experience

  1. Find the instructions ✓
  2. Prepare the invoice ✓
  3. Open the billing account → Stuck
What can the teammate safely do next?

Stop before sending anything. Ask the account owner to arrange approved backup access with the permissions needed for the job, then repeat a safe test.

Do not share passwords or use a live customer invoice as a test. Good instructions alone did not solve the access problem.

The full example and its assumptions

A studio receives $20,000 per month; one customer supplies $12,000, or 60%. Losing that customer leaves $8,000 receipts against $14,000 monthly outflows: $6,000 net burn. With $18,000 available cash, the static scenario lasts three months.

The studio also relies on one person to send invoices. During a bounded handover test, another person can prepare an invoice but cannot access the billing account. The next action is to establish approved backup access and repeat the test. Customer diversification and invoice recovery address different dependencies; neither alone resolves the other.

Illustration only, not a business forecast or a recommendation for your finances.

Try this next

Pick one job that stops without you. Ask a teammate to try it with approved access and safe test data. Keep the point where they get stuck.

What stops without it?

List the customers, people, vendors, accounts and systems involved in delivering the work and collecting cash. For each, record what stops if it becomes unavailable. Include knowledge held only by the founder and credentials available only to one person.

Use the Revenue Concentration Worksheet to record customer or platform revenue shares and compare a loss scenario against cash and monthly outflows. For vendors, identify what data can be exported and what work must be rebuilt elsewhere. Revenue concentration and technical lock-in are different risks; a single score can obscure that distinction.

Try the backup plan

Choose one job and try the recovery route. A teammate could follow the instructions, restore a backup in a separate approved environment or test an export. Agree the data, permissions and stopping point first. Never put credentials in a worksheet or interrupt live customer work to test a theory.

Keep what worked, where it stopped, how long it took and what was missing. A failed test is useful: now you know what to fix. A successful one tells you about that particular scenario, not every way the business could fail.

Fix the part that failed

Compare the cost of reducing the dependency with the likely consequence of losing it. You may decide to document a process, add a recovery option, diversify work, change terms or accept the exposure for now.

Name an owner and a review trigger for each chosen action. Repeat the exercise when an important customer, provider or operating arrangement changes. A founder-dependency assessment can help identify questions, but it does not certify the business as resilient.

  • The dependency and what stops
  • A recovery route you have actually tried
  • Someone to fix it, a cost and a reason to test again
Choose a next step

Decision worksheet

Pick one thing to do next. Keep a short plan without filling in a form.

Add detailed notes

Add notes only if they help. Answers stay in this page's memory and are never uploaded or saved automatically.

What relationship, person or system is necessary for this obligation?

What stops, and how long can the business tolerate it?

When did we last exercise the alternative, and what happened?

What will we change or explicitly accept, and who owns that decision?

Record a recovery test

Recovery exercise record

Write your answers here, then copy or export them before leaving. Answers stay in this page's memory and are never uploaded or saved automatically.

Record the actual date, time zone and person responsible for this test.

What stops if this dependency disappears, and how long can the obligation tolerate the interruption?

Which separate environment, data and access are approved? What condition makes you stop before affecting live work? Do not enter credentials or private customer data.

Before the exercise, state what a successful restore, export or handover must demonstrate and who will check it.

Record the actual instructions, backup or export version and the steps another person attempted. Keep sensitive locations out of the exported record.

What passed, what failed, and how long did the actual exercise take? Keep unmeasured times unknown and separate observation from your explanation.

Which permissions, documentation, data or skills prevented completion? A stopped test is evidence to preserve.

Where is the approved evidence kept, and what failure scenario does this exercise leave untested? Reference it without copying secrets.

Name the action, its owner and the date or change that will trigger another exercise.

Example-led guide · Updated

Work through the question

From the field

Personal accounts behind the questions. Each essay reflects when it was written.

The Day I killed our product strategy

EssayPublished

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

EssayPublished

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.

EssayPublished

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

EssayPublished

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.

Explore business resilience & dependencies →