The conditions that actually protect a second attempt are structural, not emotional: a written scope, milestone payments, the domain in your name, and a date with a stated consequence. Four items. Vendors who agree to all four rarely produce the failure you already lived through.
This isn’t advice invented by an agency. It’s roughly what buyers who have been through a failed project prescribe to each other. One wrote publicly, after losing money: pay a small amount to begin, hold the balance until the work is complete, and sign a contract.
The moment it happens
Burned once, the non-negotiable conditions to set the second time are usually formed in the wrong direction — towards refusing advances entirely, demanding everything upfront in writing from strangers, and treating every quote as a probable fraud.
That posture is understandable and mostly counterproductive. It filters out careful vendors (who decline unreasonable terms) and leaves the ones desperate enough to accept anything — which is how a second failure gets selected for.
The four conditions
1. A one-page written scope. Pages, features, who writes text, revision rounds, what’s excluded. This is the document your first project didn’t have, and its absence is why “finished” was arguable. Everything else depends on it.
2. Milestone payments. Something small at start, something at design approval, the balance at go-live. Not 100% upfront. Not 100% at the end either — that term repels the vendors you want.
3. Domain and hosting in your name, from day one. This is the condition that caps how bad a second failure can be. If the project dies and you hold the domain, you lose the advance rather than your business name, and any new developer can pick it up.
4. A date with a consequence. Not necessarily a refund — many small vendors won’t sign one. A reduced final balance, or a hard handover of files and access on a stated date, is easier to get and still real.
| Your instinct after being cheated | What actually protects you better |
|---|---|
| Pay nothing until it’s perfect | Milestones tied to visible stages |
| Trust nobody, verify endlessly | Verify once, properly: live portfolio + one reference call |
| Demand a refund guarantee | Demand a written scope and a dated consequence |
| Go cheaper to reduce exposure | Cap exposure through structure, not price |
| Avoid advances entirely | Small advance against a written scope |
That last row matters. Reducing the budget after a bad experience is the most common response and the one most likely to reproduce it — the cheapest tier is where the failure modes concentrate.
Verification that’s worth the time
Two checks give you most of the signal:
- Open four live client sites. Not screenshots. URLs you can load on your phone. Then search one of those businesses to confirm the site is genuinely theirs.
- Call one past client. Ask two questions: did it go live on the promised date, and what happened when they needed a change six months later. The second answer is where the useful information lives.
Everything beyond this — extensive interrogation, demanding unusual terms — mostly signals to good vendors that the relationship will be difficult, and they price or decline accordingly.
Reasonable to say out loud
You don’t need to hide what happened. Saying it plainly usually improves the conversation: “My last project was paid for and never delivered. So I’ll need the scope and date in writing, payments in stages, and the domain in my name. Is that workable for you?”
A vendor who finds that reasonable is the one you want. A vendor who is offended by it has told you something useful for free.
What to do this week
- Write your scope yourself, in one page, before contacting anyone. It also clarifies what you actually need.
- Register the domain in your own account today, whoever you hire.
- Ask two shortlisted vendors for four live client URLs, and call one reference.
- Propose the milestone split before discussing price.
- Ask for a dated consequence. Accept a smaller one rather than none.
If you want it done the certain way
Bring the previous project with you — chat, files, a domain sitting somewhere else — and we’ll tell you honestly what’s salvageable before quoting anything. We publish prices, put the date in writing with a refund behind it, and register the domain in your name, which are the same four conditions above written as an offer rather than a request. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- Cheated by a web developer once? The safe-rebuild guide
- How much advance is safe to pay a web developer?
- Do you need a written agreement for a website project?
- How to verify a website company before you pay
FAQ
Should I refuse to pay any advance after being cheated once?
It’s an understandable instinct, but it tends to filter out reliable vendors who won’t work unpaid. A small advance against a written scope, with the domain in your name, limits your exposure more effectively than refusing advances.
Is it rude to tell a new developer I was cheated before?
No, and it usually helps. Stating it alongside your conditions explains why you’re asking for structure, and how the vendor reacts is informative before any money moves.
Should I spend less on the second attempt?
Spending less is the most common reaction and often reproduces the problem, since the cheapest tier is where these failures cluster. Cap risk through milestones and ownership rather than through budget.
