Call for web developers: New website for EEB

Back view of businessman sitting in front of laptop screen. Man typing on a modern laptop in an office. Young student typing on computer sitting at wooden table.

Deadline: 3 July 2026

The European Environmental Bureau is inviting proposals from qualified web development agencies to redesign and rebuild eeb.org. With hundreds of thousands of visitors each year, our website is central to how we communicate our work, engage our members, and connect with policymakers, journalists, funders and the public.

The new website will be user-centred, accessible, editorially sustainable, and built for the scale and diversity of our work, replacing a site that no longer fully reflects the EEB’s impact, personality or content output.

What we’re looking for

We’re seeking an agency with experience delivering WordPress websites for NGOs, membership organisations, advocacy bodies or public-interest entities. The scope includes discovery and strategic review, information architecture, UX and visual design, CMS development, integrations (including Salesforce compatibility), search and taxonomy, accessibility (WCAG 2.2 AA minimum), content migration, training and post-launch support.

Budget and timeline

The indicative budget range is €30,000–€60,000 (excluding VAT). The target launch date is March 2027, with work expected to begin in July or early August 2026.

How to apply

Submit your proposal by 3 July 2026, 23:59 CET to tenders@eeb.org, copying samantha.ibbott@eeb.org, andreas.budiman@eeb.org and christian.skrivervik@eeb.org.

Questions may be submitted by email before 1 July 2026. Responses to relevant questions will be published on this page.

The full tender document is available to download here.

Questions & Answers:

  •  
  • Proposals will be evaluated in accordance with the EEB Procurement Policy and awarded to the most economically advantageous tender, taking into account both quality and price. The evaluation will consider, among other factors: understanding of EEB’s objectives, audiences, requirements and organisational context; the quality, relevance and feasibility of the proposed approach and methodology; the relevant experience and expertise of the proposed team; project management arrangements, timeline and risk management measures; and budget and overall value for money. Where relevant and justified, the EEB may also take environmental and social responsibility aspects into account. The contract will not necessarily be awarded to the lowest-priced offer, but to the proposal that offers the best overall balance between quality, value for money and suitability for EEB’s needs
  • The indicative budget of EUR 30,000 to 60,000 is intended to cover the full scope of the project. As specified in the tender, we request a detailed budget breakdown by phase, including optional features, licensing, hosting, maintenance and post-launch support, so that all relevant cost components are clearly identified within the proposal.

We have not specified a requirement for length or format, but would appreciate concise, clear proposals at a reasonable length. We kindly ask that proposals be submitted as a single PDF document if possible.
Beyond standard pages and posts, the site uses a handful of custom content types and templates. Several editorial formats (such as news, press releases and events) are handled as posts differentiated by taxonomy, while publications have their own content type and template, and there are a number of page templates (e.g. work areas, staff and members). That said, while content types (news, press releases, jobs, etc) will remain we do not want our current websites structure to form the basis of the new one, it should be treated as reference only, not as a starting point for the structure, design or content model of the new site.

Yes, the current site uses a mix of page builders across different pages, including Elementor, WP Page Builder and Beaver Builder. This inconsistency is something we explicitly want to avoid as much as possible on the new website, in favour of a single, consistent and maintainable approach to page building and content editing.

The live site contains 153 pages, 1,173 posts and 1,489 publications. During the process we will work with teams to decide which legacy material is brought over to the new site. We will also integrate our news site (meta.eeb.org) as part of this.

We intend to migrate evergreen content and redirect high-value content, and to run a content audit during the project to retire or archive low-traffic and dated material. We are not committed to a full 1:1 migration. For our previous website, we created an archive site (archive.eeb.org), but this is not an ideal solution.

Yes, we intend to rewrite most of the website. Core navigational and evergreen pages will be rewritten and refreshed in-house by the communications team, and only a limited amount of archival content would carry over largely as-is.

No, the current site has no integration with Salesforce, but we would like to explore the opportunity for future integration.

No, for the same reason as above. There is currently no CRM sync, but this is something we would like to explore for the future.
We are open to exploring this option. However, as our staff are already well versed in WordPress, we would need to be presented with strong argumentation to move to Drupal, including how it would benefit the EEB and provide us with a website that is secure, accessible, and easy for us to update and maintain.
This is not a major priority for the website, but there is potential for certain pages to require translation. This will be project dependent.

Yes, though with varying skill levels. The EEB’s core web team consists of experienced website managers capable of maintaining the site. The EEB does not have any in-house developers.

Our logos (both EEB and New Leaf) and colour palette are locked, but beyond that we are open to a refresh. Our homepage was updated recently and could potentially serve as a basis for this. If you would like to propose a refresh, please include it in your proposal as an optional extra, with a separate budget.