Staff augmentation
Senior Drupal, cloud and accessibility engineers embedded in your team, your tools and your reporting lines, for as long as the work needs them.
One more senior engineer inside your stand-ups, your repository and your ticket queue, not an agency. Ours have run platforms for institutions, start in weeks, and write things down so your team is stronger when they leave.
Talk about adding an engineer- Senior Drupal and cloud engineers
- Your tools, your stand-ups, your reporting
- Weeks to start, not months
What staff augmentation is for
An in-house team usually knows exactly what needs doing and lacks the hands or one specific skill to do it: a Drupal 7 migration nobody has run before, a Section 508 backlog, a cloud account that has to move into code, a security release cadence that keeps slipping. Hiring takes months and an agency brings its own process. An embedded engineer brings the skill, works inside the process you already have, and reports to your lead.
What we do with it
We place senior engineers, in Drupal, in cloud engineering on AWS, Azure and Google Cloud, and in accessibility, into your team for a defined engagement: a project, a quarter, a year. They use your repository, your CI, your ticket tracker and your meetings. They take direction from your lead and report to them. They document as they go, in your wiki, so the knowledge stays when the engagement ends. When the need changes, the engagement changes: a second engineer for the migration window, a smaller retainer once the platform is stable.
How we work
A short scoping call establishes the skill, the duration and the reporting line. You meet the engineer before anything is signed. They start with a week inside your process rather than a week of ours, and the first deliverable is a written picture of what they found. Engagements run month to month after a minimum term, with a named backup engineer so a holiday or an illness does not stop the work. Every engineer is one who has run a platform after launch, not only built one.
Why now
Drupal 10 reaches end of life on December 9, 2026 and Drupal 11 needs PHP 8.3 or later, so most institutional teams have an upgrade and a hosting change in the same year. ADA Title II puts accessibility remediation on a calendar for state and local governments. The teams that own those platforms are rarely staffed for a year like that, and a senior engineer for the duration is cheaper than a late deadline.
The terms of an engagement
Weeks
To start, not months
A scoping call, an introduction to the engineer, and a start date inside the month.
Yours
Tools, stand-ups and reporting
Your repository, your CI, your tracker, your lead. We bring the engineer, not a process.
1 + 1
Engineer, and a named backup
A holiday or an illness does not stop the work. The backup already knows the platform.
Dec 9, 2026
Drupal 10 end of life
The date most institutional teams are staffing for. Drupal 11 needs PHP 8.3 or later.
Drupal core release scheduleI want to …
add a senior Drupal engineer to my team
For the migration, the upgrade or the feature backlog: an engineer who has done it before, in your repository from the first week.
- Drupal 7 to 11 migrations, 10 to 11 upgrades, custom modules and themes
- Works in your process, reports to your lead
- Documents as they go, in your wiki
get cloud engineering without hiring for it
An engineer who puts your account into Terraform, builds the pipeline, sets up monitoring and patching, and hands the runbooks to your team.
- AWS, Azure or Google Cloud, inside your account
- Infrastructure as code, CI/CD, monitoring, patching
- Runbooks written for your team, not ours
clear an accessibility backlog with an expert
An accessibility engineer who audits, fixes at the source and trains your editors, for the months the backlog takes.
- WCAG 2.2 AA audits with a screen reader, in plain language
- Fixes in the theme and the components, so they hold
- Editor training and a gate in the build before they leave
cover a migration window
A migration needs more hands for a few months and fewer afterwards. An engagement that grows for the window and shrinks after it.
- A second engineer for the rehearsal and cutover months
- The same engineers, so nothing is re-learned
- A smaller retainer once the platform is stable
keep a platform patched while I hire
While a permanent role is open, an engineer keeps security releases, upgrades and monitoring on schedule, and hands over cleanly when the hire arrives.
- Security releases inside the advisory window
- A written handover for the incoming engineer
- Month to month, so it ends when the hire starts
bring AI into the team safely
An engineer who sets up private model endpoints in your cloud, builds the first editorial AI feature with your editors, and measures whether it earns its keep.
- Bedrock, Azure OpenAI or Vertex, inside your account
- A pilot with named reviewers and measured results
- The review step built into the workflow
From the first call to the first deliverable
Short, and mostly inside your process rather than ours.
The measure of a good engagement is that the team is stronger when it ends. The documentation is not optional.
What is changing for in-house platform teams
Checked on drupal.org and ada.gov on September 10, 2026.
A year of forced change
Drupal 10 ends on December 9, 2026, Drupal 11 needs PHP 8.3 or later, and ADA Title II puts accessibility on a calendar. Most institutional teams are not staffed for all three at once.
Hiring is slow; the calendar is not
A senior Drupal or cloud role takes months to fill. An embedded engineer covers the gap and hands over cleanly when the hire arrives.
Process belongs to the team
The best augmentation is invisible from the outside: the engineer is in your stand-up, your repository and your tracker, and reports to your lead.
Knowledge has to stay
An engagement that leaves no documentation leaves the team weaker. Writing things down is part of the job, not a courtesy.
Services that pair with this one
An embedded engineer usually arrives for one of these. When the work is bigger than one person, they are the same team.
-
Drupal development
New builds, major-version upgrades, module and theme work, and migrations from Drupal 7 onward. Every site we build is one we can keep patched, accessible and on a supported version for years, because that is the job after launch.
-
Cloud engineering
We design and run the cloud your platform lives on, in your own account, as code, with monitoring, patching and a monthly cost review in writing. We do not resell hosting, and everything we build is documented so the next engineer can run it.
-
Accessibility & AI visibility
Accessibility fixed at the source, in the theme and the editorial rules, with a conformance report you can hand to procurement. The same work makes your pages the ones AI engines cite.
Tell us who you need.
The skill, for how long, and who they would report to. We come back with who is available, when they can start, and what it would cost.
Talk about adding an engineer