Buy staff augmentation when you already have a lead who will direct the person every day: what they work on, how they do it, and whether the result is acceptable. Buy a dedicated team when you have sold the work and you do not have that lead. The difference is not a rate card. It is who holds the right to control the work, which is the same test US acquisition law and the IRS use to decide whether a contractor is really somebody else's employee. Get the choice wrong and you have either rented a manager you did not need, or handed your client a relationship you can no longer run yourself.
Agencies shop these as if they were two labels for one bench. They are two different allocations of control, plus a third thing that is neither. Staff augmentation is a person inside a method you already operate. A dedicated team is a named group with its own lead, still in your repositories and under your brand, whose lead directs the engineering because you cannot. A fixed-outcome subcontract is a result you accept or reject, without directing the people who produce it. Most of the pain in a white-label engagement comes from buying the first while needing the second, or from buying the second and then directing the individuals anyway until the client can no longer tell who works for whom.
The cleanest statement of that line is not a vendor's. The Federal Acquisition Regulation defines a personal services contract as one "characterized by the employer-employee relationship it creates" between the government and the contractor's personnel, and it tells agencies not to award one unless a statute specifically allows it. The relationship arises, the regulation says, when "as a result of (i) the contract's terms or (ii) the manner of its administration during performance, contractor personnel are subject to the relatively continuous supervision and control of a Government officer or employee." The sentence immediately after is the part agency principals miss: "giving an order for a specific article or service, with the right to reject the finished product or result, is not the type of supervision or control that converts an individual who is an independent contractor into a Government employee" (US Federal Acquisition Regulation, 37.104 Personal services contracts). Continuous direction of the person is one purchase. Accepting or rejecting the result is another.
The same section gives six descriptive elements for judging whether a contract is personal in nature. Performance on the buyer's site. Principal tools furnished by the buyer. Services applied directly to the buyer's own integral effort. Comparable work already done by the buyer's own staff. A need that can reasonably be expected to last beyond one year. And an inherent need for the buyer to direct the contractor's employees in order to protect its interest or keep responsibility for the function. You are not the federal government, and this is not legal advice — take the clause to your counsel before you treat it as a rule for your MSA. It is still the most precise published test there is for the thing agencies call staff augmentation, because staff augmentation is continuous supervision by design. A dedicated team that you direct individual by individual, on your laptop, against your backlog, for eighteen months, has wandered into the same shape even if the proposal said "team."
The tax version of the test does not care what the proposal said either. The IRS groups the evidence into three categories and tells you to weigh all of them: behavioural control, meaning whether you control or have the right to control what the worker does and how; financial control, including how the worker is paid, whether expenses are reimbursed, and who provides the tools; and the type of relationship, including written contracts, benefits, whether the relationship will continue, and whether the work is a key aspect of the business. No one factor decides it. A remote worker is not a way out: "An individual working remotely, for example, performing services for you from a location other than an office operated by you, is your employee under the common-law rules, if you can control what will be done and how it will be done. This is so even if the worker can choose to work remotely" (US Internal Revenue Service, Independent contractor (self-employed) or employee?, page last reviewed 19 May 2026). Distance is not independence. The right to direct the method is.
None of that makes a staff-augmentation placement a disguised employee, or a dedicated team automatically safe. Classification depends on the whole relationship, and this is not a determination you should reach from a blog post. The useful question, which the regulation says is always the key one, is whether you will exercise relatively continuous supervision and control. If yes, call it staff augmentation and staff the lead who will do that supervision. If no, because you sold an AI build and nobody in your firm can review it, do not buy a directed individual and hope. Buy a team whose lead can.
The statistical agencies already measure the directed version as its own category, which is useful because the industry vocabulary is not. In July 2023 the Bureau of Labor Statistics counted 862,000 workers provided by contract firms on their sole or main job, 0.5 percent of total employment, about the same share as in May 2017. It defines them as people who "work for companies that provide workers or their services to other organizations under contract, are usually assigned to one client at a time, and usually work at the client's place of business." Of those contract-firm workers, 22.5 percent were also contingent on that job — they did not expect it to last, or it was temporary (US Bureau of Labor Statistics, Contingent and Alternative Employment Arrangements, July 2023, released 8 November 2024). Read the definition slowly. Assigned to one client. Working at that client's place of business. Often temporary. That is staff augmentation as a labour statistic, not as a slide. It is a poor description of a team that brings its own lead, works in your repositories from another country, and is judged on a result your project manager accepts.
So the buying rule is short. Choose staff augmentation when three things are already true: you have a lead who can reject a pull request on the merits, the client's technical questions still come to you, and the seat is not a permanent job wearing a subcontract. Choose a dedicated team when the first of those is false and the second must stay true. The lead has to sit somewhere. If it cannot sit with you, it sits with the partner, and your project manager still owns the client, the date and the acceptance. Choosing a directed individual in that situation does not save money. It moves the review onto someone who cannot do it, which means the review moves to your client, which is how a subcontract becomes a second vendor.
What does not change between the two, if the partner is actually a subcontractor and not a body shop, is the commercial shell. The work lives in your repositories from the first commit. Your project manager runs the client. The engineers use your email domain and your tracker, or they are not introduced at all. Non-solicit, non-circumvention, the NDA and the data-processing terms are signed before anyone has access, and the intellectual property assigns to you. A replacement has a clock on it — in our case a two-week replacement guarantee, the same terms on a white-label placement as on staff augmentation — so a bad fit is a swap rather than a quarter you have to explain. Those are terms, not a claim about how many times we have used them. A white label software development partner who will not put them on your paper is selling you a team that can become your competitor. The model, dedicated or augmented, does not fix a contract that leaves the client relationship unspoken.
The failure mode that actually costs the account is the same in both models, and it is not poaching. A client leaves when every technical answer is being given by someone you cannot replace in the room. They do not leave because they once saw an unfamiliar email address. If you bought staff augmentation, that drift means your lead stopped leading. If you bought a dedicated team, it means you let the partner's lead become the client's lead. Who your client trusts when you subcontract is that problem in full. The fix is not a harsher non-solicit. It is a weekly conversation you can still hold without the delivery team present, and a scope you would sign your own name under.
The clauses that make the shell true are a different document from the staffing model. A work-for-hire sentence does not, by itself, make you the author of a software build. What belongs in a white-label subcontract is the assignment chain. Buy either model on a contract that skips it and you have rented the output. The control test will not save you at an acquisition if you cannot show title.
Some engagements are neither model. Your client has forbidden subcontracting and you want the engineers described as your employees. That is a misrepresentation, and we will not do it. You want the partner to own the client relationship. That is a referral, not a subcontract. You want the cheapest hourly seat. Directed juniors are a real product in the labour market measured above; they are a bad product when what you sold is a production AI system, because a review you cannot perform does not get cheaper when the person being reviewed does. And you need someone in your office five days a week. Continuous on-site direction is the first element on the FAR list. It is not a remote team with a weekly acceptance meeting.
You also cannot diligence this choice by asking for another agency's client. Engagements of this kind sit under the same non-disclosure we would sign with you, so they are not on this site, and a partner willing to publish the last agency's customer in order to win you will publish yours to win the next one. What can be shown is direct work, under our own name. Haystack, an AI search platform across documents, data lakes and repositories, was built that way: real-time indexing, structured and unstructured data in one layer, the search path designed for load rather than for a demo corpus. It is not an agency subcontract and it should not be read as one. It is evidence that the engineering in the dedicated-team case — the work your bench has not shipped — is a discipline we practise in public, while the agency engagements stay private because that is the term.
Price follows the control, which is why a rate card published in the abstract is a trap. Staff augmentation is a day rate or a month against a named person whose seniority you interviewed. A dedicated team is the same arithmetic across the people the lead needs, still agreed before the work starts, so you can put a fixed number under the statement of work you have already sold. Neither is a shared upside and neither is a published rack rate. Pricing states the model and not a number, on purpose: the number depends on the seniority and the hours, and a number printed here would be the wrong one for the scope you are about to describe. Markup is your business. The input cost has to be a figure you can hold still.
On Monday, before you ask anyone for a proposal, write four answers. Who can reject a pull request on this work without asking the client or the partner? Who answers the client's technical question on the next call? Whose tools are in use, and who has the right to direct the method rather than only to accept the result? If the project ended in ninety days, would this seat still be here in fourteen months? Staff augmentation is the right buy when the first answer is a lead of yours, the second answer is you, the third answer is your direction, and the fourth answer is no. A dedicated team is the right buy when the first answer is not yours and the second answer must remain you. If the second answer is already the partner, you do not have a staffing problem. You have given the relationship away, and changing the label on the invoice will not bring it back.
Find this useful? Tell Google to show you more of it.