Scope: pages, templates and languages
The number of pages matters less than the number of different page types. Twenty service pages built from one well-designed template cost less than eight pages that each need their own layout. When you plan a business website, list the page types first: home, service, case or product, article, contact, legal pages. This list is the first step of business website development.
Each extra language adds more than translated text. Each version needs its own navigation, metadata, forms and checks, and someone has to keep the versions in step after launch. A second language is often worth it, but it should be planned as a version of the site, not as a translation added at the end.
Write down what the site must do on day one and what can wait. A clear first release with a list of later improvements is usually cheaper and faster than trying to launch everything at once.
Content, design and integrations
Content is the most underestimated part of the budget. Someone has to write or edit the texts, collect facts about your services, prepare images and agree everything with the people who know the business. If texts are not ready, the design is built around placeholders and has to be adjusted later.
Design work ranges from adapting an existing visual style to creating one from scratch, with a component library and versions for different screens. Both are valid choices; they simply cost differently. Ask what exactly is included: page layouts only, or also states such as errors, empty lists and mobile menus.
Integrations often decide the complexity. Sending a form by email is simple; passing enquiries to a CRM with deduplication and a fallback when the CRM is down is a separate system integration project. The same is true for payments, booking, customer accounts and data imports.
After launch: hosting, support and changes
A website keeps costing something after launch: hosting, domain, updates of the platform and its plugins, backups and small content changes. Agree in advance who does what, how quickly urgent problems are handled and how changes are requested and estimated.
The choice of platform affects these running costs. A site your team can edit on its own saves money on every small change; a custom feature saves time every day if it matches how you work. Compare the total over a year or two, not only the cost of building.
To get a quote that reflects your situation, describe the goal of the site, the page types, languages, integrations and the state of the content. The more of this you send with the website project brief, the fewer assumptions end up in the estimate.
What changes the scope
| Factor | Smaller scope | Larger scope |
|---|---|---|
| Pages and templates | A few page types, one language | Many page types, several languages |
| Content | You supply the final texts | Texts, photos and translation are part of the project |
| Integrations | The form sends an email | CRM, payments, booking, customer accounts |
| After launch | Your team updates the site | Ongoing support and changes |
Checklist: before you ask for a quote
- List the page types and the languages the site needs.
- Separate what must be ready at launch from later improvements.
- Decide who writes and approves the texts and images.
- Name every integration: CRM, payments, booking, analytics.
- Agree who maintains the site after launch and how changes are requested.
Example: one request, two very different sites
A service company asks for “a simple website with five pages”. During the brief it turns out that every service needs its own page, the site must exist in two languages and enquiries should go straight to the CRM used by the sales team.
The “five pages” become two templates, two language versions and one integration with error handling. Neither version is wrong, but they cannot share one quote. Clarifying this before development saves both sides from a difficult conversation later.
Common mistakes
- Comparing final figures only. Two quotes can describe different sites. Compare page types, languages, content work and integrations line by line before comparing totals.
- Counting pages instead of templates. The number of distinct layouts drives the work far more than the number of pages built from them.
- Leaving content until the end. If texts and images arrive after the design, the layout is built around placeholders and has to be reworked.
- Forgetting the running costs. Hosting, updates, backups and small changes continue after launch. Agree who handles them before you sign off the build.
- Adding a language as a translation. Each language version needs its own navigation, metadata, forms and checks, and someone to keep it in step.
Questions
How much does a business website cost?
It depends on the factors in the table above: the number of page types and languages, who prepares the content, which integrations are needed and who maintains the site afterwards. A fair estimate is possible only once these are known, which is why we send a quote in EUR after reading your website project brief.
Why do quotes for the same website differ so much?
Usually because each team has filled the gaps in the request with its own assumptions. One quote may include content writing, a second language and a CRM integration; another may cover a template and nothing else. Ask each supplier to list what is included and what is not, and the difference will usually explain itself.
What is usually left out of a quote?
Content preparation, image licences, translation, analytics setup, redirects from an old site, testing on real devices and support after launch are the items most often missing. None of them is optional for a working site, so check whether each one is covered and, if not, who will do it.
Is a template site cheaper in the long run?
Often it is cheaper to build, and it can stay cheaper if the template fits your content and your team can edit it easily. It becomes expensive when the business outgrows it: unusual page types, integrations or plugins that conflict after updates. Compare the total over a year or two, not only the first invoice.
