Skip to content
Drupal web development

Drupal web development with strategic direction

Strategic consulting for complex Drupal web projects: multisite, multilingual, heavy integrations, critical security. Before programming anything, we decide whether Drupal is really what your organization needs.

TL;DR

Elevam directs Drupal web development projects from strategic consulting, not from code. We define whether Drupal is the right CMS for the case, design architecture, SEO and GEO before development, and supervise the technical partner — own or external — throughout execution. We apply the proprietary CREF© framework. We work with organizations that need complex websites: industrial groups, business groups, institutions, media and foundations.

The problem

You've been recommended Drupal. Or you already have it.

You've been recommended Drupal. Or you already have it and are about to renew it. Or you're choosing between Drupal, WordPress and custom development and you don't quite see which suits you.

You've met with two Drupal agencies. Both tell you the same thing: that Drupal is flexible, secure, scalable, perfect for your case. Of course: they live off programming Drupal. The presentations are technically impeccable. They show you modules, talk to you about Twig, about versions, about open source community.

And yet you leave with the same unanswered question: is this €40, €80 or €200 thousand investment going to be inside or outside your income statement in three years? Do you really need Drupal's complexity, or are you paying for a tool designed for your neighbor's case?

The problem isn't Drupal. Drupal is an excellent technical option for the projects it's designed for. The problem is that no one at the table has a business that doesn't depend on selling you Drupal.

This is where we come in.

What we do differently

Strategic direction of the Drupal project, not programming.

We apply CREF© — Consultoría de Crecimiento Elevam Framework — to the development of your Drupal website. We don't compete with Drupal agencies: we work above. CREF© connects each technical decision with three variables that defend the investment.

01

Real fit of Drupal with the case

Does the complexity that justifies Drupal exist in your organization, or are you paying for capabilities you won't use?

02

Total cost of ownership over 3 years

Development + maintenance + version upgrades + team needed to sustain it. Not just the initial project budget.

03

Business impact

Traffic, acquisition, authority, internal management, multilingual or multisite support, integration with critical systems — whatever has to move your organization has to be measurable.

We don't choose Drupal because it's sophisticated. We choose it when the sophistication is justified.

Work areas

Work areas on Drupal projects

Prior strategic diagnosis

Before any line of code. Analysis of the use case, content volume, governance model, critical integrations and available maintenance resources. Output: executive document with the CMS recommendation — Drupal, WordPress, headless, or custom development — and the business case that justifies it.

Information architecture and content model

Drupal's real strength is its capacity to model complex content: content types, taxonomies, views, panels, granular permissions, editorial flows. We design the model before development starts. A poorly designed model is what turns a 60K Drupal project into a 180K one two years later.

SEO and GEO on Drupal from day 1

Drupal is technically SEO friendly, but that doesn't mean Drupal websites rank by default. We design semantic architecture, content strategy, schema and GEO plan before development. We work the HSA Protocol and the Prompts × Models Matrix to ensure visibility on Google and in LLMs (ChatGPT, Claude, Gemini, Perplexity) from launch.

Multisite and multilingual

Two of the most legitimate reasons to choose Drupal. We design the multisite structure (central management?, independent brands?, hybrid model?) and the multilingual model (interface translation?, content translation?, i18n by region?) before configuring anything.

Security, accessibility and compliance

WCAG, GDPR, access controls, module audit, version upgrade plan. Drupal is secure if governed correctly. If not governed, it stops being so.

Project direction and technical supervision

We coordinate the Drupal partner — ours or yours. We validate sprints, review deliverables, ensure that what is built corresponds to what was designed. If your Drupal agency is good, we make sure it stays that way. If it isn't, we detect it early.

Maintenance and evolution plan

Drupal without a maintenance plan is Drupal abandoned in two years. We define the plan: upgrade cycle, security audits, evolution of the content model, version migration plan when due.

Cases

Real cases with verifiable metrics.

What we've done directing real projects. The cases are in public projects.

Why Elevam

Why Elevam and not a Drupal agency

We're not a Drupal agency. We don't bill Drupal programmer hours. And this changes three things that matter.

  • 01

    We have no CMS bias. A Drupal agency recommends Drupal. Always. We recommend Drupal when it's the right answer — and WordPress, headless or custom development when those are.

  • 02

    We work with general management or the investment committee. What we propose has to be approved in the board, not in a technical meeting with the CTO alone.

  • 03

    We have proprietary, published and auditable methodology. CREF©, HSA Protocol, Elevam Labs, Prompts × Models Matrix. If you want your trusted consultant to audit us, perfect. It's what we'd do in your place.

  • 04

    We integrate SEO and GEO from the architecture. A Drupal agency delivers a website «ready to optimize». We deliver it ready to rank on Google and in LLMs from day 1.

