Other Transaction Authority for Software Programs

Other Transaction Authority has become one of the most significant tools in DoD's software acquisition toolkit. Unlike traditional FAR-based contracts, OTA agreements can be structured and awarded with fewer administrative requirements, making them attractive for technology-forward programs and for companies that have commercial technology to offer.

Understanding what OTA is — and more importantly what it requires from a technology delivery standpoint — helps defense technology companies position their capabilities for this acquisition pathway.

What OTA Actually Is

Other Transaction Authority is a specific statutory authority granted to DoD agencies by Congress (10 U.S.C. § 4021 and related sections) that permits agreements outside the Federal Acquisition Regulation. OTAs are not contracts — they are "other transactions" that can be structured with more flexibility than traditional procurement vehicles.

Two primary OTA types matter for software programs:

Prototype OTAs: Agreements for research and development of prototype systems or technologies. The threshold for a sole-source prototype OTA is $100 million; competitive prototypes can go higher. Prototype OTAs do not require a standard FAR contract, certified cost or pricing data, or the full weight of procurement regulations.

Follow-on Production OTAs: If a prototype OTA results in a successful prototype, the sponsoring agency can award a follow-on production agreement without competitive procedures — provided this follow-on intent was explicitly stated in the original agreement. This pathway is why prototype OTAs attract significant commercial technology company interest.

Eligibility and Participation

OTA eligibility requirements differ from FAR contracts:

Nontraditional defense contractors: At least one participant in a consortium or agreement must be a nontraditional defense contractor — an entity that has not previously received over $1 million in DoD contracts or subcontracts under FAR in the prior fiscal year, or a small business under SBA definitions. Software companies that have built primarily commercial products typically qualify.

Consortium arrangements: Most large DoD OTA vehicles (AFWERX, DIU, Army Applications Laboratory, NSTXL) operate through consortium agreements. The government contracts with a consortium manager, and individual companies join the consortium to compete for specific prototype projects. Joining an established consortium is often the fastest way to access OTA work.

Cost-sharing: Prototype OTAs often require cost-sharing from the performer — typically 1/3 of total project costs in some form. This can be satisfied with previous IR&D investments, existing IP, or cash co-investment.

OTA Vehicles Relevant to Software

Several established OTA vehicles specifically target software and technology programs:

Defense Innovation Unit (DIU): DIU solicits commercial solutions to specific DoD problems and can award OTAs to nontraditional defense contractors. Projects typically range from $1M to $50M. DIU specifically seeks companies with proven commercial products or capabilities that can be applied to defense needs.

AFWERX (Air Force / USSF): Operates the AFWERX OTA consortium and the SBIR/STTR programs. Relevant for space-domain software, ground systems, and data platforms.

Army Applications Laboratory (AAL): Similar to DIU model — identifies commercial technology that addresses Army operational problems and awards prototype OTAs.

NSTXL: A consortium manager operating multiple OTA vehicles for DoD, NASA, and other government clients. Companies join specific consortium vehicles to bid on prototype projects within that vehicle's technical scope.

Rapid Defense Experimentation Reserve (RDER): Focused on rapid technology experimentation, including software systems. Timelines from solicitation to award can be weeks rather than months.

What OTA Programs Actually Need from Subs

Most OTA work in software is won by prime contractors who team with specialized technology companies. If you are a small business with technical capabilities, the realistic path into OTA work is through a prime's team — not as a solo OTA performer unless you have direct relationships with a program office or consortium.

What primes need from technology subs on OTA programs:

Demonstrated commercial product: OTAs are designed to access commercial technology. A sub that has built a production system at scale — with paying customers, real-world reliability requirements, and an operational track record — is more valuable than a company that exists primarily to pursue government contracts.

Delivery speed: OTA prototype timelines are typically 12-24 months. Primes need partners who can deliver working software — not PowerPoints — on these timelines. Production engineering experience is the differentiator.

Compliance readiness: Even though OTAs have fewer procedural requirements, DoD programs still require data security controls appropriate for the information handled. CUI capability, CMMC Level 1 minimum, and a credible path to higher compliance levels matter even in OTA programs.

