Drupal is not expensive or cheap — it sits at four quite different price points depending on how much of the work is configuration and how much is code, and knowing which band you are in is the whole conversation.
The bands below are the ones the market broadly works to. They are not my quote for your project, and no two agencies draw the lines in the same place. What they are good for is working out whether the thing you want and the money you have are in the same band, which is where most disappointing projects go wrong.
The four bands
| Band | What it buys | What drives the cost |
|---|---|---|
| Around $3,000 | A small nonprofit or association site: standard content types, a configured theme, no custom code | Almost entirely configuration and content entry |
| Around $5,000 | A local business site with a real design and a few bespoke content types | Design, plus theme work on top of an existing base |
| $20,000 to $100,000 | The middle market: several content types with relationships, integrations, editorial workflow, custom front end | Content modelling and integration work |
| $100,000 and up | Enterprise: multi-site, multi-language, decoupled front ends, procurement and accessibility compliance | Governance, testing, and everything that is not the build |
The interesting boundary is the third row. Below it, Drupal is configuration work and the price is driven by design and content. Above it, you are buying software development. Projects that fail usually wanted row three and budgeted for row two.
Why Drupal reaches down to the low bands at all
Not long ago the honest advice to a $3,000 nonprofit was "use something else". Two things changed that, and neither is marketing.
Recipes are in core. On Drupal 11.4.6 there are 28 recipes in core/recipes/, and a recipe installs modules and imports configuration together — a content type arrives complete with its fields, view modes and permissions. Work that used to be an afternoon of clicking is now one operation, and that time comes straight off a small project's estimate.
Layout Builder is stable in core. Editors compose pages without a developer, which removes the recurring small-change requests that used to make low-budget clients uneconomic to serve.
Both of these are core features. Neither requires a distribution or a paid product.
What enterprise budgets pay for that everyone else gets free
This is the part worth understanding if you are at the small end, because it is the actual argument for choosing Drupal on a modest budget.
When a government department funds accessibility work, it lands in core and every site gets it. When a university system funds a content workflow improvement, that improvement is in the next release for everyone. The Symfony architecture, the configuration system, the caching layer, JSON:API — these were built to enterprise requirements, and a $3,000 site runs on the same code.
You are not getting a cut-down edition. You are getting the same platform with fewer of its capabilities switched on, which is a genuinely different proposition from a tiered commercial product.
The cost nobody puts in the quote
Build cost is the number people compare. Running cost is the number that decides whether the project was a good idea.
Drupal has no unattended updates in core. In 11.4.6 the staging API package_manager is marked lifecycle: experimental and hidden: true, and the user-facing Automatic Updates module is contributed. So security patching is a line item: a managed host, a retainer, or a person on staff. On a $3,000 build, an unbudgeted maintenance obligation is the difference between a site that lasts five years and one that gets compromised in eighteen months.
Ask for it in writing in every quote. If it is not there, the quote is incomplete regardless of the number on it.
If you are still deciding whether Drupal is the right platform for the band you are in, the comparison against WordPress is the honest starting point — for the bottom band it genuinely might not be. And if you know you are in the middle band, Drupal services is where the scoping conversation starts.
How to place yourself in a band
- Count the content types and the relationships between them. One or two standalone types is the bottom band. Five types that reference each other is the middle.
- List the systems it must talk to. A CRM, a payment provider, a membership database — each integration is real development, and each moves you up.
- Decide who publishes. One person publishing directly is cheap. A draft-review-approve chain with roles is a workflow build.
- Decide about design. Configuring an existing theme and commissioning a bespoke design are different orders of magnitude.
- Name who maintains it, and price that. Twelve months of it, not one.
Common questions
Is Drupal more expensive than WordPress?
To start, usually. Over five years on a site with real complexity, often less, because the capability comes from configuration instead of a stack of commercial plugin renewals.
Can I build it myself to save money?
For the bottom band, plausibly — it is configuration work, and the learning curve is navigable. For the middle band, the learning time usually costs more than the build.
Why do quotes for the same brief vary so much?
Because briefs rarely specify the content model. Two agencies reading "a site with news and events" can be imagining projects an order of magnitude apart. Specify the model and the quotes converge.
Do I need enterprise hosting?
No. Drupal runs on ordinary PHP hosting that meets the PHP floor. Managed hosting buys you someone else owning updates and performance, which is often worth it, but it is not a technical requirement.
What is the cheapest honest Drupal project?
A standard content site on a configured theme with no custom code and no integrations. If someone quotes below that for something more complicated, the difference will surface later as change requests.
Next steps
Write down your content model before you talk to anyone — the list of things your site holds and how they relate. That one document does more to make quotes comparable than anything else you can do.
Then either read what a Drupal architect does if you are in the top two bands and need the model designed rather than described, or send me the model and I will tell you which band it lands in before you spend anything.