The Developer Disappeared: A Recovery Guide for Small Businesses

It starts with unreturned emails. Then radio silence. Eventually you realise: your developer has disappeared. The site is half-finished, or it’s live but you can’t update it, or something’s broken and you have no idea how to fix it. This happens more often than you’d think. Here’s what to do.

First: Don’t Panic (But Do Act Quickly)

The instinct when a developer disappears is either to panic or to wait and hope they come back. Neither is ideal. What you need is calm, methodical action, starting with the things that protect your business right now.

Before you worry about redesigns or rebuilds, you need to answer one question: do you actually control your own website?

That means: do you have the login details for your hosting, your domain registrar, and your WordPress admin? If you don’t, that’s the first problem to solve, and it’s more common than you’d think. Plenty of businesses have their entire web presence sitting on accounts they can’t access because the developer set everything up under their own email.

Secure What You Can

Start with your domain name. When a developer has disappeared, this is the most important thing to secure first. If you don’t know where it’s registered, a WHOIS lookup will tell you which registrar holds it. Your business name on the registration means you can recover access through the registrar directly. The developer’s name on it makes for a more complicated conversation, but you can still recover it in most cases.

Next, your hosting. Same principle: work out who the hosting provider is and whether the account is in your name. If you’re paying for it directly, you have leverage. If the developer was handling payments, contact the host and explain the situation. Most hosting companies have dealt with this before and have processes for it.

Finally, your WordPress admin access. If you can log in, change the admin password immediately. If you can’t, your hosting provider can usually help you reset it through the database. It sounds technical, but it’s a standard support request.

The goal here isn’t to fix anything yet. It’s to make sure you own and control everything that’s yours.

Assess What You’ve Actually Got

Once you’ve secured access, you need to understand the state of things. If your developer disappeared mid-project, the site may be in a very different state to what was promised. This is where it helps to get someone technical involved, but here’s what you’re looking for:

Is the site actually working? Load it on your phone and your computer. Click through every page. Fill in the contact form and see if the enquiry arrives. Check that your phone number and email are correct. Sometimes a site looks fine on the surface but key functionality has quietly broken.

When was it last updated? Log into WordPress and check the dashboard for the last update date. If you’re seeing notifications about updates that are months or even years old, that’s a sign nobody’s maintained the site. Outdated WordPress core, plugins, and themes are a security risk, but don’t just hit “update all” without knowing what you’re doing. That can break things further. The WordPress.org security page explains why keeping up to date matters

If your site is on WordPress and you’re realising it might need more than just updates, perhaps you’ve outgrown the platform it was originally built on, I’ve written a separate guide on what happens when you’ve outgrown Squarespace that covers the migration process in detail.

Do you have backups? Check with your hosting provider. Many include automatic backups as part of their hosting package. If you have a recent backup, you have a safety net. If you don’t, getting one set up should be a priority before anyone touches anything.

What was left unfinished? If the developer disappeared mid-project, list what they promised against what they delivered. This is useful for any conversations about refunds, but more importantly, it tells your next developer exactly where they’re picking up from.

Your Developer Disappeared, Now What Do You Look For?

A website isn’t a one-off project. It needs regular updates, security patches, backups, and someone to call when something breaks.

This is where most businesses feel stuck. When your developer has disappeared and you’ve been let down, the idea of trusting someone new feels risky. That’s completely understandable.

Here’s what to look for in whoever takes over:

They should be willing to audit first. Any developer worth working with will want to look at what exists before quoting you for work. A proper audit tells you whether to salvage the existing site, improve it, or replace it entirely. Be wary of anyone who quotes you for a full rebuild without looking at what you’ve got, sometimes the existing site is perfectly solid and just needs finishing or maintenance.

They should explain what they find in plain English. If you’re getting walls of jargon about PHP versions and database optimisation, that’s not helpful. You need someone who can tell you, clearly, what’s wrong, what’s at risk, what needs fixing now versus later, and what it’ll cost.

They should talk about ongoing support. One of the biggest reasons businesses end up in this situation is that there was never a proper plan for what happens after launch. A website isn’t a one-off project. It needs regular updates, security patches, backups, and someone to call when something breaks. Ask about maintenance packages and ongoing support before you commit.

They should be transparent about what they can recover. An honest developer will tell you if some of what the previous developer built isn’t salvageable. They won’t promise miracles, and they won’t trash the previous developer’s work just to justify a bigger invoice.

What This Actually Costs

I’ll be straight with you: when a developer has disappeared, recovery isn’t free, and it’s rarely cheap. But it’s almost always less expensive than you fear.

If the site is fundamentally sound and just needs securing, updating, and maintaining, you might be looking at a few hundred pounds for an audit and initial fixes, plus an ongoing maintenance arrangement.

If the site needs significant work, finishing incomplete features, fixing structural problems, or addressing security issues from months of neglect, expect to invest more. But a good developer will prioritise: fix the critical stuff first, improve the rest over time.

If the site genuinely needs rebuilding from scratch, that’s a bigger conversation. But even then, you’re in a better position than you were the first time around. You know what you need. You’ve got the right questions to ask. And you know what a bad developer relationship looks like, which means finding a good one is much easier this time.

For a more detailed look at what web development actually costs and where the money goes, I’ll be publishing a comprehensive guide to website investment soon, I’ll link it here when it’s live.

How to Avoid This Happening Again

Making sure your developer never disappears on you again comes down to a few basics:

Own everything yourself. Register your domain, your hosting, and your WordPress admin to your business email, all with passwords you control. Your developer should have access, but you should own the accounts.

Get a maintenance agreement in writing. Know exactly what it includes: how often updates happen, what the response time is for emergencies, what it covers and what it doesn’t. This doesn’t have to be expensive, but it does need to exist.

Keep records. Have a document that lists every login, every service, every renewal date. Update it whenever something changes. If your developer disappears tomorrow, whether that’s a bus or just a decision to move somewhere warm, you need to be able to hand this document to someone new and have them understand your entire setup.

Check in regularly. You don’t need to understand the technical details, but you should be logging into your site periodically. Is it working? Does it look right? Are there alarming messages on the dashboard? A five-minute check once a month can catch problems before they become emergencies.

The Silver Lining

Every business I’ve worked with where the developer disappeared has ended up with a better setup than they had before.

I know it doesn’t feel like it right now, but being in this situation isn’t all bad. You’ve learned what matters in a developer relationship. You know that communication, reliability, and ongoing support aren’t optional extras, they’re the whole point.

Every business I’ve worked with where the developer disappeared has ended up with a better setup than they had before. Not because the previous developer was necessarily bad at building things, but because now they understand what a proper web partnership looks like.

Helping businesses recover when their developer has disappeared is exactly the kind of work kupu was built for. If you’re stuck with a site you can’t access, update, or trust, I’d be happy to chat about what we could do. No pressure, just an honest conversation about whether we’re a good fit. Drop me a message at enquiries@kupu.co.uk or connect on LinkedIn.