Yes — one three-minute call to a past client tells you more than a portfolio, a rating and a meeting combined, because it’s the only check that covers what happens after you pay. Ask for the reference; a vendor’s willingness to hand you an unmanaged conversation is itself the first answer.
The moment it happens
Should you call a web company’s past clients before hiring is a step almost nobody takes, usually because it feels awkward or excessive for a ₹25,000 purchase.
It isn’t excessive. Every other check available to you covers the courtship phase. Reviews cluster at the top and barely discriminate — NCR agency ratings sit at 4.7 to 4.9 across large review counts, including firms with substantial complaint histories elsewhere. A portfolio shows finished work, not how it got finished. Only a past client can tell you what the vendor was like in week five, and what happened after final payment.
How to ask for it
One line, sent with your other questions:
Could you share one client in a similar business I could speak to for two minutes?
What happens next is informative regardless of the reference itself.
They give you a name and number readily — they’re confident about what that client will say. Strong signal.
They offer a written testimonial instead — that’s a curated statement, not a reference. Ask again for a phone number.
They say clients don’t like being disturbed — sometimes true, and also the standard deflection. Ask whether one client might agree if asked.
They decline entirely — for a project of this size that’s an answer, and worth weighing against price.
The six questions
Keep the call short and make it easy for the person. They’re doing you a favour.
1. “How long did it take, against what you were promised?” Tests the estimate and the delivery in one question. A small overrun is normal; a doubling is a pattern.
2. “What happened after you paid in full?” The most important question you will ask anyone about a web vendor. This is where most failures happen, and it’s never volunteered. Listen for whether small changes get done and how long replies take now.
3. “Is your domain registered in your own name?” Tells you how this vendor structures ownership as a matter of practice, for every client. If the answer is no, you know your own answer will be no too, whatever you’re told.
4. “Was the final price the same as the quote?” Surfaces mid-project charges and scope disputes.
5. “What was the most annoying part?” Better than asking about problems directly. Everyone has an answer, and it’s usually the honest one.
6. “Would you use them again?” The summary. Hesitation before “yes” carries as much information as a “no.”
| Answer you hear | What it means |
|---|---|
| “A bit late, but fine” | Normal. Not a concern |
| “Took three months for a two-week job” | Estimate isn’t real |
| “They still fix things when I ask” | The best answer available |
| “Nobody replies now” | The most common failure. Expect it yourself |
| “Domain’s in their name” | Yours will be too |
| “Price changed midway” | Ask what the change was for |
| A pause before “yes, I’d use them again” | Ask one more question |
Reading the reference itself
Not all references are equal.
Strongest: a business in your trade, of similar size, with a site you can open, who paid a comparable amount and has needed support since launch.
Moderate: a different trade, working site, no support experience yet — untested on the part that matters.
Discount: anyone who got the site free or heavily discounted, anyone with a commercial relationship with the vendor, and any reference who can’t describe the project specifically.
Also do the cheap version alongside: open three portfolio sites yourself and test their contact forms. Real businesses, live sites, working forms. That takes five minutes and catches a different failure.
What to do with what you learn
A reference rarely produces a clean yes or no. It produces terms.
If the answer to question 2 was “nobody replies now,” don’t necessarily walk away — instead agree post-launch support in writing before you pay, with a response time and a per-change rate. If the answer to question 3 was no, register the domain yourself before hiring. If the price changed midway, get the scope written down in detail.
That’s the real value here. You’re not looking for a perfect vendor. You’re finding out which specific term you need to insist on.
What to do this week
- Ask each shortlisted vendor for one client you can phone.
- Note who agrees readily and who deflects.
- Make the call and ask the six questions.
- Open three portfolio sites and test their contact forms.
- Convert what you learn into written terms before paying.
If you want it done the certain way
Ask us for a client in your trade and we’ll give you the number — and you should ask them what happened after they paid in full, because that’s the question that matters. Domain in your name, published price, year-two cost stated. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- How to verify a website company before paying anything
- Is that “our work” portfolio real or stolen?
- “We made [big brand]’s website” — do these claims mean anything?
- What proof rebuilds trust after a bad developer
FAQ
Should I ask a web developer for client references?
Yes. It’s the only check that covers what happens after payment, which is where most failures occur. A vendor’s willingness to hand you an unmanaged conversation is itself a strong signal.
What should I ask a web developer’s past client?
How long it took against what was promised, what happened after they paid in full, whether their domain is in their own name, whether the final price matched the quote, the most annoying part, and whether they’d use them again.
What if a web company won’t give me a reference?
For a project of this size, treat it as an answer. Fall back on structural protections — register the domain yourself, keep the advance to 20–30%, tie payments to viewable stages, and get scope in writing.
