Are High Costs Putting Drupal Projects Out of Reach?

Carlos Ospina has published a new opinion piece titled "We're Still Too Expensive, and We Should Talk About It", raising concerns about how the Drupal community structures and delivers its work. He argues that pricing, not complexity, is pushing potential projects away from Drupal.

Carlos acknowledges the community’s progress in lowering technical barriers through tools like Experience Builder, the IXP initiative, and expanded hosting options. But he believes the bigger issue is that Drupal services remain out of reach for many organizations. 

"We're pricing ourselves out of projects that should be perfect fits for Drupal," he writes.

He shares a conversation with a former client who questioned paying $160 per hour for routine updates. For Carlos, this highlights a deeper problem. Using senior-level expertise for basic tasks is costly for clients and unfulfilling for developers.

In response, Carlos has been experimenting with new delivery models. He describes how experienced architects can work alongside more affordable developers, whether in global markets like Colombia or through early-career talent pipelines such as IXP. This structure, he believes, can deliver quality results at lower cost without compromising value.

This approach reflects broader trends such as fractional teams, global collaboration, and smarter task allocation. Carlos suggests the real challenge may not be Drupal’s complexity but how teams are organized to deliver sustainable results.

He closes with a question to the community. How are you managing cost pressures in your projects? What is working, and what needs to change?

Read the full piece and join the conversation. Carlos is asking for input from across the Drupal community.