The short answer
Do this first, today, before anything else: secure access to every account in your name, and write down what you paid for and what exists. Everything after that is easier if you do this now.
Silence usually is not malice. It is more often overcommitment, cash flow trouble, a technical problem they cannot solve and cannot admit to, or something genuinely bad happening in their life.
That matters, because it changes what you should do. But it does not change what you should do first.
Step one: protect your position
Do this today
- Secure every account you ownApple Developer, Google Play, hosting, domain, database. Change passwords where you can and check who else has access.
- Get whatever code you can reachIf you have repository access, clone it now. Access can be revoked.
- Take a backup of any live data
- Screenshot everythingMessages, agreed scope, invoices, payment records. Do this before any account closes.
- Write a timelineWhat was agreed, what was paid, what was delivered, when contact stopped.
None of that is aggressive. If they come back tomorrow, nothing has been lost.
Step two: read your contract
Two questions decide most of what follows.
Who owns the code? In the UK, copyright in commissioned software stays with the author by default unless it has been assigned in writing. Many people are surprised by this. Find the clause before you have the conversation.
What did you pay for? Milestones that were not met are a different position from hours that were genuinely worked.
Step three: make one clear written contact
One message, in writing, calm and specific. Not an ultimatum.
State what was agreed, what has been paid, what you understand to be outstanding, and a specific date by which you need a reply. Ask for the code and account access regardless of what happens next.
Step four: work out where you actually stand
| What you have | What it means | Realistic next step |
|---|---|---|
| Code access and it mostly works | Best case | Another developer finishes it |
| Code access, but it's a shell | Common | Assess honestly; a rebuild is often faster |
| No code, but you own the accounts | Recoverable | Rebuild from a fixed scope |
| No code, no accounts, no contract | Worst case | Rebuild, and buy differently next time |
Step five: decide, and buy differently next time
Whatever you do next, change the structure of the deal:
- A fixed deadline, so drift is visible immediately rather than in month four.
- A fixed price, so an overrun is not your problem.
- Code ownership in writing, from day one.
- A refund position that is clear before you pay.
Common questions
How long should I wait before assuming the worst?
Two working days of silence with no explanation is enough to start protecting your position. That does not mean escalating; it means securing accounts and documenting where things stand while you still can.
Can I get my money back?
It depends on what you paid for and what was delivered. If you paid for milestones that were not met, you may have a claim. If you paid hourly for hours that were genuinely worked, you probably do not, even if the result is unfinished.
Do I own the code they wrote?
Only if your contract says so. In the UK, copyright in commissioned software stays with the author by default unless assigned in writing. Check the contract before the conversation.