Pricing guide for EU public sector websites and digital tools
For EU public sector organisations, pricing a website or digital tool is rarely straightforward. A simple brochure-style site may sit at the lower end of the range, while a service portal, consultation platform or accessibility-focused rebuild will cost more. As a practical guide, many small to medium projects fall somewhere between €1,500 and €8,000. That range is broad because public sector work has requirements that do not usually apply in the private sector to the same degree: accessibility, multilingual content, procurement rules, governance, security, privacy and long-term maintainability.
This guide explains what typically affects cost, what you can reasonably expect at different budget levels, and why a so-called free solution often becomes more expensive over time.
Why there is such a wide price range
Two projects can both be described as “a website”, yet require very different amounts of work. A basic information site for a small initiative is not the same as a website for a municipality, agency, university department or EU-funded programme with multiple stakeholders and formal compliance needs.
In public sector settings, cost is shaped less by visual design alone and more by the effort needed to make the result usable, compliant, secure and manageable. A lower-cost project may rely on an existing design system, a limited page count and standard functionality. A higher-cost project may involve structured content planning, migration, integrations, accessibility remediation, multilingual workflows and staff training.
Typical price bands: €1,500 to €8,000
€1,500 to €2,500: small and straightforward projects
At this level, the project is usually tightly defined. It may include a small website or microsite using an established template, a limited number of page layouts and standard content components.
- Suitable for: campaign microsites, pilot projects, simple information websites, landing pages for funded initiatives
- Usually includes: setup, basic design customisation, core pages, contact form, mobile responsiveness, essential accessibility good practice
- Usually excludes: complex integrations, advanced user roles, large-scale content migration, bespoke functionality, extensive workshops
This budget works best when content is ready, decision-making is quick and the organisation can work within a standard structure.
€2,500 to €5,000: standard public sector websites
This is often the most realistic range for a well-built small to medium public sector website. It allows for more planning, stronger accessibility work, clearer information architecture and some tailored functionality.
- Suitable for: local authority departments, public initiatives, research projects, institutional sub-sites, service information websites
- Usually includes: discovery, page templates, navigation planning, content support, accessibility checks, cookie/privacy setup, basic multilingual structure, editor training
- May include: events, news, document libraries, staff profiles, searchable content, embedded maps or forms
For many organisations, this range provides a sensible balance between affordability and quality. It supports a site that is not only launched properly, but can also be maintained without unnecessary friction.
€5,000 to €8,000: more complex or compliance-heavy projects
At the upper end of this range, the project typically involves more stakeholders, more content, more languages or more technical constraints. The additional cost reflects the time needed to reduce risk and produce a robust result.
- Suitable for: service portals, larger institutional websites, accessibility-led rebuilds, multi-stakeholder projects, sites with specialist workflows
- Usually includes: workshops, detailed planning, custom components, content migration support, multilingual implementation, stronger governance, advanced accessibility review, integration work and more extensive testing
- May include: CRM or database integrations, consultation tools, searchable publication repositories, complex forms, role-based editing workflows
While €8,000 is still modest for many digital projects, it can deliver a solid public sector website or tool when scope is carefully managed.
What affects cost
1. Scope and complexity
The clearest cost driver is the amount of work involved. A site with five pages and one contact form is not comparable to a site with 80 pages, news, events, publications, search filters and multiple user journeys.
Complexity often comes from combinations of features rather than any single feature on its own. For example, a document library becomes more expensive when documents need tagging, filtering, multilingual metadata and accessible file handling.
2. Accessibility requirements
Accessibility is not an optional extra for public sector organisations. Compliance with recognised standards such as WCAG affects design, development, content structure, forms, navigation, documents and testing.
Projects cost more when accessibility is taken seriously because it requires specialist work: semantic markup, keyboard navigation, contrast checking, focus states, error handling, heading structures, alt text guidance and testing with assistive technologies or audit tools.
That said, accessibility done properly from the start is far cheaper than retrofitting it later.
3. Content volume and content quality
Content is often underestimated in project budgets. If the organisation already has clear, well-structured, up-to-date content, costs stay lower. If content is scattered across PDFs, outdated pages, shared drives and different departments, the project takes longer.
Costs rise when a supplier needs to help with:
- content audits
- rewriting for web use
- plain English editing
- migration from an old system
- document restructuring
- metadata and taxonomy planning
In public sector work, content governance matters as much as content creation. If nobody knows who owns which pages, the website becomes expensive to maintain very quickly.
4. Multilingual needs
Many EU public sector organisations need content in more than one language. Even a simple bilingual site adds planning and technical overhead. Navigation, templates, URLs, language switching, editorial workflows and content updates all need to be managed properly.
The cost impact depends on whether the site is fully multilingual, partly translated or structured to support future language expansion.
5. Design approach
A project based on an existing design system or template will cost less than a fully bespoke design. That is not necessarily a disadvantage. For many public sector organisations, a well-chosen design system improves consistency, accessibility and maintainability.
Costs increase when there is a need for:
- custom visual identity work
- multiple homepage concepts
- bespoke interface components
- extensive stakeholder review cycles
- specialist user journey design
In practice, the most cost-effective approach is often not “the cheapest design”, but the design approach that creates the least friction for users and editors.
6. Integrations and functionality
Standard features such as forms, news or document downloads are usually predictable. Costs rise when the website or tool needs to connect with external systems, such as CRMs, event tools, identity systems, consultation platforms or internal databases.
Integrations are expensive because they require technical discovery, testing, error handling, security review and ongoing maintenance. Even when an external service offers an API, implementation is rarely plug-and-play.
7. Security, privacy and hosting requirements
Public sector organisations often have stricter expectations around hosting, data processing, retention and supplier accountability. If a project involves personal data, user accounts or third-party services, privacy and security work will affect the budget.
This can include:
- cookie and consent configuration
- privacy-friendly analytics
- secure form handling
- hosting arrangements
- backup and update procedures
- data processing documentation
These are not glamorous line items, but they are essential.
8. Governance, meetings and approvals
Public sector projects often involve more people in the review process. Procurement staff, communications teams, policy owners, legal colleagues, accessibility leads and external partners may all need input. The more approval layers there are, the more project management time is required.
This is one reason why two technically similar projects can have very different costs.
9. Training and handover
A website is not finished when it goes live. Editors need to know how to use it correctly. If training, documentation and post-launch support are included, the project cost will be higher, but the organisation is more likely to manage the site well over time.
Why “free” is expensive in the long term
Free website builders, donated themes, no-cost plugins and internally improvised solutions can appear attractive, especially when budgets are tight. The problem is that free usually means the real costs are hidden elsewhere.
Free tools often cost staff time
If a platform is difficult to manage, staff spend more time fighting the system. That time has a real cost. Editors may duplicate work, struggle with formatting, upload inaccessible PDFs because the CMS is awkward, or rely on one technically confident colleague to keep everything running.
Free solutions often create accessibility debt
Many low-cost or free themes and builders are not designed with public sector accessibility obligations in mind. They may look acceptable at first glance, but fail on keyboard use, heading structure, contrast, focus indicators or form behaviour. Fixing these problems later is often more expensive than building properly from the start.
Free tools can lock you in
A no-cost platform may limit export options, customisation or hosting control. Over time, the organisation becomes dependent on a tool that no longer fits its needs. Migration then becomes a larger, more expensive project.
Free products may rely on risky third parties
Some free plugins or templates are poorly maintained. Others disappear, introduce security issues or stop being compatible with the rest of the system. The short-term saving can lead to long-term instability.
Free rarely includes accountability
Public sector organisations need reliable support, clear responsibilities and documented processes. A free tool does not usually come with meaningful service levels, accessibility support or strategic guidance. When something breaks, the organisation carries the risk.
How to get better value from your budget
Define the minimum viable scope
Start with what users actually need. Not every feature belongs in phase one. A smaller, well-executed launch is usually better than a larger, fragile project.
Use proven components where possible
Templates, design systems and established content models reduce cost and risk. Bespoke work should be reserved for genuine needs, not preferences.
Prepare content early
Clear ownership, structured drafts and realistic page counts make projects more efficient. Content delays are one of the most common reasons for cost overruns.
Budget for maintenance, not just launch
A cheaper launch can become expensive if updates, support and governance are ignored. It is better to plan for sustainable ownership from the outset.
Final thoughts
For EU public sector websites and digital tools, a budget of €1,500 to €8,000 can cover a wide range of outcomes. The lower end suits small, tightly scoped projects. The middle range is often appropriate for standard institutional websites. The upper end supports more complex, multilingual or compliance-heavy work.
The key point is that cost should be judged against long-term usefulness, not just launch-day appearance. A good public sector website is accessible, maintainable, secure and clear for users. A free or ultra-cheap solution may seem efficient at first, but if it creates accessibility problems, governance issues, technical debt or staff frustration, it is not truly low-cost.
The most economical choice is usually the one that remains workable over time.