Dedicated Drupal Team

Named engineers reserved for your agency by the month, working your backlog in your tools. Drupal staff augmentation without the recruiting, the notice periods or the bench.

For agencies

What dedicated means here

Agencies do not usually have a Drupal problem. They have a capacity problem that arrives in bursts: wins that land in the same quarter, a developer who resigns mid-build, a client whose roadmap suddenly needs more people. Hiring against that is slow and leaves you carrying a bench when the burst ends. A dedicated team is the other answer: named Drupal engineers reserved for you by the month, scaled up or down with notice rather than with redundancy.

  • Reserved and named

    Specific engineers, not a pool that rotates. Their time is held for you for the term rather than sold twice.

  • Inside your process

    Your repository, your branching model, your ticket system, your definition of done, your standups. We do not run a parallel project plan that has to be reconciled with yours.

  • Our standards underneath

    Code review, coding conventions and automated test coverage on what we ship travel with the people rather than with the client. If your standards are stricter, we work to yours.

Fit

Who this is for

Agencies and studios

  • With more Drupal work than Drupal people

Product teams

  • That need senior Drupal capacity without a permanent headcount

Consultancies

  • Delivering a Drupal programme, and needing the team to be someone else's problem to staff

Roles

Roles you can staff

We are a Drupal firm with the surrounding disciplines in-house, so a team can be composed rather than just counted. Most teams are a mix: backend engineers with a part-time lead, and QA shared across the group.

  • Drupal backend engineers

    Custom modules, entity and permission modelling, integrations, migrations.

  • Front-end engineers

    Twig, the theme layer, Bootstrap and SCSS, Vue where an interface needs it.

  • QA engineers

    Automated coverage with PHPUnit and Playwright, static analysis with PHPCS and PHPStan.

  • DevOps engineers

    Docker and DDEV environments, CI/CD pipelines, deployment and rollback.

  • UI/UX designers

    Where the work needs design rather than implementation of one.

  • Technical lead or architect

    Usually part-time across a team, and usually the role that makes the difference on a programme of any size.

Time zones

Time zones and overlap

We work from Ho Chi Minh City on Indochina Time, UTC+7. Where a project needs live hours outside our day, we agree them in the contract as shifted hours for named people, rather than pretending an overlap exists.

  • Australia and New Zealand

    Effectively a shared working day. Overlap is not something anybody has to manage.

  • Europe and the UK

    Our afternoon is your morning: live overlap every day without either side working unusual hours.

  • North America

    A shared day does not exist. It works when the team runs asynchronously with a fixed daily handover window, and badly when it depends on ad-hoc conversation. We tell you which your project is before you commit.

Onboarding

How onboarding runs

An engagement that begins with weeks of reading is one both sides regret, so the ramp is short and concrete.

    1. Week zero

      Access, environments, a walkthrough of the codebase and the domain, and agreement on the definition of done and the review path.

    2. First sprint

      Real tickets, smaller than usual, chosen so the team touches the parts of the system it will live in. Output is reviewed by you, not by us.

    3. End of the first month

      A written review of throughput and fit, with the option to change the team composition. If somebody is not right for your work, changing them is a conversation rather than a negotiation.

Reporting and how you keep control

You direct the work. We do not decide priority; your backlog does.

What you get in writing: time reported against tickets, weekly progress against what was committed, and a monthly summary that includes anything we think is accumulating as risk: a dependency drifting out of date, a pattern of defects in one area, a piece of the system nobody has documented. Access to the repository and the pipeline is yours throughout, so nothing about the work is visible only to us.

If you want the team to appear as yours to your own client, that is the white-label arrangement and it is the default rather than an extra. Everything starts under NDA, and non-solicitation of your clients and your staff, and ours, is written into the contract.

Commitment, scaling and what it costs

Engagements are monthly, with a minimum term and a notice period agreed at the start. Scaling up needs lead time so that the people you get are the right ones rather than whoever is free; scaling down needs notice so that nobody is dropped mid-sprint. Both are written into the agreement, and neither is a penalty.

We do not publish a per-seat monthly rate, because the number depends on the mix of roles, the seniority you need and the term. We quote the team you actually need against the work you actually have, in writing, before you commit. Our published engagement bands are on the pricing page.

If what you have is a defined project rather than a capacity gap, a fixed price is almost always better value than a monthly team, and that is white-label project delivery or outsourced development instead. We will say which one fits before quoting for this one.

Questions

Questions agencies ask

How is this different from outsourcing a project to you?

A project is defined work at a fixed price, and the risk of estimating it is ours. A dedicated team is reserved capacity: you direct it, you set the priorities, and the scope can change every sprint. If your work is well defined, the fixed price is usually better value, and we will tell you so.

Do we get the same people every month?

Yes. Named engineers, reserved for the term. If somebody has to change for a reason on our side, you are told before it happens and there is a handover rather than a substitution.

Can we interview them first?

Yes. We expect it for a lead or architect role. You are the one who has to work with them every day.

What time zone do you work in, really?

UTC+7. That is a shared day with Australia and New Zealand, daily overlap with Europe and the UK, and no natural overlap with North America. For a North American client the engagement has to run asynchronously with a fixed handover window, and we say that plainly before you sign.

Whose process do we use?

Yours. Your repository, your branching model, your tickets, your definition of done. Our engineering standards travel with the people underneath that, and where yours are stricter, we work to yours.

What is the minimum commitment?

A minimum term and a notice period, both agreed at the start and both short enough to be honest about. Scaling up needs lead time to staff properly; scaling down needs notice so that nobody is dropped mid-sprint.

What does a seat cost per month?

We do not publish a per-seat rate, because it depends on the role mix, the seniority and the term, and a headline number would be wrong for most teams. We quote the team you actually need against the work you actually have, in writing, before you commit. The published engagement bands are on the pricing page.

Can the team work under our brand?

That is the default. Everything starts under NDA, non-solicitation runs both ways, we do not approach your client, and the work ships as yours.

Who owns what the team writes?

You do, or your client does, from the first commit. We take no licence over work we do inside your repository. Source code ownership is the position on every engagement we run, not a concession negotiated per contract.

What if it is not working?

The written review at the end of the first month exists for exactly that. Team composition can change, roles can be swapped, and the engagement can end on notice. A capacity arrangement that is hard to exit stops being capacity and starts being a liability.

Partner services

Where this sits among our partner services

This page is reserved engineers by the month, working your backlog. Each neighbouring arrangement has one intent of its own.

Tell us what you are short of

We will propose a team shape against your actual backlog, and say if a fixed-price project would serve you better.

Discuss a dedicated team
See indicative pricing