The models
What each one assumes, and how each one fails
Read the assumption row first. If it is not true of your organisation today, the model will not work however good the supplier is.
| Option | What it assumes about you | Who owns the design | How it handles change | How it fails | Best for |
|---|---|---|---|---|---|
| Staff augmentation | You have architecture, code review and engineering management capacity, and need throughput. | You do, entirely. | Easily. Reassign the person to the new priority. | Your senior engineers spend their week reviewing instead of building, and throughput falls as the team grows. | A strong internal engineering function that needs more hands. |
| Dedicated team | You have product direction and a decision-maker, and want an engineering function rather than individuals. | Shared, with your technical lead holding the final say. | Well, if the backlog owner is available. Badly if decisions queue. | Without a product owner it becomes a supplier producing status reports about work nobody prioritised. | Building a product or platform over quarters, not weeks. |
| Fixed scope | The requirement is genuinely settled and you can specify it precisely. | The supplier, within the specification. | Through change requests, which is why estimates drift. | Both sides optimise the contract rather than the outcome, and quality is the variable that gives. | A migration, an integration, or a well-understood build. |
Our position
We deliver all three, which is why this page says augment
A supplier's incentive on this question runs one way: a dedicated team is a larger, longer contract than a handful of augmented engineers. It is worth naming that, because it is the reason most comparisons of this kind conclude that a dedicated team is right for everyone.
It is not. Where an organisation has a strong technical lead, a working review culture and a clear architecture, augmentation delivers more per riyal and keeps the design where it belongs. Where an organisation is trying to build a product with a project manager and no engineering leadership, augmentation makes the problem worse — the missing capability is judgement, and hours do not supply it.
Signals
How to tell which one you are actually ready for
- 01
Who reviews the code today?
If the honest answer is nobody, or one person who is already the bottleneck, augmentation will make that worse within a month. That is a signal for a dedicated team with its own review culture, or for hiring a lead first.
- 02
How long does a question wait?
Measure it honestly for a week. A dedicated team with a two-day decision latency delivers at a fraction of its capacity, and no amount of process fixes that from the supplier side.
- 03
Is the requirement written or discussed?
Fixed scope needs a specification somebody will stand behind. If the requirement lives in three people's heads and changes when they meet, a fixed-price contract will convert every conversation into a change request.
Our role
What we do under each model
- 01
Augmentation
Named engineers working inside your process and to your standards, with your leads holding review and architecture.
- 02
Dedicated team
An engineering function with its own lead, its own review culture and a written delivery standard agreed with you.
- 03
Fixed scope
Where the requirement is settled, priced against a specification with the assumptions listed rather than implied.
Where the honest answer is that you should hire a technical lead before engaging anyone, we will say so — it is a shorter conversation now than a recovery project later.
Common questions
What buyers ask
Can we start with augmentation and move to a dedicated team?+
That is the most common path and it works well, because the people already know the system. What has to change deliberately at the transition is ownership: a team that keeps waiting for your architect to decide everything is an augmentation arrangement wearing a different contract.
Is fixed price safer for us?+
It transfers estimate risk, and it transfers it at a price — the estimate carries a contingency you pay whether or not it is used. It is genuinely the right instrument when the scope is settled and the interfaces are known. It is the wrong one for discovery work, where both sides end up negotiating instead of building.
What size should a first dedicated team be?+
Small enough that one owner on your side can keep it fed — in practice three to five engineers with a lead. Teams that start larger spend their first quarter waiting for decisions, and the cost of that is invisible until somebody compares output to headcount.
In this cluster
An honest read of which model your organisation can currently support, including the case where the answer is to hire internally first.
Work out which model fits
