Pause and run five checks: domain in your name, advance no more than 30%, invoice from a registered firm, scope in writing, and a delivery date — if all five hold, the nerves are ordinary and you should proceed. If any fails, the hesitation is telling you something specific and fixable.
The moment it happens
The moment before you hit “pay” for a website has a particular quality. You’ve decided. The number is agreed. And your thumb stops moving, and you don’t know whether that’s good instinct or ordinary anxiety about spending money.
Usually it’s a bit of both, and there’s a way to separate them in about four minutes.
The five-item check
Run these in the pause. Each one either holds or it doesn’t.
1. Is the domain going to be registered in my name and account? The most consequential item. If you don’t have a clear written yes — or better, if you haven’t already registered it yourself — stop here. This is the term that decides whether you can ever leave.
2. Is the advance 30% or less? Complaint records are full of advances of half or more followed by silence. A vendor confident of being paid on delivery doesn’t need half. If they’re asking for more, that’s the conversation to have before paying, not after.
3. Am I paying a registered firm, against an invoice? Money to a personal UPI with no invoice is recoverable, but materially harder. Ask for the invoice first — it takes one message.
4. Do I have the scope in writing? Pages by name, revision rounds, and the year-two cost. Not a brochure. A message listing what I’m buying.
5. Is there a delivery date? A specific date, not “two to three weeks.”
| Item | If it fails |
|---|---|
| Domain in your name | Don’t pay. Register it yourself first — ten minutes |
| Advance ≤30% | Negotiate. Standard practice supports you |
| Invoice from registered firm | Ask for it before paying. Not after |
| Scope in writing | Ask for it in a message. Two minutes of their time |
| Delivery date | Ask. A vendor who won’t date it hasn’t planned it |
If all five hold, the remaining feeling is ordinary nerves about spending money on something you can’t yet see. That’s normal and it doesn’t get resolved by waiting.
What your hesitation is often actually about
Four common sources, each with a different remedy:
You can’t picture what you’re buying. Understandable — you’re paying for something that doesn’t exist. Remedy: ask for the staging link commitment now. “Will I get a link I can open from the first build day?” A yes converts an abstraction into something you’ll be able to watch.
A story you heard. Someone’s cousin lost ₹40,000. That story is doing more work in your decision than the vendor in front of you. Remedy: the five checks. They address exactly what went wrong in that story.
You don’t fully trust the person. Sometimes accurate. Remedy: don’t try to resolve it by getting more confident. Cap the downside instead — the five items make being wrong survivable rather than catastrophic.
You’re not sure you need the website. A different question, and worth separating. If you can’t name a specific customer or opportunity you’ve lost, the hesitation may be about the purchase rather than the vendor.
The message to send instead of paying
If any check fails, send this. It costs one message and a day:
Before I transfer the advance — can you confirm in writing: the domain will be registered in my name and account, these pages [list], [number] revision rounds, live by [date], and the year-two cost for domain and hosting. Also please share the invoice. Happy to pay 30% on receipt.
Two outcomes. They confirm, and you pay with the five checks satisfied. Or they resist, and you’ve learned something worth far more than the day’s delay.
A vendor who finds this request unreasonable is telling you how the next four weeks will go.
What not to do with the hesitation
Don’t resolve it by paying more. Price is largely uncorrelated with whether you get delivered to. A higher quote buys presentation, not protection.
Don’t resolve it by paying less. The floor of the market is where post-launch support has no economics and domains sit in vendor accounts.
Don’t resolve it by postponing indefinitely. This is the most common outcome and it costs the most. Website projects die in the pause more often than in the build.
Don’t resolve it by skipping the checks because the vendor was recommended. Referral projects fail through missing paperwork more than through fraud.
The one thing to do before any of this
Register the domain yourself, in your own account, today. About ₹1,000 a year, ten minutes, and it converts the worst realistic outcome from “lost my business name and my money” to “lost a small advance.”
Do that and much of the hesitation resolves itself, because the thing you were actually afraid of is no longer possible.
What to do this week
- Register your domain in your own account before paying anyone.
- Run the five checks and see which, if any, fail.
- Send the confirmation message rather than paying immediately.
- Ask whether you’ll get a staging link from day one.
- Pay 30% on receipt of the invoice and the written confirmation.
If you want it done the certain way
Send us the five checks as questions and you’ll get five plain answers in writing before you pay anything — domain in your name, 30% advance, GST invoice, scope and date, year-two cost. We’d also suggest registering the domain yourself first, with us or anyone. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- How much advance is safe to pay?
- What finally makes a nervous buyer pay?
- Personal UPI or company account — does it matter?
- What paper should your advance actually buy you?
FAQ
Should I pay an advance to a web developer I’m unsure about?
Run five checks first: domain registered in your name, advance no more than 30%, an invoice from a registered firm, scope in writing, and a specific delivery date. If all five hold, proceed. If any fails, ask for it before paying.
How do I stop worrying about paying a website advance?
Cap the downside rather than trying to become confident about the person. Register the domain yourself first, keep the advance to 20–30%, and tie later payments to stages you can open on your phone.
What if a developer refuses to put my scope in writing?
Treat it as information. Asking for a message listing pages, revision rounds, delivery date and year-two cost takes two minutes of their time — resistance to that predicts how disputes later will go.
