Short answer: first take control of every account (domain, hosting, database, code repository, app stores), then get a copy of the code, then have another developer review it before you spend more. Most abandoned projects can be finished or repaired; a review tells you which, and what it will cost.
Warning signs before a developer disappears
- Replies slow from hours to days, and deadlines move without explanation.
- You have never seen the code, or it is only on the developer's machine.
- Accounts for hosting, the domain or app stores are in the developer's name.
- Requests for payment ahead of milestones, or for "final payment before handover".
If you see two of these, start step 1 below now, while the developer is still responding.
The 7 steps
- List every account the software uses. Domain registrar, DNS (for example Cloudflare), hosting or cloud (AWS, Vercel, Render, a VPS), database, code repository, email service, payment gateway, Google Play and Apple developer accounts, analytics.
- Change ownership and passwords. Where the developer owns an account, ask them in writing to transfer it. Where you own it, remove their access and turn on two-step sign-in.
- Recover the code. If there is no repository you can access, the code can often be copied from the server the app runs on. For mobile apps, check what the store accounts and build files hold.
- Back up everything now. Database, uploaded files and the server configuration, before anyone changes anything.
- Get an independent review. How the system is built, what is unfinished, what is unsafe, what it runs on, and what each fix costs.
- Decide: finish, repair or rebuild. Finishing is cheapest when the code is sound; rebuilding only makes sense when the foundations are wrong.
- Put it under maintenance. A maintenance contract with a named contact, backups and monitoring, so this does not happen again.
What a takeover review should cover
- How the system is built: languages, frameworks, database, hosting, integrations.
- What is finished, half-finished and missing, compared with what you were promised.
- Security: exposed keys, open databases, outdated libraries, missing backups.
- How hard the code is to change, and why.
- A plan with costs: finish, repair or rebuild, and what to do first.
Typical timeline: the review takes one to two weeks; urgent fixes and moving accounts into your name follow in the next one to two weeks; then routine maintenance.
The account checklist
| Account | Why it matters |
|---|---|
| Domain registrar | Whoever controls it controls your website and email |
| Hosting or cloud | Where the app and often the code live |
| Database | Your customers and your business records |
| Code repository | Without it, every change is harder |
| App store accounts | Updates to mobile apps are impossible without them |
| Payment gateway | Your money and refunds |
How to prevent it next time
- Every account in your company's name from day one.
- Code pushed to your repository at least every week.
- Documentation as part of every milestone.
- A contract that assigns the IP to you on payment.
How we help
We take over software built by others, in India and abroad: a fixed-price assessment (₹25,000–75,000, or about $300–900), stabilisation, then maintenance. See software maintenance and AMC, or WhatsApp +91 93091 93613.
