Photo: Google Gemini · AI-generated
Two quotes land on your desk. One is a dedicated team. One is staff augmentation at a lower hourly rate.
The rate is the easiest number to compare. It is also the least useful one, because it is not the number you actually pay per unit of work.
Before going further, one caveat worth stating plainly: almost every published figure in this area — contractor turnover rates, ramp-up times, “savings versus hiring” — comes from companies selling one model or the other, including ours. So this piece will not quote any of them. What follows is the shape of the arithmetic. Put your own numbers in it.
The number you compare is not the number you pay
An hourly rate buys attendance. What you need is completed work, and the gap between those two is filled by three things nobody quotes.
Ramp. A new engineer is billable immediately and useful somewhat later. During that window you pay full rate for partial output, and you also pay a second, invisible cost: your senior people answer questions instead of building.
Rotation. If people move on and are replaced, you pay ramp again. Not once — every time. This is the term that compounds, and it is the one left out of the comparison.
Write-off. When someone leaves, what they knew about your system leaves too. Not the code — the reasons. Why that workaround exists, which module is fragile, what broke last time someone touched billing.
Run it yourself
Take your two quotes and add three assumptions you can actually defend for your own situation:
- How long before a new engineer on your system is fully productive?
- What fraction of the team turns over in a year?
- How much senior time does each new arrival consume?
Then compare cost per productive hour over the whole engagement, not rate per hour.
The pattern that falls out is consistent even when the inputs vary a lot. Short engagements favour the lower rate, because ramp is paid once and rotation may never happen. Long engagements favour stability, because rotation keeps re-charging you for the same onboarding while the knowledge write-off never appears on any invoice.
Somewhere between those, the lines cross. Where exactly depends on your three numbers — which is the point. If a partner tells you the crossover without asking about your system, they are selling, not calculating.
What actually resets
The write-off term is the one people underestimate, because it does not look like a cost. It looks like a new person being slower.
We have written separately about why an embedded team only works if context compounds — how context accumulates, and how easy it is to structure an engagement so it never does. The arithmetic here is the same fact seen from the finance side: continuity is not a soft benefit, it is the mechanism that stops you re-buying the same knowledge.
You can see the difference in what long engagements grow into. With CarLicence, a real-time licence renewal API that partners embed in their own websites, apps and ATMs, the dedicated team covers development, cloud infrastructure and DevOps together — CI/CD, environments, production monitoring. That scope is not something you brief in. It is something a team ends up holding because it has been there long enough to be trusted with it.
Dinifi, a POS and ordering platform across iOS, iPadOS and tvOS, has the same shape: mobile development, cloud migration and ongoing integration work, held by the same team rather than handed between suppliers.
When staff augmentation is the right answer
It often is, and pretending otherwise would be dishonest.
Take the lower rate when the work is genuinely separable and short — a fixed piece of build-out, a known technology, a capacity spike with a defined end. Take it when you have strong internal engineering that owns the architecture and needs hands, not judgement. Take it when the alternative is not hiring at all.
The model breaks down when the work is long-running, entangled with the rest of your system, and dependent on knowing why things are the way they are. That is when the rate advantage quietly funds its own erosion.
Ask a different question
“What is your hourly rate” has an answer that tells you very little. These tell you more:
Who specifically will work on this, and what happens if they roll off? Do you charge for onboarding a replacement? What does your team turnover actually look like on engagements this length?
A dedicated team that cannot answer the last one is offering staff augmentation with better branding.
If you are weighing two quotes and want help putting real numbers in the model, we should talk.