Where the engagement stops and the work starts
A diagnostic ends well. The client agrees with the finding, the sponsor funds the next phase, and the question arrives that no deck answers: who builds it. An advisory firm has three responses and only three. Hire the engineers. Rent bodies from a staffing firm and supervise them. Or bring in a partner that takes an outcome and is accountable for it. Most firms pick by reflex and rationalize afterward, which is backwards, because the inputs are knowable before anyone commits: how repeatable the work is, what the firm's independence obligations permit, what contract the firm holds, and who owns the code at the end.
This is written for the person making that call, not for the engineer and not for the client. That person is weighing a permanent change to the firm's cost structure against a dependency on somebody else's delivery, under a deadline set by a client who has already been told the problem is solved.
What the firm is actually buying
A technical delivery partner is not a pool of hours with a different logo on it. Four distinct purchases are on the table, and a given engagement usually needs two of them, not all four.
Capacity that does not become a fixed cost. Engineering demand inside an advisory firm arrives in bursts tied to which clients said yes this quarter. Payroll does not arrive in bursts. A partner turns a step-function cost into a variable one, which moves a practice's margin more than the hourly rate does.
A single owner of the word "done." Staff augmentation leaves the definition of done with the buyer. A delivery partner takes acceptance criteria and answers for meeting them. That transfer is the whole product, and it is why the two arrangements are not price-comparable even when the hourly numbers look alike.
Separation the firm may be required to have. On federal work and on audit-adjacent commercial work, the party that advised is sometimes barred from building. That constraint is covered below, because it is the one most often discovered after a proposal is already out.
The first month and the last month. Standing up an environment and wiring identity and data access, then the closing stretch where the system has to pass security review, accessibility review, and handover. Both stretches eat calendar and use skills a strategy bench does not keep sharp.
Conditions that argue for a delivery partner over an internal bench
Editorial weighting, illustrative rather than measured. The last row is deliberately low: resale is the strongest case for owning the bench.
The arithmetic of an internal bench
An engineering bench is a fixed cost pointed at variable demand, and that sentence governs the economics. Cost per billable hour is not salary divided by 2,080. It is the fully loaded cost, including benefits, tooling, cloud accounts, recruiting, and the management time to keep four engineers pointed one direction, divided by the hours actually sold. A team selling sixty percent of its capacity carries roughly 1.67 hours of cost per hour billed. At forty percent it carries 2.5. That is the reciprocal of utilization, not an estimate, and it is what turns an apparently cheap internal team into the most expensive option a practice has.
Three second-order effects follow, and they compound. Hiring lead time for a senior engineer is measured in months, which means the bench answers the engagement after next, not this one. Skills decay when unused, so a team idled for two quarters is not the team that was hired. And an engineering bench sits awkwardly inside a pyramid built on associates and analysts, because the senior individual contributor worth hiring is not a person that model knows how to price.
None of that argues against ever building the bench. It argues for building it against a demand curve rather than a single client. Internal engineering earns its cost when the work repeats across accounts, when the same asset is sold more than once, or when the firm intends to hold a product rather than a practice. Then the fixed cost has a variable revenue stream underneath it and the arithmetic reverses.
On federal work, independence is a rule and not a preference
This is the part that surprises commercial practices moving into public sector work. In federal contracting, the question of whether the firm that advised may also build is answered by regulation, not by the client's comfort. FAR Subpart 9.5 covers organizational and consultant conflicts of interest, and FAR 9.505 states two underlying principles: "preventing the existence of conflicting roles that might bias a contractor's judgment," and "preventing unfair competitive advantage."
Two provisions do most of the work. FAR 9.505-1(a) says a contractor that provides systems engineering and technical direction for a system without having overall contractual responsibility for its development, integration, assembly and checkout, or production "shall not (1) Be awarded a contract to supply the system or any of its major components; or (2) Be a subcontractor or consultant to a supplier of the system or any of its major components." The second half is the one people miss. It closes the workaround of subcontracting quietly to whoever wins.
FAR 9.505-2 reaches the other common advisory posture. A contractor that prepares, or assists in preparing, a work statement to be used in competitively acquiring a system or services generally may not supply that system or those services, subject to stated exceptions for sole-source situations, development participants, and acquisitions involving multiple contractors. A contractor that prepares and furnishes complete specifications covering nondevelopmental items is barred from furnishing those items for a period covering at least the initial production contract.
The contracting officer is required to look for this early. FAR 9.504(a) directs contracting officers to analyze planned acquisitions to "identify and evaluate potential organizational conflicts of interest as early in the acquisition process as possible" and to "avoid, neutralize, or mitigate significant potential conflicts before contract award." Where a conflict exists and award is still in the government's interest, FAR 9.504(e) routes the matter to a waiver under FAR 9.503. A waiver is possible. It is not something to plan a pursuit around.
Two recent GAO decisions show agencies being held to a real investigation rather than a paragraph of assurance. In DirectViz Solutions, LLC, B-423366 et al., June 11, 2025, GAO sustained a protest alleging impaired objectivity where the awardee was concurrently performing a related task order that had it helping set standard operating procedures and reviewing performance across the same units whose work it would then execute; GAO found the Army's review inadequate rather than merely debatable. In Castro & Company, LLC, B-423689, November 13, 2025, GAO sustained again where the awardee would provide acquisition support and financial support services for the same office under two contracts. The lesson is not that conflicts are fatal. It is that the analysis has to exist in writing and survive someone reading both statements of work side by side.
One caveat on citation, because this area is in motion. On January 15, 2025 the FAR Council issued a proposed rule implementing the Preventing Organizational Conflicts of Interest in Federal Acquisition Act, Public Law 117-324, enacted December 27, 2022. It would remove FAR Subpart 9.5 and create a new Subpart 3.12 with defined terms for unequal access to information, impaired objectivity, and biased ground rules. Comments closed in March 2025 and the rule was not final as of this writing. Separately, the Revolutionary FAR Overhaul has been reissuing FAR parts through agency class deviations, and the Part 9 deviation text retains the 9.5 coverage. Confirm which deviation text the contracting activity uses before relying on a section number. The substance has held through both efforts.
Audit affiliation adds a second independence problem
A firm whose network includes an assurance practice carries a constraint that has nothing to do with procurement law. Under the SEC's auditor independence rule at Regulation S-X 2-01(c)(4), several categories of non-audit service are prohibited for an audit client, and financial information systems design and implementation is one of them. For that category and several others, the service is permissible only where it is reasonable to conclude the results will not be subject to audit procedures during the audit of the client's financial statements. Building the system that produces the numbers is exactly the fact pattern the rule contemplates.
On the government side, the 2024 revision of Government Auditing Standards, the Yellow Book, carries requirements and guidance on independence for auditors performing nonaudit services, including identification of services that always impair independence and services that ordinarily would not. It is effective for financial audits, attestation engagements, and reviews of financial statements for periods beginning on or after December 15, 2025, and for performance audits beginning on or after that date, with early implementation permitted. Firms subject to it had to design and implement a system of quality management by December 15, 2025, and to evaluate that system by December 15, 2026.
The practical consequence is the same in both regimes. When the build touches something the firm or an affiliate audits, it has to sit with a party outside the network, documented before the client's expectations are set. That is a scheduling problem more than a legal one. Found in week two it is an ordinary teaming decision. Found in week ten it is a broken commitment.
The contract you hold may not carry the build
Independence is not the only gate. Scope is. A firm on the GSA Multiple Award Schedule under SIN 541611, Management and Financial Consulting, holds a consulting instrument. Software design, development, and implementation sit under SIN 54151S, Information Technology Professional Services, aligned to NAICS 541512. Holding one does not give a firm the other. The ways through are to add the SIN, to place the build with a partner that holds it, or to move the work to a different vehicle. Only the second takes days rather than months.
Two more scope facts belong in the same check. FAR Subpart 37.2 governs advisory and assistance services and states plainly that such services "shall not be used in performing work of a policy, decision-making, or managerial nature which is the direct responsibility of agency officials" and shall not be used to bypass or undermine personnel ceilings, pay limitations, or competitive employment procedures. And if the firm is other than small on the applicable NAICS code and the award offers subcontracting possibilities, a small business subcontracting plan is required above the threshold, which the FAR Council's inflation adjustment raised to $900,000 effective October 1, 2025, with $2 million for construction of a public facility. A named technical partner with a real scope is better content for that plan than a percentage with nobody attached to it.
Check size status against the code on the solicitation rather than the code the firm prefers. The SBA receipts-based standard has stood at $24.5 million for NAICS 541611 and $34 million for 541512, and SBA proposed inflation increases to more than two hundred receipts-based standards in August 2025 that were not final as of this writing.
Four ways to get engineers, compared
The table is the decision in one view. The column that fits is rarely the same for two engagements in the same practice, which is the real argument for keeping more than one of these arrangements live.
| Dimension | Hire an internal bench | Staff augmentation | Technical delivery partner |
|---|---|---|---|
| Who owns "done" | The firm, through its own management line | The firm. The supplier owns attendance, not outcome | The partner, against written acceptance criteria |
| What you pay for | Capacity, whether or not it is sold | Hours, at a markup on a wage | A defined result, priced to scope or to a capped increment |
| Time to first working code | Hiring cycle plus onboarding, typically months | Weeks, then a ramp on the client's stack | Days to weeks, depending on environment access |
| Between engagements | The cost continues and utilization decides the margin | Contract ends; the knowledge leaves with the person | Cost stops; retain a support increment if continuity matters |
| Independence separation | None. The advisor and the builder are one entity | None. The staff work under the firm's direction | Real, if the partner holds its own scope and its own contract |
| Who owns the code | The firm, subject to the client agreement | Usually the firm, if the supplier agreement assigns it | Whoever the assignment clause names. Write it down |
| Typical failure mode | Utilization falls and the practice carries a bench | Nobody is accountable when the result misses | Bought as hours, then asked for an outcome nobody scoped |
What the firm keeps
The fear behind this decision is rarely economic. It is that the partner ends up owning the client. That risk is real and addressable, and the addressable part lies almost entirely in how the engagement is drawn.
The firm keeps the client relationship, the framing of the problem, the analysis and its methods, and the account plan. None of those transfer by building software. What has to be negotiated explicitly is attribution, the channel through which the partner talks to the client's engineers, and whether the partner is visible at all. On commercial work, delivering under the firm's brand is ordinary and a partner should expect a name-free posture. On federal work the calculus flips: a named subcontractor with a real, scored scope usually reads better than an anonymous resource pool, and concealing who did the technical work sits badly beside a key-personnel evaluation. Decide the posture before the proposal goes out, not after the client asks who wrote the code.
The clauses that decide the outcome
Most of what goes wrong in these arrangements was decided in the agreement and discovered in delivery. Check the following before signature.
- A present assignment of intellectual property, not just a work-made-for-hire recital. Under 17 U.S.C. § 101, a commissioned work qualifies as a work made for hire only if there is a written agreement and the work falls within one of nine enumerated categories. Software is a literary work and is not among the nine. A written present assignment of copyright is what transfers ownership; the work-for-hire language alone can leave a firm holding an implied license instead of title.
- Background intellectual property carved out, with a license back. Any partner worth engaging arrives with existing tooling. Name it, exclude it from assignment, and take a perpetual license to use it in the delivered system so a future maintainer is not blocked.
- Acceptance criteria written as tests rather than adjectives. "Accurate," "scalable," and "production-ready" are not acceptance criteria. A measured threshold on a named dataset, a latency number at a stated load, and a deployment that runs from a clean checkout are.
- Named people with committed percentages and a substitution path. Ask who specifically does the work, at what allocation, and what happens if the start slips a quarter. A stated constraint is planable. An optimistic resume is not.
- A mutual non-solicitation drafted to state law. The FTC's 2024 non-compete rule was set aside in litigation, the Commission acceded to that vacatur in September 2025, and the rule was removed from the Code of Federal Regulations in a February 2026 conforming action. Restrictive covenants are governed by state law and case-by-case enforcement, so the workable term is a narrow mutual non-solicit rather than a broad covenant.
- Security posture stated in writing, matched to the destination. For defense work, DFARS 252.204-7012 flows down to subcontractors handling covered defense information and carries the NIST SP 800-171 control set plus 72-hour incident reporting. The CMMC clause at DFARS 252.204-7021 exists, though the Department suspended the Phase 2 third-party assessment milestone in July 2026 pending a program review; the 7012 obligations were unaffected. Ask what is in place today rather than what is planned.
- Section 889 representations, insurance, and the ordinary paperwork. FAR 52.204-24 and 52.204-26 representations, professional liability and technology errors-and-omissions coverage at the limits the client contract requires, cyber coverage, and a certificate naming the right entity.
- Data handling written before the first extract. Where client data may live, who may touch production, whether any of it may train a model, and what gets destroyed at the end. Silence here is the fastest route to a legal review that stops the project.
- An exit that is a deliverable. Source, build pipeline, infrastructure as code, environment configuration, credential rotation, and a runbook, delivered as a condition of final payment rather than as a favor after it.
Five ways this goes wrong
The partner is bought as hours and then asked for an outcome. The most common failure. Hours were priced, so the partner staffed to hours, and the firm expected accountability it did not purchase. Decide which arrangement is being bought and price it that way.
The scope is written in adjectives. When acceptance is subjective, acceptance never arrives, and the engagement ends in an argument about whether the work was good rather than whether it met the criteria. Numbers in the statement of work prevent this.
Independence is checked after the proposal is out. The conflict analysis, the vehicle scope check, and the audit-affiliation check are cheap in week one and expensive in week ten. Run all three before a commitment reaches the client.
The pilot is built where it can never be deployed. A prototype standing on a personal cloud account with a copy of production data is a prototype that dies in security review. Build in the environment the system will live in, or against a stated accreditation path from the first sprint.
Knowledge leaves with the partner because nobody wrote the exit. A handover is a rehearsal, not a document. Someone on the receiving team should deploy the system while the partner watches, before the last invoice.
A first engagement structured to stay reversible
The best way to reduce the risk of an unfamiliar partner is sequencing rather than diligence. Make the first engagement small enough that ending it costs a few weeks and nothing else, and stage it so each step leaves something the firm keeps.
A first engagement, staged so each step is separable
What a useful first brief to a partner contains
Partners who deliver well are usually booked, and the brief is how a firm reaches the front of that queue. One page, answering the questions a competent engineer will ask in the first ten minutes anyway. What the client has already decided and funded. What system the result must live inside, named by product and version. What data exists, where it sits, and who can grant access. The security destination, including any accreditation the result must reach. The date that matters and what happens on it. The contract instrument. Who signs, and who can approve a scope change.
What to leave out: a formal proposal request before any technical conversation, and the problem described in the language of the deck rather than the language of the system.
Bottom line
This decision has four inputs and three are checkable in a week. Utilization arithmetic says whether an internal team can be carried between engagements. The independence rules say whether the firm is permitted to build what it advised, and on federal work they reach the subcontract as well as the prime position. The vehicle says whether the instrument the firm holds can carry a software build at all. Only the fourth input, whether this particular partner delivers, needs judgment, and a small, staged first engagement is how a firm buys that judgment cheaply. Running all four before the client is given a date removes most of what goes wrong.
Frequently asked questions
It depends on whether the demand repeats. A bench is a fixed cost against variable demand, and cost per billable hour is the fully loaded cost divided by hours actually sold, so a team selling sixty percent of its capacity carries about 1.67 hours of cost per hour billed. Hire when the work repeats across accounts or the same asset is sold more than once. Bring in a partner when the build is one-time, the deadline is shorter than a hiring cycle, or independence rules bar the firm from building what it advised.
Often not. FAR 9.505-2 provides that a contractor that prepares or assists in preparing a work statement for a competitive acquisition generally may not supply that system or those services, subject to stated exceptions. FAR 9.505-1(a) bars a contractor providing systems engineering and technical direction without overall contractual responsibility from supplying the system or its major components, and from being a subcontractor or consultant to a supplier of it. FAR 9.504(a) requires the contracting officer to identify and evaluate these conflicts as early in the acquisition process as possible.
Not automatically. Under 17 U.S.C. § 101 a commissioned work qualifies as a work made for hire only if there is a written agreement and the work falls within one of nine enumerated categories, and software does not. A written present assignment of copyright is what transfers ownership from an independent contractor. Pair it with a named carve-out for the partner's pre-existing tooling and a perpetual license back to use that tooling in the delivered system.
It depends on the destination. On commercial work, delivering under the firm's brand is ordinary and a partner should expect to be name-free. On federal work, a named subcontractor with a defined and evaluated scope generally reads better than an anonymous resource pool, and key-personnel evaluation makes concealment awkward. Decide before the proposal goes out; changing posture afterward raises questions that are hard to answer well.
The funded decision, the target system named by product and version, the data and who grants access to it, the security or accreditation destination, the date that matters, the contract instrument, and the person who can approve a scope change. A partner given those seven can return a scoped, priced statement of work quickly. A partner given a deck spends two weeks reconstructing them.