Short answer: Secure your access first, before anything else. Confirm you control your domain registrar, hosting account and site admin, then take a full backup and document what exists. Only after that should you chase the developer, pursue a refund, or hire a replacement. Access is the thing that turns a bad situation into an unrecoverable one, and it is the thing people deal with last.
First, Is It Actually Abandonment?
Before escalating, rule out the ordinary explanations. Developers get ill, take leave, or lose a message in a spam folder, and treating a delay as abandonment can end a salvageable relationship.
| Signal | Likely meaning |
|---|---|
| No reply for two or three days | Usually ordinary. Follow up on a second channel |
| No reply for a week, no prior warning | Concerning. Begin securing access |
| Missed deadline but still communicating | A delivery problem, not abandonment |
| Replies that avoid specifics repeatedly | Often trouble ahead; ask for a demo of working functionality |
| Profile removed, or platform account closed | Treat as abandonment and act immediately |
| Requests more money before showing progress | Warning sign; do not pay before seeing work |
Try a second channel before concluding anything — email, phone, and the platform you hired through if applicable. Give a clear deadline for a response and say what you will do if you do not receive one.
Step 1: Secure Access Immediately
Do this today, in this order, regardless of how the situation resolves. Each item you do not control is leverage you do not have.
- Domain registrar. The single most important asset. If the domain sits in the developer’s account, your business email and website depend on someone who is not responding. Confirm you can log in and that the registrant contact is you.
- Hosting account. Confirm you are the account holder and that billing is in your name. Hosting registered to the developer means your site can vanish when a card expires.
- WordPress or platform admin. Confirm you have an administrator account, and create a second one if only one exists.
- DNS control. Sometimes managed separately from the registrar, for instance via Cloudflare.
- Repository and file access, if a code repository was used.
- Third-party accounts — payment gateway, analytics, email service, any API keys created for the project.
If you cannot access something, most providers have a recovery process for the legitimate owner. Contact them directly with proof of business ownership rather than waiting for the developer.
Step 2: Preserve What Exists
- Take a full backup of files and database, and store it somewhere you control, not on the same server
- Screenshot the current state of the site, including staging if you can reach it
- Export any content that only exists in the CMS
- Save your entire communication history, including the brief, quotes, invoices and any scope agreements
- Note what was paid, when, and against which milestones
Do not delete anything, even work you consider unusable. It is evidence of what was delivered, and a replacement developer will want to see it before quoting.
Step 3: Assess What You Actually Have
This determines whether the project can be continued or has to be restarted, and it is difficult to judge without technical help. A short paid review from another developer is usually money well spent before making a bigger decision.
| What you find | Usual implication |
|---|---|
| Working site, incomplete features | Continuable; another developer can finish it |
| Working site, undocumented custom code | Continuable but slower; budget for orientation time |
| Half-migrated or broken site | Assess carefully; may be cheaper to restart |
| No access to source files or repository | Often a restart, since you cannot build on what you cannot reach |
| Site built on a licence held by the developer | Licences may need repurchasing in your name |
| Nothing beyond a design mockup | Restart, but the design work may still be usable |
Step 4: Pursue What You Are Owed
Recovery depends heavily on how you paid and where you hired, so be realistic about the odds while still trying.
- Hired through a marketplace: open a dispute through the platform’s process. Escrow-held milestones are the most recoverable situation
- Paid by credit card: a chargeback may be available. Time limits apply, so act promptly
- Paid by bank transfer: recovery is difficult without legal action, and often not worth it for smaller sums
- Paid a deposit against milestones: document precisely what was delivered against what was agreed
Weigh the cost of pursuing recovery against simply moving forward. Many businesses spend more in time and stress chasing a modest sum than the sum is worth, while the project sits stalled.
Step 5: Hire a Replacement Properly
The instinct after being let down is to hire fast and cheap. That is precisely the pattern that produced the problem, and repeating it is common.
- Be transparent about the situation. Any competent developer will want to know they are inheriting someone else’s work
- Pay for an assessment first. A few hours of review before a full quote protects both sides from an inaccurate estimate
- Expect a higher quote than the original. Inheriting undocumented work genuinely costs more than starting clean, and a quote that ignores this is not credible
- Prioritise continuity this time. A team with backup cover cannot disappear the way one person can
- Confirm ownership arrangements upfront — domain, hosting, code and licences all in your name from day one
- Ask what happens post-launch, including whether there is a defined bug-fix warranty
If you are re-hiring, it is worth working through a proper vetting checklist rather than moving on instinct, and understanding how marketplace hiring differs from working with an established team, since continuity is exactly what failed here.
How to Make This Impossible Next Time
Nearly every case of a disappeared developer becomes serious for the same structural reasons. All are preventable at the start of an engagement.
| Protection | Why it matters |
|---|---|
| Domain registered in your name | You never lose control of your own address |
| Hosting account in your name, billed to you | The site cannot disappear with someone else’s card |
| Your own administrator account from day one | You are never locked out of your site |
| Milestone payments tied to deliverables | Limits exposure to what has been delivered |
| Regular deployments to somewhere you control | Work exists outside the developer’s machine |
| Your own backups, independent of the developer | Recovery does not depend on their cooperation |
| Licences purchased in your name | No repurchasing later |
| A team rather than an individual | One person’s absence does not stop the project |
The last row is the structural fix rather than a procedural one. An individual freelancer is a single point of failure by definition, which is fine for contained work and risky for anything your business depends on.
Frequently Asked Questions
What should I do first if my web developer disappears?
Secure your access before anything else. Confirm you control the domain registrar, hosting account and site administrator login, then take a full backup stored somewhere you control. Chasing the developer or pursuing a refund matters less than making sure you are not locked out of your own assets.
What if my developer owns my domain name?
Contact the registrar directly and use their dispute or recovery process, providing proof of business ownership such as company registration and invoices. This is a recognised situation and registrars have procedures for it. If the domain was registered on your behalf as part of a paid engagement, you generally have a strong claim to it.
Can I get my money back from a developer who disappeared?
It depends how you paid. Marketplace engagements have dispute processes and escrow-held milestones are the most recoverable. Credit card payments may allow a chargeback within time limits. Bank transfers are difficult to recover without legal action. Weigh the cost of pursuing it against simply moving the project forward.
Will a new developer finish an unfinished project?
Usually yes, provided you have access to the source files and the existing work is sound. Expect a higher quote than the original, because inheriting undocumented code genuinely takes longer than starting clean. Paying for a short assessment before requesting a full quote is worth doing.
How do I stop this happening again?
Register the domain and hosting in your own name, keep your own administrator account and backups, tie payments to delivered milestones, and require regular deployments to an environment you control. Working with a team rather than a single freelancer removes the single point of failure entirely.
Picking up a project someone else abandoned? We do this regularly, and every engagement includes a fixed quote within 24 hours, a 30-day bug-fix warranty, and full ownership of everything in your name. See how we work or get a free quote.