The cheapest website quotation may be the right one. A small business with ready content and a straightforward enquiry form does not need an elaborate discovery process or a custom application. But you cannot tell whether a quote is good value until the suppliers have priced the same work.
“Ten pages, responsive design, SEO included” is not the same scope as ten agreed pages, finished copy, a working CRM connection and a documented handover. The difference becomes expensive after the deposit, when each side discovers what the other assumed.
We keep website development cost ranges in India separately. This is the step after looking up a price: turning two or three proposals into a comparison you can actually make. It applies whether you hire a freelancer, an agency or someone recommended by a friend.
Why can two quotes for the same website be so different?
Usually because the description is broad enough to hide several different jobs. A “product page” might mean a designer laying out a reusable template, someone entering fifty products into it, or an integration that keeps stock and prices synchronised with another system. Those are separate deliverables.
Ask every supplier to distinguish unique layouts, total published pages and content entry. A home page, a service-page template and a contact page are three layouts. Twenty services using that template still need twenty sets of content, images and checks. Neither counting method is wrong; leaving it undefined is the problem.
Then separate a new site from a replacement. A fresh business has no old URLs, search history or forms to preserve. An established business may have advertising landing pages, downloadable brochures and enquiries arriving through integrations nobody documented. Rebuilding the visible pages does not automatically preserve those functions.
The question is not “why are you more expensive?” yet. It is “which work have you included that the other proposal has left to us?”
What should a website development quotation include?
Copy this table into your comparison sheet. Mark each item included, excluded or unanswered. An unanswered item is an open question, not a free inclusion.
| Item | What to ask the supplier to specify |
|---|---|
| Pages and layouts | Named pages, unique templates, languages and who enters the content |
| Design | Template adaptation or original design, approval stages and revision rounds |
| Content | Who writes, supplies, edits and approves copy, images and downloads |
| Functionality | Forms, search, accounts, payments and the exact workflow each supports |
| Integrations | Named systems, data direction, credentials owner and failure handling |
| Migration | Content import, old URL inventory, redirects and launch responsibilities |
| Measurement | Analytics accounts, agreed events and evidence that they work |
| Acceptance | Devices, browsers, workflows and defects checked before sign-off |
| Running costs | Hosting, domain renewal, licences, usage charges and support |
| Handover | Accounts, source where applicable, licences, documentation and training |
Ask for exclusions as well. “No translation, product photography or historical order migration” is useful information. A proposal that admits its boundaries is easier to manage than one promising everything.
For an integration, go beyond “CRM connected”. Does the form create a lead, update an existing contact or both? Who is notified when the CRM rejects it? What happens if the visitor presses submit twice? These questions expose work that a screenshot cannot show.
Who is responsible for the content and approvals?
Name one person on each side. A launch date dependent on “client content” is meaningless unless someone owns the content list and the approval deadline.
For every page, agree whether the supplier receives finished copy, interviews your team and writes it, or edits a rough draft. Identify who checks service descriptions, pricing statements and contact details. A developer cannot reliably invent your refund policy or decide which claims your sales team can support.
Define a revision round too. Collecting feedback once on an agreed design is different from changing the business positioning after development. Ask how feedback is consolidated, which stage it applies to and how a change to an already approved stage is priced.
Avoid asking suppliers to include “unlimited revisions” as a substitute for thinking. A clear approval process protects your budget better. If requirements are still unsettled, buy a small discovery phase with an agreed output before asking for a fixed build price.
How do you compare the total cost rather than the deposit?
Separate the build, missing launch work and recurring charges. Then compare the same period. Here is a deliberately invented example, not a market rate or a Cloud9 quotation. Every amount excludes tax; the point is the method.
| Cost over the first year | Proposal A | Proposal B |
|---|---|---|
| Initial build | ₹60,000 | ₹95,000 |
| Required copywriting, quoted separately | ₹20,000 | Included |
| Required migration, quoted separately | ₹15,000 | Included |
| Hosting and licences for one year | ₹12,000 | ₹12,000 |
| Agreed maintenance for one year | ₹24,000 | ₹24,000 |
| Comparable first-year total | ₹1,31,000 | ₹1,31,000 |
The lower build price becomes the same total once the missing work is added. That does not make Proposal A dishonest. It might suit a buyer who can write and migrate the content internally. Your team's time still belongs in the decision, even if it does not appear on a supplier invoice.
Ask which renewals are introductory prices, which are charged in foreign currency and which vary with usage. Request the tax treatment and payable total in writing rather than assuming every quote uses the same basis. Do the comparison again for year two, when launch work disappears but renewals and support remain.
Do not add optional services just to make a bigger package look competitive. If you do not need monthly content changes, price the realistic alternative: updates when required, with someone clearly responsible for security and recovery.
What does “SEO and analytics included” actually mean?
Ask for deliverables, not a label. For launch, those might include editable page titles and descriptions, working canonical tags, an accessible sitemap and checks that production pages can be indexed. An ongoing SEO programme involves further work; a launch checklist does not promise rankings.
For a replacement site, require an inventory of existing URLs and a decision for each important page. Google's site-move guidance recommends mapping old URLs to their new equivalents and using permanent server-side redirects when URLs change. It also warns that search visibility can fluctuate during a move. “SEO preserved” is therefore a process to inspect, not a guarantee to buy.
Measurement needs the same specificity. A form submission, a click on a phone number and a qualified enquiry are different events. Agree which the website records and how the team will reconcile them with actual enquiries. If you run ads, include a check that the security policy and consent configuration allow the intended tracking behaviour without counting the same action twice.
Keep business access to the accounts. Google's Analytics user-management documentation supports granting users access at account or property level. A report emailed by the supplier is not a replacement for your ability to access and manage your own property.
How will you know the website is finished?
Write acceptance examples before development. “Looks professional” cannot settle whether a feature works.
For an enquiry site, a useful example is: a visitor on a phone submits valid details, sees a confirmation, and the intended team receives one enquiry in the agreed destination. Invalid input produces an understandable error. If delivery fails, the website should not falsely tell the visitor that the enquiry reached the team.
For a store, agree the payment and order states to demonstrate, including failures and refunds where those are in scope. For a member area, test access with the actual roles: an administrator's successful login does not prove that an ordinary member is restricted correctly.
Name the browsers and device types, who supplies test data, who signs off and how defects are recorded. Separate defects against agreed requirements from new requests. A different colour preference after approval is different from a submit button that never works.
Connect payments to observable milestones such as design approval, a working preview and accepted launch. Agree those milestones before the deposit; do not invent new acceptance conditions when the final invoice arrives.
What should you receive at handover?
Start with access, not a zip file. Your business should have appropriate control of its domain, hosting or platform subscription, website administration and measurement accounts. The supplier can retain delegated access for support. Avoid making a departing employee's personal email the only route to recovery.
For custom software, ask what source code, deployment instructions and configuration documentation you receive, and what remains third-party intellectual property. For a hosted platform, ask what can be exported and which features depend on an ongoing subscription. Owning the content does not mean owning the platform beneath it.
WordPress illustrates the difference. Its Tools Export documentation describes an XML export containing content such as posts and pages. A recoverable site needs more: WordPress's backup guidance covers both database and files. A content export alone does not hand over the installed theme, plugins and complete working environment.
Request a restore demonstration or documented recovery procedure appropriate to the platform, plus the renewal list and an explanation of licence transfer limits. Finally, have someone from your team perform a normal edit. Training has worked when they can make the change, not when they have watched a recording.
What should you not use to choose the winner?
Do not choose on page count alone. Ten useful pages can require more work than fifty pages copied into one template. Do not assume “custom” guarantees quality, or that a template is inherently unsuitable. Match the approach to what the business needs to operate.
Do not reward jargon. “AI-powered”, “enterprise-ready” and “fully optimised” need a concrete behaviour or deliverable behind them. If a claim cannot be demonstrated or inspected, do not pay a premium for it.
Do not demand a new platform simply because the current website disappoints you. If the real problem is outdated copy, broken forms or missing account access, fix that first. Our web development service is relevant when there is a genuine implementation problem; it is not the necessary answer to every weak website.
And do not reject the cheapest supplier merely for being cheapest. A small, well-defined job is allowed to have a small price. The warning sign is an essential question that nobody will answer in writing.
What should you send suppliers before requesting a revised quote?
Send one shared brief: the site's purpose, named pages, examples of required workflows, available content, existing systems, target date and the handover checklist. Ask each supplier to return the same included/excluded table, dependencies and full first-year costs.
Resolve the largest unanswered items before negotiating the total. If a proposal exceeds the budget, remove a feature or phase the work openly. Keeping every promise while quietly reducing testing or handover only postpones the argument.
Send us the scope you are comparing if you want help identifying what is missing. Sometimes the right recommendation is the smaller quote, with two or three responsibilities made explicit before you sign.
Bharat Vasireddy
Founder & Digital Marketing Strategist8+ years of experience in performance marketing and web development. I help businesses scale through data-driven SEO, Google Ads, and high-performance websites.