The instinct that quietly sabotages the handoff
Ask a solo founder who should take over if they suddenly couldn't, and the answer comes fast: a spouse, a sibling, a best friend, a co-founder from a company three startups ago. The name arrives before the question is even finished, because it isn't really a decision. It's a reflex. We reach for the person we trust most in the world and assume trust is the qualification.
It isn't. Trust is necessary, but the work of unwinding or continuing a business after you're gone is mostly technical, procedural, and unglamorous. The person who would sit with your family at the hospital is not automatically the person who can rotate a leaked API key, transfer a domain before it lapses, or tell a panicked customer why their subscription just failed. Choosing a digital executor well means noticing that you are quietly conflating two very different things, and refusing to.
We judge people on two axes, and pick on the wrong one
There's a well-replicated finding in social psychology, often called the stereotype content model, developed by Susan Fiske, Amy Cuddy, and Peter Glick. It holds that across cultures, people size each other up along two basic dimensions: warmth (are you on my side, do you mean me well) and competence (can you actually do the thing). The two are largely independent. Someone can be radiantly warm and hopeless at the task, or coldly capable and not someone you'd confide in.
The relevant part is what happens under emotional load. When we're afraid, grieving, or imagining our own absence, warmth dominates the judgment. We instinctively sort the world into allies and threats long before we evaluate skill. So when a founder pictures death, the brain hands back the warmest name available, not the most competent one for the specific job. The choice feels obvious and final, which is exactly the problem. It was made by the part of you that wants to feel safe, not the part that wants the work done.
A digital executor's actual to-do list is almost entirely a competence list. Find the credentials. Understand which services are load-bearing. Decide what to keep alive and what to let die gracefully. Communicate with customers, contractors, and a payment processor that does not care about your feelings. Warmth gets the family through the funeral. It does not get the production database migrated.
The role is two jobs wearing one title
The cleanest way out of the trap is to stop treating "executor" as a single seat. In practice the handoff splits into two roles that rarely live comfortably in the same person.
The first is the trustee: the person with the authority, the relationship to your family, and the moral standing to make judgment calls. This is the warmth seat. Their job is to decide what should happen — whether the business is sold, shut down, handed to a customer, or kept running for a year so a key client isn't stranded. They hold the values. They don't need to know what DNS is.
The second is the operator: the person who can actually execute those decisions. This is the competence seat. They read the runbook, log into the registrar, talk to Stripe, and don't flinch when a service throws a verification error. They may barely know your family. That's fine. They aren't deciding anything; they're carrying out decisions the trustee makes.
When these two are the same person, you've found someone rare and you should write it down immediately. Far more often, forcing both jobs onto one warm, trusted, non-technical person guarantees a slow, stressful failure — or a single competent person who has total access and no one checking their judgment. Naming both, and naming them separately, turns an impossible ask into two reasonable ones.
What competence actually looks like here
It's worth being concrete, because "technical" gets used loosely. The operator does not need to be an engineer. They need a narrower and more teachable set of traits.
They need to be literate enough to follow instructions without improvising — someone who can read "log into the domain registrar, the login is in the vault, transfer ownership to the trustee's email" and do exactly that. They need tolerance for tedium under stress, because the work is a hundred small steps during a terrible week. They need to be reachable and likely to outlive the crisis — not your 78-year-old mentor, not the friend who changes numbers every year. And they need to be someone who will say no, because part of the job is resisting a grieving family's understandable but expensive impulses.
Notice none of that is about love. You are not honoring someone by naming them your operator. You may, frankly, be handing them a burden. The honor goes to the trustee. The operator gets a clear task and, ideally, your gratitude in advance.
The test most choices fail
There's a simple way to check whether you've chosen well, and almost no one runs it: imagine the moment, and walk it forward step by step.
Your operator gets the call. Now what? Do they know they were named? Do they know where the credentials are? Can they get in — past your two-factor authentication, past the password manager, past the recovery email that also requires a code sent to a phone now sitting in a drawer? Do they know which five services matter and which forty are noise? Do they know who the trustee is, so they know whose decisions to follow?
Most plans collapse at the first question. The founder chose a person, felt the relief of having chosen, and never closed the loop between the name and the knowledge. A digital executor who doesn't know they hold the role, or can't reach the information the role requires, is not a plan. It's a name on a piece of paper doing the emotional work of a plan while providing none of its function.
The fix is unromantic. Tell them. Tell them what they'd need to do, where it lives, and who else is involved. Let them say no — better now than in the moment. Then make the information they'd need real and reachable, not theoretical.
Why the warm choice still matters
None of this means trust is irrelevant. The operator will have, by necessity, the keys to your professional life: customer data, banking access, the ability to send email as you. Competence without trust is its own kind of disaster. The point isn't to swing from warmth to cold competence. It's to stop letting one stand in for the other. You want a trustee you'd trust with your children and an operator you'd trust with your passwords, and you want to be honest that those are often not the same human.
The founders who get this right tend to feel a small, specific relief afterward — not the vague comfort of having "someone in mind," but the concrete kind that comes from knowing a particular person could perform a particular task on a particular day. That relief is the signal that you've actually decided something, instead of just naming the person who makes the fear quiet down.
Where Heirloom fits
This is the gap Heirloom is built to close. It lets you name the roles separately — the trustee who decides and the operator who acts — and then attaches the thing a name alone can't carry: the vault of credentials, the runbook of what matters, and a handoff that reaches the right person at the right moment instead of sitting in a drawer. You make the warm choice and the competent one, and the app makes sure neither is just a name.
If you've already pictured who'd step in, you've done the hard emotional part. The honest next step is making that picture executable. You can start at heirloom.lumenlabs.works — quietly, today, while it's still a decision and not an emergency.