Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

The only developer who knew our system has left

Short answer

When the only person who knew the system leaves, the first job is not to fix anything. It is to make sure you can still get in: accounts, servers, code, domain, store listings and payments. Remove the leaver's access only after you have your own, then list what the system depends on and put a second person on it.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The developer's last day has passed and nobody knows how to deploy.
  • Only they had the server password or the store login.
  • Something broke and no one on the team can say where to look.
  • I do not know where the code, the database or the backups are.
  • Bills for hosting and services still go to the developer's email.

Why does this happen?

  1. All knowledge sat in one head

    In a small team, one person sets up the server, the deploys and the keys, and nobody else needs to know. It works until that person leaves, and then nothing is written down.

  2. Accounts were registered to a person, not the company

    Hosting, domain, store and code accounts opened with a personal email follow the person, not the company.

  3. Only one person had top-level access

    GitHub recommends keeping the organization owner role small but never below two people, so that ownership continues if one owner becomes unavailable. A company with a single owner has no such cover.

  4. Secrets are known only to the person who set them

    Keys, tokens and passwords may sit in a file on one laptop or in a repository history.

What can I do about it today?

  1. Make a list of everything the product touchesDomain, hosting, database, email sender, payments, store accounts, push notifications, analytics, code repository. Next to each, write who has access today.
  2. Get access to the accounts you can reach as the companyStart with the ones tied to a company email: the domain registrar, hosting and billing. Add a second administrator wherever the service allows it.
  3. Ask the developer for a short call or a written noteIf the leaving was friendly, a few hours of questions can save weeks. Ask where the code is, how a release is made and what runs on a schedule.
  4. Do not remove the leaver's access yetRemoving it before you have your own can lock you out. Plan the removal and the password changes for the day you are in.
  5. Take a backup of the database and files you can reachIf you can, ask your host for a snapshot now. Do not change the live system.
  6. Do not start a rewriteA rewrite of a system nobody understands is expensive. First learn what you have.

When should I bring someone in?

  • Nobody on the team can log in to the server or deploy.
  • Something is already failing and the person who knew why has gone.
  • You need a second pair of hands while you hire a replacement.

How do I handle it?

  1. Map the system from what is runningFrom the domain, the hosting dashboards and the app itself, I rebuild the picture: what runs where and how it talks to the rest.
  2. Get the company in controlAccounts move to company-owned emails, a second administrator is added and the leaver's access is removed in an agreed order.
  3. Write the missing handoverA short document: where everything lives, how to release, how to restore a backup and what to watch. Written from the system, not from memory.
  4. Stay as the second person until you hireI can keep things running and make small changes while you recruit, and then hand over to your new developer.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Should I contact the developer after they left?

Yes if the parting was on good terms and your contract allows it, with specific questions and a time limit. If it was not, speak to a lawyer about what you can ask.

How do I stop this happening again?

Company-owned accounts, at least two administrators, the code in a company repository and a short written runbook, checked every few months.

Do I need a full-time replacement straight away?

Not always. A stopgap while you hire gives you time to choose well instead of in a hurry.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.