Staff augmentation or a dedicated development centre? A decision framework
Duration, domain depth and IP sensitivity decide this — not headcount. The four questions we ask every client before recommending a model.
Talent Practice
Tvisha Scale Division
Clients usually arrive at this question having already decided the answer by headcount: "we need six engineers, so that is a team." Headcount is the least useful input. Four other variables decide it, and they are worth ten minutes before you sign anything.
1. How long is the work?
Under nine months, staff augmentation wins on almost every axis. You are renting capability for a known window, the commercial terms are monthly, and nobody is amortising a recruitment investment that will not pay back. Past eighteen months, the arithmetic inverts: augmentation rates compound, while a dedicated centre lets us hire specifically for you and hold the cost flat.
2. How deep is the domain?
Ask your best engineer how long it takes a competent newcomer to be genuinely productive on your system. If the honest answer is under a month, augmentation is efficient. If it is a quarter — which is common in insurance, clinical systems and anything with a settlement cycle — then every rotation costs you a quarter of productivity, and you should be buying continuity, not flexibility.
3. How sensitive is the IP and the data?
A dedicated centre can be configured as an extension of your own security perimeter: named individuals, your device management, your access reviews, physical segregation where required. Augmented engineers working inside your teams can meet the same bar, but the administrative overhead per person is higher. Above roughly ten people in a regulated environment, the centre model is usually cheaper to govern.
4. Who is doing the managing?
This is the question clients skip and then regret. Augmented engineers report to your leads and consume your management capacity. A dedicated centre comes with its own delivery lead, its own people operations and its own retention problem to solve. If your engineering managers are already at capacity, adding six augmented engineers does not add six engineers of output.
- Augmentation: you manage the work, we manage the employment
- Dedicated centre: we manage both, against outcomes you define
- Hybrid: a centre for the core product, augmentation for peak load
The honest summary
Short, shallow, flexible work: augment. Long, deep, sensitive work: build a centre. Everything in between is a judgement call, and the right answer usually becomes obvious the moment someone answers question four truthfully.
Keep reading
The technical interview questions that actually predict performance
After several thousand technical assessments, the signals that correlate with a successful twelve-month placement are not the ones most panels test for.
7 min readRetrofitting AI into legacy enterprise systems without a rewrite
Most enterprises do not need a greenfield platform to benefit from machine learning. A pragmatic pattern for wrapping models around the systems you cannot replace.
8 min readAnatomy of a tiger team: 140k lines of dead code and $2M saved
How a five-person unit stabilised a Fortune 500 loan origination platform in eleven weeks — the instrumentation, the sequencing and the politics.
11 min read