When a Founder Dies: Handing Over Business Accounts

Most founder estate planning starts with the shares. That is the wrong end. Between a death and a grant of probate there is a window of weeks or months in which the company still has customers, invoices, staff and a website, and almost every one of those depends on an account that only the founder could log into. This is not an inheritance problem. It is a continuity problem that happens to be solved with the same inventory.

Conclusion: continuity first, ownership second

Split the work in two and do them in order. First make the business runnable without the founder: someone other than the founder must be able to pay staff, keep the site up and answer customers. Second, and only then, sort out who owns what. Reversing the order produces the common failure, where the estate is settled cleanly a year later and the customers left in month one. The account inventory behind this is the same one used for personal planning and is set out in the digital legacy checklist.

The five accounts that cause immediate damage

• Payment processing — Payouts freeze when verification fails. A processor that cannot confirm who is operating the account may hold funds for months, and the funds are the business
• Domain and DNS — One expired renewal takes the storefront, the email and every login that uses that domain as its identifier. This is the shortest fuse on the list
• Hosting and cloud — Cards decline, instances stop, backups stop being taken. Data loss usually happens in the gap after service lapses, not at the moment of death
• Advertising accounts — Spend continues until the card fails, then the account is suspended for suspicious activity. Reinstatement needs the same identity documents as probate
• Business email — The mailbox is the recovery route for almost everything else. Losing it locks the rest of the list, which is why it is the first thing to protect

Licensed access, not inherited property

Almost every business platform grants a personal, non-transferable licence, so the account cannot be handed over as property. What can be done is different: designate an additional admin while alive, keep credentials in a vault with named emergency access, and document the recovery route for each service. The distinction between what is inherited and what is only licensed is covered in licensed versus owned digital assets.

Two fatal patterns in small companies

The first is the single-operator company where every login belongs to the founder and every second factor lands on the founder's phone. The technical name is a bus factor of one, and the fix is administrative rather than technical: name a second admin on the five accounts above, today. The second pattern is the opposite, where access was shared widely and nobody can say who holds what. Shared credentials feel resilient and behave like a liability, because every former contractor still has a working login and no one can revoke it selectively.

What the arrangement should contain

• A named operator and a named backup — Two people, not one, with authority to act on the operating accounts. The backup exists because the first choice may be on the same flight
• A credential vault with emergency access — Named access beats a shared password every time. See password vault for how release conditions work
• A written sequence for the first 72 hours — Payroll, domain renewal date, card on file for each platform, who to call at each provider. Concrete dates beat good intentions
• Domain and hosting renewal calendar — One page listing every renewal date and the payment method attached. This single page prevents the most common failure in this list
• A boundary between business and personal — The people who should run the company are not the people who should read your letters. Keep the two plans in separate vaults with separate recipients

Where the advisers fit

Lawyers handle authority, accountants handle tax and filings, and neither will log into your payment processor. The gap between legal authority and operational access is where small companies fail, and it is closed by documentation that an operator can follow without a court order. If the business owns domains or infrastructure, the recovery path for those assets is worth writing out separately: see domain inheritance and server account handover.

The test that tells you whether you are ready

Ask one question: if you were unreachable for thirty days starting tomorrow, could someone else pay the staff, renew the domain and answer a customer? If the answer requires your phone, your password or your presence, the business does not have a succession plan, it has a single point of failure with a legal document attached. Fixing that is a few hours of administrative work, and it is the only part of this that has to happen while you are alive.

Disclaimer

This article is general information about operational continuity and digital accounts. It is not legal, tax or corporate advice. Rules on director authority, probate, business relief and platform terms differ by jurisdiction and change without notice. Consult a qualified lawyer or accountant for your own structure before relying on anything described here.