Your Developer Disappeared Mid-Project: What to Do Next

You paid the deposit, waited for months, and the website still isn't finished. Messages go unanswered and calls ring out. It happens more often than most business owners expect, especially when a project rests on a single freelancer.

The good news is that a stalled project can usually be rescued. This guide walks through what to do from the moment you suspect your developer has gone quiet to the point where a new team takes over.

Warning signs your project is being abandoned

Developers rarely vanish overnight. More often, they fade out. Watch for these signs:

Replies that slow from hours to days
Deadlines pushed back again and again, with no clear reason
Promises that it's "almost done", but nothing you can actually see
Requests for the next payment before the current milestone is delivered
Hesitation when you ask for the source code or admin access

If two or more of these sound familiar, start preparing now rather than waiting for complete silence.

What to secure right away

This is the most important step. If your developer leaves holding every login, a new team may have to start almost from scratch. Check that you have:

Domain name registered to your company, not to the freelancer
Hosting or cloud account where the site runs, and who pays for it
Source code or access to the repository, such as GitHub or GitLab
Database backups of your customers, products and orders
Connected service logins, such as payment gateways, email and LINE Official Account
Project documents, including the contract, quotation, design files and the chats that define the scope

Ask politely first; many developers will hand everything over when asked directly. Once you have access, change every password and move account ownership to a company email address.

Finish it or start over?

The right answer depends on the actual condition of the work, not on the percentage your previous developer quoted. Any team taking over should review the code before giving you a price.

Situation	Usually the better path
Clean code on well-supported technology	Continue from the existing work and save time and budget
Some parts work, others are broken	Keep what works and rebuild only the problem areas
Messy, undocumented code or security holes	Rebuild; it usually costs less over the long run
No code at all, only a live site you can view	Rebuild, using the existing design and content as a reference

It can feel like rebuilding throws away money already spent. But forcing new features onto broken code often costs far more in endless fixes. Focus on the total cost from here on, not on what has already been paid.

How to choose a team that won't leave you stranded again

They review before they quote. A good team asks to see the code and system first, then explains what they found in plain language.
They have a real track record, ideally including projects they took over or rebuilt.
They are a team, not one person. If someone is sick or leaves, your project keeps moving.
Work is split into milestones you can see. Pay when there is something you can open and test.
You own the code and accounts from day one. Keep the repository under your company's account and put it in the contract.
They stay after launch. Ask clearly who fixes problems once the site is live.

How Celestial Code can help

Taking over unfinished projects is one of the things we do most. We start by reviewing what you have, show you what is usable and what needs fixing, and lay out both options, continuing or rebuilding, so you can decide with confidence.

Based in Bangkok, we have delivered more than 100 projects for businesses, studios and agencies, and we stay available after launch for updates, fixes and new features. Our team works comfortably in both English and Thai.

Is your project stuck? Send us the details and we'll assess it. Talk to an expert

Developer Disappeared Mid-Project? What to Do Next

Ready to build something great?