Staff augmentation
Our engineers join your team and take direction from your leads. You keep the roadmap, the repository and the decisions. We supply the capacity to execute them.
Why this comes up
The roadmap is agreed, the problem is understood, and the team that would build it is already committed to something else. Nothing about that situation calls for an agency to come in and decide what to build. It calls for more hands on the plan you already have.
Hiring is the obvious answer and the slow one. A permanent engineer is three to six months from first conversation to first useful commit, and the quarter you needed them for is the one you spend interviewing.
This model exists for the gap in between: people who work the way employees do, on a contract that ends with 30 days’ notice rather than a redundancy process.
HOW IT WORKS
How it actually runs
- Your leads set the priorities; we do not run a parallel roadmap
- Our engineers commit to your repository, under your review rules
- They attend your standups, on your calendar, in your tools
- You get the same people week to week, not a rotating pool
One engineer, or a team with its own lead
- A single engineer when you need one skill you do not have
- A dedicated team of three to six when a whole workstream is unowned
- With a team we can supply a tech lead, or your lead keeps the team
- Either way the people are named before you commit, never allocated later
Hours that overlap yours
- We are in Lagos, GMT+1: a full working day with the UK and Europe
- Four to five hours of overlap with the US East Coast every afternoon
- West Coast overlap is the morning only, which we say before you sign
- Nothing is handed to a night shift you never speak to
Starting and stopping
- Two to three weeks from agreement to first commit, usually
- A two-week paid trial, and you can end it at the end of it
- 30 days' notice after that, either direction
- Your code, your repository, your pipeline, from day one
What you get
- Named engineers, with their real experience, before you commit
- A two-week trial priced as two weeks, not as a quarter
- One monthly invoice per engineer, no recruitment fee and no placement fee
- Code review and delivery discipline carried over from our own projects
- A direct line to us when someone is not working out
Right when
You know what needs building, you have someone able to direct the work, and the only thing missing is people to do it.
Wrong when
Nobody on your side has the time to direct an engineer. Added capacity under absent direction produces code that has to be explained later. Take the build partner model instead, where owning delivery is our job rather than yours.
WHO OWNS DELIVERY
That is the whole difference between the three models. Everything else is a billing detail.
You are here
Staff augmentation
Per engineer, per month
You own delivery. We supply the people, and your leads direct them.
You want outcomes, not headcount
Build partner
Monthly retainer
We own delivery. An embedded team shipping on a fixed cadence, accountable for the outcome rather than for filling seats.
How we run itScope is known
Fixed cost
Priced per project
A known scope at a known price. We carry the overrun risk, which is why we scope carefully first.
How we run itOn the vocabulary
Staff augmentation, dedicated development team, remote engineers, offshore, nearshore. These mostly describe the same arrangement from different sides of a contract. What matters is who sets the priorities, who reviews the code and how quickly either side can stop. Those three answers are above.
NEED HANDS ON A PLAN YOU ALREADY HAVE?
Tell us the stack, the gap and when you need someone in the repository. We will tell you who we would put on it and when they could start.
Start a project