What happens to your SaaS access if your CTO is gone tomorrow
Most small companies run on SaaS tools that one person set up, one person pays for and one person can recover. The question is not whether that person is trusted. It is what happens on the day they cannot answer the phone.

Ask the founder of a twenty-person company who owns their cloud hosting account and the answer is usually "the company". Ask whose name is on the admin login, whose phone receives the security code and whose card pays the invoice, and the answer is usually one person. Often it is the CTO, sometimes a co-founder, occasionally a contractor who left two years ago.
Illness, an accident, a sudden resignation or a death all produce the same practical problem. The company may well own its data and its subscriptions, but nobody who is still there can log in to them.
Key person risk: who actually holds the keys?
Software access in a small company tends to collect around whoever set it up. The person who opened the hosting account typically became its root user. The person who registered the domain is usually the registrant. The person who created the workspace is often its super administrator, and the person who connected the payment processor is the account owner the provider recognises.
That concentration is rarely anyone's decision. It builds up one sign-up at a time. A useful exercise is to list the services the business could not trade without for a week and write one name beside each:
- email and the shared calendar
- the domain name and its DNS
- cloud hosting and the code repository
- the payment processor and the business bank's online banking
- accounting, payroll and the customer database
- the password manager itself
If the same name appears more than twice, the business has what engineers call a low bus factor: the number of people who would have to disappear before the work stops. For many small companies that number is one, and more often than not the one is the CTO.
What happens on day one
The first thing people discover is that "the company owns it" and "the company can get in" are different statements. A provider will usually want to hear from the account holder or from someone it can verify has authority over the organisation. Proving that authority takes documents, time and a support queue, and each provider runs its own process.
Meanwhile the ordinary machinery keeps running. A domain renewal fails because the card on file was a personal card that has now been stopped. A security alert goes to an inbox nobody can open. Two-factor codes arrive on a phone locked in a drawer. A customer asks for a refund through a payment dashboard that only one person could reach.
Any one of these is manageable. Together they can leave a business unable to bill, deploy or even read its own email for weeks, at the moment the people left behind are also dealing with the human side of what has happened. This is key person risk in its most ordinary form, and for most small companies it is a business continuity gap in the SaaS stack rather than a people problem.
Why a password spreadsheet makes it worse
The instinctive fix is to write every password down somewhere a colleague can find it. That trades one risk for a larger one. A shared list of live credentials is a security exposure every day it exists, it goes stale the first time anyone rotates a password, and it still fails at the second factor.
What a successor needs is far less sensitive: which services exist, which of them matter most, who is named as the owner or administrator on each, where the credentials are kept and who is authorised to use them, and what the recovery route is if the named person is unavailable.
What can be arranged in advance
Several of the steps that help most cost nothing but an afternoon. Many business software providers support more than one administrator, and a second named admin on the services that matter removes much of the lockout risk before it starts. Billing can usually be moved to a company card rather than a personal one. Recovery email addresses can point at a shared role mailbox that outlives any individual. The same questions come up for founders planning their own continuity, which is why they sit on our page for startups as well.
The rest is record keeping. A business succession plan records who takes over, who steps in temporarily and where business credentials are held, without holding the credentials themselves. Our business succession planning tool captures your successor, co-owners, key people and credential locations in one structured plan alongside your will. It can release your plan to your chosen successor once your death is confirmed, and it produces a successor handover pack that gives them what they need to act without ever including a password. Its Authority Gap Checklist lists what you must arrange yourself, because the platform records intentions: it does not transfer accounts, change directorships or move bank mandates.
For the accounts themselves, a digital services record catalogues each service with its purpose, its two-factor method, its recovery email and hints about where the credentials live: the kind of record someone else would otherwise have to rebuild from invoices and old emails.
Incapacity is not the same as death
Most succession thinking assumes a death, but the more common scenario is a key person who is alive and simply unable to act for a while: a long illness, a serious accident, a hospital stay with no phone. A will does nothing in that situation, and a succession plan set to release on death does not release either. Whether anyone can act on a person's behalf while they are alive depends on the arrangements in place, such as a power of attorney, and on the rules of the country concerned. It is worth knowing which of your plans cover incapacity as well as death, and which cover only one.
When the personal and the business overlap
For a founder, the line between personal estate and business assets is rarely clean. Shares, a director's loan, intellectual property registered in a personal name and a personal card paying company bills all sit on both sides of it. Our guide on whether you can write your own will lists business interests among the situations where a professional's input is usually worth having. For a founder that matters because a will and a company's own documents can point in different directions.
A short checklist to start with
1. List the services the business could not run without for a week. 2. Write one name beside each, then find every name that appears more than twice. 3. Add a second administrator where the provider allows it. 4. Move billing from personal cards to company ones. 5. Record where credentials are held and who may use them, not the credentials themselves. 6. Decide who takes over, who steps in temporarily, and make sure they know.
A business that only one person can open is only as available as that person.
This article is general information, not legal, tax or financial advice. Rules on company authority, account ownership and powers of attorney differ between countries. Speak to a qualified professional about your own circumstances.
Written by
TheWILL.ai Team
The editorial team at TheWILL.ai, dedicated to making estate planning accessible and modern.