How we work

Four phases, no blind sprints.

  • 2-4 weeks

    CREF© diagnosis

    We analyze the case, information flows, integrations, internal resources and digital scenario. Deliverable: executive document with the CMS recommendation and the business case that backs it.

  • Before the first commit

    Strategic project plan

    Information architecture, content model, SEO/GEO plan, consolidated 3-year budget, team and governance plan. It's the document on which the investment is approved.

  • Implementation

    Execution under Elevam direction

    We coordinate the Drupal development partner — ours or yours. We validate sprints. We ensure that what is built corresponds to what was designed.

  • Post-launch

    Launch, maintenance and evolution (Elevam Labs)

    Maintenance plan, upgrade cycle, security audits and learnings applied from Elevam Labs, our internal R&D unit. We don't experiment on you: we experiment first.

Spokesperson
Asier López

Asier López

CEO and Founding Partner, Elevam
Drupal is an excellent tool when the decision is justified. And a very serious budget hole when it isn't. I've seen too many organizations invest €80, 120, 200 thousand in Drupal projects that didn't need that complexity. Elevam exists so that decision is made earlier with judgement, not later with an invoice.
FAQ

Frequently asked questions

What does a Drupal web development consultancy do?
A Drupal web development consultancy evaluates whether Drupal is the right CMS for the project, designs the information architecture, the content model and the SEO/GEO plan before development, and directs the technical team — own or external — during execution. Unlike a Drupal agency, it doesn't program: it directs and supervises. Elevam applies the proprietary CREF© framework to this work.
When is Drupal the best option versus WordPress or other CMS?
Drupal stands out when the project requires a complex content model, real multisite, deep multilingual, granular permission control, sophisticated editorial flows, integrations with critical systems or high security requirements (public sector, healthcare, financial, professional media). For standard corporate websites, blogs or conventional eCommerce, more efficient options usually exist.
Do you develop Drupal or just direct it?
Both are possible. We execute with trusted Drupal partners under our direction, or we direct the internal Drupal team or the agency the client already has. What we never do is bill Drupal development hours as our primary business: that would reintroduce bias into the initial recommendation.
How much does it cost to develop a website on Drupal?
The budget of a serious Drupal project for a medium-sized organization is typically between €40,000 and €250,000 of initial development, not counting maintenance or evolution. The range is enormous because it depends on the complexity of the content model, the number of sites/languages, integrations and security requirements. Before requesting quotes, it's worth defining the strategic scope: cheap without clear scope ends up being expensive two years later.
Is Drupal secure?
Yes, Drupal is one of the most secure CMS on the market when governed correctly: updates applied on time, audited modules, correct permission configuration and periodic reviews. Abandoned Drupal, on the other hand, is insecure Drupal. That's why the maintenance plan is part of the project, not an add-on.
Is Drupal SEO friendly?
Drupal has excellent technical capabilities for SEO: clean URLs, metadata control, schema, redirect management, XML sitemaps, advanced multilingual. But «SEO friendly» doesn't mean «automatic SEO». A Drupal website without an SEO/GEO strategy is still invisible on Google and in LLMs. That's why we design semantic architecture and GEO plan before development, not after.
How long does a Drupal project directed by Elevam last?
A Drupal project of medium-high complexity typically runs from 5 to 12 months from diagnosis to launch, depending on content model, integrations, multisite and multilingual. Anyone promising Drupal in 8 weeks is selling a template, not a project.
Do you offer Drupal website maintenance?
Yes. The maintenance plan is a structural part of the project, not an optional additional service: core and module upgrade cycle, security audits, content model evolution and version migration plan when the support cycle requires it. It's quoted specifically for each case.
What type of organization do you work with?
Industrial groups and business groups with multiple brands or regions, institutions, professional digital media, NGOs and professionalized foundations, administrations. Organizations whose website has real complexity — multisite, multilingual, high security, heavy integrations — and for which the CMS decision is strategic, not technical.
Before investing, validate

If you're going to invest in Drupal, let's ask the right question first.

Request your CREF© strategic evaluation

Initial 45-minute meeting, no cost, no commitment. We only continue if there's a fit.