The make-or-buy decision determines whether you develop custom code or use existing modules and services. In Drupal projects, this applies to every feature: custom module or contrib module, own server or managed hosting. Since 2012, arocom has made these decisions data-driven — with the principle: contrib where possible, custom where necessary. Every custom development generates maintenance costs that accumulate over years.
A vibrant outdoor market stall showcasing handcrafted textiles, baskets, and decor items under a canopy. — Make or Buy: Eigen- vs. Standardloesung

Make or Buy: Custom Development vs. Standard Solution

Last updated: March 2026 · Reading time: 4 minutes

"We'll build it ourselves" sounds like control and independence. In reality, every line of custom code means long-term maintenance responsibility. The make-or-buy decision is one of the most important in any web project.

When to Make, When to Buy?

Make (custom development) pays off when the requirement is unique, no suitable contrib module exists and the functionality represents a competitive advantage.

Buy (standard solution) is the better choice when an established contrib module covers the requirement, an active community maintains the module and security updates appear promptly.

In the Drupal world, "buy" doesn't necessarily mean license costs. Contrib modules are open source. The costs lie in integration and configuration — but not in maintaining the source code.

Consider Total Cost of Ownership

Development costs are only part of the equation. Custom modules must be checked and adapted with every Drupal update. Security patches must be written by you. Documentation and onboarding new developers cost additionally.

arocom recommends an honest TCO calculation over at least three years. Often a contrib module with minor adjustments is cheaper than custom development — even if it appears more expensive in initial effort.

Your next step

Facing a make-or-buy decision? The Drupal Future Check evaluates your existing code base and identifies custom modules that can be replaced by contrib.

How does arocom decide between custom and contrib?

We first check whether a maintained contrib module exists. If yes, we use it. We write custom code only when the requirement is truly unique or no suitable module exists.

What happens with custom modules during a Drupal upgrade?

Custom modules must be manually adjusted with every major upgrade. This is effort that the community bears for contrib modules. Therefore: the less custom code, the cheaper the upgrades.

Read more

Discover a random article

Digital Strategy: ...
Commission Models ...
Stakeholder Analys...
Lead Generation wi...
Password Security:...
UI Design: Interfa...
Project Management...
Planning a Website...

Questions about this topic? We'd love to help.

Free · PDF document

CMS Comparison 2025

Drupal vs. WordPress vs. TYPO3: An objective comparison for enterprise projects.

Was this article helpful?