Pricing

Drupal Development Pricing

Starting prices for each project size from Micro to Strategic, with the price fixed once the architecture is agreed, plus an hourly rate for each role and the monthly band for maintenance.

Tell us what you are building Book a short call

An engineer reads it and replies within one business day.

  • Nothing is due before you see it running
  • Warranty of 1 to 3 years inside the project price
  • Maintenance agreed monthly, with no lock-in
Micro Basic Informational Website A small, real piece of work. You judge us on what we deliver before trusting us with more. $1K+ 1–2 weeks

How we deliver a project this size

    1. 1

      Talk it through

      One call, fifteen to thirty minutes. You describe the site; we confirm a standard build covers it and quote on the spot.

    2. 2

      See it before you commit

      We build the home page and one inner template in your real theme. Nothing is invoiced to get here.

    3. 3

      Scope and start

      A one-page scope: page list, forms, languages. The fixed price attaches to that page. 50% starts the build.

    1. 4

      Build, with you watching

      Configuration-led, one pass. Staging URL from day one, moving weekly. We check browsers, phone, forms and contrast before you see it.

    2. 5

      Approve, launch, hand over

      You approve it on staging. We point DNS, issue SSL and go live on managed hosting, then hand over the repository and a recorded walkthrough.

    3. 6

      Warranty and what comes next

      One year, same developer, inside the price, with security releases applied during it. Other updates on a light monthly plan. New pages by the hour; model changes are re-quoted.

Included in the price

  • SEO and performance baseline at launch. Technical SEO setup, metadata and structured data, an XML sitemap, redirects from the old site, Search Console and analytics connected, and a Lighthouse target checked before launch.
Small Professional Corporate Website Content becomes reusable types rather than hand-built pages, and someone approves before anything goes live. $5K+ 1–2 months

How we deliver a project this size

    1. 1

      Talk it through

      A call and a short brief. We sketch the content model before quoting, because the model sets the price, not the page count.

    2. 2

      See it before you commit

      A clickable prototype of the main journeys, on the first cut of the design system. Navigation changes here, at our cost.

    3. 3

      Scope and start

      Content model and page inventory annexed to the contract. 50% starts the build, 50% at launch. Kick off names who approves copy.

    1. 4

      Build, with you watching

      Weekly increments on staging, each steered by your last review. The old site migrates in the same rhythm. A separate QA engineer runs the pass.

    2. 5

      Approve, launch, hand over

      We hand it over tested; you approve it on your own content against the page inventory. Cutover out of hours with every redirect applied. Editors trained by role.

    3. 6

      Warranty and what comes next

      One year on the build, including migration faults and security releases. Other updates and small fixes on a monthly agreement. New sections quoted as fixed packages.

Included in the price

  • SEO and performance baseline at launch. Technical SEO setup, metadata and structured data, an XML sitemap, redirects from the old site, Search Console and analytics connected, and a Lighthouse target checked before launch.
Medium Advanced Digital Experience Several markets and languages, with a translation workflow and per-market content behind them. $10K+ 2–4 months

How we deliver a project this size

    1. 1

      Analyze & Consulting

      A working session on markets and languages. We fix which market is the reference, because that drives translation, layout and approval.

    2. 2

      Proof of Concept

      Art direction, then the signature journey running with its real motion. Each market reviews before anything is contracted.

    3. 3

      Solution Design

      Design taken to sign-off, with translation workflow, hreflang and the reference market settled. The build price is fixed against it.

    1. 4

      Contract & Kick off

      Two contracts in sequence: design first, build fixed against the signed design. 30/40/30. Kick off names a contact per market.

    2. 5

      UI/UX Design

      Bespoke art direction and motion. Templates are proved against the longest translation, not the shortest.

    3. 6

      Build, demo and migrate

      Weekly demos, staging per branch. Translation workflow live early so content runs in parallel. Migration runs per language, rehearsed.

    1. 7

      QA, Security & Accessibility

      Every template in every language. Campaign rules against the rule table, hreflang per pair, performance on mid-range phones.

    2. 8

      UAT

      Each market's contact accepts their own market. Feedback is reconciled centrally, so one market cannot reopen an agreed direction.

    3. 9

      Deploy, stabilise and hand over

      Markets launch together or in sequence, decided before the window. Hreflang, redirects and analytics verified first. Handover covers design sources and the translation workflow.

    1. 10

      Warranty, maintenance and next phase

      One year, covering layout and translation faults in every market. Retainer for updates and campaign edits. A new market returns to Solution Design.

