- Signs your developer has actually ghosted you
- What to do in the first 48 hours
- Recovering access if you're locked out
- What it costs to finish or rescue the project
- How a rescue developer evaluates what's already built
- Real example: a half-built WooCommerce store
- How to avoid this happening again
- FAQs
Signs Your Developer Has Actually Ghosted You
Freelancers get busy, and one slow week isn't ghosting. But a pattern is a pattern. Watch for: no response across email, WhatsApp, and phone for more than a week; repeated missed deadlines with no explanation; vague "almost done" updates with nothing to show for weeks; invoices sent for work that hasn't visibly progressed; or a portfolio/social presence that's suddenly gone quiet or deleted.
If two or more of these apply, it's time to stop waiting and start recovering — the longer a half-finished site sits untouched, the more it costs your business in lost leads and outdated content.
What to Do in the First 48 Hours
Recovering Access If You're Locked Out
This is the part that actually determines your rescue cost. There are three common situations:
| Situation | How to recover | Difficulty |
|---|---|---|
| You own domain + hosting, developer just built on it | Reset passwords on your own accounts, cut off developer access | Easy — no extra cost |
| Developer registered domain/hosting in their name | Contact registrar/host support with proof of payment and ownership; can take 1–3 weeks | Moderate — sometimes needs a support ticket escalation |
| No access at all, no response, files unknown | A rescue developer can sometimes pull a copy from search engine caches or the Wayback Machine, but functionality (forms, database) is often lost | Hard — may mean rebuilding, not recovering |
What It Costs to Finish or Rescue the Project
| Scenario | Typical Cost |
|---|---|
| Site is 70%+ done, you have full access, just needs finishing | $300–$700 |
| Site is 30–70% done, some cleanup of messy/broken code needed | $600–$1,200 |
| Site is barely started or code quality is unusable | $1,000–$2,500 (effectively a fresh build) |
| No access recovered, starting from scratch | Same as a standard new website build |
The biggest cost driver isn't how much work is left — it's how usable the existing code is. A half-finished site built cleanly is often faster to finish than a "finished-looking" site built with shortcuts that break the moment you touch them.
How a Rescue Developer Evaluates What's Already Built
Before quoting, a rescue developer should check:
- Whether the site uses a legitimate, licensed theme or a pirated/nulled one (a real security risk — see our WordPress security guide)
- Plugin quality and whether any are outdated or abandoned
- Whether the database and any custom functionality are intact or broken
- How much of the original scope (pages, features, content) is actually complete versus just visually placeholder-filled
- Whether it's faster to repair the existing build or start clean
Be wary of any developer who quotes a rescue price without actually looking at the site first — a proper evaluation takes 30–60 minutes and should always happen before a number is given.
Real Example: A Half-Built WooCommerce Store
A skincare brand hired a freelancer for a WooCommerce store. Ten weeks in — well past the agreed four-week deadline — the freelancer stopped responding entirely, with the payment gateway still unconnected and product pages half-populated. The owner had registrar and hosting access under her own accounts, which made the recovery straightforward.
A rescue evaluation found the theme was legitimate and most of the design work was solid, but the checkout flow needed to be rebuilt from scratch and several plugins were outdated. Total rescue cost: $650, completed in nine days — versus an estimated $1,800–$2,200 it would have cost to rebuild the whole store from zero.
How to Avoid This Happening Again
- Always keep domain and hosting in your own name — this alone prevents the worst-case lockout scenario.
- Use milestone-based payments, not full payment upfront — pay in stages tied to visible progress.
- Ask for weekly check-ins, even brief ones, as a standard part of the agreement.
- Check reviews or references before hiring — a pattern of past ghosting usually shows up somewhere if you look.
Frequently Asked Questions
My developer has my domain login — is that a problem?
Yes, this is the single riskiest setup. Domains and hosting should always be registered in your name, even if the developer manages them day-to-day. If a developer currently holds sole access, request a transfer of ownership in writing as soon as possible, even mid-project.
Can I get a refund from a developer who disappeared?
It depends on how you paid. Platforms like Upwork and Fiverr have dispute processes; PayPal and credit cards often allow chargebacks within a window (typically 60–120 days). Direct bank transfers are the hardest to reverse — this is one reason platform-based payment is safer for freelance hires.
Is it cheaper to finish the existing site or start over?
It depends entirely on code quality, not just how much is visually done. A rescue developer should evaluate this directly — a properly built 40%-finished site is often cheaper to complete than a messily built 80%-finished one.
What if I don't have access to the website files at all?
A rescue developer can sometimes recover a partial copy via cached versions or the Wayback Machine, but this rarely restores functionality like forms, databases, or e-commerce features — in most no-access cases, a fresh build ends up being the realistic path.
How fast can a rescue developer actually finish the project?
For sites that are 70% or more complete with clean code and full access, one to two weeks is typical. Heavily broken or barely-started projects take closer to a standard full-build timeline.
Should I report the freelancer somewhere?
If they were hired through a platform (Upwork, Fiverr), yes — report through the platform's dispute system, which also protects other clients. If hired directly, a documented paper trail is still useful if it escalates to a payment dispute.
