Category
Knowledge base
Subject
Web development
Reading time
14 minutes
Level
Decision maker
Updated
May 2026

What does it cost to build a website?

An honest explanation of what determines the price of a new website: functionality, integrations, design, content and the choice between WordPress and custom. Written for decision-makers who want more than a quote and want to understand where the money goes.

What determines the cost of building a website?

Anyone searching for "website development cost" is quickly presented with a wide range of figures, from a few hundred euros for a template site to a serious six-figure budget for a complex web application. That spread is no marketing trick — it simply reflects how broad the term "website" is. A one-pager with a contact form and a SaaS portal for thousands of users both fall under the heading "website", but the build behind them is completely different.

For a realistic picture of the price, five factors come up every time, whether you want to build a corporate brochure site, a webshop or a complex platform. If you understand these five levers, you can assess a quote better — and you'll also know what happens when one of them is changed during the project.

  • Functionality and complexity: how many different types of page, how much interaction, how much logic behind the scenes? A static site with ten pages is fundamentally different from a platform where users log in, make transactions and view data.
  • Integrations with other systems: does the site need to talk to your CRM, ERP, accounting software, email marketing, a PIM or an external API? Every integration is a mini-project of its own, with its own testing and maintenance.
  • Design and branding: are you working with an existing brand book, or does a visual concept need to be developed first? How many iterations and how much custom component work? Standard templates are cheap; custom design takes design days.
  • Content volume and complexity: ten pages or three hundred? In one language or several? Do you have the copy and images ready, or do editing and photography need to be included too?
  • Technical choices (CMS and codebase): an off-the-shelf CMS such as WordPress, a headless setup, a framework like Astro or Next.js, or fully custom in your own codebase. Each choice affects build time, maintenance burden and flexibility.
i
In short

The price of a website is not a fixed number — it's the outcome of choices about functionality, integrations, design, content and technology. Change one parameter and the quote moves with it.

What types of website are there, and how does the cost structure differ?

It helps to place your own requirements within a handful of clear categories. We see roughly five types of project, and for each one the bulk of the cost sits in a different place. Keep in mind that this is about where the budget goes, not about absolute amounts.

1. The brochure site or one-pager

A handful of static pages presenting your organisation: home, about us, services, contact. No accounts, no complex forms, no integrations. The bulk of the budget here goes on design and content — the technology is relatively simple. For many freelancers, service providers and local businesses this is the right level, provided it looks good and is sound from an SEO perspective.

2. The WordPress or template-based site

A more extensive site with a blog, news, case studies, and possibly a simple form or resource library. Often built on WordPress with a premium theme or a page builder. The budget shifts here towards configuration, plugin selection, performance optimisation and setting up a CMS that your own marketing team can work with independently.

3. The webshop

For webshops, we look at the number of products, variants, the complexity of pricing rules, stock management, shipping methods, payment methods and integrations with the back office. A Shopify shop with ten products sits at the lower end of this segment. A B2B webshop with customer-specific pricing, an ERP integration, stock synchronisation and a complex quote process sits at the top end — you can read more about this on our Magento 2 website page.

4. The headless or custom corporate site

A site where marketing teams manage content in a modern headless CMS (Directus, Sanity, Contentful), while the frontend runs on a framework such as Astro or Next.js. Fast, SEO-friendly, multi-channel and flexible. The budget goes into architecture, a component library, integrations with marketing tools and setting up an editorial workflow.

5. The web app or platform

A user portal, a SaaS product, a marketplace, a dashboard. This is no longer a "website" in the classic sense — it is a product. Here the vast majority of the budget goes into functionality, user authentication, data models, business logic and testing. For the broader context, read our page on web development.

WordPress versus custom: what are the trade-offs?

This is probably the question we get asked most often: "Should we go for WordPress or custom?" The honest answer is that it depends on what you want to achieve, how long you expect the site to run and how closely your requirements match what WordPress does out of the box. Both options have legitimate use cases. The problem arises when you choose WordPress for something it wasn't designed for, or choose custom where WordPress would have been perfectly adequate.

