Staff augmentation: how it works, what it costs, and the contract terms that matter

Agencies meet staff augmentation from two directions. A client asks whether they can “just have two of your developers for six months”, and you find yourself selling it. Or you win a project that needs a skill you are short on, and you find yourself buying it from another shop. The service is the same. The economics are close to opposite, and most of the money made or lost on it is decided by four or five contract terms.

This article covers both chairs. It is the pillar of the Team hub, and the other articles there go deeper on the neighboring decisions.

What staff augmentation is

Staff augmentation is a commercial arrangement with three parties.

• The provider employs or contracts the individual, pays them, and bills for their time.
• The buyer directs the individual’s day-to-day work, sets priorities, reviews output, and is responsible for what gets delivered.
• The individual works inside the buyer’s team, in the buyer’s tools, on the buyer’s schedule, usually for one buyer at a time.

The unit of sale is time. Sometimes it is an hourly rate against approved timesheets. Sometimes it is a flat monthly fee for a full-time person. Either way, the provider’s promise ends at a competent person who shows up. Whether the project ships is the buyer’s problem.

That single fact, that the buyer manages the work and owns the outcome, is what separates augmentation from everything else that gets called outsourcing.

How it differs from project outsourcing and managed teams

Vendors use these three terms loosely, and some use them interchangeably on purpose. The differences are real and they show up in price, in risk, and in who gets the phone call when something is late.

A few things follow from this table.

Augmentation is the cheapest per hour because the provider takes the least risk. The provider’s only exposure is that the person turns out to be weak or leaves. If the buyer’s project is badly specified, runs late, or gets cancelled, the provider still bills every hour worked.

Project outsourcing costs more per hour of effort because the vendor is pricing in the chance of being wrong. A fixed-price vendor who estimates 800 hours and spends 1,100 eats the difference. That risk has a price, and you pay it up front as contingency whether or not it is ever used.

A managed team sits between the two. You buy a block of capacity with its own lead, so you set direction weekly instead of reviewing work daily. It is the right shape when the work is ongoing and you do not have a manager to spare.

The practical test is simple. Ask who decides what this person works on tomorrow morning. If the answer is the buyer, it is augmentation, whatever the proposal calls it.

The seller’s chair: margin math

Agencies drift into selling augmentation because it is an easy yes. The client already trusts you, the sale has no scoping phase, and the revenue is predictable while it lasts. Before you say yes, do this arithmetic.

Take a mid-level developer on a salary of $110,000. Add 25 percent for payroll taxes, benefits, equipment, and software, and the loaded cost is $137,500 a year. A full-time placement produces about 1,800 billable hours a year after holidays, vacation, and sick days.

A 19.6 percent gross margin has to cover your account management, recruiting, office costs, your own salary, and profit. It will not. And that is the good year, where the person is placed for all twelve months.

Now add one gap. The client ends the engagement with 30 days’ notice and it takes you six weeks to place the developer again.

One six-week gap takes the margin from 19.6 percent to 7.2 percent. Two gaps and you are paying to employ someone for the client’s convenience.

Pricing it properly

Work backward from the margin you need. If you want a 40 percent gross margin on a fully placed person:

So the honest rate for this developer is about $127 an hour, and that still assumes no gaps. To allow for one six-week gap a year, divide by 1,560 hours and the rate becomes about $147.

Most clients asking for augmentation have a number in mind that is closer to $95 than $147. They are comparing your rate to the salary they would pay an employee, and forgetting everything an employee costs them on top. Show them the loaded-cost arithmetic. If they still want $95, the deal does not work for you, and it is better to learn that before you sign.

What augmentation does to an agency that sells it

There are three effects beyond the margin, and I have seen each of them damage a healthy shop.

It takes your best people out of your own projects. Clients ask for the developers they already know. Those are the same people who anchor your project teams. Every person you place is a person you cannot staff on higher-margin project work.

It turns your agency into a line item. Project work is bought by someone who wants an outcome. Augmentation is bought on rate, often by a procurement function, and compared against other providers on rate. You lose the conversation about value entirely, which is the conversation that supports retainer pricing and every other model with real margin.

It sets up the conversion problem. A person who spends a year inside a client’s team becomes part of that team. The client will want to hire them. The person may want to go. Without a conversion clause, you lose the employee, the revenue, and the recruiting cost in one move.

