"How much for a website?" is a fair question that usually gets an evasive answer. Here are the actual ranges we work with, and — more usefully — what moves a project from one band to the next.
The Ranges
A professional website in India typically falls between ₹15,000 and ₹2,00,000+:
- ₹15,000 – ₹40,000 — a landing page. One page, a clear offer, a contact route.
- ₹40,000 – ₹1,00,000 — a standard business website. Several pages, a CMS or structured content, proper SEO groundwork.
- ₹1,00,000+ — a custom web application. Accounts, dashboards, payments, integrations, anything with real logic behind it.
Two things to note about these bands.
First, they are wide on purpose. A "5-page website" is not a unit of work — five pages of static copy and five pages with booking, payments and a customer login are different projects wearing the same description.
Second, the bands are about scope, not quality. A ₹25,000 landing page should still be fast, accessible and correctly marked up. If it is not, you did not buy a cheaper website — you bought a worse one.
What Actually Moves The Number
Content readiness
The most underestimated cost on any project, and it is not a development cost at all.
If copy, images and product information are ready, a build moves quickly. If they are not, the project stalls — and worse, whoever wrote the quote either has to wait or start writing your copy, which almost nobody prices correctly upfront.
Ask yourself honestly whether your content exists before you ask what a site costs.
Design origin
Three routes, three costs:
- A template, lightly adapted — cheapest, fastest, and looks like a template.
- A custom design from an existing brand — you have logo, colours and type; the site is designed around them.
- Design and brand from scratch — the site plus the identity it sits on.
Most quote confusion comes from comparing option 1 against option 3 as though they are the same purchase.
Integrations
Every external system is a cost multiplier: payment gateways, CRMs, inventory, booking, WhatsApp, analytics, email automation. Each brings credentials, edge cases, failure states and testing.
One integration is a feature. Six integrations is an architecture.
Who builds it
A freelancer, a small studio and an agency price differently and carry different risk. The relevant question is not who is cheapest but what happens in month seven when something breaks and you need the person who wrote it.
The Costs That Come After
Quotes usually cover the build. These continue:
- Hosting — from near-free for a static site to meaningful monthly cost for an application with a database
- Domain — annual, small, easy to forget until it lapses
- Maintenance — dependency and security updates. Not optional on anything with a login or a payment path.
- Content updates — either you can make them yourself, or every change is a support ticket
- SEO and content — an ongoing activity, not a build-time checkbox
That fifth point causes the most friction. "SEO-optimised" in a quote usually means the technical foundations — fast loading, semantic HTML, structured data, correct metadata, mobile responsiveness. That is real and it matters. It is not the same as ranking for competitive terms, which is a content strategy that runs for months.
Get clear which one you are buying.
Questions To Ask Before Accepting Any Quote
- What exactly is in scope? Page count is a weak proxy. Ask what each page does.
- How many revision rounds are included, and what counts as one?
- Who owns the code and the accounts — domain, hosting, analytics? The answer should be you.
- Can I edit content myself? If not, what does a change cost and how long does it take?
- What happens after launch? Is there a support window, and what does it cover?
- What is explicitly excluded? The most useful question on this list.
How Payment Usually Works
Most fixed-price web projects in India are structured across milestones rather than paid upfront or on completion. A common shape:
- A deposit to begin — typically 30–50%, which covers discovery and design
- A milestone at design sign-off — before development starts
- The balance at launch — or shortly after an agreed review window
Two things to watch. First, a 100%-upfront request removes all of your leverage and most of your recourse. Second, paying nothing until launch sounds safer but tends to produce rushed discovery, because nobody is funded to think properly at the start.
Also agree explicitly what "launch" means. Deployed to a staging URL, deployed to your domain, and deployed with content loaded and DNS switched are three different events, and the gap between them has ended more engagements badly than any technical failure.
Red Flags Worth Naming
- A quote with no questions attached. If nobody asked about your content, integrations or timeline, the number is decorative.
- Page count as the only unit. It tells you nothing about what the pages do.
- "Unlimited revisions." Either it is untrue, or the price already absorbs the risk, or the project has no definition of done. None of those help you.
- No mention of who owns the accounts. Domain, hosting and analytics should be registered to you, not to the agency.
- SEO promised as a ranking, not as groundwork. Nobody can guarantee position for a competitive term.
- A timeline with no dependency on you. Every real project waits on client feedback and content. A plan that pretends otherwise will slip in week two.
A Note On Cheap Quotes
A quote far below the ranges above is not automatically wrong, but it usually means one of three things: the scope is smaller than you think, a template is being reskinned, or the work will be rushed and you will pay again later.
The reverse is also true. A high number is not automatically thoroughness. Ask what it buys.
The most useful signal is not the figure at all — it is whether whoever wrote it asked you enough questions to arrive at it. A quote produced without understanding your content, your integrations and your timeline is a guess with a decimal point.
