Staff augmentation vs body shopping looks like a distinction without a difference: in both, a vendor supplies engineers who work on your projects. The difference is what the vendor stands behind. A body shop sells hours from whoever is available and walks away from the outcome. A real staff augmentation partner screens hard, matches people to your stack, and takes responsibility when an engineer doesn't work out. Same contract shape, very different deal. Here is how to tell which one you are talking to.
Key Takeaways
- "Body shopping" started as a description of Indian IT firms placing programmers at client sites in the 1980s and 1990s, and it is now mostly used as an insult.
- The model is identical on paper. The differences are vetting, matching, accountability and how the engineers are treated.
- Five questions in the first sales call will tell you which kind of vendor you have.
- Some body shops are fine for low-risk work. They are a bad fit for senior engineers inside your core product.
Where the term comes from
Wikipedia describes body shopping as "the practice of consultancy firms recruiting workers (generally in the information technology sector)" and contracting them out, and notes that the firms involved insist they provide real services rather than "the 'sham' of merely farming out professionals" (Wikipedia). The article itself carries a neutrality warning, which tells you how loaded the term is.
The history is more specific. In his book on Indian IT, Dinesh C. Sharma writes that sending programmers to work on the customer's computers at the customer's site "became a dominant way of doing software business in the 1980s," and that "the industry gave this model the name of 'body shopping'." The contracts were "short-term (6 to 18 months), and low in risk, value addition and investment," and "a high margin business" (YaleGlobal excerpt). Wikipedia dates the big IT wave to the mid-1990s, when Y2K created demand for mainframe and COBOL skills.
Anthropologist Xiang Biao's study of the system, Global "Body Shopping" (Princeton University Press), describes another feature: workers kept idle on "the bench" between projects, waiting for the next placement.
So the original complaint was precise. The vendor added little beyond the person, took little risk, and treated engineers as inventory.
We use the word bench too, so here is the difference that matters: an engineer appears on ours only after passing both of our evaluations and confirming in the last 30 days that they are available, and you choose who joins your team.
Staff augmentation vs body shopping: the five differences
| Body shop | Staff augmentation partner | |
|---|---|---|
| Vetting | Resume match, maybe one call | Structured technical assessment before you see anyone |
| Matching | Whoever is free this week | Matched to your stack, seniority and time zone |
| Accountability | Hours delivered | A replacement guarantee and a named person who owns the relationship |
| Engineer treatment | Interchangeable inventory, often swapped without notice | Stable assignment, the same engineer for the engagement |
| Transparency about who you get | Bait and switch is common: the senior in the interview, a junior on the work | The engineer you interviewed is the one who joins |
None of these differences show up in the contract title. Both call themselves staff augmentation, team extension or IT staffing. You find out in how they answer questions.
Five questions to ask in the first call
1. "What does your technical screen consist of, and what fails it?" A real answer has a format, a scoring rubric and a pass rate. "We have a rigorous process" with nothing behind it is a warning. For reference, our own process is a graded coding assessment (pass at 70 out of 100) and an AI-led technical interview (pass at 3.0 out of 5), and about 1 in 5 applicants clear both.
2. "Will the engineer I interview be the engineer who does the work?" Ask to have it in writing.
3. "What happens if the engineer underperforms in the first two months?" Look for a defined replacement process with a time limit, not "we'll talk."
4. "How long have your engineers been with you, on average?" High churn means you will be onboarding someone new every few months.
5. "Can I talk to a client who has used you for more than six months?" Body shops tend to have short engagements and few long references.
If you want a longer list, I wrote about staff augmentation red flags and how to evaluate a staff augmentation provider.
A Concrete Version
Two vendors pitch you for a senior React engineer. Both quote a similar monthly rate.
Vendor A sends six resumes within an hour. You interview two. The one you pick is strong. Five weeks in, just as the engineer understands your codebase, the vendor rotates them to a bigger client and sends a replacement you never interviewed. Three weeks after that, you have spent 20 hours of your senior engineer's time reviewing pull requests that miss the point. The vendor offers another resume.
Vendor B sends three profiles two days later, each with a coding score, interview notes and a clear seniority call. You interview two, pick one, and that engineer starts. When a problem shows up in week five, the vendor has a written process: a cure period, then a replacement from a new shortlist.
Same rate, same contract name. Vendor A cost you a month and roughly 20 hours of senior review time. That is body shopping, whatever the website says.
The Honest Counterpoint
Body shops are not always the wrong choice. If you need ten people to run manual QA scripts or migrate content for six weeks, and the work is well defined and easy to check, a cheap vendor that supplies warm bodies may be exactly right. You are buying hours, and hours are what they sell.
The risk grows with the seniority and the blast radius of the work. A junior on a scripted task is low risk. A senior engineer with production database access is high risk. That is where vetting and accountability are worth paying for.
It is also fair to say that the label gets thrown at vendors who don't deserve it. Plenty of large IT services firms started with the onsite model and built real engineering organizations. Judge the vendor in front of you by the five questions, not by the country it is in.
Frequently Asked Questions
What is body shopping in IT?
Body shopping is a term for IT consultancies that recruit programmers and place them at client sites, adding little beyond the person. It describes the onsite outsourcing model of Indian IT firms in the 1980s and 1990s, and today it is mostly used to criticize vendors that sell hours without vetting or accountability.
Is staff augmentation the same as body shopping?
The contract structure is the same: a vendor supplies engineers who work under your direction. The difference is what the vendor does before and after the placement: technical vetting, matching to your stack, keeping the same engineer on your project, and replacing anyone who doesn't perform. See what is staff augmentation for the full definition.
How do I avoid a body shop when hiring developers?
Ask how the technical screen works and what fails it, get the "same engineer" promise in writing, and check for a replacement clause with a time limit. Then interview the engineers yourself, even if the vendor has already screened them.
The Bottom Line
The label matters less than the behavior. A vendor that vets hard, keeps the engineer you chose, and stands behind the placement is doing staff augmentation. One that sells whoever is free is a body shop, whatever it calls itself. If you want to see what a vetted shortlist looks like, request one or read how we vet.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
