Other Transaction Authority: a founder’s guide to defense prototype deals

Which kind of OT are you discussing?

The Department of Defense uses OTs for research, prototypes, and follow-on production. The authority, funding, participants, and path to an award differ, so “we have an OTA” is not enough to describe an opportunity. DARPA’s overview identifies the three types and explains why an OT differs from a conventional procurement contract.

• Research OT: Supports qualifying research. The scope is exploration rather than a guaranteed purchase of a fielded product.
• Prototype OT: Funds a project directly relevant to a defense mission or capability. The prototype may test a product, subsystem, process, or operational use—not merely produce a demo video.
• Production OT: A possible follow-on to a successfully completed prototype OT when statutory conditions are met. A production effort can also be awarded through a contract; neither result is automatic.

Many founders encounter OTAs through a prototype solicitation, an agency program, or a consortium project. Do not assume every innovation challenge uses an OT or that every OT is a DIU agreement; read the actual notice and instrument.

When is a prototype OT a good fit?

A strong candidate has a named defense problem, a sponsor who can evaluate the result, a feasible test plan, and a route to operational use if the test succeeds. Existing commercial technology that needs adaptation or validation for a military environment can be a better prototype candidate than an open-ended research pitch.

Under 10 U.S.C. § 4022, a prototype project must meet one of several participation or funding conditions, such as significant participation by a nontraditional defense contractor or nonprofit research institution, participation by only small businesses or nontraditional defense contractors, qualifying non-federal cost share, or an exceptional-circumstances determination. The government agreements team decides whether the project and team qualify. Being a startup alone does not establish eligibility.

Before pursuing a notice, write down the operational user, what will be tested, the measurable success criteria, the test environment, who supplies government data or equipment, and who could fund the next step. If those answers are missing, work on the customer case before choosing an acquisition label.

Where to find opportunities

1. Check official solicitations. Review SAM.gov opportunities and agency-specific calls. Search for the mission problem and terms such as “prototype,” “other transaction,” “commercial solutions opening,” and “broad agency announcement.” Confirm the notice’s actual authority and submission instructions.
2. Review DIU’s open solicitations. DIU posts commercial solution needs and explains how to submit a solution brief. Its process is one example, not the template for every agency.
3. Assess consortium opportunities. Some project calls run through a consortium manager. Check the membership terms, dues, access to calls, proposal rules, agreement structure, and what role the manager plays before paying to join. Membership creates access to a channel, not an award.
4. Trace the buyer. Use recent award records, program announcements, and industry days to identify the sponsor and mission need. A prior award is evidence of past activity, not proof of current funding or an open solicitation.

Follow the specific call’s communication and submission rules. A good introduction to an end user cannot replace a compliant response when the buyer has opened a competitive process.

Build a proposal around a decision the buyer can make

Make the prototype a bounded experiment. State the baseline problem, the capability you will deliver, the environment in which it will be tested, the evidence you will collect, and the decision that evidence will support. Show that your team can deliver on the proposed timeline with realistic access to test users, sites, data, and integration partners.

• Technical proof: What works now, what still needs development, and what independent or customer evidence supports each claim?
• Milestones: Which deliverables and demonstrations trigger review or payment, and who accepts them?
• Transition: Who would own deployment, what additional integration or authorization is needed, and what budget could pay for production?
• Price: What does the prototype cost, what is included, and what would a later unit or subscription cost? Keep the commercial model understandable to the government buyer.

Do not claim a prototype has been “successfully completed” merely because it was awarded or demonstrated once. Capture acceptance and results against the agreement’s criteria.

Read the agreement terms before committing

OT flexibility means the agreement’s words matter especially much. Ask counsel or an experienced agreements adviser to review material terms before signing, particularly when the prototype uses your core product or proprietary data.

• Scope and change control: Define the deliverables, test environment, government-furnished inputs, acceptance standard, and process for changing requirements.
• Payment and cost share: Identify milestone payments, invoice evidence, termination treatment, and any required non-federal contribution. Do not assume cost share is required in every prototype OT.
• Intellectual property and data: Identify background technology, data and software created under the project, rights to use or disclose each, markings, source-code access, and whether future contractors may receive the deliverables. OT terms are negotiated; do not import a familiar FAR or SBIR clause by assumption.
• Security and delivery: Confirm the actual rules for CUI, cyber controls, export-controlled information, personnel access, facilities, testing, and subcontractors. Being outside the FAR does not make these obligations disappear.
• Follow-on path: Ask whether the original solicitation and agreement contemplated production, what counts as successful completion, which participants might qualify, and who would make and fund a later purchase.

See the CMMC guide for scoping cyber help and the SBIR Phase III guide if the work derives from an SBIR/STTR award. Those are distinct issues from OT authority.

What happens after a successful prototype?

A successfully completed prototype can create a path to a follow-on production OT or contract without a new competition when the statutory conditions are satisfied. The DoD OT guidance addresses the conditions, including the original prototype selection and successful completion. This is an available authority, not an obligation to buy. The government still needs a requirement, funding, an authorized award decision, and acceptable terms.

Design the transition plan while negotiating the prototype: identify the buying office, operational sponsor, deployment dependencies, likely appropriation, target quantities or users, and evidence needed for a production decision. After the test, document the result and ask the agreements team which follow-on path is available. DIU’s solutions catalog illustrates one organization’s approach to making successful prototypes visible to buyers; other agencies use different processes.

Questions to ask before pursuing an OT

1. Who is the operational sponsor, and what decision will the prototype help them make?
2. Which OT authority and eligibility condition does the agreements team expect to use?
3. Is this a direct agency solicitation, a DIU process, or a consortium project? Who will sign the agreement and pay us?
4. What are the success criteria, test resources, schedule, milestone payments, and termination terms?
5. Which data, software, and intellectual-property rights does each party need during and after the project?
6. Was a production follow-on contemplated in the prototype competition and agreement, and who could fund it?

If the buyer cannot yet answer these, treat the conversation as market discovery. For the broader path to a government buyer, use our first government contract guide.

Common questions

Does OTA mean no competition?

No. DoD is directed to use competitive procedures for prototype OTs to the maximum extent practicable. Some qualifying production follow-ons may avoid a new competition, but only if the applicable conditions are met.

Do I need to join a consortium?

Only for opportunities run through one. Direct agency and DIU pathways also exist. Compare the actual calls and membership terms before investing time or fees.

Do I need a SAM.gov registration?

Follow the notice and agreements officer’s instructions. An OT opportunity may require an entity identifier or additional registration even if it is not a conventional FAR contract. Do not assume the requirements are identical across agencies or intermediaries.

Will a successful prototype become a production contract?

Possibly, but not automatically. Success may permit a follow-on without another competition; a funded buyer and separate award decision are still necessary.

OTA vs. FAR, CSOs and consortia: separate the decisions

An other transaction is an agreement made under a particular statutory authority. A FAR procurement contract is a different legal instrument. A commercial solutions opening (CSO) is a solicitation approach; a consortium is a way an organization may administer a community and solicit work. Neither label alone tells you the final instrument, rights or eligibility requirements. Read the notice and draft terms. For example, DFARS 212.7002 describes CSOs resulting in fixed-price procurement contracts.

Before joining a consortium, find at least one relevant opportunity and understand its current submission process. Membership can create access to notices and relationships; it does not establish that a funded project fits your product. Use the Department’s OT policy resources and the actual call to resolve the details.