Custom Drupal 10 and 11 modules, scoped and priced before we start. Contrib-first, so we only build what genuinely needs building.
Base scope of work — applies to all tiers. See the tier comparison below for hours and SLA specifics.
What the module does, how it is configured, and where it sits in the site, agreed before we write code so the scope is a real number.
Written to drupal.org coding standards on Drupal 10 or 11, in your repository, owned by you with no license strings attached.
Tests that cover the module's behavior so the next developer can change it without guessing what they might break.
A short, plain doc covering what the module does and how it is set up. No archaeology required when you hand it to someone else.
Transparent process — you always know what stage we're at and what comes next.
A short call to pin down what the module must do and what it talks to. We check the contrib list here, then write a fixed spec. Deliverable: signed brief and price.
The module is written and wired up on a staging copy of your site, never the live one. You see progress on a real environment, not screenshots.
Automated tests written, code reviewed against Drupal standards, edge cases checked. Nothing ships that we would not put on our own site.
We deploy to production, hand over the code and docs, and walk your team through how it is configured.
Pick the level that fits your size and required response time. You can switch tiers between months.
One focused module with a clear spec: a custom block, a tailored content workflow, a small admin tool. Built, tested, documented.
A module that talks to an outside system: payment gateway, CRM, ERP, or shipping API, with queues, cron, and real error handling.
Several related modules, custom entities, and their own admin screens. The scope is set by a discovery phase before a fixed quote.
Scope transparency — no surprises in the monthly report.
Access we require — passed via secure channel (1Password / Bitwarden).
Our brackets are around $2,500 for a single focused module, $8,000 for an integration module that talks to an outside system, and $20,000 and up for a multi-module build with custom entities. Price tracks complexity and integration risk, not the number of lines. We quote a fixed number after a short discovery call.
We check the contrib list before quoting any build. Drupal has thousands of community modules, and many requests are already solved by Webform, Paragraphs, Views, or similar. If a stable contrib module does the job, we tell you, and it becomes a configuration task instead of a development project. We write custom code only when there is a real reason: an integration, business logic no module models, or a performance problem.
Drupal 10 and 11. We do not write new custom modules for Drupal 7, which lost security support in January 2025. If you are on Drupal 7 and need new functionality, the right first step is a migration to a supported version, then the module on top of that.
Yes. The module lands in your repository and you own it outright, with no license that ties you to us. If the module is general enough and you agree, we may also contribute a version back to drupal.org, but anything specific to your business stays private.
Every module ships with automated tests. That is not a nice-to-have. Tests are how the next developer changes the module without breaking it, and they are how we keep the 30-day warranty honest.
Usually, yes. We start by reading the existing code and telling you whether it is worth extending or cheaper to rebuild. Either way you get an honest read before any work, not a reflexive ‘rewrite everything’ quote.
Search “Drupal module development” and you get tutorials. The drupal.org docs, a Zend guide, a few YouTube courses, all teaching you to write a module yourself. Useful if you have a developer with a free month. Not useful if you have a business that needs a feature shipped and tested. This page is the other half of the conversation: what it costs to have us build a Drupal module, how we scope it, and the times we tell you not to build one at all.
Drupal has thousands of community modules, and a fair number of “custom module” requests we get are already solved by something on drupal.org. Webform covers most form logic. Paragraphs handles flexible content. Views does more reporting than people expect. So the first thing we do is check whether the thing you want already exists, configured, free, and maintained by people other than us.
That costs us a quote sometimes. We are fine with it. A contrib module you configure is cheaper to build and cheaper to live with than custom code only we understand. We write custom modules when there is a real reason: a third-party system to integrate, business logic no contrib module models, a performance problem a generic module cannot solve. If a stable contrib module does the job, we will tell you, and the bill will be an afternoon of configuration instead of a development project.
A custom module from us is not a zip of code that works on the developer’s laptop and nowhere else. Every build ships with the module written to drupal.org coding standards, automated tests so the next person can change it safely, a short doc on what it does and how it is configured, and a code review before anything touches your production site. You own all of it. We work on Drupal 10 and 11, on a staging copy of your site, never directly on the live one.
Module work splits into three rough buckets, and the price tracks complexity, not line count. A focused single module with a clear spec is the small end. An integration module that talks to a payment gateway, a CRM, or a shipping API, with queues and cron and error handling, is the middle. A set of related modules with custom entities and their own admin screens is the large end. We quote a fixed number after a short discovery call, so you are not signing a blank check tied to hourly billing.
Two cases come up often. First, when the request is really a configuration job dressed up as development, which we cover above. Second, when the site itself is the problem. If you are sitting on a Drupal 7 install asking for a new module, the module is not your real issue. Drupal 7 lost security support in January 2025, so new custom code on it is building on a foundation nobody is patching. In that situation we point you at a Drupal migration first, and the module comes after, on a version that will still be supported next year.
If you already know which contrib modules you want and just need them installed and configured well, that is closer to our Drupal support work than a development project, and it is priced very differently.
When a module we build for you is general enough to help other people, and you are happy for us to release it, we contribute it to drupal.org. That is good for the ecosystem we all depend on, and it means a wider set of developers can read and fix the code later. Anything specific to your business stays private. You decide which bucket a given module falls in.
Tell us what the module needs to do and what it has to talk to. We will tell you whether it should be custom code or a contrib module you already have access to, and give you a fixed price either way.
30-day warranty on the module we shipped. Any bug in our code, we fix it without a separate invoice.
