MENTARA
Workforce Solutions

You own delivery. That has to mean something in how the engagement is set up.

Augmentation fails when someone is embedded in your team but managed as a vendor. MENTARA sets the accountability boundary — including what we do not hold.

The decision in front of you

Staff augmentation and contract staffing are frequently sold as the same thing, and the difference matters. In augmentation the person joins your team, takes direction from your leads, works to your backlog and is subject to your engineering practice. You own delivery. We own supplying and supporting the right capability.

That boundary sounds obvious and is routinely blurred in practice, usually in one of two directions — either the supplier is held accountable for delivery outcomes they cannot influence, or the augmented person is excluded from the team's decisions and context while still being expected to produce as a full member of it.

The failure mode

Embedded in the team, excluded from the context.

The most common augmentation failure has nothing to do with capability. Someone competent joins, and is kept outside the things that would let them be effective — not in the planning conversation, not on the architecture decision, no access to the systems that would let them diagnose rather than ask, treated as capacity to be assigned tickets rather than as a person who could tell you the ticket is wrong.

This is rarely deliberate. It comes from a reasonable caution about access and from the fact that including someone in context takes effort. The result is that you pay senior rates for someone constrained to junior work, and then conclude that augmentation does not work well.

The mirror failure is accountability drift. Because the supplier is a company rather than an employee, it becomes tempting to hold them responsible when the sprint slips — even though the backlog, the priorities, the architecture and the definition of done are all yours. That confusion is best resolved in writing at the start, because resolving it during a difficult delivery period is much harder.

How MENTARA works

The boundary, stated explicitly.

01What you ownThe backlog, priorities, technical direction, engineering standards, definition of done, and the delivery outcome. Augmentation adds capability to your model; it does not replace your judgement.
02What MENTARA ownsThat the person supplied has the capability represented, is supported, is replaced promptly if that turns out to be wrong, and that the commercial and classification position is correct.
03Integration expectations, agreed upfrontWhat access, context and inclusion the person needs to be effective — agreed as a condition of the engagement, because without it you will not get what you are paying for.
04Honest capability representationWe tell you where someone is strong and where they are not. An augmented engineer who is excellent on the backend and inexperienced on your frontend framework should be deployed accordingly, not oversold and then found out.
05Escalation that works both waysIf the person is being under-used, blocked or excluded, we raise it with you. That is uncomfortable and it is the job.
06Classification correctnessCo-employment exposure, employment status and statutory obligations addressed for your jurisdiction before the engagement starts.
Co-employment

The exposure that comes with integration.

Augmentation deliberately integrates someone into your team, and that integration is exactly what creates classification exposure. The more the engagement looks like employment — your direction, your hours, your equipment, your performance management, indefinite duration — the more likely it is to be treated as employment by a tax authority or a tribunal, regardless of the contract's wording.

In the United States this is co-employment risk, and it is affected by how you actually manage the person day to day. In the United Kingdom, off-payroll rules mean an integrated, directed, long-running engagement is very likely inside IR35, and the determination and its consequences sit with you. In India the position depends on engagement structure and the applicable statutory obligations.

None of this means augmentation is a bad model. It means the structure should be chosen deliberately: if the engagement genuinely looks like employment, that should be priced and documented as such rather than dressed as something else. Where a role is long-running, central and directed by you, permanent hiring is frequently the more honest and cheaper answer, and we will say so even though it earns us less.

Approach

How the engagement runs.

  1. 01 Define the boundary in writing

    Who directs, who prioritises, who is accountable for what — recorded before anyone starts, because it is the thing that gets disputed later.

  2. 02 Agree integration conditions

    Access, context, inclusion in planning and technical decisions. Without these the engagement will underperform and the cause will be misattributed to the individual.

  3. 03 Match on the actual work

    Assessment against what the person will really be doing within your practice and stack, with weaknesses stated rather than smoothed over.

  4. 04 Review honestly, early

    Structured check-ins with both sides. If it is not working we would rather replace quickly than let it run to a contract boundary.

Questions

What buyers ask.

How is this different from contract staffing?

Contract staffing supplies a person for a defined scope of work, often with more independence. Augmentation embeds someone in your team under your direction and your practice.

The distinction matters commercially and legally, not just semantically — it changes the classification position and it changes who is accountable when delivery slips.

Can you supply a whole team this way?

You can augment several people into your existing team, and that works. But if what you actually want is a team with its own lead, its own delivery accountability and a defined outcome, that is a dedicated delivery team rather than augmentation, and the governance is different.

Choosing augmentation for something that is really a dedicated team is a common and expensive mistake, because nobody ends up accountable for the whole.

What if we want to hire the person permanently?

Conversion terms are agreed in the framework at the start, with a defined fee or qualifying period rather than a penalty invented at the point you ask.

We would rather you hired someone good than lose them because converting was made difficult.

07

Where MENTARA fits best.

Scope

We fit senior individual contributors and small groups where capability and fit matter more than volume, and where you want a supplier who will tell you when the engagement should be a permanent hire instead.

Large-scale augmentation — twenty people onboarded across several teams in a quarter — sits beyond our current capacity.

Bring the gap in your team and how you want it owned.

Share the business context, constraints and expected outcome. MENTARA will identify the relevant accountable route.

One partner. One plan. Measurable outcomes.