Augmentation has a place in an agency’s mix. It keeps people billable between projects, which helps bench management, and it can open a client relationship that later turns into project work. Treat it as a deliberate, priced, time-limited offer. Agencies that let it become the default find that their utilization rate looks excellent while their profit shrinks.

The buyer’s chair: when it beats hiring

Now sit on the other side. You have won a six-month project that needs a senior backend developer you do not have. You can hire one or rent one.

The augmented developer costs $85 an hour from a provider. You bill the client $150 an hour for the role.

The comparable hire earns $130,000, with a loaded cost of $162,500 a year, or $13,542 a month. Monthly, the two cost almost the same. The difference is everything around the monthly figure.

For a six-month need, augmentation is about $25,000 cheaper and starts while a hire would still be interviewing. The hire also leaves you with a senior salary on the bench in month seven unless you have sold the next project.

The comparison turns around as the engagement gets longer. Over three years of steady work, the hire costs roughly the same per month and you keep the knowledge, the loyalty, and the option to move the person between clients. The rule I use: augment for needs under nine months or needs I am unsure about, and hire once I can see twelve months of revenue for the role. The article on when to partner instead of hire covers the third option, where you hand the whole piece of work to a specialist firm.

What you take on as the buyer

You are buying a person, and people need managing. Budget for it.

• A lead who directs the work. An augmented developer with no one assigning and reviewing their work will be busy and unproductive. Plan three to five hours a week of a senior person’s time per augmented developer.
• Onboarding. Access, environments, coding standards, client context. The first week is rarely billable at full value, and you are paying for it anyway.
• Quality control. The provider vetted the person against a generic bar. You have to check them against your own. Run the first two weeks as a trial, with a contract clause that lets you swap the person without penalty.
• The client relationship. If your contract with the client restricts subcontracting, you need consent before an outside person touches the work. Check the master services agreement before you sign anything with a provider.

If the provider is in another country, the comparison in nearshore vs offshore applies in full. Hours of overlap matter more for augmentation than for any other model, because the person is supposed to work inside your team’s day.

The contract points that decide who wins

Staff augmentation agreements are short and look harmless. Five clauses carry nearly all of the commercial risk. Read them from whichever chair you are in.

Conversion fees

If the buyer hires the augmented person directly, the provider loses an employee and a revenue stream. A conversion clause sets the price for that.

If Client hires or directly engages any Provider personnel assigned under this Agreement, during the assignment or within twelve (12) months after it ends, Client will pay Provider a conversion fee equal to twenty percent (20%) of that person’s first-year base compensation. The fee reduces to ten percent (10%) once the person has been assigned to Client for twelve (12) consecutive months, and to zero after twenty-four (24) months.

As a seller, never sign without one. As a buyer, negotiate the step-down. A fee that falls over time is fair to both sides: the provider has earned its margin on a long placement, and the buyer has an honest route to hiring someone who has become central to the team. A flat fee with no step-down, or a clause that bans hiring outright, mostly produces resentment and workarounds.

Notice and term

Notice is the provider’s protection against the gap that destroyed the margin in the seller’s table above. It is also the buyer’s flexibility. Thirty days is the usual middle.

Points to settle:

• Notice to end an individual’s assignment. Thirty days is common. Buyers often get a shorter period, such as five business days, during the first two to four weeks so that a poor fit can be corrected quickly.
• Notice to reduce hours. A buyer who can cut a full-time person to ten hours a week without notice has a termination right under another name. Tie hour reductions to the same notice period.
• Minimum commitment. If the provider is recruiting specifically for the role, a three-month minimum is reasonable.
• Replacement. If the person resigns or is removed for cause, the provider should supply a replacement within a stated time and cover the overlap needed for handover at no charge.

Intellectual property

The buyer usually needs to own everything the augmented person produces, and often needs to pass that ownership on to its own client. That requires an unbroken chain of written assignments: from the individual to the provider, from the provider to the buyer, and from the buyer to the end client.

The chain breaks most often at the first link. The provider’s agreement with its own worker may be weak, missing, or governed by a country’s law that does not treat work product as belonging to the employer by default. Contractors are a particular risk, since in many places a contractor owns what they create unless a written assignment says otherwise.

Provider assigns to Client all right, title, and interest in all work product created by Provider personnel in the course of the Services, effective on creation. Provider represents that it has written agreements with all personnel sufficient to make this assignment, and will provide copies on request.

