On this page
- 01The short answer
- 02Define what the website must do
- 03Separate the workstreams that create the website
- 04Choose a commercial model suited to uncertainty
- 05Find costs that appear late in weak proposals
- 06Compare outcomes, responsibilities and assumptions
- 07Provide enough information for a useful estimate
- 08Budget beyond launch
- 09Frequently asked questions
A website has no responsible universal price because ‘website’ can mean a template-based brochure or a multilingual digital product with original content, integrations and migration. The useful estimate separates discovery, content, design, development, technology, launch and ongoing ownership, with assumptions and exclusions stated clearly.
Two quotes for ten pages may describe different products. One may reuse supplied copy and a theme; another may include customer research, information architecture, writing, a component system, CMS modelling, redirects, analytics and quality assurance. Comparing totals before scope creates false precision.
For strategy, UX/UI design, development and CMS implementation as one project, see Qreativa’s web design and development service.
Purpose
Audience, business role, journeys and measurable outcomes.
Content
Structure, writing, media, migration and governance.
System
Design, components, CMS, integrations and accessibility.
Ownership
Testing, launch, maintenance, hosting and future change.
Define what the website must do
| Type | Primary job | Complexity often comes from |
|---|---|---|
| Marketing website | Explain the business and generate relevant action | Positioning, content, services, proof and conversion paths |
| Editorial or SEO platform | Publish and organise substantial expertise | Taxonomy, templates, migration, search and governance |
| Ecommerce | Support product discovery, purchase and service | Catalogue, checkout, feeds, logistics, accounts and compliance |
| Portal or web application | Enable tasks for known users | Roles, workflows, data, states, security and integrations |
| Multilingual website | Serve markets with appropriate language and structure | Localization, hreflang, governance and regional content |
If the requirement is one campaign-specific conversion journey, compare the scope with a landing page rather than a full website.
Separate the workstreams that create the website
Discovery
Stakeholder, audience, analytics and technical review; goals and requirements.
Content architecture
Sitemap, journeys, page roles, content model and internal linking.
Content production
Research, copywriting, editing, photography, video and localization.
UX and visual design
Wireframes, interface direction, components, responsive states and accessibility.
Development
Frontend, CMS, integrations, forms, performance and quality assurance.
Launch
Migration, redirects, analytics, domains, training and post-launch checks.
Choose a commercial model suited to uncertainty
| Model | Useful when | Risk to manage |
|---|---|---|
| Fixed project fee | Scope, assumptions and acceptance criteria are stable | Changes become disputes when discovery was skipped |
| Time and materials | Requirements are evolving or technically uncertain | Budget needs checkpoints and transparent priorities |
| Paid discovery then build | The problem needs definition before a credible estimate | Discovery outputs and decision rights must be clear |
| Ongoing product team | The website changes continuously after launch | Capacity, roadmap ownership and service levels need definition |
A fixed price can be valuable when the work is understood. It becomes expensive when suppliers add a risk margin for ambiguous requirements or exclude essential work to keep the headline low. A short discovery phase can replace hidden contingency with evidence.
Compare outcomes, responsibilities and assumptions
Normalise scope
Create one list of required work and mark each quote included, excluded or unclear.
Inspect the team
Identify who leads strategy, content, design, development and quality.
Review change rules
Understand revisions, approvals, new requirements and schedule effects.
Check ownership
Confirm accounts, code, editable files, content, licences and handover.
Ask for examples that resemble the project’s complexity, not merely its visual style. A beautiful portfolio does not prove migration discipline, CMS quality or integration capability. A long technology list does not prove clear user journeys or persuasive content.
Provide enough information for a useful estimate
Include in the brief
- Business objective and priority audiences
- Current website, analytics and known problems
- Required journeys, functions and integrations
- Languages, markets and accessibility expectations
- Approximate content inventory and migration needs
- Brand, copy, media and approval responsibilities
- Technology or security constraints
- Target dates and the event behind them
- Budget range if it affects the viable approach
Budget beyond launch
| Ongoing area | Examples | Planning question |
|---|---|---|
| Infrastructure | Hosting, domains, CDN, monitoring and backups | Who owns accounts and responds to failure? |
| Maintenance | Security, dependencies, browser changes and fixes | What is preventive and what is billable? |
| Content | New pages, media, localization and governance | Can the team publish safely without developers? |
| Improvement | Research, analytics, testing and performance | Who owns the roadmap after launch? |
| Third parties | CMS, forms, consent, search and integrations | Which fees rise with traffic, seats or usage? |
A cheaper build can create a higher three-year cost if routine changes require specialists, licences multiply or the system is difficult to maintain. Evaluate flexibility, documentation and operational ownership alongside launch price.
These two worked estimates use hypothetical European costs. They show the calculation method; they are not market averages or Qreativa quotes. VAT, ecommerce, original photography, translation and paid media are excluded.
| Scenario | Initial build | Annual ownership | Three-year total |
|---|---|---|---|
| Focused marketing website | Discovery €1,200 + content €3,200 + design €2,400 + development €4,200 + QA and launch €900 + setup €1,000 = €12,900 | Hosting and software €720 + maintenance and improvements €1,800 = €2,520 | €12,900 + (€2,520 × 3) = €20,460 |
| Structured content platform | Discovery €3,000 + architecture and content €8,000 + design €5,500 + CMS development €12,000 + migration €3,800 + QA and launch €2,500 = €34,800 | Infrastructure and software €1,800 + maintenance and content improvement €5,400 = €7,200 | €34,800 + (€7,200 × 3) = €56,400 |
Website cost FAQs
How much does a small business website cost?
It depends on the site’s job, content, templates, integrations and who supplies each input. A simple site using existing brand and copy is different from a strategic redesign with research, original content, CMS modelling and migration. Request an itemised scope instead of relying on a generic average.
Why do website quotes vary so much?
Quotes may include very different levels of strategy, content, custom design, development, migration, testing and post-launch support. Suppliers also price risk differently when requirements are unclear. Compare responsibilities and assumptions before totals.
Is a template website always cheaper?
It can reduce design and development effort when the requirements fit the template. Costs rise when the template needs heavy modification, content does not fit, performance is weak or licences and maintenance accumulate. Suitability matters more than the label.
Does website cost include copywriting and SEO?
Not automatically. Some projects include research, copy, information architecture, on-page SEO, redirects and structured data; others expect final content from the client. The proposal should assign every responsibility explicitly.
What ongoing website costs should be expected?
Typical costs include domain, hosting, software licences, maintenance, monitoring, backups, support, content updates, analytics and future improvements. The exact mix depends on the platform, integrations, traffic and internal capability.
How can website project costs be controlled?
Clarify outcomes and requirements early, complete discovery before committing to uncertain features, prioritise reusable templates, assign content ownership, set approval deadlines and use change control. Preserve a contingency for genuine unknowns rather than hiding them.
Michele Eccher


