--- title: "OTA Prototype Authority: What PMs Get Wrong — ME Insights" description: Most program offices treat OTA as a contracting workaround. It's a congressionally designed strategy for acquiring commercial AI and software now. image: https://www.matternenergy.com/hubfs/matter-energy/og-default.jpg --- [![Matter + Energy home](https://www.matternenergy.com/hs-fs/hubfs/matter-energy/logo/me-logo-horizontal.png?width=273&height=32&name=me-logo-horizontal.png)](https://www.matternenergy.com/) - [Home ▾](https://www.matternenergy.com/) [Who we are](https://www.matternenergy.com/company) [Technology Ecosystem](https://www.matternenergy.com/technology-ecosystem) [Teaming & Partnerships](https://www.matternenergy.com/teaming) - Solutions ▾ [Overview](https://www.matternenergy.com/solutions) [Technology Value Management](https://www.matternenergy.com/it-financial-management) [AI Adoption & Productivity](https://www.matternenergy.com/solutions/ai-adoption-productivity) - Services ▾ [Our Approach](https://www.matternenergy.com/services) [Maturity Assessment](https://www.matternenergy.com/services/maturity-assessment) [Proof of Value](https://www.matternenergy.com/services/proof-of-value) [Integration & Data Architecture](https://www.matternenergy.com/services/integration-data-architecture) [Retained Operations](https://www.matternenergy.com/services/retained-operations) - Government ▾ [Federal Capabilities](https://www.matternenergy.com/government) [Commercial Solutions Openings (CSO)](https://www.matternenergy.com/government/commercial-solutions-offerings) [OTA & Rapid Prototyping](https://www.matternenergy.com/government/rapid-prototyping) [Solutioning as a Service™](https://www.matternenergy.com/solutioning-as-a-service) [Book a Lab Session](https://www.matternenergy.com/schedule-lab-sessions) - [Insights](https://www.matternenergy.com/insights) - [Events](https://www.matternenergy.com/events) [Schedule a Call](https://www.matternenergy.com/discovery) [![Matter + Energy home](https://www.matternenergy.com/hs-fs/hubfs/matter-energy/logo/me-logo-horizontal.png?width=205&height=24&name=me-logo-horizontal.png)](https://www.matternenergy.com/) Home ▾ [Home](https://www.matternenergy.com/) [Who we are](https://www.matternenergy.com/company) [Technology Ecosystem](https://www.matternenergy.com/technology-ecosystem) [Teaming & Partnerships](https://www.matternenergy.com/teaming) Solutions ▾ [Overview](https://www.matternenergy.com/solutions) [Technology Value Management](https://www.matternenergy.com/it-financial-management) [AI Adoption & Productivity](https://www.matternenergy.com/solutions/ai-adoption-productivity) Services ▾ [Our Approach](https://www.matternenergy.com/services) [Maturity Assessment](https://www.matternenergy.com/services/maturity-assessment) [Proof of Value](https://www.matternenergy.com/services/proof-of-value) [Integration & Data Architecture](https://www.matternenergy.com/services/integration-data-architecture) [Retained Operations](https://www.matternenergy.com/services/retained-operations) Government ▾ [Federal Capabilities](https://www.matternenergy.com/government) [Commercial Solutions Openings (CSO)](https://www.matternenergy.com/government/commercial-solutions-offerings) [OTA & Rapid Prototyping](https://www.matternenergy.com/government/rapid-prototyping) [Solutioning as a Service™](https://www.matternenergy.com/solutioning-as-a-service) [Book a Lab Session](https://www.matternenergy.com/schedule-lab-sessions) [Insights](https://www.matternenergy.com/insights) [Events](https://www.matternenergy.com/events) [Schedule a Call](https://www.matternenergy.com/discovery) [Home](https://www.matternenergy.com/)/ [Insights](https://www.matternenergy.com/insights)/ [Perspectives](https://www.matternenergy.com/insights#perspectives)/ OTA Prototype Authority Federal Acquisition # OTA Prototype Authority: *What Program Managers Get Wrong* Most program offices treat OTA as a contracting workaround. It is not. It is a congressionally designed acquisition strategy for exactly the kind of commercial AI and software capabilities agencies are trying to deploy now — and the misread costs programs 12 to 18 months they do not have. Matter + Energy ◆ Federal Practice ◆ 7 min read ◆ March 9, 2026 There is a persistent mischaracterization of OTA prototype authority in parts of the federal acquisition community. 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. Much of that characterization misreads the statute. Overly narrow readings of prototype authority can cause eligible prototyping approaches to be overlooked for commercial technology and AI efforts. 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 statute's definition is deliberately broad. Under 10 U.S.C. § 4022(e), a prototype project includes a proof of concept, model or process (including a business process), a pilot or novel application of commercial technologies for defense purposes, and agile development activity. Software, data and AI capabilities fit comfortably within it. The idea that OTA applies only to hardware or weapons systems is an outdated reading. The feature program offices most often overlook is what can follow. When a competitively awarded prototype is successfully completed, and the agreement provides for it, the agency may award a follow-on production contract or transaction without further competition (§ 4022(f)). Congress built that path in, and it works only if the prototype is structured for it from the start. § 4022(e) Prototype projects include business processes and commercial technology pilots § 4022(f) Follow-on production when the statute's conditions are met ## 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. OT agreements are not FAR contracts, so the FAR's Justification and Approval process for sole-source contracts doesn't apply to them. That doesn't make them protest-proof or condition-free: GAO has sustained a protest of a follow-on production OT that didn't meet the statute's conditions (*Oracle America*, B-416061, 2018). The protection is structure, not exemption: compete the prototype, write the follow-on into the agreement, and document successful completion against criteria agreed up front. ### 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's participation conditions (§ 4022(d)) can be met when a nontraditional defense contractor participates to a significant extent, when all significant non-government participants are small businesses or nontraditional defense contractors, or through a one-third cost share. The structure was built to bring commercial and smaller companies into defense work, alongside the large primes. ### 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 can all qualify as prototypes, provided the project is directly relevant to enhancing mission effectiveness, as § 4022(a) requires, and can be 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 determine whether the prototype was successfully completed, which is one of the conditions for any follow-on award — 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. How follow-on production actually works Under § 4022(f), a follow-on production contract or transaction may be awarded without further competitive procedures when the prototype agreement was entered into using competitive procedures, the participants successfully completed the prototype project, and the agreement provided for a follow-on. The award remains the government's decision, subject to the approvals DoD requires. The production award may be an OT or a FAR contract. ## 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 opportunity is announced through a competitive call that describes the need, such as a consortium request or a CSO-style solicitation used to award prototype OTs. That format is distinct from a FAR-based Commercial Solutions Opening contract under 10 U.S.C. § 3458; the two are separate authorities. 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 is scoped to the problem, often in months rather than years. The government evaluates the prototype against the agreed criteria. If it succeeds and the agreement provides for it, the agency can move to a follow-on production award without re-competing. > OTA prototype authority is not a workaround. It is an authority Congress designed for bringing commercial AI and software capabilities into defense use with appropriate risk management. ## 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 terms are negotiated rather than prescribed. Under FAR-based DoD contracts, DFARS clauses such as 252.227-7013 set the government's license rights by default. OT agreements don't carry those clauses automatically, so the parties negotiate data rights, background IP and licenses in the agreement. A commercial vendor can negotiate to protect its pre-existing IP and set terms for improvements. For commercial technology companies weighing federal work, this can be the deciding factor. 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 nontraditional defense contractor as defined in 10 U.S.C. § 3014 and an SBA-certified small business, both relevant to the participation conditions in § 4022(d). If your program office is evaluating an OTA prototype approach for a commercial AI or technology capability, [start a conversation →](https://www.matternenergy.com/contact) About this article The perspectives and analysis presented in this article represent Matter + Energy's own interpretation and are intended for informational purposes only. We make no representations as to the accuracy or completeness of any information here, and shall not be held accountable for any errors or omissions. Readers should conduct their own due diligence before relying on any information for operational or investment decisions. Contents What OTA authority actually is Five misreadings Not a sole-source workaround No SOW required Non-traditional contractor Software qualifies Success criteria The IP question Key Point § 4022(e) Prototype projects include business processes, commercial technology pilots and agile development. Statute **10 U.S.C. § 4022** — OTA Prototype Authority, DoD. Follow-on production under § 4022(f), when its conditions are met. **10 U.S.C. § 3014** — Nontraditional defense contractor definition. **10 U.S.C. § 4022(e)** — Definition of a prototype project. [DoD OTA Guide 2023 →](https://www.acq.osd.mil/asda/dpc/cp/policy/docs/guidebook/DoD%20OT%20Guide%20(July%202023)%20-%20508%20Update_11Jul2025.pdf) Related Page Matter + Energy's OTA & Rapid Prototyping page covers our approach: defining the need, building and validating, and informing the production decision. [View OTA & Rapid Prototyping →](https://www.matternenergy.com/government/rapid-prototyping) Next Perspective The Best Solution Is the One That Fits the Problem [Read next](https://www.matternenergy.com/insights/best-solution-fits-the-problem) [![Matter + Energy home](https://www.matternenergy.com/hs-fs/hubfs/matter-energy/logo/me-logo-horizontal-white.png?width=239&height=28&name=me-logo-horizontal-white.png)](https://www.matternenergy.com/) - [Company](https://www.matternenergy.com/company) - [Solutions](https://www.matternenergy.com/solutions) - [Services](https://www.matternenergy.com/services) - [Government](https://www.matternenergy.com/government) - [Teaming](https://www.matternenergy.com/teaming) - [Insights](https://www.matternenergy.com/insights) - [Careers](https://www.matternenergy.com/careers) - [Contact](https://www.matternenergy.com/contact) - [Privacy](https://www.matternenergy.com/hubfs/ME-Privacy-Policy.pdf) - [Terms of Use](https://www.matternenergy.com/hubfs/ME-Terms-of-Use.pdf) - [Lab Session Terms & Conditions](https://www.matternenergy.com/hubfs/ME-Lab-Session-Terms.pdf) © 2026 Matter + Energy. All rights reserved. ```json { "@context" : "https://schema.org", "@type" : "Article", "author" : { "@type" : "Organization", "name" : "Matter + Energy", "url" : "https://www.matternenergy.com" }, "dateModified" : "2026-09-20", "datePublished" : "2026-03-09", "headline" : "OTA Prototype Authority: What Program Managers Get Wrong", "image" : { "@type" : "ImageObject", "height" : 630, "url" : "https://www.matternenergy.com/hubfs/matter-energy/og-default.jpg", "width" : 1200 }, "mainEntityOfPage" : "https://www.matternenergy.com/insights/ota-what-program-managers-get-wrong", "publisher" : { "@type" : "Organization", "name" : "Matter + Energy", "url" : "https://www.matternenergy.com" }, "url" : "https://www.matternenergy.com/insights/ota-what-program-managers-get-wrong" } ``` ```json { "@context" : "https://schema.org", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://www.matternenergy.com/", "name" : "Home", "position" : 1 }, { "@type" : "ListItem", "item" : "https://www.matternenergy.com/insights", "name" : "Insights", "position" : 2 }, { "@type" : "ListItem", "item" : "https://www.matternenergy.com/insights/ota-what-program-managers-get-wrong", "name" : "OTA Prototype Authority", "position" : 3 } ] } ```