As a buyer, ask for the “provide copies on request” language and use it once. As a seller, check your own employment and contractor agreements before you make that representation. The full treatment of how ownership moves through an agency is in who owns the code.

Non-solicitation

Two non-solicits belong in an augmentation deal, and people often remember only one.

The first protects the provider’s staff from being hired away, and overlaps with the conversion clause. The second protects the buyer’s clients. An augmented developer working on your client’s project meets your client’s team, learns the account, and reports back to an employer who also sells development services. Without a clause, nothing stops the provider from pitching your client directly.

During the term and for twelve (12) months after, Provider will not solicit or accept work from any client of Client to which Provider personnel were introduced through the Services, except through Client.

Keep both non-solicits mutual in structure, limited to twelve months, and limited to the people and clients involved in the engagement. Broad restrictions are harder to enforce, and some jurisdictions restrict them heavily. Have a lawyer check the wording for your state or country.

Rates, timesheets, and increases

The rate clause should answer four questions. What is billable: hours worked, or a monthly flat fee? Who approves timesheets, and how long do they have before hours are deemed approved? Is there overtime, and at what rate? When can the rate go up?

For engagements longer than a year, an annual increase tied to a stated percentage or a published inflation index saves a difficult conversation. Sellers who leave this out end up giving their own employee a raise out of a margin that was already thin.

Also settle expenses, travel, the tools and licenses each side supplies, and what happens to hours the client disputes. A cap on the provider’s liability, set at the fees paid over some period, is standard and sellers should insist on it.

Classification and co-employment

When a person works full time under a buyer’s direction for a long period, a regulator or a court may ask whose employee they really are. In the US this is usually discussed as co-employment or joint employment, and misclassification of contractors carries tax and penalty exposure. The UK has its own rules on off-payroll working that can shift tax responsibility onto the end client. The details vary by jurisdiction and change, so treat this as a question for counsel. The practical protections are consistent everywhere: the provider handles pay, benefits, time off, and performance management, and the contract says so.

Where staff augmentation goes wrong

Most failures fall into a handful of patterns. I have been on the receiving end of all of them.

Nobody is managing the person. The buyer assumed the provider would manage, and the provider assumed the buyer would. The developer picks tickets off a board for three months and nobody notices that half the work has to be redone. Name the manager in the contract.

The person is treated as an outsider. No access to the planning meeting, no context on the client, a separate chat channel. They produce exactly what the ticket says and nothing more, because nobody told them why any of it matters. Augmented people do good work when they are treated as team members for the duration.

Knowledge walks out the door. The engagement ends on thirty days’ notice and the only person who understands the billing integration goes with it. Make documentation and handover part of the role from the first week, and review it monthly.

The work quietly grows. An augmented team has no scope document, so there is nothing to creep against. That sounds like freedom. In practice it means a buyer can run up six figures of hours without ever deciding to. Set a monthly budget and review it, the same way you would manage scope creep on a fixed project.

Hidden subcontracting. The provider you signed with has passed the role to a second firm, which has passed it to a freelancer. Rates have been marked up twice, the IP chain has two more links you have never seen, and the person you interviewed may not be the person doing the work. Require written consent for any subcontracting, and ask directly who employs the individual.

The seller forgets to sell. An agency with eight people placed on long engagements stops doing business development, because the revenue feels safe. Then two engagements end in the same quarter. Placement revenue ends on thirty days’ notice, so keep the pipeline moving even when everyone is billable.

The placement outlives its purpose. A six-month gap-fill becomes a three-year arrangement at a rate that made sense for six months. If you are the buyer and the role is now permanent, the cheaper and healthier move is to hire, either the person through the conversion clause or someone new. The guide to hiring remote developers covers that process.

How to decide

From the seller’s chair, sell augmentation when the rate covers your loaded cost with real margin, the contract has a conversion fee and thirty days’ notice, and the people you place are ones you could spare from project work. Decline it, politely, at any rate that only works if the placement never ends.

From the buyer’s chair, buy augmentation when you need a skill you already know how to manage, for a period you can roughly define, and you have a lead with time to direct the work. If you cannot manage the skill yourself, augmentation hands you a person you are unable to evaluate. That is a case for a managed team or a delivery partner.

In both chairs, read the five clauses before you look at the rate. The rate decides how much you make in a good month. The clauses decide what happens in a bad one.