A good referral legitimately removes the identity checks — you can skip the complaint search, the portfolio verification and the reference call — but it removes none of the terms, and written scope matters more with a referral, not less. The most common way referral projects fail is that trust from the introduction replaces the paperwork.
The moment it happens
Your CA or friend recommended a web company — what checks can you skip is a question you ask because the checks now feel insulting. Someone you trust has vouched for this person. Asking for a GST invoice and a written scope feels like you’re calling them a liar.
You’re not. You’re documenting a commercial arrangement, which is what your CA does for a living.
What a referral genuinely tells you
Be clear about what a good referral has already established:
They exist and they finish work. Someone paid them and got a website. That eliminates the entire category of vendors who take advances and vanish, which is the risk you were most worried about.
Their work is of a knowable standard. You can look at the referred site.
They’re accountable through a relationship. They can’t disappear without consequence in a network they depend on. This is real and it’s the strongest protection a referral offers.
Their price is roughly known. Your referrer paid something. Ask what.
That’s a lot. It’s not everything.
The three checks you can reasonably skip
| Check | Why you can skip it |
|---|---|
| Searching their name plus “complaint” | Your referrer’s direct experience outranks a search — though it’s still five minutes if you want it |
| Verifying the portfolio is real | You can see one real site and know who paid for it |
| Calling a reference | You’ve just spoken to one. Ask your referrer the six reference questions instead |
Do ask your referrer the reference questions properly, though — particularly what happened after they paid in full, and whether their domain is in their own name. A referral without those two answers is just an introduction.
The four things that matter more, not less
1. Written scope. More important with a referral, because the relationship makes people casual. “He’s good, we didn’t need paperwork” is how referral projects end up in disputes about what was agreed. One page: pages by name, revision rounds, delivery date, year-two cost.
2. The domain in your own account. Not a trust question at all. It’s about what happens in three years when your friend’s contact has moved cities or changed business. Register it yourself before starting.
3. A small advance, 20–30%. The awkwardness of asking is exactly why referral projects often involve large advances. Keep it standard.
4. A GST invoice, where they’re registered. Your CA will want it anyway, and if you’re registered the input credit may make it the cheaper route.
Why referral projects fail differently
They rarely fail through fraud. They fail through drift:
Nobody wants to chase. Following up firmly on someone your CA recommended feels rude, so you follow up softly, and softly doesn’t work.
Nothing was written, so nothing is enforceable. Both sides remember different scopes and neither is lying.
Deadlines slip without consequence. There’s no term to invoke and invoking one would strain the relationship.
Complaining costs you twice. Raising a problem means potentially embarrassing your referrer, so problems go unraised until they’re large.
All four are prevented by the same thing: one page in writing at the start, agreed pleasantly, before anyone is invested.
How to ask without awkwardness
The framing that works, sent as a message rather than said in a meeting:
Great to be working together — [referrer] speaks highly of you. Just so we’re both clear on paper: [list of pages], [number] revision rounds, live by [date], domain registered in my name, and the year-two cost for domain and hosting. Advance of 30% on confirmation. Let me know if any of that needs adjusting.
Two things make this land. It attributes nothing to suspicion. And it’s phrased as clarity for both parties, which is what it actually is — a good developer prefers a defined scope too, because it protects them from an endless revision loop.
The one thing to ask your referrer
Before you engage, ask them this:
Would you use them again — and what happened after you paid in full?
If your referrer hesitates on either, you’ve learned something the introduction concealed. Referrals often come from a good build experience and skip over a poor support experience, because the person made peace with it.
What to do this week
- Ask your referrer the six reference questions, especially about post-payment support.
- Ask what they paid and whether the final price matched the quote.
- Register the domain in your own account before starting.
- Send the one-page scope message, framed as mutual clarity.
- Keep the advance to 20–30% regardless of the introduction.
If you want it done the certain way
If someone referred us, ask them what happened after they paid in full — that’s the question worth asking about anyone. We’ll put the scope, revision rounds, date, domain ownership and year-two cost in writing before you pay, referral or not. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- When a relative recommends “their website guy”
- Who connected you to a developer who delivered?
- Should there be a written agreement for a website project?
- How to verify a website company before paying anything
FAQ
Do I still need a contract if a web developer was referred to me?
Yes, and more so. Referral projects commonly proceed without documentation, and that’s how they end in disputes where both sides genuinely remember different scopes. One page covering pages, revisions, date and year-two cost is enough.
What checks can I skip with a referred web developer?
The identity checks — the complaint search, verifying the portfolio is real, and calling a reference, since your referrer is one. Ask your referrer what happened after they paid in full and whether their domain is in their own name.
Should the domain still be in my name with a referred developer?
Yes. It isn’t a trust question but a continuity one — people move cities, change businesses and lose old email access, and the domain outlives all of that. Register it yourself before work starts.