The case for WordPress

  • Lower initial investment. The CMS is free, there are thousands of themes and plugins, and plenty of developers are available.
  • A quick start. A professional site goes live relatively quickly if the functionality falls within the standard options.
  • Familiar to marketing teams. Many marketers already know the editor, so there is less of a learning curve.
  • A huge plugin ecosystem. For SEO, forms, analytics, e-commerce, member portals: there is almost always a plugin already.

The case against WordPress

  • Performance. An average WordPress site with several plugins is rarely as fast as a well-built headless or static site. For some use cases (think SEO-critical content or heavy media sites) that makes a real difference.
  • Security and maintenance. Because of its popularity, WordPress is a major target for attacks. Anyone running it has to update structurally — otherwise vulnerabilities appear.
  • Plugin rot. The more plugins, the more dependencies, and the more things that can break with an update.
  • The limits of customisation. Once your requirements go beyond what plugins can do, you end up with a tangle of workarounds.

Custom development comes into play as soon as you want to build something the standard options don't do, as soon as performance is business-critical, or as soon as you want to keep using the site for more than a few years without maintenance becoming a second full-time job. We have written at length about this in our knowledge base article build vs buy: when to choose what — the same reasoning applies to websites.

How is a quote for a website put together?

Agencies roughly build quotes for a website project in one of three ways. Which one suits your situation depends on how clearly defined your requirements already are and how much uncertainty you can absorb.

Fixed scope, fixed price

The classic. You supply a requirements document, the agency estimates it and builds it for a fixed amount. Advantage: budget certainty. Disadvantage: all the uncertainty is hidden in the price (agencies add a risk margin) or in the scope (if anything changes, extra work follows). It works well for projects where you really know what you want and the scope no longer shifts — for example, a redesign of an existing corporate site with the same functionality.

Sprint budget (time & materials)

The way we usually work. We work in sprints at a fixed rate per sprint, and you decide sprint by sprint what has the highest priority. Advantage: you can adjust course along the way, prioritise what matters most and stop when what has been built is already enough. Disadvantage: you have to accept up front that the exact end date and final cost only become clear as you make decisions about scope.

Hybrid: discovery + build

You start with a short, paid discovery phase in which scope, design and technology are worked out. Only after that phase is the actual build budget estimated, often far more accurately, because the uncertainty has been removed. This works well for larger or more complex projects where you want to take the first step separately without immediately committing to a large sum.

!
Tip

For every quote, ask explicitly: what is included, what is not, and what happens with additional work? A good quote has a clear scope appendix and a clear agreement on how changes are handled.

Where are the hidden costs?

The purchase price of a website is rarely the whole story. There are four categories of cost that are regularly overlooked, and after a few years they can add up to as much as the initial build costs.

Hosting and infrastructure

A site has to run somewhere. For a small WordPress site, that is a few tens of pounds a month. For a serious e-commerce or platform application, it can rise to substantial monthly amounts, especially when a CDN, redundancy, backups and staging environments are involved. Always ask a supplier to estimate the annual hosting costs, not just the build budget.

Maintenance, updates and security

CMS updates, plugin updates, framework updates, security patches. A site that is not maintained will run into problems sooner or later. Allow for a regular hour or a maintenance contract, depending on complexity. For a WordPress site with many plugins, this is a more significant item than for a static headless site.

Content creation and editing

Many quotes assume that you supply the copy and images. That sounds logical, until go-live approaches and it turns out nobody in your organisation has the time. Budget in advance for copywriting, photography, video and, where relevant, SEO content, otherwise you go live with a beautiful shell and empty pages.

SEO, analytics and ongoing optimisation

Launching a new site is not the same as being found. Allow for a programme of technical SEO work (sitemaps, structured data, Core Web Vitals), setting up analytics and conversion tracking, and an ongoing rhythm of content expansion and optimisation. Agencies that promise "SEO included" often only do the technical part, so ask exactly what is covered.

What determines a web developer's hourly rate?

