Stop when the expected recovery no longer exceeds what continuing to chase costs you — and count your attention and the missing website in that cost, not just fees. For most small advances paid to an untraceable vendor, that line arrives sooner than people allow themselves to accept.
The moment it happens
When do you stop chasing a developer and accept the loss? Usually you don’t decide. You just find yourself, two months later, still checking whether a number connects, still not having a website, and no longer sure what you’re waiting for.
The reason this drags is that stopping feels like letting them win. It isn’t. Stopping is a decision about where your next month goes.
The test
Three questions. Answer them honestly and the decision usually makes itself.
1. Is the vendor traceable? A real firm name, a verifiable address, a GST number, an invoice, money paid to a named business account — recovery is realistic and pursuit is rational. An anonymous UPI ID, a phone number that’s now switched off, no invoice — pursuit is a long shot.
2. Does the amount justify the process? A legal notice has a cost. A commission filing takes your time across months. Put a number on the fees and the hours, and compare it with what you paid.
3. What is the delay costing you? This is the question people skip. Every additional month of chasing is a month without a website, and for many businesses that has a larger price tag than the advance itself.
| Traceable vendor | Amount vs. pursuit cost | Reasonable move |
|---|---|---|
| Yes | Amount well above pursuit cost | Pursue — start with a legal notice |
| Yes | Amount similar to pursuit cost | Send the notice; skip longer routes |
| No | Amount well above pursuit cost | File the free online complaints; cap further spending |
| No | Amount similar to pursuit cost | Salvage what you can, then stop |
Salvage before you walk
Whatever you decide, do this first. Some of it is worth more than the money.
- The domain. Run a WHOIS lookup. If it’s registered in your name, take control of the account — the name itself has value and continuity.
- Hosting access. If you have or can get it, download a copy of whatever was built. A half-finished site can occasionally save a new developer a few days.
- Your own content. Text, photographs, logo files you sent. Collect them into one folder. This is the material that will be needed again, and re-gathering it is the slowest part of any restart.
- The evidence file. Export the chat, save the payment records. Keep it even if you stop pursuing — a later victim’s complaint can revive a dormant matter, and you’ll want the file intact.
- The free complaints. File on the cybercrime portal if payment was online, and leave a factual review. Both cost nothing and help the next buyer.
Stopping is not the same as forgiving
You can close the pursuit and still leave a permanent, factual public record. Write what happened without adjectives: dates, amounts, what was promised, what was delivered, what happened when you followed up.
That record is the part that has downstream value. The complaint boards burned buyers read before hiring exist because people did this.
Restarting without repeating it
The most common mistake after a loss isn’t emotional. It’s structural — going straight to the next cheap quote because the budget was already spent once.
Three changes make a repeat almost impossible, and none of them require a bigger budget:
- Register the domain yourself, in your own account, before hiring anyone. It costs about a thousand rupees a year and it’s the single thing that makes you unable to be held hostage.
- Pay against stages you can open on your phone, not against dates or descriptions.
- Keep the advance small — enough to be serious, not enough to be the whole loss.
There is a fuller list of second-time conditions elsewhere on this site. The three above are the ones that would have prevented most of what you just went through.
The honest reframe
You paid for a lesson at a price you didn’t agree to. That’s a real loss and it’s fair to be angry about it.
But the useful question now isn’t whether they should pay. It’s what gets you a working website in the next three weeks. Those are different projects, and only one of them earns anything.
What to do this week
- Answer the three questions and write down the decision.
- Run a WHOIS check and secure the domain if it’s yours.
- Collect your content and any built files into one folder.
- File the free online complaint and leave a factual review.
- Set a spending cap on further pursuit — and a start date for the rebuild.
If you want it done the certain way
Send us the domain and whatever you have, and we’ll tell you honestly what’s salvageable and what isn’t. Where we rebuild, the domain and logins are in your name from day one and payments follow stages you can see — the structure that makes a second loss impossible rather than a promise that it won’t happen. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- Recovery routes when a developer vanishes
- Add up everything: the true cost of failed website attempts
- The conditions to set the second time
- What files and access can you demand?
FAQ
Should I keep chasing a developer who took my advance?
Weigh three things: whether the vendor is traceable, whether the amount justifies the cost of pursuit, and what another month without a website costs your business. If the vendor is untraceable and the amount is modest, salvage and stop.
What should I get from a developer before I give up?
Control of the domain if it’s in your name, a copy of anything built, and all the content you supplied. Also keep a full evidence file — exported chats and payment records — even if you stop pursuing.
How do I avoid this happening with the next developer?
Register the domain yourself before hiring, keep the advance small, and tie each payment to a stage you can open on your own phone. Those three change the structure rather than relying on trust.