Included in the price

  • SEO and performance baseline at launch. Technical SEO setup, metadata and structured data, an XML sitemap, redirects from the old site, Search Console and analytics connected, and a Lighthouse target checked before launch.
Large Complex Content / Transaction Platform The platform now holds rules, not just content: search, staged approval, and two-way traffic with your systems of record. $30K+ 4–8 months

How we deliver a project this size

    1. 1

      Analyze & Consulting

      Working sessions rather than a single call, before any contract and at no charge. We model the content and data domain and write down the rules the platform must hold.

    2. 2

      Proof of Concept

      An architecture plus a working demo on real code: faceted search and one transactional path actually running.

    3. 3

      Solution Design

      Data model, search design, business rules, an integration contract per system of record, and the migration plan. The price commits against this.

    1. 4

      Contract & Kick off

      Contract against the architecture and migration plan. 30/40/30. A named change-control route for what discovery could not foresee.

    2. 5

      UI/UX Design

      The surfaces people act on: facets and results including empty and error states, transactional forms, and the editorial screens your staff live in.

    3. 6

      Build, demo and migrate

      Weekly demo on real data. Automated tests alongside the features. Migration runs from week one, so data problems surface early, not at cutover.

    1. 7

      QA, Security & Accessibility

      Regression on every commit across transactional paths and roles. Search tested at production volume. Load test. Keyboard and screen reader, not just a scanner.

    2. 8

      UAT

      We walk your product owner and each domain owner through their own role on migrated data, for approval. Defects and change requests are separated.

    3. 9

      Deploy, stabilise and hand over

      Cutover rehearsed on a copy; the rehearsal produces the runbook. A named rollback owner. The build team stays on after go-live.

    1. 10

      Warranty, maintenance and next phase

      One year, extendable to three, against what you signed off at UAT. Managed support is separate. New domains return to Solution Design.

Included in the price

  • SEO and performance baseline at launch. Technical SEO setup, metadata and structured data, an XML sitemap, redirects from the old site, Search Console and analytics connected, and a Lighthouse target checked before launch.
Extra Large Secure Portal / Intranet Everything sits behind a login. Roles decide what each person can reach, and the system records who opened what. $50K+ 6–10 months

How we deliver a project this size

    1. 1

      Analyze & Consulting

      Discovery on audiences, roles and what each may see. Your IT and information security are in the room from the first session.

    2. 2

      Proof of Concept

      A prototype of the authenticated experience, with single sign-on proven against a test tenant of your directory.

    3. 3

      Solution Design

      The role and permission matrix designed in full and validated against the real directory. The assurance gate is drafted as an acceptance condition.

    1. 4

      Contract & Kick off

      Permission matrix and assurance gate as contract annexes. 30/40/30. Kick off secures directory access and names who signs the gate.

    2. 5

      UI/UX Design

      Designed per role, because permission decides what exists on the page. Components built to WCAG 2.2 AA from the start.

    3. 6

      Build, demo and migrate

      Sprints against the permission matrix, demoed by signing in as each role. Documents and their permissions migrate together.

    1. 7

      QA, Security & Accessibility

      Auditors who did not build it. Structured security audit over the matrix, sessions and document access. WCAG 2.2 AA audit, remediated and re-tested.

    2. 8

      UAT

      Each role is approved by the person who holds it, signing in through your own identity provider. Information security accepts the findings alongside business sign-off.

    3. 9

      Deploy, stabilise and hand over

      Identity moves from test tenant to production directory, rehearsed with your IT. Logging and alerting on before users arrive. The team stays through the first real sign-ins.

    1. 10

      Warranty, maintenance and next phase

      One year, patches applied on release. Covers access-control defects and the audited WCAG baseline. Matrix changes return to Solution Design.

