Don’t panic. On day one, secure your passwords and access, gather any notes the person left, then bring in someone to map the system before you decide anything. The software can be picked up by another team — you don’t have to rebuild it or replace them today.
What is the first thing to do?
Take a breath. Nothing breaks the moment someone walks out the door. Your first job is to secure access: change or lock down the key passwords and logins, calmly, as normal offboarding. This keeps your accounts and customer data safe while you sort out the rest.
How do I stop things from breaking?
Find out where your software lives and make sure your company can reach it. You need the accounts the code sits in, plus any logins that keep it running. If you’re not sure your company holds these, start there. Our guide on who owns the source code shows what you should have in your name.
Can someone else take over the work?
Yes. A working system isn’t locked to the person who built it. Another capable team can read it, understand it, and keep it going. They’ll need a little time to learn how it fits together first. That’s normal, and it’s far cheaper than starting over.
| Do this first | Not yet |
|---|---|
| Lock down passwords and access | Rush to hire a full-time replacement |
| Confirm your company owns the accounts | Promise customers big changes |
| Get someone to map the system | Rebuild the software from scratch |
| Gather any notes they left behind | Make a decision while panicked |
Do I need to replace them right away?
Usually not. Keep the software safe and running first, then decide slowly. Hiring under pressure often means hiring the wrong person. Once someone has mapped your system, you’ll know whether you need a full-time hire or just steady support to keep things ticking.
How do I avoid this happening again?
Make sure your company owns the accounts and the code, not any single person. Ask for plain notes as work happens, so nothing lives only in one head. A short handover after each big piece of work protects you. Our guide on what a good handover includes lists exactly what to ask for, and is it risky to hire a solo developer covers spreading that risk.
At Givore Studio we step in when the one person who knew everything is gone. We map what you have, keep it running, and hand you plain notes you actually own. One team, one point of contact, no knowledge trapped in someone’s head. Lost your lead developer? Tell us on WhatsApp.