When a Freelance Developer Disappears Mid-Build: A Recovery Playbook for the Rest of Us

Question

As developers, we've all heard the horror stories — or been the rescue call ourselves. Here's a practical breakdown of what actually happens on the recovery side when a client's original developer goes dark, from an access-and-ownership perspective that's worth knowing whichever side of that call you're on.

The access problem is the real problem
Most "my developer disappeared" panic isn't really about the missing person — it's about who legally controls the domain registrar and hosting account. If those were set up under the client's own name from day one, recovery is a non-event: reset passwords, move on. If the previous developer registered them under their own account, you're now waiting on registrar support tickets, which can run one to three weeks even with clean proof of payment.

Evaluating someone else's half-finished code
Before quoting a rescue job, a proper evaluation checks: is the theme legitimately licensed (nulled themes are a real security liability), are plugins current or abandoned, is the database/custom functionality intact, and — critically — is it faster to patch what exists or rebuild the affected sections clean. A visually "80% done" site with shortcuts baked in can take longer to untangle than a cleanly built 40%-done one.

A real cost data point
On a recent WooCommerce rescue — client had full access already, which simplified things — the checkout flow needed a full rebuild but the rest of the design was solid. $650, nine days. A comparable fresh build would have run $1,800–$2,200. That gap is basically the value of "don't touch what's already working."

Full writeup with the access-recovery matrix and a broader cost table: https://amanurrahman.com/blog-post/developer-disappeared-website-rescue-cost