A frequently asked question is "what does a web developer cost per hour?". The answer varies greatly by market, by level and by type of agency. We don't quote figures here, but we do list the factors that explain why the range is so wide.

  • Experience and specialisation. A junior front-end developer from a large talent pool sits at the lower end. A senior full-stack developer with domain experience in, say, fintech, e-commerce or manufacturing sits considerably higher.
  • Agency versus freelance. With an agency, you also pay for account management, project management, quality assurance and continuity. A freelancer is usually cheaper per hour, but the risk profile is different.
  • Location and currency. Dutch agencies sit in a different price bracket from offshore teams in Eastern Europe or Asia. Both have their place; for projects where close collaboration, language and domain knowledge are crucial, Dutch availability carries a lot of weight.
  • Responsibility in the contract. Someone who only delivers code is cheaper than an agency that takes on delivery guarantees, security responsibility and lead time.
  • Stack and scarcity. Scarce skills (think experienced Astro developers, DevOps engineers with Kubernetes experience, specialist ERP integrators) command higher rates than general front-end work.

So the question "what does an hour of web development cost?" is less relevant than "what do I get for that hour?". A cheap hourly rate that ends up needing three times as many hours is more expensive than a higher rate with an efficient specialist.

Can we start small and expand later?

The short answer is yes, provided you set up the architecture for growth from day one. Many clients choose to build in phases: first an MVP with the core functionality live, then continued development based on what users and the market show.

This works well under two conditions. First, the first version must be set up technically so that expanding it doesn't mean rebuilding everything. That calls for a well-considered stack, a clean component library and a CMS that grows with you. Second, the first version must deliver enough value that it doesn't feel half-finished. An MVP is not the same as an unfinished site.

The alternative, thinking everything through perfectly upfront and only going live once everything is done, costs more time and more budget, and keeps you stuck on assumptions about what users want for longer. For most organisations, we see a phased approach working, especially on larger projects. You can read how we do this in practice on our page about web development and in the broader article on custom software costs.

Frequently asked questions about website costs

What has the biggest influence on the price of a website?

The combination of functionality and integrations weighs the heaviest. A static site with ten pages and no integrations has to be estimated very differently from a platform with user accounts, payment flows and integrations with ERP or CRM. Design and content volume are the second major factor: a corporate redesign with photography and editorial work costs considerably more than reusing existing brand material.

Is WordPress cheaper than custom?

In the build phase, often yes. In the long term, rarely so simple. WordPress is cheaper if your requirements fall within the standard options and you accept that ongoing maintenance is needed. As soon as your requirements fall outside what plugins can do, or once performance and security become business-critical, the maths flips. We advise you to first take an honest look at what the site needs to do, not at what is popular.

What is and isn't usually included in a website quote?

Typically included: design, development, basic SEO, a CMS environment, a set of pages or templates and go-live support. Typically not included: content creation (copy and imagery), hosting after the first few months, ongoing maintenance, advanced SEO programmes, multilingual translation work and marketing integrations that require specific configuration work. Read every quote with these items in mind, because this is where most of the confusion arises afterwards.

How long does it take to build a website?

That depends on scope and complexity. A brochure site can be live within a few weeks if design and content are sorted quickly. A serious web shop or corporate redesign runs over a few sprints. A complex platform is a project of multiple sprints with multiple people. We work in sprints so you can see what is being built along the way and adjust course. Nobody wants a big-bang delivery after a long silence.

Can we start small and scale up later?

Yes, and we often recommend it. The crucial point is that the architecture is ready for expansion from the start, otherwise you'll be rebuilding after a year. We regularly help clients launch a first version with the core functionality and then expand in phases based on user feedback and business priorities. A similar approach works for app projects, and you can read more about that in app development costs.

How can we avoid hidden costs?

With every quote, explicitly ask about annual hosting costs, the maintenance arrangement, what happens with additional work, and who is responsible for updates and security patches. Also ask whether content creation is included. Hidden costs almost always arise on items that haven't been explicitly discussed, not out of ill intent, but because of assumptions that were never spelled out.

The three key points.

01

Price follows scope

Functionality, integrations, design, content and technology choices together determine the budget. Change one parameter and the quote moves with it.

02

WordPress or custom is not a matter of taste

WordPress is cheaper to start with, while custom often wins in the longer term. The right choice depends on your requirements, performance needs and lifespan.

03

Factor in the hidden costs

Hosting, maintenance, content creation and SEO are ongoing costs. A good quote makes them explicit.

Talk to us about your website project.

A half-hour introduction. We listen to what you want to build, help you think through the scope and give you an honest indication of complexity, lead time and budget.

Edit content