What should a website actually cost in India?

Ask four agencies to quote the same website and you will get four numbers that are nowhere near each other. That is not because three of them are lying. It is because "a website" describes a brochure site that takes two weeks and a logged-in platform that takes five months, and the brief you sent probably did not say which one you meant.

This is a guide to reading those quotes. It deliberately does not give you a price list, for a reason we will come to at the end.

What actually drives the number

Almost none of the cost is the pages themselves. Five things move a quote far more than page count does:

• Integrations. A contact form is an afternoon. A payment gateway wired to your courier, your accounting and your GST invoicing is weeks, because every one of those has its own failure modes and you need retries and reconciliation for all of them.
• Data quality. Migrating a clean catalogue is routine. Migrating eleven years of product data with inconsistent SKUs and three spellings of every brand name is a project of its own.
• Who decides. A build where one person approves moves at twice the speed of one where a committee meets fortnightly. This is the single most underestimated cost on any project, and it is entirely on the client side.
• Compliance. If you handle health data, financial data or anything that needs an audit trail, the engineering is not harder but there is a great deal more of it.
• What happens after launch. A site nobody can update without calling you is cheaper to build and vastly more expensive to own.

How to tell a thin quote from a real one

A low number is not automatically bad. A low number with no written scope always is. When you compare quotes, the questions that separate them are not about price:

• What is explicitly NOT included? A quote that cannot answer this has not been thought about.
• Who writes the code, and can I meet them before signing? If the answer is vague, you are being sold a pitch team.
• What happens when scope changes? "We will absorb it" is a warning, not a kindness. It means either padding now or an argument later.
• What do I own at the end, and when? Code, designs, domains and cloud accounts should transfer to you, and you should know on what date.
• What does it cost to run per month? Hosting, domains, paid APIs and AI inference are real and recurring. A build quote that ignores them is incomplete.

The ranges nobody will print

We will not publish a price list, but we will tell you what moves the decision. A marketing site for a small business, built properly, is a matter of weeks, not months. An e-commerce store on Shopify is usually cheaper in total cost of ownership than a custom build until you are past roughly a thousand orders a month. A platform with accounts, permissions and billing is a different category of work and should be quoted as one.

If a quote for the third thing looks like a quote for the first thing, somebody has misunderstood the brief — and it may well be you.

Why we ask your budget instead

Any number we published would be wrong for almost everyone reading it.

The same brief genuinely costs wildly different amounts depending on the five factors above. So we work the other way round: tell us the number you have, and we design the largest useful thing that fits inside it, written down as a fixed scope with milestones and acceptance criteria.

That is not a negotiating tactic. If your budget will not cover what you are describing, you hear that on the first call, before you have spent anything — because a project that starts underfunded ends badly for both sides, and we would rather lose the work than take it on knowing that.