Quick Answer
Immediately secure your codebase, credentials, and documentation. Then engage a managed developer service to have a developer assigned within 24 hours and delivering code within 24 to 72 hours. Far faster than re-hiring through job boards, which takes 8 to 12 weeks.
In This Guide
The First 48 Hours
The first 48 hours after a developer quits are critical. Most of the damage control happens here.
Hour 1: Revoke Access
Before anything else, remove their access to all systems. Do this calmly and immediately.
- Git repositories: remove from all repos
- Cloud provider: revoke IAM access
- Production database: rotate credentials
- Slack, Notion, Linear: deactivate account
- Domain registrar and DNS panel: remove access
- Third-party SaaS tools (Stripe, Twilio, SendGrid)
Hour 2: Back Up Everything
Take a full backup of your current production database and all source code. Protect what exists.
Hour 3: Document the Current State
Get the outgoing developer to write down what is complete, what is in progress, and any credentials not already documented.
Protect Your Codebase
Ensure You Own the Repository
Check that your company account owns the Git repository, not the developer's personal account.
Rotate All Secrets
Treat all API keys, tokens, and passwords as compromised. Rotate database passwords, API keys, and session keys immediately.
Assess the Damage
Understand what shipped, what is half-done, and what is at risk. This assessment shapes how quickly you need a replacement and what experience level they need.
Your Options for Moving Forward
| Option | Time to Resume | Upfront Cost | Risk Level |
|---|---|---|---|
| Job Board | 8 to 12 weeks | Low | High |
| Recruitment Agency | 4 to 6 weeks | High fee | Medium |
| Freelancer | 1 to 3 days | None | High |
| Managed Subscription | 24 hours | None | Low |
How to Prevent This Next Time
Never rely on one developer
Single-developer dependency is a major risk. Ensure code is documented and version-controlled.
Own all credentials
All accounts should be registered under your company email, never a contractor's personal account.
Consider a managed model
With a managed developer subscription, the provider carries the continuity risk. If one developer is unavailable, the provider handles replacement.
Frequently Asked Questions
My developer quit today. What do I do first?
Revoke their access to all systems immediately: Git repositories, cloud accounts, databases, and third-party services. Then back up all code and data.
Can I get a replacement developer in less than a week?
Yes. Hokantan can assign a dedicated developer within 24 hours, with first delivery in 24 to 72 hours. Traditional hiring takes 8 to 12 weeks.
What if my codebase is a mess?
A codebase audit is standard. Your new developer will spend 1 to 3 days reviewing existing code before continuing work. This is normal.
Who owns the code?
With Hokantan, you own 100% of the source code from Day 1. All intellectual property belongs to you.