The plan that assumes the phone call
Every estate plan you have ever read quietly assumes a phone call.
Someone finds out. A spouse, a sibling, a friend who hadn't heard back in a while. They make calls. A lawyer is contacted. A folder is opened. The machinery of grief and paperwork begins to turn because, somewhere near the start of it, a human being learned that another human being had died and decided to do something about it.
For most people, that assumption is safe. Their life is woven into other lives. The absence is loud.
For a solo founder, it often isn't. You can be missing from the internet for a week and look exactly like someone who is busy. Your servers answer. Your Stripe charges renew. Your scheduler posts the email you queued in advance. The business you built to run without you does precisely that — it runs without you, indifferent to whether you are on vacation, in a hospital, or gone.
This is the part almost no one plans for. Not access. Not passwords. The trigger. The moment someone learns there is something to handle at all.
Access is the second problem, not the first
When people finally sit down to think about death and their digital life, they reach immediately for the locked door. How does my executor get into my password manager? How do they recover the two-factor codes? Those are real questions, and they matter.
But they are the second question. They only become relevant after someone already knows to start knocking.
Think about the actual sequence. For your carefully prepared vault to help anyone, four things have to happen in order: someone has to learn you are gone, someone has to know that a handoff exists, that someone has to be able to reach it, and they have to know what to do once inside. Most planning obsesses over the third and fourth steps and silently skips the first two.
The gap between "you have died" and "the right person has noticed and decided to act" can be days. For someone who lived alone, traveled often, or simply kept work and personal life in separate rooms, it can be much longer. And every day in that gap, your automated infrastructure keeps making decisions on your behalf that no living person is watching.
Why automation makes the silence longer, not shorter
There is a quiet irony in modern solo work. The better you are at automating yourself out of the loop, the longer your absence can go undetected.
A business that needs you daily fails loudly and fast. Clients call. Things break. The alarm sounds within hours. But a well-built solo operation is designed for latent stability — it is meant to hum along without intervention. That same property means there is no heartbeat tied to you specifically. The system cannot tell the difference between a founder who is asleep and a founder who is never waking up. It just keeps billing, renewing, and posting, a lamp left on in an empty house.
This is what safety researchers call a latent failure: a problem that is already present in the system but produces no immediate signal. It sits dormant until the exact moment it matters, and by then no one is positioned to catch it. Your death, to your infrastructure, is a latent failure. Everything looks fine on the dashboard. The danger is precisely that it looks fine.
The bystander problem, applied to your own absence
There's a second mechanism working against you, and it's a human one.
In the late 1960s, psychologists John Darley and Bibb Latané studied why people in groups often fail to help in an emergency. Part of what they found was diffusion of responsibility: when responsibility is spread across several people, each individual feels less of it, and assumes someone else will act. The more potential helpers there are, the less likely any single one steps forward.
Now map that onto your own situation. You may have several people who could notice something is wrong — a co-founder you talk to weekly, a partner, a friend group, a few clients. But if none of them has been explicitly named as the person responsible for raising the alarm, responsibility diffuses. Your partner assumes your business contacts will notice the silence. Your contacts assume your family is handling things. Everyone is gently, reasonably waiting for someone else to be the one who says something is wrong, and I am going to do something about it.
A crowd of people who care about you is not the same as one person who knows it is their job to act. The first is comforting. The second is a plan.
What a dead man's switch actually is
The old, literal version comes from trains: a control the operator has to keep holding. The moment their hand goes slack, the train stops automatically. The system assumes the absence of a signal is itself meaningful.
That inversion is the whole idea. Instead of relying on someone to send an alarm when something is wrong, you build a system that fires when the regular, expected signal stops. You don't have to predict the emergency. You only have to keep doing one small ordinary thing, and the system treats your failure to do it as the trigger.
For a digital life, a dead man's switch can be modest. A recurring check-in — a tap, a reply, a confirmation — on a known cadence. If you respond, nothing happens; the clock resets. If you go quiet past a defined grace period, the system escalates: first nudging you, then, after a buffer wide enough to rule out a bad week or a lost phone, notifying the specific person you named and pointing them to the instructions you left.
The elegance is that it converts your inaction into a signal. You no longer have to be alive to start the process. You only have to stop holding the lever.
How to think about your own trigger
If you take one thing from this, let it be a question most plans never ask: how, concretely, would anyone find out in time?
Name one person, not a crowd. Diffusion of responsibility dissolves the moment a single human knows the job is theirs. Tell them plainly: if you don't hear from me and can't reach me for this long, this is what's happening, and here is where to go.
Choose a grace period honest about your own life — wide enough that a silent retreat or a dead phone won't fire it, tight enough that it won't sit dormant for a season. And separate the trigger from the vault. Knowing that there is something to handle, and knowing how to handle it, are two different problems, and the first one is the one almost everyone forgets to solve.
You can build a version of this yourself with calendar reminders and a trusted friend, and for some people that is genuinely enough. The point is not the tooling. The point is to stop assuming the phone call.
Where Heirloom fits
Most of what we built into Heirloom is the vault and the handoff — the part that helps once someone is already inside. But the reason it begins with a quiet check-in is everything above: a death binder no one knows to open is just a locked drawer. Heirloom holds the lever for you. You keep tapping to say you're here, and if that signal ever stops, it does the one thing your humming, self-running business never will — it notices, and it tells the person you chose.
If you've built something that runs without you, it's worth making sure your absence doesn't run silently too. You can see how it works at https://heirloom.lumenlabs.works.