Included in the price

  • SEO and performance baseline at launch. Technical SEO setup, metadata and structured data, an XML sitemap, redirects from the old site, Search Console and analytics connected, and a Lighthouse target checked before launch.
Enterprise Integrated Workflow Application The system runs the work itself: cases, approvals, and live links to ERP, CRM or finance. When it stops, people stop. $80K+ 8–12 months

How we deliver a project this size

    1. 1

      Analyze & Consulting

      Process discovery with the people who do the work. We map the current path and its exceptions, the cases handled by phone or spreadsheet.

    2. 2

      Proof of Concept

      The critical workflow on real code, wired to a sandbox of an actual system of record. Process owners run their own live cases.

    3. 3

      Solution Design

      Workflows specified state by state with exceptions and named owners. The integration map fixes direction, authority per field, and what the audit trail records.

    1. 4

      Contract & Kick off

      Phased fixed price or capacity agreement. 20% deposit, then milestone by milestone. Kick off names the sponsor and each process owner.

    2. 5

      UI/UX Design

      Judged on how fast a trained person completes a case. Queue, case and approval screens drawn around the real task, exception paths included.

    3. 6

      Develop · Demo · Feedback

      Weekly demos where process owners run their own live cases. CI/CD and environment parity, so what you see demoed is what deploys.

    1. 7

      Data Migration

      Open cases arrive mid-process in the right state with the right owner. Historical data reconciled against the systems of record.

    2. 8

      QA, Security & Accessibility

      Regression on every pipeline run at production parity. Each integration tested against a sandbox, including how the workflow behaves when that system is down.

    3. 9

      UAT

      We run real cases in parallel with the existing process and show process owners the comparison to approve.

    1. 10

      Deployment & Cutover

      Phased by team or region, each phase with its own rehearsal, rollback point and go/no-go. Cases already in flight are planned explicitly.

    2. 11

      Hypercare

      Named engineers available while the team that just switched is working. Exceptions discovery missed are handled here and folded into the runbook.

    3. 12

      Document & Training

      Runbooks, integration contracts, the regression suite, and the reasoning behind each workflow decision. Train-the-trainer by role before each cutover phase.

    1. 13

      Warranty

      One year. A defect that stops work is triaged ahead of everything else. Our side of every integration, not the far end.

    2. 14

      Maintenance

      Managed service: monitoring, release management, integration health. It deliberately excludes new capability, so enhancements get funded rather than absorbed.

    3. 15

      New Phase & Change Requests

      Inside an existing workflow, it enters the sprint. A new workflow or system of record returns to Solution Design with its own acceptance gate.

Included in the price

  • SEO and performance baseline at launch. Technical SEO setup, metadata and structured data, an XML sitemap, redirects from the old site, Search Console and analytics connected, and a Lighthouse target checked before launch.
Multi-Entity Enterprise Multisite / Institutional Platform One platform, many units. Each keeps its own brand and timetable inside standards the centre sets, and they go live in waves. $100K+ 10–16 months

