You paid your developer. Half the money upfront. They shipped some things, promised more, then stopped replying. Now your project is half-built, deadlines are missed, and you are wondering if you just lost the money.
I do codebase rescue as one of my services. I have seen this exact story more times than I can count. This post is the honest emergency guide — what to do in the first 48 hours, how to figure out what you actually have, and how to decide whether to try to save it or start over.
Do not panic. Do not spend more money yet. Do this first.
Before anything else, protect what you have.
If the developer has access to any of these, they can lock you out of your own product at any time. This is the first thing to do. Today.
If the developer put the code on their own account (a real risk), you need to get access before they revoke it. Contact them politely, in writing, asking for the code transfer. Do not accuse. Do not threaten. Just ask.
Before you go looking for a new engineer, make a list:
This list is what you will hand to the next engineer. Without it, they will need to spend 20 hours doing this discovery themselves and charge you for it.
You now need someone technical to look at what you have and give you an honest opinion. This is called a codebase audit or rescue audit.
Do not hire the next developer to build. Hire them to audit first. Two very different things.
A proper rescue audit answers:
A proper audit takes 3-8 hours of engineering time for most projects. Expect to pay ₹15,000 – ₹40,000 for it. Anyone offering "free audit" is going to give you a sales pitch, not an honest assessment.
After the audit, you will have a recommendation. Here is how to interpret it.
If most of these apply: fix it. Budget for 40-60% of the original scope's cost to finish and stabilise.
If most of these apply: rebuild. Budget for 70-90% of the original scope's cost, but with a proper engineer who knows what they are doing.
Sometimes the answer is "salvage the database and rewrite the code." Your user data, payment records, and business logic values are the valuable parts. Rebuilding the UI and business logic on top of preserved data is often the fastest path.
I see the same failures over and over. If you recognise any of these, you know why your project failed:
One person building a full product with no code review, no oversight, no accountability. Six months in, they realise they underestimated by 3x and either quit or ghost.
Prevention: for any project over ₹1.5L, either work with an established team or insist on weekly demos and a fixed milestone schedule.
A cheap offshore team quoted ₹80,000 for what should have been a ₹2L project. They assigned juniors who copied code from Stack Overflow. Six weeks in, nothing actually worked.
Prevention: if a quote is 40% below the market rate, the vendor is either losing money (they will quit) or cutting quality (you will get garbage).
You paid via Google Pay or bank transfer. Never signed a scope document. No milestones. No IP transfer. When the freelancer disappeared, you had no recourse and no clarity on what was owed.
Prevention: always have a written scope, a milestone schedule, and an IP clause that says the code belongs to you once payment is complete.
The original scope was 4 weeks. Then you added 5 features. Then you asked for a redesign. Then you changed the payment provider. The developer never pushed back, kept saying yes, ran out of budget and time, and eventually gave up.
Prevention: any scope change gets a written amendment with an updated cost and timeline. If the developer will not do this, they are setting themselves up to fail.
If your first developer failed, do not just hire someone cheaper the second time. Look for:
Red flags:
I do codebase rescue work exactly for these situations. The first conversation is always the same:
Based on that, I can usually tell you within 2 hours whether it is a fix job or a rebuild job. Then I quote fixed price to complete it, or I tell you honestly that I am the wrong fit and point you at someone better.
Message me on WhatsApp with what happened and what you have. I will not sell you anything you do not need.
How do I evaluate if an abandoned codebase can be saved or needs a rewrite?
Have a real engineer do a paid audit. Signs of "save" — standard tech, understandable structure, working core features. Signs of "rewrite" — custom framework, security holes, core features that do not work.
How can I regain control of my AWS, GitHub, or server credentials if the developer is unresponsive?
Contact the platforms directly with proof of ownership (payment history, domain records). AWS, GitHub, and most cloud providers have account recovery processes for this exact situation. It takes 3-15 days.
How long does a technical rescue audit take?
3-8 hours of engineering time for most small-to-medium projects. You should have a written audit and recommendation within 1 week of hiring an engineer.
What are the most common fatal flaws found in abandoned offshore builds?
Missing authentication (anyone can access anyone's data), payment logic errors (users can be charged wrong amounts), database schema without foreign key constraints (data drifts silently), no error monitoring (things break and nobody knows).
How do we ensure future developers do not repeat the same mistakes?
Written contracts. Milestone-based payment. Weekly demos. Code reviews for any project over ₹1.5L. Insist that the code goes to YOUR GitHub, not the developer's. IP transfer clause in the contract.
Or message me with what you have. I will give you a straight answer.