My Developer Ghosted Me

Your developer ghosted you. I don’t mean slow replies. I mean gone. The emails go unanswered, the phone rings out, the chat shows your last five messages and nothing back. You have a half-built app, money already spent, and no idea what state anything is in.

Here is what to do, in the order to do it. Most of it can be done this week, and none of it requires knowing how to code.

When to treat it as real

One unanswered email is a busy week. A week or two of silence on every channel you have is something else.

At that point, start protecting yourself. You don’t have to be certain they’re gone. If they turn up tomorrow with a good explanation, you’ve lost nothing by having secured your own product. If they don’t, you’ve saved yourself weeks.

Secure what you can reach

Keep it that short. You want a written record that you asked plainly and gave a deadline, and you want to leave the door open for them to hand things over without an argument.

If they hold the keys

The third group on your list, the accounts you can’t reach, is the hard part.

Start with the domain. It is the most urgent thing on the list, because your website and often your email both depend on it, and a domain that lapses can be bought by someone else. Find out who it’s registered to. If it’s in your name or was paid for on your card, the registrar’s support team can usually get you back in once you prove who you are.

Hosting and code are harder. If they sit in the developer’s own accounts, the companies that run those accounts will generally not hand them to you, whatever you paid the developer. Ask anyway, and bring every invoice and email you have.

If the developer is in your country and real money is involved, a letter from a lawyer sometimes produces a reply when nothing else has. If they’re overseas, be realistic. A contract with someone on the other side of the world is very hard to enforce, which I wrote about in what happens after an offshore MVP is “done”.

If you need someone’s cooperation to reach your own product, you don’t have a product yet.

Why contractors disappear

It helps to know this is rarely personal.

The most common version I see starts with a price that was too low. The developer quoted a number to win the job, the work turned out bigger than the number, and the money ran out before the project did. Finishing would mean working for nothing, and another client is paying this month. So they drift toward the paying work and stop opening your emails, because every one of them is a reminder of a job they can’t afford to finish.

Sometimes they hit a problem they couldn’t solve and couldn’t bring themselves to admit it. Sometimes they took on more clients than they could serve. With a contractor you found online, far away, there is very little holding them to you once the project stops being worth it to them.

None of that excuses it. It does tell you where the risk came from, and most of it was visible in the first quote.

What you still have in the worst case

Suppose it all went the wrong way and you can’t reach the code or the hosting. You still have more than it feels like.

You have the recording of the app working. You know what it’s for, what was awkward about it, and what you’d change. A developer starting again from a working example and a founder who has already used the thing has a much shorter job than the first one had. The second build is usually faster than the first.

Bringing in someone new

If you do have the code, whoever comes next has to read it before they can tell you what it’s worth. That reading is real work, and you should pay for it. Usually some of it is kept and some is rebuilt. Be wary of anyone who gives you a verdict in either direction without having looked.

When you hire again, change three things:

• Own every account from the first day. Open them yourself and invite the developer in. I covered how in Your AI Prototype Stalled. How to Hire Someone to Finish It.
• Be suspicious of the lowest quote. A price nobody else can match usually means a scope nobody has defined.
• Check in every week. I Think My Developer Is Lying to Me has five checks that need no technical knowledge. A developer who is about to go quiet shows it there first.

If you’d rather have someone on your side doing that with you, that’s the work I do as a fractional CTO.

Frequently Asked Questions

What should I do if my developer stops responding?

After a week or two of silence on every channel, treat it as real. List every account the app depends on and check which ones you can log into. Record the app working, copy any code and data you can reach, then change the passwords on the accounts you own. Send one short written message with a deadline asking for the code and logins.

My developer disappeared with my code. Can I get it back?

Sometimes. If the code is in an account you own or can reach, download a copy now. If it sits in the developer's own account, the company hosting it will generally not release it to you. A lawyer's letter can work when the developer is in your country. Overseas, it is very hard. What Happens After Your Offshore MVP Is "Done" explains why.

Can another developer finish an app someone else started?

Often, yes, if you have the code. The new developer has to read it before they can say what it is worth, and that review is paid work. Usually some is kept and some is rebuilt. If you have no code, a recording of the app working still makes the second build much faster than the first.