Ask five agencies to quote for the same website and you can get five very different numbers. That is frustrating, but it is not always a sign that someone is overcharging. Website quotes vary because the brief usually leaves room for interpretation, and each supplier fills the gaps with different assumptions.

This guide explains what actually drives the cost of a CMS website, so you can read quotes with more confidence, compare them fairly and decide where your budget is best spent. We have deliberately not put figures on it. Rates vary widely by region and supplier, and a number without context is more misleading than helpful.

Pages matter less than templates

People often describe a project by page count, but page count on its own says little about effort. What matters is how many distinct templates the site needs.

A site with two hundred blog posts might only need one article template and one listing template. A site with fifteen pages might need twelve different layouts if each page is designed individually. The second can easily cost more than the first.

When you brief a project, list the types of page rather than the number: home page, service page, case study, article, team page, contact page and so on. That gives suppliers something concrete to price.

Custom features and functionality

Content pages are the predictable part. Custom features are where budgets move most.

  • Search and filtering beyond a basic search box, such as a product finder or a resource library filtered by several criteria.
  • User accounts with logins, member areas, gated content or saved preferences.
  • Booking, quoting or calculators that follow your business rules.
  • E-commerce, especially with complex pricing, subscriptions, trade accounts or product configuration.
  • Multilingual content, which affects templates, content entry, workflows and SEO setup.

Each of these may be handled by an existing plugin or module, adapted, or built from scratch. Which one applies makes a large difference, and a good supplier will tell you which approach they have assumed.

Integrations with other systems

Connecting the website to your CRM, email platform, ERP, inventory system, payment provider or booking software is often underestimated. A simple form that sends leads to a CRM is usually straightforward. Two-way syncing of products, stock and orders with an ERP is a project in its own right.

The cost depends on how good the other system’s API is, how clean its data is, and what should happen when something fails. Ask suppliers how they plan to handle errors and retries, not just whether they can connect the systems.

Content migration

If you are rebuilding an existing site, moving content across is a real piece of work. The effort depends on volume, how structured the old content is, and how different the new content model will be.

  • Copying a few dozen pages by hand is simple.
  • Migrating thousands of articles, products or documents usually needs scripted migration, checking and clean-up.
  • Content buried in messy page builder markup takes longer to move than content stored in clean fields.

Do not forget redirects from old URLs. They protect the search visibility you have built up and they are easy to leave out of a quote.

Before asking for quotes, decide which old content you are actually keeping. Archiving material that gets no traffic is often the cheapest saving available on a rebuild.

Design depth

Design ranges from adapting an existing theme to a fully bespoke design system with custom illustration, motion and detailed component libraries. Both are valid. The right choice depends on how important the website is to your brand and how much you need to stand out.

Things that add design effort include the number of unique layouts, separate mobile designs for complex pages, rounds of revisions, brand development work and user research or testing. Things that reduce it include a clear existing brand, an agreed set of reusable components and a decisive sign-off process.

Licences and third-party costs

Some costs sit outside the build fee entirely, and they recur.

  • Premium plugins, modules or themes, usually with annual renewals.
  • CMS licences, for platforms that charge, such as Craft CMS Pro or certain headless CMS plans.
  • Platform subscriptions, for hosted systems such as Shopify, Webflow or HubSpot CMS.
  • Third-party services such as search, forms, maps, translation or email delivery.

Ask for these to be listed separately in any quote, so you can see the running cost of the site, not just the launch cost.

Hosting and infrastructure

Hosting ranges from inexpensive shared plans to managed platforms and dedicated cloud setups. A small brochure site does not need much. A busy online shop or a site with heavy traffic spikes needs reliable infrastructure, caching, backups, staging environments and monitoring. Cheap hosting tends to show up later as slow pages and stressful outages.

Ongoing care after launch

A CMS website is software. Core updates, plugin updates, security patches, backups, uptime monitoring and small content or design changes all need someone’s time. Budgeting nothing for this is how sites drift into the slow, insecure state that leads to an expensive rebuild a few years later.

Rough tiers, in words

Without quoting figures, here is how projects typically compare relative to each other.

Type of project Typical scope Relative cost
Small brochure site A handful of templates, contact form, simple CMS, theme-based or light custom design Lowest
Established business site Custom design, structured content, blog or resources, CRM integration, content migration Moderate
E-commerce store Product catalogue, checkout, payments, shipping rules, some integrations Moderate to high, depending on catalogue and integrations
Large or complex platform Many content types, multilingual, user accounts, several integrations, large migration Highest

Platform choice also shifts cost. A hosted platform such as Webflow or Shopify can reduce hosting and maintenance work but adds subscription fees. A self-hosted CMS such as WordPress or Craft CMS gives more control but needs more care. A headless setup adds flexibility and usually adds front-end development effort. Our CMS development overview covers the platforms in more detail.

How to get quotes you can compare

  • Share a list of page types and features, not just a page count.
  • Say which systems the site must connect to.
  • Be clear about how much content is moving across.
  • Ask each supplier to state their assumptions and what is excluded.
  • Ask for one-off costs and recurring costs to be shown separately.
  • Share a budget range if you have one. It lets suppliers propose the best solution for it rather than guessing.

Phasing is also worth considering. Launching a solid core site first and adding advanced features later spreads cost and lets real usage guide what you build next. Our process page shows how we break projects into stages.

Want a clear estimate for your project?

If you would like a realistic estimate based on your actual requirements, get in touch and we will walk through it with you.