What sets the cost of a Drupal project
A project's cost follows from its scope: the content and data it holds, the systems it connects to, the roles and languages it serves, and how long it has to be maintained after launch. A public-sector site adds drivers of its own, such as accessibility that has to be evidenced, multilingual publishing, legacy systems that stay in place, and procurement.
Articles on cost and pricing
We build your product for 10% of the development price
How WeebPal's investment model reduces a product's upfront development payment in exchange for a minority equity stake.
How much does a government website cost?
How accessibility, multilingual delivery, legacy integration, procurement, and governance shape the budget for a government website.
How much does a Drupal website cost?
A practical breakdown of Drupal project cost bands and the architecture, integrations, migration, roles, and uncertainty that move a budget.
Project sizes and where the prices are
We place a project in one of these sizes, from a basic website to a mission-critical ecosystem:
- Micro: basic informational website
- Small: professional corporate website
- Medium: advanced digital experience
- Large: complex content or transaction platform
- Extra Large: secure portal or intranet
- Enterprise: integrated workflow application
- Multi-Entity: enterprise multisite or institutional platform
- Strategic: mission-critical digital ecosystem
The price, timeframe and delivery process for each size are on the pricing page.
How we run this work
Before a build project is signed, we build a prototype at no charge: a design, a clickable prototype or a working demo on real code, so you decide against something real. The build is then quoted at a fixed price against a written scope, and that price moves only if the scope does. Development work carries our warranty: one year by default, up to three. Keeping the site current after that is a separate maintenance agreement.
- Pricing: the project sizes, the rate card and maintenance.
- Why you own the source code: what you receive at handover, and what that means for whoever maintains the site next.
- Tell us about your project.