Why "We'll Do It Cheaper" Is a Losing Position

There is always somebody cheaper, and in this market there is always somebody dramatically cheaper — a student, a cousin, a template reseller, an offshore team quoting a fifth of your number. Competing there is not a strategy, and the reason is arithmetic rather than pride.

Price competition only works when you have a real cost advantage — automation, a standardised delivery process, genuine operational efficiency. Without one you are not competing on price, you are selling at a loss and calling it competing.

The general advice about competing on value assumes the buyer can perceive value, and for a first website they mostly cannot.

A business that has never had a website has no basis for judging one. They cannot evaluate whether your work loads in two seconds or nine, whether it works properly on a phone, whether the enquiry form actually delivers mail, or whether it will still be maintainable in two years. Every one of those is invisible to them, and every one is where your price difference actually lives.

So price becomes the only axis they can see — not because they are unsophisticated, but because it is genuinely the only number in front of them.

That reframes the whole problem. You are not trying to justify a higher price against a visible quality difference. You are trying to make a second axis visible.

Four things a local buyer can actually perceive, none of which is design quality.

Two visible rows out of seven. That imbalance is the whole problem, and only the last two are being compared.

It will happen, and the instinct — to explain why the other quote is bad — is the losing move. It sounds defensive, it insults a decision they are considering, and it invites them to defend it.

Agree that it is cheaper, then ask one question: "That's a good price. Did they say what happens after it's live — who updates it, who fixes it if something breaks?"

You have not criticised anybody. You have introduced the axis that the cheap quote is silent on, and you have done it as a question rather than a claim, so the client discovers the gap rather than being told about it.

If the cheaper quote *does* include ongoing support at that price, they may genuinely be the better option and it is worth saying so. That happens rarely, and being the person who said it is worth more than the job.

Sometimes the cheap option is correct, and the honest position is worth holding.

A business with eleven reviews that needs a single page with its timings and phone number does not need a ₹30,000 build, and a template at ₹4,000 will serve it. Telling that owner so — and pointing them at the cheaper route — costs you a job you would have regretted and buys you something more useful in a market where everybody talks.

The version to avoid is doing the ₹30,000 work for ₹8,000 because you wanted the job. That client gets a rushed site, no monthly, and no reason to refer you, and you have spent a week proving your own price is negotiable.

Everything above is tactics for a conversation you should mostly not be having, and if you are having it constantly the problem is upstream.

Qualification. A business with a real review count and a transaction worth thousands is not comparing you against a student. If most of your conversations turn into price comparisons, look at who you are prospecting rather than what you are saying.

Specialisation. Three sites for hardware suppliers changes the fourth conversation from a price comparison to a shortlist of one. This is the compounding benefit of working a vertical in sequence, and it is the only durable answer.

The care plan. A relationship priced monthly is not comparable to a one-off quote, which removes the axis rather than arguing on it.

And the arithmetic underneath all of it: a local client is worth several times the build across their lifetime, which means winning on price and losing the care plan is a worse outcome than losing the job.