Why do quotes for the same website vary so much between vendors?

Because the amount of work hiding behind the word "website" varies enormously. The differences usually come from four places: whether the design is an off-the-shelf template or built from scratch, the actual number of pages and features, whether the admin interface is an existing system or purpose-built, and whether testing, launch, training, and ongoing maintenance are included at all. Many low quotes are low because the later items have simply been removed. The right way to compare is to write your requirements into a single list and ask every vendor to quote against that same list.

Are there ongoing costs after the website launches?

Yes, and they are routinely overlooked. Three categories are guaranteed once a site is live: the domain name (renewed annually), hosting or cloud services (billed monthly or annually according to traffic and specification), and security updates plus troubleshooting. If the site includes payments, member accounts, or an admin system, add third-party service fees and scheduled maintenance on top. When you budget, include the first year of recurring costs alongside the build quote — otherwise the overrun shows up right after launch.

What is the difference between using a template platform and having a site custom-built?

Flexibility and long-term cost. Template platforms start fast and cost little up front, which suits straightforward needs where the content is mostly introductory. The limitation is that layout and functionality can only be adjusted within what the platform allows, so the moment your business process needs something custom, or you need to connect to a system you already run, you hit a wall — and the data and layout are usually hard to take with you. Custom development costs noticeably more at the outset; what you get in return is functionality that grows around your process, and source code you can take with you.

Website Development Cost: What Drives the Quote

“How much does a website cost?” is a question the internet will never answer honestly, because the question itself is missing too many conditions.

A website is not a product so much as an interior fit-out. The same floor area costs one thing if you are replacing the flooring and quite another if you are rebuilding every room. What you actually need is not a number, but an understanding of where the money goes, which factors push the total up, and what is missing from the proposal in front of you.

First, work out which kind of website you need

The work involved differs enormously by type. Four are common:

Landing page. A single page with one clear purpose, usually paired with an ad campaign, an event, or a new product launch. Little content, simple structure — the lightest of all the types.

Corporate website. The company’s front door: typically a homepage, an about page, service or product pages, case studies, and a contact form, sometimes with a news section or blog you can update yourself. This is what most small and mid-sized businesses actually need.

E-commerce site. Everything a corporate site has, plus product management, a shopping cart, payment integration, order and fulfillment flows, and member accounts. Each of those is a separate functional module, and each carries its own testing and maintenance cost.

Custom system. Moving an internal operating process online — order management, quoting, appointment scheduling, a dealer portal. The cost here sits less in the visual design than in untangling the process and turning it into logic.

The distance between the first and last of those is not a matter of degree. Before you talk budget, confirm which box you are in.

The cost structure behind a quote

Whichever vendor you use, the money ends up in these buckets:

Item	What it covers	What makes it expensive
Requirements discovery	Turning vague ideas into a defined specification	Shifting requirements, many stakeholders, nobody deciding
UI/UX design	Layout, visual design, interaction flow	Fully bespoke work, many page types, building a design system
Front-end development	Turning designs into pages that render correctly on every device	Heavy animation, complex interaction, legacy browser support
Back-end development	Data storage, permissions, business logic	Member accounts, payments, reporting, external integrations
Content preparation	Copy, images, loading product data	Vendor writes the content, or large volumes of data to migrate
Testing and launch	Cross-device checks, fixes, deployment	Broad feature set, multiple rounds of acceptance

The two most underestimated lines are requirements discovery and content preparation. The first determines whether everything downstream has to be redone; the second is the one both sides quietly assume the other party will handle, which is how projects end up stalled with no copy and no product photography. NETVANA’s software development process puts requirements discovery in the first phase and produces a written specification, precisely for this reason — clear requirements are what let everything after them move quickly.

Six factors that move the quote

One: the number of pages, and the number of page types. What drives the hours is not how many pages exist but how many distinct layouts do. Twenty product pages sharing one template cost far less than five pages that each look different.

Two: how bespoke the design is. Roughly, from most to least expensive: fully custom visual design, an extension of an existing design system, an adapted template. This factor usually has the most direct effect on the total.

Three: how deep the admin functionality goes. “I want to be able to edit the content myself” can be built many ways, from simple text fields to a full drag-and-drop layout editor, and the workload between them is very different. List the things you will genuinely update yourself rather than asking for everything to be editable.

Four: multiple languages. Multilingual is not just a second set of translations. URL structure, switching logic, a content maintenance workflow for each language, and language markup for search engines all have to be handled. If the goal is mainly to look international, assess the real overseas demand first.

Five: payments and third-party integrations. Payment gateways, logistics, invoicing, CRM, ERP — each one involves an application process, testing, and error handling. The quality of the external system’s documentation and the responsiveness of its provider directly affect the hours, which is why this category is the hardest to estimate precisely.

Six: who prepares the content. Copy, product photography, and specification tables supplied by you will save a meaningful amount. Asking the vendor to write or shoot them is a separate professional discipline and should be quoted as its own line item.

