The two vendors look identical on the quote sheet
Two firms answer the same request. Both send a deck with the same technology logos on slide four. Both propose three engineers with similar resumes. One quotes $185 per hour, the other $205. On the quote sheet the gap is eleven percent, which looks like a rounding decision. In delivery the gap is whether the program ends with a working system or with a stack of approved timesheets and a half-finished repository. The two firms are running different businesses that happen to describe themselves with the same forty words.
A staffing body shop sells qualified availability. Its product is a person who shows up, is competent, and follows direction. Its economics reward utilization: hours billed against hours available. Its risk is bench time, not technical outcome. When the schedule slips, the body shop has still delivered exactly what it sold, because it sold hours and the hours happened.
An engineering subcontractor sells a defined outcome. Its product is a component, a service, a model, a pipeline, a report that passes acceptance. Its economics reward efficiency: the fewer hours it takes to reach acceptance, the better the margin. Its risk is technical, and that risk is priced into the number on the quote. When the schedule slips, the engineering subcontractor eats the slip, because it sold the result and the result is late.
Both are legitimate businesses. Buying either one on purpose works fine. The expensive failure is buying one and expecting the other, which happens constantly because the marketing language is close to identical and because most buyers compare rates instead of comparing what the rate buys.
Test one: who owns the deliverable when it goes wrong
Ask the question in its ugly form. "The integration milestone is two weeks late and the cause is a design decision your engineer made in week three. What happens next?" Listen for whether the answer contains the word "we" attached to a remedy, or the word "we" attached to more hours.
The staffing answer sounds reasonable and is: the engineer worked the hours, followed the direction given, and the design call was made inside your program. More hours are available. The engineering-subcontract answer is different in kind. The rework is inside the price, the schedule recovery plan arrives with the explanation, and nobody is invoicing for the correction of their own defect.
Ownership has a second layer that buyers routinely skip, which is legal ownership of what gets produced. Under 17 U.S.C. § 101, a commissioned work qualifies as a work made for hire only if it falls into one of nine enumerated categories and there is a signed agreement saying so. Custom software is generally not in those nine categories. Absent a written assignment, the vendor's engineers wrote it and the vendor's employer owns the copyright, no matter who paid. On federal work the picture is set by data-rights clauses instead: FAR 52.227-14 gives the government unlimited rights in data first produced under the contract, DFARS 252.227-7014 governs noncommercial computer software for defense work and sets the government-purpose-rights default when development was mixed-funded, and DFARS 252.227-7018 carries the SBIR and STTR data protection period. A body shop rarely thinks about any of this because it does not believe it is producing an asset. An engineering subcontractor has to, because the asset is the product.
Risk carried by the vendor under a deliverable-based subcontract
Editorial weighting of where risk typically lands under a deliverable-based subcontract. Illustrative, not a measured statistic.
Test two: who writes the definition of done
This is the fastest of the four tests and it takes one email. Ask each vendor to send, before pricing, the acceptance criteria they would sign against.
One vendor sends a list of testable statements. Ingest rate at a stated volume. Extraction accuracy measured on a held-out set the buyer controls. Latency at a stated percentile under a stated load. Deployment into the buyer's environment with a named runtime and a named authentication path. Documentation sufficient for a new engineer to reproduce the build. The other vendor asks what the team should work on in the first sprint. Neither response is dishonest. They describe two different products.
Federal contracting already encodes this split and gives buyers vocabulary for it. FAR 37.102(a) makes performance-based acquisition the preferred method for services. FAR 37.601 says a performance-based contract shall include a performance work statement, measurable performance standards in terms of quality, timeliness and quantity, and the method of assessing performance against those standards. That is precisely the artifact a body shop cannot produce in advance, because measurable standards convert hours into obligations. A buyer in a commercial deal with no FAR obligations at all can still use the FAR 37.601 structure as a screening tool, and should.
Test three: does the work survive the person leaving
Every engagement eventually meets turnover. The senior engineer takes another offer in month five, gets pulled onto a hotter account, or goes on leave. Ask both vendors what happens in that week.
The staffing answer is a replacement resume and a two-week ramp that the buyer pays for. The replacement is often good. The problem is that the knowledge was never written down, because nothing in the contract required writing it down, and reconstructing it is billable. Buyers who have lived through this recognize the pattern: the second engineer takes six weeks to reach the productivity the first one had, and the invoice never dips.
The engineering answer is a list of artifacts that make replacement cheap. A repository with a README that takes a new engineer from clone to running system. Infrastructure defined in code rather than in someone's terminal history. Tests that encode the requirements. A short architecture decision record explaining why the design went one way instead of the other. A runbook for the failure modes already seen. Ask for a cold-start demonstration and put a number on it: how long does it take a new engineer, with no prior exposure, to stand the system up and get a passing test run. A vendor that answers "one afternoon" and can show it has already built the thing that makes turnover survivable. Federal solicitations reach for the same protection with key-personnel designations and substitution-approval requirements, but a clause naming a person is a weaker guarantee than a codebase that does not need that person.
Test four: what the contract actually buys
The contract type is the plainest signal available, and it is written on the first page.
A firm-fixed-price arrangement under FAR 16.202 sets a price that is not subject to adjustment on the basis of the contractor's cost experience. Cost risk sits with the vendor. A time-and-materials arrangement under FAR 16.601 acquires services on the basis of direct labor hours at fixed hourly rates, with materials at cost. FAR 16.601(c) allows it only when it is not possible at the time of award to estimate the extent or duration of the work with any reasonable confidence, FAR 16.601(d) requires a determination and findings saying no other type is suitable, and FAR 16.601(e) requires a ceiling price the contractor exceeds at its own risk. A labor-hour contract under FAR 16.602 is the same instrument with the materials stripped out, which is staff augmentation stated in its own terms.
There is a further line worth knowing, because it constrains what government buyers may do even when they want more control. FAR 37.104(a) defines a personal services contract as one characterized by the employer-employee relationship it creates between the government and the contractor's personnel, and agencies may not award one without specific statutory authority. FAR 37.104(c)(2) lists the descriptive elements that push an arrangement across the line: performance on a government site, principal tools and equipment furnished by the government, services applied directly to the agency mission, comparable services performed by civil servants, a need expected to last beyond one year, and work whose nature requires direct government direction. Read that list against a program built on staff augmentation and the tension is visible immediately. The deliverable-based subcontract keeps supervision inside the vendor, which is where the FAR wants it.
| Dimension | Staffing body shop | Engineering subcontractor |
|---|---|---|
| Unit of sale | An hour of a labor category | An accepted deliverable |
| Payment trigger | Approved timesheet | Acceptance against written criteria |
| Who defines done | The buyer, sprint by sprint | Both parties, in writing, before work starts |
| Who absorbs rework | The buyer, at the same rate | The vendor, inside the price |
| Turnover exposure | Buyer pays the ramp | Vendor covers continuity |
| Typical instrument | T&M or labor-hour (FAR 16.601, 16.602) | Firm-fixed-price by milestone (FAR 16.202) |
The cost picture is not the rate picture
Rate comparison is the wrong arithmetic, and it is the arithmetic most procurement spreadsheets are built to do. A staffing seat transfers supervision to the buyer. Someone on the buyer's side writes the tickets, reviews the pull requests, answers the design questions, unblocks the environment access, and carries the schedule. That someone is usually the most expensive engineer or program manager on the buyer's staff, and their time is not on the vendor's invoice.
Put a number on it before comparing. If a $185 seat consumes a quarter of a senior architect's week to stay productive, and that architect's fully loaded internal cost is $150 an hour, the true cost of the seat is closer to $222. Three seats consume most of a person. The eleven-percent rate gap in the opening paragraph is now inverted, and it was inverted before anyone discussed technical outcome at all.
On the federal side the pricing analysis is formal and the prime carries it. FAR 15.404-3 makes the prime contractor responsible for conducting price or cost analysis on its subcontracts, and FAR 15.403-4 triggers certified cost or pricing data above the $2 million threshold when no exception applies. Fixed-price subcontracts with defined deliverables are far easier to defend in that analysis than a stack of hourly rates with no bounded scope, because there is a thing being bought that an analyst can compare to something else.
Ask both vendors for the acceptance criteria they would sign against
One will send a list of testable statements with numbers in them. The other will ask what the team should work on first. That single reply sorts the field faster than any capability deck, any reference call, and any rate comparison.
Where the distinction becomes load-bearing on federal work
In commercial work the difference costs money. In federal work it can also cost compliance, which is why the structure deserves attention before award rather than after.
Limitations on subcontracting. On a small business set-aside for services, FAR 52.219-14 and 13 CFR 125.6 bar the prime from paying more than 50 percent of the amount received from the government to firms that are not similarly situated. Work performed by a similarly situated small business is excluded from that calculation. How the workshare is structured, and who it goes to, is a compliance fact and not a preference.
SBIR and STTR performance of work. Under 13 CFR 121.702 and the SBIR and STTR Policy Directive, the small business must perform at least two-thirds of the research effort in a Phase I SBIR and at least half in a Phase II. STTR splits differently: at least 40 percent by the small business and at least 30 percent by the single partnering research institution. A subcontractor whose contribution is a bounded, describable work package can be accounted for cleanly against those floors. A pool of hours that flexes month to month is much harder to defend if anybody asks.
Data rights and the deliverable trail. Rights follow what was delivered and how it was funded. If nobody wrote down what the deliverable was, the rights conversation at closeout has nothing to attach to. This is the quietest way a program loses control of its own software.
Accounting exposure. Time-and-materials billing rests on compliant timekeeping and labor distribution. DFARS 252.242-7006 sets the accounting-system criteria that include labor distribution, and hourly billing invites the kind of audit attention that milestone billing on accepted deliverables does not.
When a body shop is exactly the right buy
The honest version of this article has to include the cases where hours are the correct purchase, because there are several and a buyer who ignores them wastes money in the other direction.
- Surge on a system your team owns. The design is settled, the architecture is yours, and the only missing input is capacity.
- Cleared seats in a space you control. The work must happen inside your facility, on your network, under your direction, and no other structure fits.
- Deliberate knowledge retention. You want the institutional memory to stay in-house, so outside engineers work under your people by design.
- Genuinely unbounded discovery. The extent of the work truly cannot be estimated yet, which is the exact condition FAR 16.601(c) describes.
- Short-duration specialist input. Three weeks of a narrow expert to unblock one decision, where a deliverable wrapper adds paperwork and nothing else.
What makes those cases work is that the buyer is choosing them, has the management bandwidth to supervise, and has priced its own supervision. What breaks is buying seats while quietly expecting a system.
Run the whole test in one meeting
None of this requires a procurement overhaul. It requires four questions and about ninety minutes of preparation.
The four-question screen
Step six is the one people skip. A deliverable list that lives in a slide has no contractual weight. The same list in the statement of work, with acceptance criteria attached to each line and payment attached to acceptance, changes the vendor's incentives on day one.
Where we sit, and what we take
We take deliverable ownership. Not seats.
Precision Federal is an SBIR and STTR shop that builds production AI, ML, data and cloud systems, and we work as prime or as a subcontractor on federal, state and commercial programs. Our team is led by a former professor in technology who ranks in the Kaggle Top 200 out of more than 200,000 competitors, the top 0.1 percent, and holds seven cloud certifications, with twenty years building production systems for federal agencies across five consulting firms, three of them federal. Behind that sits a standing bench of named engineers, licensed professional engineers, and domain specialists across defense, health, energy, transportation and public-sector data. We are SAM.gov active, CAGE 1AYQ0, and JCP and DD-2345 certified.
What that means in a subcontract is specific. We write the acceptance criteria before we price the work, and we send them to you first. We quote a fixed price against those criteria wherever the scope admits it. Rework caused by our design decisions is ours. Continuity is ours: if an engineer rotates off, the replacement is our problem and our cost, because the repository, the tests, the infrastructure code and the runbook were built so that replacement is cheap. You get the artifacts, in your repository, on a schedule written into the agreement rather than promised in a meeting.
We will tell you plainly when hours are the better buy for your situation, and point you elsewhere for them. That answer costs us a deal now and a great deal less than a mismatched engagement costs both sides later.
Frequently asked questions
Staff augmentation sells hours of a labor category, and the buyer directs the work, defines done, and absorbs rework and turnover ramp. A deliverable-based subcontract sells an accepted result at an agreed price, with the vendor carrying technical risk, schedule risk to acceptance, and continuity. Both are legitimate. The mistake is buying the first and expecting the second.
Time-and-materials and labor-hour arrangements under FAR 16.601 and 16.602 buy hours at fixed rates against a ceiling. Firm-fixed-price under FAR 16.202 buys a result at a price not subject to adjustment for the contractor's cost experience. Contract type is the plainest signal on the page, and it is on page one.
On commercial work, absent a written assignment, the vendor's employer generally owns the copyright, because custom software rarely qualifies as a work made for hire under 17 U.S.C. § 101. On federal work the data-rights clauses control: FAR 52.227-14 for civilian agencies, DFARS 252.227-7014 for defense noncommercial software, and DFARS 252.227-7018 for SBIR and STTR data. Settle it in the agreement, not at closeout.
Add your own supervision cost to the hourly bid before comparing. Staff augmentation moves ticket-writing, code review, design decisions and schedule ownership onto your staff, and that time is real money that never appears on the vendor invoice. A quarter of a senior engineer's week is often enough to erase a twenty percent rate advantage.
Yes. FAR 52.219-14 and 13 CFR 125.6 cap what a set-aside prime may pay to firms that are not similarly situated, and 13 CFR 121.702 sets performance-of-work floors for SBIR and STTR awards. Bounded work packages are straightforward to account for against those floors. An open pool of hours is much harder to defend.