How we deliver a project this size

    1. 1

      Analyze & Consulting

      Discovery across units to answer one question: what must be shared, and what may each unit decide. That line is the whole programme.

    2. 2

      Proof of Concept

      A reference site on the shared design system, with the governance rules in writing beside it. Units argue their exceptions against something real.

    3. 3

      Solution Design

      The operating model in writing: mandated, local, and who adjudicates. Design system, multisite architecture, and a per-unit template that can price a wave.

    1. 4

      Contract & Kick off

      Platform contracted first, then each wave against the per-unit template. 20% deposit, then milestone by milestone. Kick off convenes the steering group.

    2. 5

      UI/UX Design

      A governed design system, not a site design: shared library, the latitude each unit gets, and written rules on what may change.

    3. 6

      Develop · Demo · Feedback

      Platform and design system built once, demoed weekly to the central owner and the current wave. Fixes go back into shared components, not local workarounds.

    1. 7

      Data Migration

      Productised as a per-unit kit, refined wave after wave. Each unit cleans its own content against a standard checklist and launches when its dry run reconciles.

    2. 8

      QA, Security & Accessibility

      The platform tested once at the source, so a component fixed there is fixed everywhere. Every unit runs the same pre-launch checklist.

    3. 9

      UAT

      The platform is accepted once by the central owner and steering group. Every unit accepts its own site against the same checklist.

    1. 10

      Deployment & Cutover

      Platform released first, units in waves on their own dates. The same runbook each wave, shorter as exceptions are designed out. Rollback per unit.

    2. 11

      Hypercare

      Per unit at its own launch, run by the rollout team that onboarded it. What one unit stumbles on feeds the next wave's kit.

    3. 12

      Document & Training

      Design system, governance rules and a per-unit onboarding kit, versioned like product docs. The central team is trained to onboard the next unit alone.

    1. 13

      Warranty

      One year on the platform; each unit site from its own launch date, so the periods overlap. Local content and config are the unit's.

    2. 14

      Maintenance

      Platform retainer plus per-unit support. The design system is released like a product: staying current is maintenance, new components are not.

    3. 15

      New Phase & Change Requests

      Three routes: the rollout team, Solution Design when it lands on everyone, or a funded programme phase. Each wave costs less than the last.

Included in the price

  • SEO and performance baseline at launch. Technical SEO setup, metadata and structured data, an XML sitemap, redirects from the old site, Search Console and analytics connected, and a Lighthouse target checked before launch.
Strategic Mission-critical Digital Ecosystem You have to prove it, not assert it: independent security and accessibility audit, and availability written into a contract. $200K+ 12+ months

How we deliver a project this size

    1. 1

      Analyze & Consulting

      Discovery across services, data domains and obligations, with risk, legal and information security present from the first session.

    2. 2

      Proof of Concept

      Aimed at the one constraint capable of stopping the programme, and nothing else until it is answered, on the intended architecture.

    3. 3

      Solution Design

      Architecture across services and data domains, with security, accessibility and availability evidence specified as deliverables. High availability and disaster recovery drawn against the SLA.

    1. 4

      Contract & Kick off

      Programme contract with staged funding, audited gates and an SLA carrying named remedies. 20% deposit, then milestone by milestone.

    2. 5

      UI/UX Design

      One design system across every service, published so other suppliers build to it. Formal design review with the board.

    3. 6

      Develop · Demo · Feedback

      Parallel domain teams on one architecture, integrated continuously. Cross-domain interfaces are proved by running code, not by agreement.

    1. 7

      Data Migration

      Each data domain migrates on its own schedule against the gates. Provenance and retention honoured, reconciliation evidenced to the board.

    2. 8

      QA, Security & Accessibility

      Assurance carried out independently of the teams that built it. Security review and WCAG 2.2 AA per service. Performance and failover against the contracted SLA.

    3. 9

      UAT

      Acceptance at each gate: the business accepts behaviour, risk and information security accept the evidence. A failed gate is not waived.

    1. 10

      Deployment & Cutover

      Each service on its own schedule into the high-availability architecture, coordinated with other suppliers. Documented rollback at every step, disaster recovery rehearsed first.

    2. 11

      Hypercare

      Per service. The domain team and SRE watch real traffic against the thresholds the design assumed, the only honest point to tune them.

    3. 12

      Document & Training

      An audited deliverable: decision records, disaster-recovery runbooks, assurance evidence and integration contracts, readable by the other suppliers.

    1. 13

      Warranty

      Per service from its own go-live, under the programme SLA, measured against the gate evidence. Regulatory change is new scope.

    2. 14

      Maintenance

      SRE, security patching, assurance re-testing, rehearsed disaster recovery, a governed change pipeline. Availability and remedies are written into that contract.

    3. 15

      New Phase & Change Requests

      The board funds in stages and picks the route: a service build loop, Solution Design with its own gates, or a new programme.

