There is a persistent mischaracterization of OTA prototype authority inside federal program offices. It circulates as received wisdom, it shapes acquisition decisions, and it costs programs time they cannot recover. The mischaracterization goes like this: OTA is a procurement shortcut — a way to bypass competition requirements when you already know who you want to award to. It is legally risky, subject to protest, and best avoided unless the requirement genuinely cannot be met through normal FAR channels.
Every part of that characterization is wrong. And because it is wrong, program offices that accept it default to FAR Part 15 for commercial technology and AI acquisitions that OTA was specifically and deliberately designed to handle — adding 12 to 18 months to acquisition timelines for no reason other than a misread of the statute.
This piece is about what OTA prototype authority actually is, what the most common misreadings are, and what a program office needs to understand to use it correctly.
What OTA prototype authority actually is
Other Transaction Authority for prototype projects is authorized under 10 U.S.C. § 4022 for DoD agencies, with analogous civilian authority under various agency-specific statutes. It allows a federal agency to enter into a prototype agreement — an agreement that is not a contract under the FAR — with one or more parties to develop and demonstrate a prototype capability against a defined operational need.
The statutory definition of a prototype is deliberately broad. It includes proof-of-concept work, pilot programs, models, novel applications of commercial technology, and — critically for the current environment — software systems and AI capabilities. Congress expanded the prototype definition explicitly in NDAA FY2016 to ensure that software and AI systems qualified. The idea that OTA applies only to hardware or weapons systems is a pre-2016 read of the statute that has not been current for nearly a decade.
The critical feature of an OTA prototype agreement is not what it bypasses. It is what it creates: a statutory right to award a sole-source follow-on production contract to the successful prototype contractor, without re-competing the requirement. This is not a workaround. It is a congressionally granted right, explicitly created to give agencies a path from prototype to production without going back through full-and-open competition each time.
The five misreadings that stall OTA programs
Misread 1: OTA is a sole-source workaround and therefore risky
This is the most damaging misread because it inverts the legal reality. Under FAR, a sole-source award requires a Justification and Approval — a formal written document that must survive legal review and, above certain thresholds, public posting. The J&A creates protest exposure because it represents an exception to competition requirements that a disappointed offeror can challenge.
Under OTA, the sole-source follow-on production right is not an exception to competition. It is a statutory right created by Congress. There is no J&A required. There is no competition exception to justify. The legal basis for the sole-source award is the prototype agreement itself — and that agreement is not protestable on competition grounds because it is not a procurement under the FAR. The protest risk that program offices fear is substantially lower under OTA than under FAR sole-source, not higher.
Misread 2: OTA requires a statement of work
FAR acquisitions require a Performance Work Statement or Statement of Work because the procurement framework is built around specifying what you want before you solicit for it. OTA is not. An OTA solicitation defines an area of interest — a broadly stated operational problem or capability gap. It does not require a detailed SOW, a CDRL, or the specification-first thinking that governs FAR procurements.
This is not a procedural distinction. It reflects a fundamentally different acquisition philosophy. The traditional FAR approach assumes that the government knows what it needs in enough detail to specify it before procurement begins. For commercial AI and software capabilities that already exist, already work, and can be demonstrated in weeks, that assumption is both unnecessary and counterproductive. OTA replaces the specification-first approach with a problem-first approach: define the operational need, let commercial vendors propose solutions, and evaluate on demonstrated merit.
Misread 3: OTA only works for large defense primes
The opposite is true. OTA prototype authority was specifically designed to bring non-traditional contractors — commercial technology companies, software developers, AI researchers, and specialized service providers who have not been subject to full cost accounting standards coverage — into the federal acquisition ecosystem. The statute requires that the prototype effort either involve a non-traditional defense contractor as a significant participant, include a small business, or involve cost-sharing between the government and the contractor.
This requirement was not an accident. Congress wrote it to create a structural forcing function: agencies that want access to commercial AI and software innovation must engage with the commercial companies that built it, not just the large primes who aggregate and resell it. The OTA participation structure is more favorable to smaller, specialized commercial vendors than any other federal acquisition vehicle.
Misread 4: The prototype must be a physical deliverable
A prototype under OTA authority does not need to be a physical item. It does not need to be a hardware system, a device, or a tangible product. Software platforms, AI systems, data architectures, agentic workflow automation, decision-support tools, and governance frameworks all qualify as prototypes under the current statute — provided they can be demonstrated against a defined operational need and evaluated against agreed success criteria.
The practical implication is that an agency seeking to demonstrate a commercial ITFM platform, an AI governance capability, or an agentic process automation system can use OTA prototype authority to fund that demonstration. The fact that the deliverable is a configured software system rather than a physical prototype does not disqualify the effort from OTA authority.
Misread 5: Defining “successful prototype” is the government’s job alone
This is the misread that most often causes OTA programs to fail at the follow-on stage, even when the prototype itself succeeds technically. The definition of what constitutes a successful prototype — the criteria that, if met, trigger the sole-source follow-on production right — is negotiated between the government and the contractor as part of the prototype agreement. It is not unilaterally defined by either party.
Program offices that treat success criteria as a government-controlled specification, defined after the award and applied retroactively to evaluate the contractor's performance, create legal exposure and contractor disputes. Success criteria must be agreed upon before performance begins. They must be specific enough to be objectively evaluable. And they must reflect what the government actually needs the capability to demonstrate in order to justify moving to production — not a moving target that expands as the prototype progresses.
The follow-on production right: how it actually works
When a prototype is completed and the contracting officer determines that it meets the agreed success criteria, the procuring agency has the statutory authority to award a sole-source follow-on production contract to the prototype contractor. This authority exists under 10 U.S.C. § 4022(f). It requires no J&A, no competition justification, and no re-solicitation. The production contract may be issued as an OTA production agreement or as a FAR fixed-price contract, depending on the agency's preference. The prototype agreement is the sole legal basis for the award.
What a well-structured OTA prototype engagement actually looks like
A program office that understands OTA correctly approaches a commercial technology or AI acquisition differently from the first conversation. The acquisition planning question is not “how do we write a SOW for this?” It is “what operational problem are we trying to solve, and what would a successful demonstration of a commercial solution look like?”
The solicitation goes out as a Broad Agency Announcement or a sources-sought notice describing the operational need. Vendors respond with solution briefs, not full proposals. The government evaluates on merit, selects one or more vendors for prototype agreements, and negotiates the success criteria, IP rights, cost-sharing arrangements, and timeline as part of the agreement itself.
The prototype phase runs 60 to 120 days in most well-structured commercial technology efforts. The government evaluates the prototype against the agreed criteria. If it succeeds, the follow-on production agreement is awarded sole-source. The entire process — from initial solicitation to production award — can complete in under a year for a straightforward commercial capability. That timeline is not achievable under FAR Part 15 for anything approaching comparable complexity.
OTA prototype authority is not a workaround. It is the acquisition vehicle Congress designed for exactly the situation most program offices are in right now: trying to bring commercial AI and software capabilities into federal service quickly, with appropriate risk management, and without the 18-month overhead of full-and-open competition for capabilities that already exist and already work.
The IP question program offices avoid asking
One of the most consequential features of OTA prototype agreements is one that program offices rarely lead with: intellectual property rights are fully negotiable. Under FAR contracts, data rights and IP ownership are governed by a prescribed set of clauses — DFARS 252.227-7013 and related provisions — that default to government rights in technical data and computer software developed under the contract. These defaults are difficult to negotiate away and create significant IP risk for commercial technology vendors.
Under OTA, there are no prescribed IP clauses. The government and the contractor negotiate data rights, background IP ownership, and license terms as part of the prototype agreement. This means a commercial vendor can enter an OTA prototype agreement retaining ownership of its pre-existing IP and the improvements developed during the prototype — subject to whatever license terms are negotiated. For commercial technology companies evaluating whether to engage with federal procurement, this is often the deciding factor. OTA makes federal engagement viable for commercial vendors that would otherwise decline to participate because of FAR IP exposure.
For program offices, this means the OTA negotiation is not just about price and schedule. It is an opportunity to structure an IP arrangement that gives the agency the rights it actually needs — use rights for the capability, access to technical data for interoperability purposes, modification rights if required — without demanding ownership of the vendor's commercial IP and foreclosing the commercial relationships that make the technology viable over time.
Matter + Energy is a non-traditional defense contractor under 10 U.S.C. § 3014 — satisfying the OTA participation requirement directly, without a cost-sharing arrangement. If your program office is evaluating an OTA prototype approach for a commercial AI or technology capability, start a conversation →