A business owner's hands over two printed proposals in the light of a desk lamp

How Much Does a Website Cost? What Drives the Price

"How much does a website cost?" is the first question in almost every inquiry, and the honest answer is "it depends." That sounds like a dodge, but the spread in website development prices comes down to very specific things: the scope of work, the depth of the work, and what the vendor included in the estimate versus what it left out.

In this article we break down what drives the cost of a website, which pricing models exist, how to compare estimates from different agencies and where you shouldn't cut corners. There won't be specific figures: they go stale faster than an article gets indexed and, without context, only confuse. But by the end, you'll be able to break any estimate down into clear parts yourself and ask your vendor the right questions.

Why one website can have three different prices

A typical scenario: a company sends the same short brief to five vendors and gets quotes that differ several times over. That doesn't necessarily mean someone is overcharging. More often, each vendor filled in what the brief left out in its own way.

One vendor reads "we need a 10-page corporate website" as a template with the client's copy dropped in. Another reads it as a custom design with a prototype and responsive layouts. A third reads it as a project with competitor research, copywriting, CRM integration and analytics setup. All three estimates are honest, but they describe three different products.

The cost of a website makes sense to discuss not as one number but as a sum of work.

So below, we go through the main components of that sum.

What drives the cost of a website

Type of website

A landing page, a corporate website, a catalog, an online store and a website with a customer portal are different classes of work. A landing page is one page with one goal; most of the work is in messaging and design. A corporate website is a set of sections, page templates and an admin panel. An online store adds a catalog with filters, a cart, payments, shipping and data exchange with an inventory system. A customer portal is essentially a web service with roles, permissions and business logic.

Number of pages and templates

Pricing "per page" isn't quite accurate. What matters more is how many unique templates the website has. A hundred product pages built from one template cost less than ten pages that each have a different structure.

Custom design or a template

A ready-made theme is faster and cheaper at the start. But you get someone else's structure that you squeeze your content into, and you look like hundreds of other companies. Custom design starts with research and a prototype: first we decide what the user should see and in what order, and only then do we design. It takes longer, but the website is built around your goals, not the other way around.

Integrations

Integrations are what most often turn a "simple website" into an expensive one: a CRM such as HubSpot or Salesforce, telephony, an ERP or accounting system, a payment gateway, shipping carriers, partners' external APIs. Each integration isn't just code; it's working through someone else's documentation, test access, error handling and coordination with people on the client side. If the ERP sync runs both ways and includes stock levels by warehouse, it may well be the most labor-intensive part of the project.

Content

Copy, photos, illustrations, video. If the client prepares the content, that needs to be agreed in writing, with time built in for it arriving later than planned. If the vendor writes the copy, that's separate work with its own budget: interviews with the company's experts, structure, editing, approvals.

CMS and tech stack

The choice of technology affects both the cost of development and the cost of ownership. A traditional CMS such as WordPress offers lots of ready-made plugins and an admin panel many teams already know. A modern framework, such as Next.js with a separate headless CMS, gives more freedom in the interface and better speed, but requires developers with the right skills for ongoing support. We work with both and choose the stack based on the task and on who will be maintaining the website a year from now.

Responsive design

Responsive layouts are standard today, not an option. But the amount of work varies: you can simply "shrink" the desktop version, or you can think through mobile scenarios separately, with a different block order, different navigation and simplified forms. If most of your audience comes from phones, the second approach pays off.

SEO groundwork

Clean URLs, editable meta tags, a correct heading structure, a sitemap, structured data, load speed, redirects when migrating. This isn't promotion; it's the technical foundation without which promoting the website later costs more.

Post-launch support

CMS and library updates, backups, monitoring, small improvements, bug fixes. It's rarely included in the first estimate, but it's what determines how much the website costs you per year, not just at launch.

Pricing models: fixed price or T&M

There are two basic ways to agree on money, and each has its own area of use.

Fixed priceTime & Materials
How it's calculatedA set amount for a clearly defined scope of workActual hours spent at an agreed rate
When it fitsThe task is clear: there's a structure, a prototype or a detailed specificationRequirements get refined along the way: complex integrations, new products, ongoing development
Upside for the clientEasy budget planning; the risk of a wrong estimate is on the vendorRequirements can be adjusted as work progresses
DownsideChanges go through contract amendments; the price includes a buffer for uncertaintyRequires transparent reporting on tasks and hours, and trust in the team

In practice, a combination often works: discovery and design are paid at a fixed price, which produces an accurate development estimate, and further development runs on T&M or a monthly block of hours.

How to compare vendor estimates

Comparing totals is pointless until you know what's in them. Here's a process that helps.

  1. Bring the proposals to the same scope. List the work from every estimate in one table: discovery, prototype, design, front end, back end, integrations, content, testing, data migration, analytics setup, support. You'll immediately see who left what out.
  2. Check how many templates and design variants are included. "Website design" can mean a single home page concept or a full set of mockups for every page type and screen size.
  3. Look at the hours per stage. If testing gets almost no time and the CRM integration is estimated as a small task, that's either optimism or future contract amendments.
  4. Ask what's not included. Hosting, CMS licenses, paid plugins, stock photos, copywriting, migrating old content, staff training.
  5. Clarify the terms for revisions and warranty. How many rounds of revisions, what counts as a bug and what counts as a new task, how long the warranty period lasts.
  6. Find out who will do the work. An in-house team or subcontracted freelancers, whether there's a project manager, who's accountable for the result.
  7. Look at similar work. Not the prettiest projects, but the ones closest to your task. Ours are collected in our portfolio.

A good website estimate makes sense without a call: it's clear what work is included, in what volume and with what deliverable at the end of each stage.

Where not to cut corners

Budgets are almost always limited, and something will have to be trimmed. But there are line items where cutting costs more than it saves.

A structural mistake is cheap to fix in a prototype and expensive to fix after development.

How to get a realistic estimate

The more precise the input, the more precise the number. Before asking for an estimate, gather:

Don't be afraid to name a budget up front. It's not an invitation to "fit" the price; it's a way to quickly understand what can realistically be done within that range and what to move to a second phase.

If the project is complex, it's more honest to start with a short discovery and prototyping phase. As a custom website development agency, we find that after it, the development estimate becomes accurate rather than "give or take a factor of two."

FAQ

Can I get an exact website price from a short description?

Only a rough range. An accurate estimate comes once the structure, number of page templates, integrations and responsibility for content are pinned down. For complex projects, it's given after a discovery and prototyping phase.

Which is better value: a template website or a custom design?

A template is cheaper at the start and fits when you need to test an idea quickly or the task is standard. A custom design pays off when the website is your main sales channel, standing out from competitors matters, and the structure needs to be built around your scenarios rather than someone else's theme.

Why do integrations affect the price so much?

Each integration means working through another system's API, getting access, handling errors and testing data exchange across different scenarios. A two-way sync with an ERP or CRM can take as much effort as building the front end of the entire website.

Is support included in the price of a website?

The price usually includes a warranty period for fixing bugs. Ongoing support, such as updates, backups and improvements, is arranged separately, as a block of hours or a monthly retainer. Clarify this before signing the contract.

Which pricing model should I choose: fixed price or T&M?

A fixed price fits well-defined tasks with a ready structure or specification. T&M fits projects where requirements will change along the way. A combination often works best: discovery and design at a fixed price, development and ongoing work billed by actual hours.

Let’s discuss your project
Related reading