Template or custom: how to choose without regretting it

This is not a question of which is better. It is a question of whether your website will change over the next three years.

A template or platform build suits you if the site is mainly there to present information, there is no unusual process involved, the budget is limited, you want to be live soon, and you have no technical staff in-house.

Custom development suits you if the site has to carry a real operating process, needs to connect to systems you already run, has demanding requirements for load speed or search performance, or will predictably keep growing new functionality.

There is a middle option that gets overlooked: build on a mature content management system and customize only the parts that need it. That buys most of the flexibility within a controlled budget, and in practice it is the best-value answer for a lot of small and mid-sized businesses.

One thing worth flagging is the cost of moving. When a site is built on a platform, what you can usually take with you later is text and images; the layout and functionality have to be rebuilt. Ask the question before you commit: if we leave one day, what can we take?

One-time costs versus recurring costs

Most blown budgets are not the result of a mis-estimated build. They are the result of never counting what happens after launch.

One-time: requirements planning, design, development, testing, deployment, training.

Recurring:

The domain name (renewed annually; letting it lapse takes the site offline)
Hosting or cloud services (billed by plan and traffic)
SSL certificates (included in most cloud plans, but worth confirming)
Security updates for the system and its packages
Content updates and small functional adjustments
Monthly fees for third-party services (payments, email marketing, support tools)

The sensible way to budget is to look at the build cost and the first year of recurring cost together. Confirm two things before signing as well: are small changes after launch included in the maintenance fee or billed separately, and is that billing per request, per hour, or monthly?

What to look for in a proposal

A proposal you can actually compare should answer at least the following:

Scope: pages, features, and deliverables listed specifically, not “corporate website, one set”
What is excluded: explicitly stated exclusions, such as copywriting, photography, or hosting fees
Timeline and milestones: the duration of each phase, and the points where your input is required
Revision rounds: how many revisions the design phase includes, and how additional ones are priced
Acceptance criteria: what counts as finished
Ownership of source code and files: what you receive at the end (NETVANA’s practice is that once final payment is received, source code, design files, and documentation are transferred in full)
Warranty and maintenance: the warranty period, what it covers, and what the maintenance plan looks like afterwards

For a full method of evaluating vendors, see How to Choose a Software Development Company.

Common low-price traps

When a quote comes in noticeably below the others, work out where the savings came from:

Acceptance testing, QA, and launch training have been excluded. Development finishing is not the same as the site being usable, and those three items are not a small number of hours.

Unlicensed templates and assets of unknown origin. Licensing problems with fonts, stock images, and plugins tend to surface after launch.

Desktop only. Mobile browsing carries the majority of traffic in most industries; skipping responsive design means giving up most of your visitors.

Recurring costs hidden further down. The build quote is very low, but hosting, maintenance, and future changes are locked into an expensive monthly fee.

No source code handover. The site gets built, but you cannot change vendors, and every future change has to go back through the same company.

Basic search and speed conditions ignored. Page titles, descriptions, URL structure, image compression, and mobile speed are baseline quality, not paid extras. If you plan to redesign later, this debt all comes due at once; see the Website Redesign SEO Checklist for the risks involved.

Phasing the work when the budget is tight

With a limited budget, the worst choice is to build a crude version of every feature. The practical approach is to build the smallest scope that validates the requirement, confirm it works, and expand from there — the same logic that underpins building an MVP for a new product.

Concretely: in phase one, make the brand presence and conversion path solid — findable, understandable, contactable. In phase two, let real data decide whether to add member accounts, payments, or a custom admin system. The precondition is that the phase-one architecture can hold phase two, which is something to state clearly during requirements discovery.

There is no standard answer for what a website costs, but where the money goes can be stated clearly. The more specific the questions you can ask, the more comparable the quotes you receive, and the lower your chances of a bad outcome.

If you already have an initial set of requirements, or you are comparing proposals and want to check whether anything is missing, talk to NETVANA about your website — we clarify scope before we discuss numbers. NETVANA’s software services are quoted individually rather than sold as fixed packages; for what each service includes and delivers, see the software services overview.

Further reading: for how the cost structure differs on an app project, see the Complete Guide to App Development Costs. If you are weighing outsourcing against building an in-house team, see Outsourcing vs. an In-House Team. And if you are about to redesign an existing site, start with the Website Redesign SEO Checklist. For comparing shared, VPS, cloud, and static hosting, see How to Choose Web Hosting; and for how your CMS choice moves the quote, see How to Choose a CMS; and for contract models, SLAs, and handover terms, see What Website Maintenance Actually Covers. For the domain and certificate line items quotes tend to skip, see Domains and DNS in Plain English; and for how many languages you need, and what that adds, see The Multilingual Website Development Guide. Before pricing a website, decide whether your business needs one at all, see Does a Small Business Need a Website. After understanding cost structure, learn to break down an actual quotation line by line, see How to Read a Software Quotation.