What does a website cost? Real prices and ranges
Real price ranges with the reasoning behind them - what a website is made of, what moves the number most, and where it's sensible to save.
4 June 2026 · 5 min read · Rixio Digital
The most common question in a first call is "what does a website cost?". Most articles answer that with "it depends" and move on. So let's start with the numbers and justify them afterwards.
Our prices
| What | Price | When it fits |
|---|---|---|
| Small website | €499 – 990 | One to five pages, your content, one revision round. Fixed: 1 page €499, up to 3 €790, up to 5 €990. |
| Website | from €1,200 | Most projects €1,200 – 4,000. A brochure site with custom design and manageable content. |
| Online store | from €1,499 | Most projects €1,499 – 6,000. WooCommerce with payment and delivery set up. |
| Web application | from €3,900 | A portal, an internal tool or an MVP. Scoped after an initial mapping. |
| Maintenance | €50 – 199/mo | Updates, backups, monitoring and an agreed allowance of changes. |
These are starting points rather than final numbers - what moves them is below. VAT is added on top.
Where the range comes from. A five-page brochure site with content ready sits at the bottom of it. The top is a multilingual site with several content types, custom blocks and an integration into a system you already run. Most projects land somewhere between.
Why we're not the cheapest. You can buy a website in Estonia for €300 – 700, and those are real websites. The difference shows up a year later: a bought theme with ten plugins works fine on launch day and then degrades as updates start breaking each other. We build a custom theme and keep the plugin count low. If what you actually need is a couple of simple pages, we'll say so and point you at the small website from €499.
The rest of this is about which decisions move that number.
What affects the price most
The number of pages, and the number of content types
The page count on its own says very little. What matters is how many different kinds of page have to be designed and built. Twenty service pages using one template are cheaper than five pages where each one is unique.
The same goes for content types: if a site needs projects, job listings, locations or events alongside ordinary pages, each of those is a separate piece of work - its own fields, its own listing view, its own filters.
Custom design versus a template
Customising an off-the-shelf theme is cheaper to start and more expensive to live with. A custom design costs more up front but gives you a site that looks like your company and whose content you can manage without fighting for every change.
We build custom themes and blocks rather than buying templates. In practice that means the site doesn't accumulate dozens of third-party plugins whose updates start breaking each other a year later.
Content - who writes it, and when
Content is the most common cost driver that goes unaccounted for at the start of a project. If the text and images come from the client, that work is free, but it affects the timeline. If copy is commissioned, it's a separate line in the budget.
The most expensive version is the one where content is written during the build and the structure changes several times as a result.
More than one language
A second language doesn't double the price, but it isn't free either. It adds translation management, per-language URLs, menus, forms and SEO configuration. A third language costs considerably less than the second, because the structure already exists.
Integrations
Every interface to another system is a project within the project. A booking system, a CRM, accounting software, a listings feed - each needs mapping, building, testing and error handling.
What affects the cost of an integration most is the quality of the other side's API. A well-documented interface is quick; a poorly documented or absent one means most of the time goes into working out how to get at the data at all.
Where it's sensible to save
- Start smaller. The first version doesn't have to contain everything. Publishing a solid five-page site and adding a blog three months later beats delaying launch by six months.
- Use repeating blocks. If pages are built from the same blocks, new pages can be made without a developer.
- Prepare content earlier. Having the content ready before design starts shortens a project more than any technical decision.
- Decide the integrations up front. Adding one later is almost always more expensive than accounting for it from the beginning.
Where it is not worth saving: hosting, backups and maintenance. They are the cheapest part of a project and the most expensive place to economise.
How we quote
We give a fixed quote once the structure and the required features are agreed. That usually means one working session and a short document listing the pages, content types, integrations and languages.
That step takes a couple of days and prevents the situation where, halfway through, it turns out half the project was never agreed. If the scope changes later, it's clear what changed and what it costs.
What you need to get a quote
A goal and a short description are enough to start: what the site has to do, who it is for and when it should be live. Existing content, your logo and brand files, and a few examples of sites you like all help.
If you already have a site
If your question isn't "what does a new site cost" but "why isn't the current one bringing anything in", a diagnosis is worth more than a price list. The website health check is a fixed-price €390 review that tells you what's holding the site back — and the list it produces is usable with or without us.