How we turn "how much for a website?" into a quote you can defend: a developer's scoping checklist

Brightcode — Mon, 19 Oct 2026 04:12:15 +0000

By the Brightcode team, a small web agency in Delhi NCR. Reviewed by Gaurav Khokkar, Founder.

If you build websites for small businesses, you know this message. "How much for a website?" And the person wants a number in the next reply.

We're a small web team in Delhi and that question reaches us every week. Answering with a number straight away feels helpful. It rarely is. Either the client compares it with a quote that covers half the work, or three weeks in you learn that "simple website" meant online booking plus a CRM sync.

So we stopped quoting off the first message. Below is the checklist we now use to get from a vague ask to a scope we can price and stand behind. It's written for developers and freelancers. If you're the one buying a site, it shows what a good quote should rest on.

1. Count templates, not pages

"10 pages" tells you very little. Ten blog posts share one template. A home page, a service page, a product page and a checkout are four separate builds. Each has its own layout, states and edge cases.

So we list every unique template and price those. Pages that reuse a template are content entry, and the quote says so. That single change explains most of the gap between a ₹15,000 quote and a ₹1.5 lakh one, when both sides are calling it "a 10-page site".

2. Write down the project type before anything else

Clients use the same words for very different jobs:

Brochure site: mostly read-only content and a contact form
Lead-gen site: landing pages, forms, conversion tracking, ad-ready structure
Store: catalogue, cart, checkout, payments, shipping, returns
Web app: logins, roles, dashboards, reports
SaaS: one codebase serving many customers, billing, multi-tenancy

The further down that list, the more testing and long-term maintenance you're signing up for. When a brief straddles two types, like a service site with a client portal, we split the quote in two. That way the expensive part is out in the open.

3. Treat every integration as its own mini-project

Here in India the integrations list tends to look the same: a payment gateway (Razorpay, PayU, Cashfree), WhatsApp alerts, a CRM, Google Sheets. Sometimes accounting software like Tally, or an ERP.

Every one of those means setup, auth, error handling and a test plan. Plus the webhook that fails at 2 a.m. A gateway isn't finished when the happy path works. It's finished when refunds, failed payments and duplicate webhooks are handled too. Older systems with thin API docs take longer, and we flag that as a risk in the estimate instead of hiding the hours.

When a client asks "can you just connect it to X?", our answer is "yes, and here's what that involves". A lot of software and API integration work hides inside projects that get called "a website".

4. Decide the platform by who edits the site after launch

WordPress, Shopify, Next.js, custom. We try not to start from what we enjoy writing. We start from who will update the site, how often, and what it'll cost to run over the next two or three years.

WordPress suits content-heavy sites where non-developers publish often. Someone still has to own updates and security.
Shopify gets a store live fast. The monthly plan and paid apps are ongoing costs.
Next.js or custom gives you speed and control, for more development effort up front.

There's a longer write-up of the trade-offs in WordPress vs a custom website. Short version: picking a platform also picks the running costs, so bring it into the quote conversation early.

5. Ask who supplies content and photos

Cheap quotes almost always assume finished copy and photos show up on day one. They rarely do. In our experience content is the most common reason a project runs late. So we ask straight out: who writes the copy, who shoots the product photos, does anything need translating? If the answer is "you", it becomes a separate line item with its own timeline.

6. Put migration and SEO in writing

If the client already has a site that ranks, a redesign without a redirect map can quietly wipe out years of traffic. We list migration as its own line: URL inventory, redirect map, and a Search Console check after launch. Basic on-page SEO (titles, meta, headings, sitemap) comes with every build we ship. Anything deeper gets scoped separately. Our website migration checklist is the list we actually work from.

7. Show the first-year cost, not just the build cost

If the quote only shows the build price, month four brings a nasty surprise. So we add a short running-costs section: domain and SSL, hosting, yearly theme or plugin licences, platform plans like Shopify, gateway fees, SMS/email/WhatsApp API charges, and maintenance.

People rarely complain about running costs they were told about upfront. It's the ones nobody mentioned that cause the argument.

8. Agree on what "done" means

Our scope documents end with the dull bits. They're also the bits that prevent fights later:

How many revision rounds
Who owns the domain, hosting account and code (always the client)
What's covered after launch, and for how long
What counts as a change request

The red flags we see in other quotes

Clients sometimes show us a competing quote. These are the things that make us wince, and they're worth checking in your own quotes too:

One line: "Website – ₹X", no scope
Nothing about revisions, hosting or maintenance
Domain, hosting or code registered in the agency's name
Mobile layout, speed or basic SEO sold as extras
No redirect plan when replacing a live site

Wrapping up

None of this is hard. It just means having one proper conversation before the number instead of after it. The quote takes a little longer to write. In exchange, it survives being compared line by line with someone else's.

On the buying side and want to see how all this turns into real price ranges in our market? We published a longer guide: what decides website development cost in Delhi NCR. It has the ranges other agencies publish for each type of site, the running costs, and a prep list for getting quotes you can compare.

What's on your scoping checklist that isn't on ours? Tell us in the comments.

Written by the team at Brightcode, a Delhi NCR agency that does website development, e-commerce and web apps.

DEV Community: Brightcode