What your team needs if the founder is unreachable
In small companies one person often holds every key. A practical plan for the accounts, access and instructions your team needs if you cannot be reached.
In a small company, one person often holds the keys to everything: the domain, the bank, the cloud account, the payment provider. That works perfectly until the day that person is on a long flight, in hospital, or simply out of reach for two weeks, and the website goes down or payroll is due.
This is called the bus factor: how many people would have to become unavailable before the business stops working. For many small companies the answer is one. This guide shows how to raise it without handing everyone the keys today.
Step 1. Map what only you can do
Spend half an hour listing every task and account that depends on you alone. Typical examples:
- Domain and DNS. The registrar account. If the domain expires or DNS breaks, the website and email stop.
- Email and identity. The admin account for company email, often the recovery address for everything else.
- Cloud and hosting. The main account for servers, storage and databases, and who receives its billing alerts.
- Money. Business bank, company cards, the payment provider that takes customer payments, payroll.
- Code and product. Source code hosting, app store accounts, deployment access.
- Two-step sign-in. The phone or security key that receives the codes. This is the most commonly forgotten item: a password is useless if the code goes to your pocket.
- People and paperwork. Your accountant, lawyer, key clients, and where contracts and company documents are kept.
Step 2. Decide what should happen, and who should do it
For each item, decide what someone would need to do in the first days, and who that should be. Not everyone needs everything:
- your co-founder or operations lead may need the domain, hosting and payment provider;
- your accountant may only need to know where the invoices are;
- a family member may need to know who to call at the company.
Write the answer next to each item. This becomes your team’s plan.
Step 3. Share access properly where you can
For anything people need regularly, do not share your own login. Give them their own:
- add a second administrator to the domain registrar, cloud and company email;
- use team or role-based accounts where the service offers them;
- move shared logins into a team password manager;
- register a second two-step sign-in method, such as a security key kept in the office safe.
This is good practice anyway: it means people can do their jobs without borrowing yours.
Step 4. Prepare “break-glass” access for everything else
Some access should not be shared day to day: the owner account of the cloud provider, the bank, the recovery codes for the main email. Security teams call the emergency version of this break-glass access: credentials kept sealed, used only in an emergency.
For a small company, a good break-glass package contains:
- the owner or root credentials for the most critical accounts;
- recovery codes for two-step sign-in;
- a short runbook: what to check first, what to renew, who to call;
- contact details for your accountant, lawyer, bank manager and key clients.
The difficulty is keeping it sealed while you are available and making sure it reaches the right person when you are not. A Parcel Rocket parcel does exactly that. You put the break-glass package in a parcel, choose who receives it, and set a release date. It is encrypted on your own device before upload, so it stays private, even from us. We remind you before the date and you move it with one click; if the date ever passes without you moving it, your co-founder receives a link and opens the parcel by answering questions only they can answer. Each parcel has its own recipients, so your co-founder and your family can each receive only what is meant for them.
Step 5. Write the runbook in plain words
Your team will read it under stress. Keep it short and specific:
- “If the website is down, check the domain renewal first: registrar account, auto-renew is on the company card.”
- “Payroll runs on the 25th from the business account. The accountant can run it if you give them the approval code.”
- “Do not cancel the cloud account. Downgrade the plan only after talking to our developer.”
Our “If something happens to me” letter template works well as a starting point.
Step 6. Test it, and keep it current
- Ask your co-founder to read the runbook and tell you what is unclear.
- Check every six months that the credentials still work and the people are still right.
- Update the parcel whenever you change a critical password.
In short
Map what only you can do, give people their own access where they need it regularly, and keep a sealed break-glass package for everything else, with a short runbook they can follow. It is a few hours of work that can save the company weeks. For a full list of personal accounts to plan for as well, see our digital legacy checklist.