10 August, 2026
Umbraco CMS

How much does an Umbraco website cost in 2026?

A professionally built Umbraco website typically costs somewhere between €15,000 and €100,000+, depending mainly on integrations, design, content migration, languages and accessibility requirements.

However, that the range is useless without context. A straightforward marketing site, and a multilingual platform connected to an ERP are technically both “Umbraco websites”, but they are not remotely the same project.

min reading time
Image about office desk and text: What does an Umbraco Site actually cost?

Why nobody publishes this number

Search for what an Umbraco website costs and you will find agency pages that say "it depends" and then ask you to book a call. They are not being evasive for fun: the range really is wide, and a number you cannot stand behind is a liability.

The effect, though, is that a buyer cannot build a budget without entering a sales process, and the first real figure they hear comes from someone with an incentive. So here are the ranges I work with. They are based on my own delivery experience in the Nordic and Western European market, they exclude content production and paid media, and they assume a build that is meant to last more than two years.

The three bands

€15,000 – €30,000: a standard marketing site. Ten to thirty pages, an existing brand and design direction, a structured content model, standard integrations (analytics, a newsletter tool, forms), one language or a simple second one. Built on an existing foundation rather than from a blank Umbraco install. Six to ten weeks. This is where many small and mid-sized company websites can land when the project starts from an established technical foundation rather than rebuilding the basics from scratch.

€30,000 – €65,000: a corporate site with real requirements. Custom design system rather than a theme, three to five integrations, proper multilingual setup, site search, editor training, and accessibility work that is planned rather than retrofitted.
Three to four months.
This is roughly what the standard platform I'm selling contains.

€65,000 – €100,000+: integration-heavy or multi-site. ERP, CRM, authentication or pricing systems in the critical path; several sites or brands on one installation; migration of thousands of pages into a new content model; a formal accessibility audit. Five to nine months.

What actually drives the number

  1. Integrations. The single biggest multiplier, by a wide margin. Each one is discovery, authentication, error handling, monitoring and an ongoing support.

  2. Design. A design system costs more than a theme and is worth it if the site lives five years or more. If it does not, buy less design.

  3. Content migration. Page count multiplied by structural difference. Two hundred pages moving into the same shape is cumbersome, but relatively cheap. Two hundred pages moving into a new content model is its own project, and it is the line item that most often blows a fixed price.

  4. Languages. A second language adds maybe 10–20% if it is planned from day one.

  5. Accessibility. Cheap when built in, expensive as remediation. Since the European Accessibility Act came into force this stopped being a nice-to-have for a lot of organizations, and is now taken very seriously.

The cost of ownership

The cost of the initial build is the number everyone compares. The five-year cost is the number that - according to myself - actually matters.

  • Hosting: Umbraco Cloud is €45 per month on Starter, €280 on Standard and €730 on Professional at 2026 pricing, plus €70 per month for a staging environment. Self-hosting on Azure is usually cheaper in raw infrastructure and more expensive in attention. Neither is wrong.

  • Umbraco add-ons: Professional Support runs €11,000 a year and Umbraco Deploy on-premises €1,100–€2,800.

  • Maintenance: Budget 10–20% of the build cost per year for security patching, minor version upgrades and small changes. A retainer with a trusted developer or agency is the way to go here.

  • Major version upgrades: Once per LTS cycle (usually 3 years), and they are real projects. Umbraco 13 reaches end of life on December 14, 2026, which is the current live example of a cost that was predictable for years and still surprised people.

As a planning figure: five-year total ownership usually lands at 0.6 to 1 times the build cost. If a proposal implies otherwise, something has been left out. While this may not be the exact truth, it's a good thing to calculate by.

Where my own rates sit

Senior .NET and Umbraco consultants in the Nordic market typically charge around 1,300–1,700 SEK (~€115–€150) per hour, with specialist and architect-level work reaching 1,700–2,200 SEK (~€155–€200), according to compiled rate data from Brainville, Cinode and Dataföreningen.

My own rates typically range from €85 to €130 per hour, depending on the scope, commitment and length of the engagement. That puts me below much of the published Nordic senior-consultant range, particularly for longer projects.

But hourly rate is only half of the equation. A €90/hour developer who needs 500 hours costs considerably more than a €120/hour developer who needs 300 hours to do the same job.

Five ways to make the number smaller

  1. Cut integrations. Integrations drive cost; ask whether an integration is really needed.

  2. Start from a foundation, not a blank install. A surprising amount of an Umbraco build goes into infrastructure that is largely the same from project to project.
    Depending on the project, that can eliminate around 100–150 hours of foundational development, or roughly €10,000–€15,000 at typical senior development rates.
    See the platform I created here.

  3. Decide the content model before the design. Redesigning a page is cheap. Restructuring content after the model is built is not.

  4. Minimize third-party packages: While they can save you money here and now, third-party packages needs to be updated regularly, but when a major version of Umbraco is released, the package may not be available, and you need to reapply any page using that feature in a new way. This is usually very costly!

  5. Do content migration in-house: Yes, this is typically a huge cost saver. Imagine you have 200 pages; if the developer in charge is doing the migration, not only is this a costly resource to migrate everything, but he/she will move things mindlessly, rather than asking if the content is still relevant or could be removed.
    On top of that, the employee learns Umbraco fluently.

Getting a real number for your project

Ranges are for budgeting. They are not a quote, and anyone who gives you a fixed price from a one-paragraph brief is either padding it heavily or planning to make it up in change requests.

If you want a number that you can take to a budget meeting, describe the site: page count, the systems it has to talk to, how many languages, who maintains it afterwards. I will tell you which band you are in and why. Use the form below.

Let’s discuss your project

Need help with web development, Umbraco CMS, SEO, performance, or technical improvements to an existing website? Send a message using the form below, and we can have a virtual coffee to discuss your needs and the best way forward.



Share this article