Not confidence in the vendor — a capped downside. Buyers who’ve been burned describe the same set of conditions afterwards, and every one of them limits what a failure costs rather than trying to predict whether one will happen.
The moment it happens
What finally makes a nervous buyer pay for a website is worth understanding because most advice gets it backwards. The usual suggestion is to research more, meet the person, check the portfolio — all of which aim at feeling certain.
You won’t feel certain. People are hard to read, and complaint records are full of buyers who found their vendor entirely convincing. The buyers who proceed successfully aren’t the ones who got confident. They’re the ones who arranged things so being wrong was survivable.
The five conditions
Buyers who’ve been through a bad experience tend to prescribe the same list. It’s worth taking seriously, because it’s written by people who paid to learn it.
1. The domain in your own account, registered before hiring. About ₹1,000 a year, ten minutes. This alone converts the worst case from “lost my business name and my money” to “lost a small advance.” Nothing else on this list comes close.
2. An advance of 20–30%, not half. Enough to be a serious commitment, not enough to be the whole loss. A vendor confident of being paid on delivery doesn’t need half.
3. Payments tied to stages you can open on your phone. Not to dates and not to descriptions. Design approved. Pages built and viewable on a link. Live on your domain. Each stage visible before the next payment.
4. Written scope. Pages by name, revision rounds numbered, delivery date, and the year-two cost. One message is enough.
5. An invoice from a registered firm. A traceable entity, a record of what you bought, and the document every recovery route asks for.
| Condition | What it caps |
|---|---|
| Domain in your name | Loss of your business name and continuity |
| 20–30% advance | The maximum amount at risk |
| Stage-linked payments | How far a failure can progress before you stop |
| Written scope | Disputes about what was agreed |
| Invoice | Your ability to recover anything |
Why this works better than feeling confident
Two reasons.
It’s checkable. Each condition is a yes or a no. “Do I trust this person?” has no answer you can verify; “will the domain be in my name?” has one, in writing.
It works even when you’re wrong. With all five in place, a vendor who vanishes costs you 30% of a modest build and a few weeks. Recoverable. Without them, the same vendor costs you the domain, the full amount, the season, and a second purchase.
You’re not trying to pick correctly every time. You’re trying to make picking wrongly cheap.
The message that sets all five
Send this once, before paying:
Before I transfer the advance, please confirm in writing: the domain will be registered in my name and account; 30% advance with the balance split across design approval, build, and go-live; these pages [list]; [number] revision rounds; live by [date]; year-two cost for domain and hosting is ₹[amount]. And please send the invoice.
A vendor who confirms this has given you real assurance. One who resists has told you which condition they need you to give up — and that’s usually the one that matters.
What doesn’t help
Being honest about the things buyers reach for that don’t reduce risk:
Paying more. Price is largely uncorrelated with delivery. A higher quote buys presentation and sometimes process, not protection.
A meeting at their office. Offices are rentable. Meeting someone is worth doing for other reasons, but it isn’t a safeguard.
A high star rating. NCR agency ratings cluster at 4.7 to 4.9 across large review counts, including firms with complaint histories elsewhere. The score barely discriminates.
A referral, on its own. Referrals remove the identity risk and remove none of the terms. Referral projects fail through missing paperwork more than through fraud.
Waiting longer. The most common response to nerves, and the most expensive. Projects die in the pause.
The honest limit
None of this makes a good outcome certain. What it does is turn an unbounded risk into a bounded one, and that’s the achievable goal.
There’s one thing the five conditions don’t cover: what happens after launch, when you need a phone number changed. Settle that separately in writing — a response time and a per-change rate, or a monthly plan. Responsiveness during the sale doesn’t predict it, because the economics change once the build is paid for.
What to do this week
- Register your domain in your own account today.
- Send the five-condition message to your chosen vendor.
- Refuse an advance above 30%.
- Split the balance across three visible stages.
- Agree the post-launch response time and change rate separately, in writing.
If you want it done the certain way
Send us the five-condition message and you’ll get five confirmations in writing before you pay — domain in your name, 30% advance, stage-linked balance, written scope and date, published year-two cost. Plus the post-launch response time and change rate. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- The moment before you hit “pay”
- How much advance is safe to pay?
- Safe payment milestones for a website project
- “I’ll pay only when everything is done” — why it backfires
FAQ
What is the safest way to pay a web developer?
A 20–30% advance with the balance split across stages you can open on your phone — design approved, pages built, live on your domain — against an invoice from a registered firm, with the domain already registered in your own account.
How can I feel safe paying for a website when I don’t know the developer?
Stop trying to become confident and cap the downside instead. With the domain in your name, a small advance and stage-linked payments, a bad choice costs you weeks and a modest amount rather than everything.
Does paying more make a website purchase safer?
No. Price is largely uncorrelated with whether you get delivered to. What protects you is the domain in your own account, a small advance, payments against viewable stages, written scope and an invoice — all of which are free.