Integration capability: Defense systems rarely operate in isolation. Technology subs that understand government API standards, data formats, and integration patterns are more useful than those who only understand their own product stack.

The Prototype-to-Production Transition

The follow-on production pathway is the primary reason commercial technology companies pursue OTA work. When a prototype OTA includes language authorizing follow-on production, a successful prototype can transition to a production agreement without re-competing.

This transition is not automatic. The government must:

1. Evaluate the prototype as "successfully completed"
2. Determine that the technology meets the operational need
3. Have programmed funding available for production
4. Execute a follow-on agreement within the timeframes established in the original OTA

For technology companies, the implication is clear: the prototype phase is an evaluation period. Systems that operate reliably, are well-documented, integrate with existing government infrastructure, and demonstrate readiness for broader deployment are most likely to transition to production.

Rutagon has built production systems that served as the foundation for government programs — not just prototype demonstrations. That delivery model, covered in our delivery philosophy, is what creates value in OTA relationships.

Compliance Architecture in OTA Programs

A common misconception is that OTA programs have no compliance requirements. This is incorrect — OTAs simply exempt agreements from FAR procedural requirements. Data security, export control (ITAR/EAR), and operational security requirements apply based on the nature of the data and the system, not the contract vehicle.

For software OTA programs:

• CUI handling: If the system processes Controlled Unclassified Information, NIST 800-171 and DFARS 252.204-7012 requirements apply regardless of whether the agreement is an OTA or a standard contract
• ITAR compliance: If the technology has defense applications that fall under the USML or EAR's CCL, export control applies
• Cybersecurity: DoD Instruction 8510.01 (RMF) applies to DoD information systems regardless of acquisition vehicle

Building compliant-by-design architecture from the start — as described in our cloud-native compliance approach — means your prototype system is already compliance-ready when the government evaluates it for production transition.

Frequently Asked Questions

What is the difference between an OTA and an SBIR contract?

SBIR (Small Business Innovation Research) is a congressionally mandated program administered under FAR, specifically for small businesses to conduct R&D. OTAs are non-FAR agreements that can involve businesses of any size, though nontraditional defense contractors receive specific eligibility advantages. SBIR Phase I and II are R&D phases; SBIR Phase III allows production contracts, often without competition. OTAs offer larger potential values and faster award timelines but don't carry the guaranteed Phase III mechanism. Both are routes to defense IT work, and the best path depends on your company's size, technology maturity, and specific opportunity.

Do OTA agreements require SAM.gov registration?

While OTAs are not traditional contracts and are not subject to all FAR requirements, most DoD agencies and consortium managers require active SAM.gov registration and a valid UEI and CAGE code as a baseline administrative requirement. This ensures the company is a legitimate legal entity, is not on debarment lists, and has current representations and certifications on file. Companies pursuing OTA work through established consortiums typically need to complete the consortium's own vetting process as well.

Can a startup with no past performance win OTA work?

Potentially yes — this is one of OTA's design features. OTAs are specifically intended to attract nontraditional defense contractors who may not have government past performance but have relevant commercial experience. A startup with a production SaaS platform serving commercial customers, demonstrable reliability, and applicable technology can compete for prototype OTAs based on commercial performance rather than government contract history. The key word is "production" — demo software is not sufficient.

How does follow-on production OTA pricing work?

OTA agreements are not subject to FAR part 15 cost or pricing data requirements (Truth in Negotiations Act / TNICA). Pricing is negotiated between the government and the performer based on the agreed scope. For production follow-ons, pricing typically references the prototype costs as a baseline and scales based on deployment scope, support requirements, and licensing structures. Both parties have more flexibility than under a traditional FAR contract — but government program officers still have fiduciary responsibilities and will negotiate pricing they can justify.

What acquisition support does Rutagon provide for OTA programs?

Rutagon participates in OTA programs as a technology sub, not as an acquisition consultant. We provide the technical delivery capability — cloud infrastructure, DevSecOps pipelines, software engineering — that prime OTA performers need to deliver prototype and production systems. Our value in an OTA team is the same as in any government IT program: working software, delivered on schedule, with compliance baked in from the start.

Work with Rutagon on your next program →