In brief
- Choose a scoped project when the outcome is clear and you want someone else accountable for delivering it.
- Choose staff augmentation when the work is ongoing or still taking shape and you want senior capacity working under your own direction.
- Choose permanent recruitment when the role will exist for years and belongs inside your organisation.
- Many teams combine them: a project to prove the approach, an embedded consultant to extend it, a permanent hire once the role is understood.
When a company needs more data, software or AI capability than it has, there are three ways to get it: commission a project, bring outside people into the team, or hire. They are often confused, sometimes deliberately by vendors who sell whichever they have available. This guide separates them by the questions that actually matter: who directs the work, who carries the risk, how quickly it starts and what it costs over time.
The three models, defined
Scoped project consulting
You describe an outcome; the consultancy proposes a scope with deliverables, milestones and acceptance criteria, then delivers it. The consultancy directs its own people and is accountable for the result. Typical examples: a first data pipeline and reporting layer, an internal application, an automation of a specific process, a knowledge assistant over a defined document set.
Staff augmentation (embedded consultants or a dedicated team)
Senior specialists join your team for an agreed capacity and duration, working in your tools, your rituals and your hours, under the direction of your technical leads. You own the backlog and the priorities; the consultancy supplies the people, the continuity and the quality bar. Typical examples: a data engineer alongside your product team for two quarters, an AI engineer to build out an assistant your team has designed, additional senior developers during a delivery crunch.
Technology recruitment
You hire a permanent employee into your organisation. A recruitment partner helps define the role, find and assess candidates and coordinate the process; you make the hiring decision and employ the person directly. Typical examples: a head of data, a lead engineer for a new product, a permanent platform team.
Side by side
| Question | Scoped project | Staff augmentation | Permanent recruitment |
|---|---|---|---|
| Who directs the day-to-day work? | The consultancy, against an agreed scope | Your technical leads | You, as the employer |
| Who carries delivery risk? | Shared, with the consultancy accountable for the scope | Mostly you; the consultancy is accountable for the person's quality and continuity | You |
| How quickly does it start? | After scoping, typically one to three weeks | Usually fastest once a fit is confirmed | Slowest: weeks to months depending on the role |
| Best when | The outcome is clear and bounded | The work is ongoing or still emerging | The role is long-term and core to the business |
| Cost structure | Fixed or milestone-based price for the scope | Agreed capacity and duration, priced accordingly | A recruitment fee plus ongoing salary and overheads |
| Knowledge stays with | You, via documentation and handover | Your team, because the work happens inside it | You, as long as the employee stays |
| Flexibility to stop or change | At milestone boundaries | High, within the notice terms | Low; hiring is a long-term commitment |
How to decide
Start from the shape of the work
If you can write the outcome on one page with acceptance criteria, it is a project. If you can only describe a stream of work and a direction, it is capacity, which points to augmentation. If you can describe a role that will still exist in three years, it is a hire.
Then consider who should be in control
Project consulting suits teams that want to buy an outcome and get on with their own work. Augmentation suits teams with strong technical leadership who want more senior hands without giving up direction. Recruitment suits organisations building durable in-house capability.
Then think about risk and reversibility
A project has a natural end and clear acceptance, which limits the downside. Augmentation is easy to scale up or down. A permanent hire is the largest commitment and the hardest to reverse, which is why it deserves the most careful brief.
Common mistakes
- Buying a project when you need a team. Fixed scopes fight with emerging requirements. If the roadmap is uncertain, embed people instead.
- Buying "staff augmentation" that is really outsourcing. If you never meet the engineers and cannot direct them, it is not augmentation, whatever the contract says.
- Hiring permanently for a temporary spike. Six months of intense delivery followed by maintenance is a job for consultants, not a new headcount line.
- Treating recruitment and consulting as interchangeable. They have different scopes, fees and obligations. A good partner will tell you which one you are actually asking for.
Combining the models
The most effective sequence we see is: a scoped project to prove an approach and establish trust; an embedded consultant to extend it while priorities settle; and a permanent hire once the organisation understands the role well enough to write it. Each step reduces the risk of the next. A partner that offers all three, as MV.tech does, can move with you through that sequence without a change of vendor, but the model you choose at each step should follow the work, not the vendor's preference.
Frequently asked questions
Is staff augmentation the same as outsourcing?
No. In staff augmentation, named consultants work inside your team under your direction, in your tools and your hours. In outsourcing, a vendor takes over a function or a scope and directs its own people. Augmentation keeps control and knowledge with you; outsourcing trades some of that for a managed outcome.
Can an embedded consultant work in our timezone?
Yes, within an agreed window. A remote consultant in India can typically overlap US Eastern mornings, most of the UK and European working day, Gulf business hours or Australian afternoons. The specific hours, meetings and response expectations should be written into the engagement.
Can a consultant later become a permanent hire?
Sometimes, if all parties agree and the arrangement allows it. It is better to decide up front whether the engagement is intended as a trial for a permanent role and to set the terms accordingly than to negotiate it under pressure later.