Other Transaction Authority for Software Companies: A Route Around the FAR
#ota#contract-vehicles#saas#federal-market
By Philip Luca — Founder of GovExpress; prior domain experience at Bloomberg Government and GovWin IQ.
Most advice for a software company entering the federal market assumes the long road: register, pick your codes, win a GSA Schedule or a GWAC seat, then start competing for task orders. That road is real, and it takes years.
There is a second road that many commercial software companies never hear about until a program office suggests it. Other Transaction Authority lets certain agencies fund research, prototypes and follow-on production through agreements that sit outside the Federal Acquisition Regulation entirely. For a company with a product the government needs and no vehicle to sell it through, an OT can be the fastest honest path to a first federal customer.
This guide covers what an OT is, when an agency can use one, why the follow-on production provision is the part that matters, how companies actually reach OT work, and what an OT leaves in place.
What an OT is
An other transaction is a legally binding agreement that is not a procurement contract, a grant, or a cooperative agreement. Because it is not a procurement contract, the Federal Acquisition Regulation and most of its clauses do not apply. The agency and the company negotiate the terms.
Only agencies that Congress has given the authority can use one. The Department of War uses it most heavily, under three sections of Title 10:
| Authority | Section | What it funds |
|---|---|---|
| Research | 10 U.S.C. 4021 | Basic, applied and advanced research |
| Prototype | 10 U.S.C. 4022 | Prototype projects directly relevant to mission effectiveness |
| Follow-on production | 10 U.S.C. 4023 | Production after a successful prototype |
Several civilian agencies hold their own versions of the authority. The prototype authority is the one software companies meet most often.
When an agency can use a prototype OT
A defense prototype OT is not available for any project an agency likes. The statute requires at least one of the following:
- A nontraditional defense contractor or nonprofit research institution participating to a significant extent.
- Every significant participant other than the government being a small business or a nontraditional defense contractor.
- At least one third of the total cost paid by parties other than the federal government.
- A written determination by the senior procurement executive that exceptional circumstances justify it.
The first condition is the one that makes OTs a software company’s route. A commercial company that has not held covered defense contracts is usually a nontraditional defense contractor already. You do not have to be a small business, hold a set-aside certification, or bring a cost share. Your absence from the traditional defense base is the qualification.
Follow-on production is the prize
A prototype on its own is a pilot, and pilots end. The provision that turns an OT into a business is follow-on production: if the prototype was awarded using competitive procedures and the participants successfully completed it, the agency can award a follow-on production contract or OT to those participants without a new competition.
That makes the prototype paperwork load-bearing in a way first-time participants often miss. Two things decide whether the follow-on door is open when the prototype ends:
- How the prototype was competed. An award that did not meet the competitive-procedures condition cannot carry a follow-on, however well the prototype performed.
- What successful completion means. If the agreement never defines it, the question gets argued at the moment you most need it settled.
Read both before you sign. A company that negotiates hard on price and ignores these two lines can deliver an excellent prototype and still have to win the production work from scratch.
How software companies actually reach OT work
Few OTs are awarded one company at a time. Two routes carry most of them.
Consortia
An agency awards a large OT to a consortium manager, and member companies compete for individual projects under it. Consortia are usually organised around a technology area. Membership is the entry ticket: it typically means an application, an annual fee, and agreeing to the consortium’s terms. Once inside, you see project opportunities that never appear as public solicitations.
The practical question is which consortium covers the problems your product solves. Joining several on speculation costs fees and attention; joining the one whose project calls match your category is how most members win their first project.
Commercial solutions openings
A commercial solutions opening publishes a problem statement rather than a detailed requirement. Companies respond with a short solution brief. The agency invites the strongest to pitch, then negotiates with the ones it selects.
The format suits commercial software well. You describe a product that exists, not a compliance matrix written to someone else’s specification. The discipline it rewards is watching for problem statements in your category, rather than waiting for a traditional solicitation that may never be written.
What an OT does not remove
An OT removes the FAR. It does not remove everything else a federal customer needs.
- Security requirements stay. If the software will touch government systems or controlled information, the agency’s authorization requirements and the handling rules for CUI still apply. An OT does not grant an ATO.
- Intellectual property is negotiated, not standard. That cuts both ways. A company can protect its commercial product better than a standard FAR clause would, or give away more than it realises by accepting the first draft. Have someone who reads data rights terms read yours.
- You still need a customer. A prototype with no program office that intends to use the result will end as a prototype. The strongest OT pursuits start from a user with a problem, not from an authority looking for a project.
Is an OT the right route for you?
An OT is worth pursuing when three things are true: your product addresses a problem an OT-holding agency is actively trying to solve, you can find that problem in a consortium call or a solutions opening, and you are prepared to negotiate terms rather than accept a standard contract.
It is not a replacement for the rest of federal readiness. Your SAM.gov registration, your security posture and your record of federal work all still come up. What an OT changes is the order: it lets you earn a first federal customer before you hold a vehicle, instead of after.
Score your company’s federal readiness to see where contract vehicle strategy stands next to the other categories buyers look at.
Related reading
The CMMC brief
What the Phase 2 suspension changed and what it did not — the obligations that still bind, the assessment path a contract puts you on, the scoping decision that drives the cost, and the sequence that fits inside a pipeline. Sourced from the primary record.