Included in the price

  • SEO and performance baseline at launch. Technical SEO setup, metadata and structured data, an XML sitemap, redirects from the old site, Search Console and analytics connected, and a Lighthouse target checked before launch.

Payment

You see working software before every milestone

The schedule follows the length of the work. In all of them nothing is due before you have seen the idea running, and every payment after that lands on something you can check for yourself.

Micro – Small

Short project

  1. 0%Proof of conceptA design you can click, or a demo on real code. Nothing is due before you have seen it.
  2. 50%KickoffAgainst a one-page scope at a fixed price. The deposit starts the build.
  3. 50%Go-live and handoverDeployment, content, and the repository in your hands.

Short enough that a middle milestone would add paperwork rather than protection.

Medium – Extra Large

Standard project

  1. 0%Proof of conceptA product demo or a working prototype on real code, before you commit to anything.
  2. 30%Project kickoffAgainst a scope that is already written down, and a price already fixed against it.
  3. 40%UAT and approvalOnce you have tested the complete system yourself and said it does what it should.
  4. 30%Go-live and handoverDeployment, documentation, training, and the repository in your hands.

Long enough that you should be paying against tested software rather than against elapsed time.

Enterprise and above

Multi-phase programme

  1. 0%Proof of conceptArchitecture, plus the hardest constraint proved on real code: the one capable of stopping the programme. Nothing is invoiced before the contract is signed.
  2. 20%DepositStarts the programme, against a signed architecture and a delivery plan broken into phases.
  3. ThenMilestone by milestoneEach phase released against written acceptance criteria (foundation, core delivery, then scale and migration), followed by hypercare under an SLA.

Phases are funded as they are accepted, so neither side carries the whole programme at once.

In the price

What is inside the price rather than billed beside it

These sit inside the number above rather than arriving as a separate line later.

A running system

Deployed, live, and doing the job it was bought for, on your domain, with your data and your users on it. Not a repository you then have to find someone to install.

Full access to the source code

The whole repository from the first commit: application code, custom modules, theme, build tooling and deployment configuration. No licence fee on your own platform, and no part of it held back as leverage.

Documentation and training

Written for a developer who has never met us, and sessions for the people who will actually run it. That is the only version of documentation still worth anything a year later.

A warranty of one year or more

One year by default on development projects, up to three by agreement, carried inside the project price rather than billed beside it. Same team that built it, no charge for defects, and Drupal core and contributed security releases applied during the term.

What is genuinely separate is ongoing maintenance, which is a different thing from a warranty and is agreed monthly against the system you end up running.

After launch

Maintenance and support

Maintenance and support runs from $100 to $5K and above per month, per project, sized to the system. It is agreed monthly against the system you end up running, with no lock-in period. Published first-response targets are four hours for critical issues, one business day for high priority and three business days for normal; out-of-hours cover is optional and adds to the monthly price.

What sits in this band

Support and maintenance retainers, Drupal hosting, and security audit and remediation work. A site audit, an SEO audit or a performance audit sits here too, as one piece of work quoted at a fixed price rather than a monthly fee. Agencies pay the same band as our direct clients.

What moves a system within it

Traffic and uptime expectations, environment count, how many contributed and custom modules are carried, how many integrations have to keep working, whether out-of-hours coverage is needed, and the ticket volume the system actually generates.

Systems we did not build

A paid takeover audit comes first: codebase, dependencies, permissions, deployment and backups. It turns those factors into a number, and the number is fixed for the term once agreed.

Not sure where you fit?

Most people sit between two rows. Fifteen to thirty minutes on a call and we will tell you which size it honestly is, including the times it turns out smaller than you feared.

Tell us what you are building See what we build