The asset nobody can find

When a solo founder dies, the legal questions get answered eventually. Copyright in the code passes to the estate automatically — intellectual property is property, like a house or a brokerage account, and it moves through a will or through intestacy whether or not anyone planned for it. On paper, your family inherits the business.

In practice, they inherit a name they can't prove, hosted on servers they can't reach, earning money into an account they can't see the inside of. The asset exists. It's just illegible. And an asset no one can read is an asset no one can sell.

This is the gap most continuity planning misses. Keeping the lights on is one problem. Turning the thing into money — actual money your spouse or kids can use — is a different one, and it has a clock on it.

A buyer pays for proof, not for code

Here's the counterintuitive part. The source code is rarely the valuable thing. Anyone can rewrite software. What a buyer pays for is evidence that the software already makes money and that the money will keep coming after the handover.

When someone acquires a small profitable SaaS — and there's a real, active market for these, through broker marketplaces built specifically for sub-million-dollar online businesses — they don't start with the repo. They start with diligence. They ask for:

  • Proof of revenue. Not a screenshot of a dashboard. Statements from the payment processor and the bank that tie out to each other, ideally twelve months deep.
  • Proof of traffic. Read access to the real analytics, so they can see where customers come from and whether the trend is up or down.
  • A clean chain of title. That the code, the domain, the trademark, and the brand assets are genuinely owned and freely transferable — not entangled with a contractor who was never paid or a logo bought under an unclear license.
  • The operating manual. What breaks, how often, and what a human has to do each week to keep it running.

A price gets set as a multiple of the business's yearly profit. But the multiple is fragile. Every question the seller can't answer cleanly drags it down, because every gap is a risk the buyer now has to price in. With a living founder, those gaps get filled in a phone call. With a dead one, they can't be filled at all — and a question that can't be answered isn't a discount. It's often a deal-killer.

Sellability decays faster than the business does

The cruelest part is the timeline. People assume a profitable business is a stable thing that will sit and wait while the estate works itself out. It won't.

Probate routinely takes months. A small SaaS does not have months. Customer cards expire and nobody updates the failed-payment dunning. Support tickets go unanswered and refunds get filed. A renewal notice for the domain lands in an inbox no one is watching. The hosting bill auto-charges a card that gets cancelled when accounts are frozen, and one morning the product simply returns an error page.

Each of these is survivable alone. Together, over eight or ten weeks, they compound. Revenue that was the entire basis of the valuation starts visibly falling — and now the business isn't just hard to sell, it's demonstrably declining, which is the worst possible story to walk into a negotiation with. The estate often ends up settling for a fraction of what the same business was worth the week the founder died, or letting it die quietly because nobody could move fast enough to catch it.

The value didn't disappear because the product got worse. It disappeared because the proof rotted while the paperwork crawled.

The bus factor, applied to your estate

Engineers have a grim shorthand for this: the bus factor. How many people would have to be hit by a bus before the project stalls? For most solo founders, the answer is one. You are the entire bus factor — and not just for the work, but for the knowledge that makes the work sellable.

Think about everything that lives only in your head. Which email is attached to the payment processor. Whether the trademark was ever actually registered or just used. That the analytics live under a personal Google account, not the business one. That there's a second AWS account from a migration three years ago that still hosts the image assets. None of this is written down because you've never needed to write it down. You just know.

That tacit knowledge is exactly what a buyer's diligence is trying to extract — and exactly what dies with you. The business can survive your absence. Its legibility cannot, unless you make it legible in advance.

Build the diligence packet while you're alive

The fix is not complicated, which is what makes it easy to keep postponing. You assemble the packet a buyer would eventually ask for, before anyone needs it, and you keep it somewhere your family can actually reach.

Work backward from the diligence questions:

  • A revenue trail that proves itself. A short note on which processor, which login, which bank account — and where the last year of statements can be pulled. The point isn't to export everything today; it's that the path to the proof is written down.
  • An inventory of what's owned and where it lives. Domain registrar, code repository, design files, the trademark status as it actually is. List the accounts, not just the assets, because access is the thing that's missing, not ownership.
  • The honest operations note. What you do each week. What breaks. Which vendor sends the scary email. Written for someone who has never seen the inside of the business and is reading it on the worst day of their life.
  • A named human and a plan. Whether the realistic outcome is sell it or wind it down gracefully, and who you'd trust to run that process — a technical executor who can speak to a buyer in a language you no longer can.

Notice what this packet does even if you never die: it's the exact document you'd hand a buyer the day you decide to sell on purpose. The work isn't morbid overhead. It's the same work that makes the business sellable at all — you're just doing it before the deadline picks itself.

What you're really leaving behind

There's a quiet dignity in this that's worth naming. A solo business is often the most valuable thing a founder builds, and the most invisible. It doesn't look like an inheritance. There's no deed, no statement that arrives in the mail, no advisor who knows it exists. If you don't make it findable and provable, the most likely outcome isn't that your family sells it for less. It's that they never realize it was worth anything, and it evaporates while they're grieving.

Making it sellable is, in the end, an act of translation — turning something only you can read into something the people you love can hand to someone who'll pay for it.

That translation is precisely what Heirloom is built to hold. It's a death-binder for solo founders: a single vault for the accounts, the proof, the IP chain, and the operating notes, paired with a structured handoff to the person who'll act on them and the beneficiaries who'll receive what it's worth. Not a folder you'll get to someday — the diligence packet, kept current, ready to become money instead of mystery.

If you've ever thought my family would have no idea what this is worth, that's the thing to fix first. You can start your binder at heirloom.lumenlabs.works — and leave behind an asset, not a riddle.