The will transfers the company. It does not transfer the password.

Imagine the most ordinary version of the worst day. A solo founder — call him the one-person company that thousands of people quietly are — doesn't wake up one morning. He left a will. The will is clear: the business goes to his sister. Ownership transfers cleanly, exactly as the law intends.

And then his sister sits down at his laptop and discovers that owning the company and operating it are two completely different things. The laptop wants a password. The password manager wants a master password. The master password is protected by two-factor authentication tied to a phone that is now locked, and the phone's recovery is tied to an email account she also can't open.

She owns everything. She can reach none of it.

This is the gap almost no one plans for, because we instinctively treat death as a legal event — a matter of wills, executors, and probate. For a modern business, it is first an access event. The legal layer answers who gets it. It says nothing about how anyone touches it. And the access layer fails in days, not months.

Ownership is a legal fact. Access is a technical one. They don't travel together.

Here is the mechanism that surprises people. When you die, the law moves ownership of your assets through your estate. But most of what actually runs a digital business — your email, your hosting, your Stripe account, your domain registrar, your customer database, your code repository — isn't an asset you "own" in the simple sense. It's a service you access under a contract, governed by that provider's terms of service.

Those terms almost universally say two things that matter enormously here: the account is non-transferable, and credentials may not be shared. The account doesn't pass to your heir the way a deed to a house does. It sits behind a login designed, deliberately, to keep everyone out except the person who set it up — including the people you wanted to have it.

This isn't a loophole. It's the system working as intended. Authentication exists precisely to make access non-transferable. The feature that protects you in life becomes the wall your successors hit in death.

The law has tried to help — and it reveals how deep the problem runs

The United States actually wrote a law for this. It's called RUFADAA — the Revised Uniform Fiduciary Access to Digital Assets Act, drafted by the Uniform Law Commission in 2015 and now adopted in most states. It gives executors and other fiduciaries a legal pathway to access a deceased person's digital assets.

But read how it's structured and the real lesson jumps out. Under RUFADAA, a provider first honors any online tool the user set up to designate access — think of the legacy-contact and inactive-account features some platforms offer. If there's no such tool, the provider looks to the will or trust. And if there's nothing there either, it falls back to the provider's own terms of service, which often default to no disclosure of content at all.

In plain terms: the law's own priority order rewards the person who planned ahead and quietly punishes the person who didn't. The strongest, fastest access comes not from a court order but from instructions you left while alive. The legal machinery is real, but it's slow, it's state-specific, and it was built as a backstop — not a substitute for you having written things down.

What actually decays, and how fast

The cruelty of the access gap is its clock. While your estate winds its way through probate — which can take many months — the operational side of a business keeps demanding attention it can no longer get.

A domain name renews on a card that will eventually expire or get cancelled, and when it lapses, the website and every email address on that domain can go dark. Recurring infrastructure bills fail silently and servers get suspended. Customers keep paying into a Stripe account no one can reconcile or refund. Support emails pile up in an inbox no one can open. A SaaS product keeps running until the day it doesn't — and then there's no one with the keys to even tell customers why.

None of this waits for probate. The legal estate operates on a timeline of months. The technical estate operates on a timeline of renewal cycles — sometimes days. By the time ownership is formally settled, the thing that was owned may have quietly degraded into a shell.

The fix is an access map, not just a will

The antidote isn't more legal paperwork. It's something closer to operational documentation — a map of how the business actually works at the level of access.

Think about what a competent stranger would need on day one to keep the lights on. Not eventually. Day one.

  • The entry points. Where does access begin — which email account and which password manager unlock everything downstream? This is the root of the tree; everything else hangs off it.
  • The recovery paths. Where do the 2FA codes live? What device or backup keys are needed, and where are they physically? This is the part wills never capture and the part that breaks first.
  • The load-bearing accounts. Domain registrar, hosting, payment processor, the customer database. The handful of logins whose lapse would cause irreversible damage, flagged by how urgent each one is.
  • The in-flight obligations. Who is mid-purchase, what's owed, which renewals are imminent. The living parts of the business that don't pause for grief.
  • The plain-language context. Not just credentials, but a sentence each on what this is and what to do with it. A password to a service no one understands is only marginally better than no password at all.

The goal is a document that lets someone act before the courts have finished deliberating — and then hands cleanly to whoever the courts ultimately name.

Why this is so hard to do — and why that's not a character flaw

If this is so important, why does almost no solo founder do it?

Part of it is ordinary optimism bias — the well-documented human tendency to believe misfortune lands on other people. Part of it is that estate planning is framed around death, and we avoid the things we're afraid of by simply not looking at them. But part of it is structural and worth naming kindly: the information is scattered, by design. Your access lives in a password manager. Your legal wishes live in a will. Your operational knowledge lives in your head. There has never been one place that holds who gets it, how they reach it, and what to do next together.

So the task feels impossibly large, and the impossibly large tasks are the ones we postpone forever. The reframe that helps: you're not planning your death. You're writing the onboarding doc for the person who replaces you — the one document every solo operation needs and almost none have.

Where Heirloom fits

This is the single problem Heirloom was built to solve. It's a death-binder for solo founders that holds the three layers in one place: a vault for the credentials and recovery paths that actually unlock the business, a clear record of beneficiaries so ownership and access point the same direction, and a structured handoff so a successor knows not just what they've inherited but what to do first. It's the access map described above, made concrete — so the gap between owning your business and being able to run it never opens.

If you've been meaning to write all this down and never knew where it would live, that's the whole idea. You can see how it works at https://heirloom.lumenlabs.works — and even if you build your own access map on paper this weekend, build it. The keys are the part the will forgets.