The single most common fear founders bring to Army SBIR is: if the government pays for my R&D, do they own my technology? The short answer is no — you keep it. But the details matter, and small mistakes can quietly hand the government broader rights than the law requires.
Under SBIR, the small business retains ownership of inventions it makes and title to the technical data and software it develops. The government does not take your patents and does not take your source code. What it receives instead is a license — called SBIR data rights — to use, for government purposes, the data generated under the award.
Crucially, during the protection period the government cannot release your SBIR-developed data outside the government (including to your competitors) without your permission. That is the wall that keeps a rival contractor from getting your work handed to them.
If your project needs simulation to prove feasibility, ask us about an Ansys evaluation license with live engineering support — no cost while you're pre-funding.
See if you qualify for an Ansys eval The MVP playbook →Historically the SBIR data-rights protection period ran 5 years from the completion of the award. Policy has since extended that dramatically — newer awards carry protection for roughly 20 years. The practical takeaway: the protection is long, but it is not infinite, and the clock is tied to the specific award. Track your dates.
Anything you invented before the contract, or with other money, is your background IP — it stays fully yours and is not subject to SBIR data rights at all. Only what the SBIR award pays to develop falls under the government license. This is why disciplined founders document their background IP up front, so there is no ambiguity later about what the government's license does and does not cover.
Founders sometimes assume a government license is the same as losing exclusivity. It is not. SBIR data rights are limited to government purposes — the government can use your data internally to evaluate, integrate, and support what it bought, but it cannot commercialize it, cannot license it to your competitors, and cannot post it publicly. You remain free to sell the same technology commercially, to other agencies, and to allied customers. In practice, a well-run SBIR company treats the government as one large customer that funded a version of the product, not as a co-owner.
First, mark every deliverable with the correct SBIR data-rights legend, every time — an unmarked deliverable is the most common way rights leak. Second, keep a running IP inventory that separates background IP from SBIR-funded IP, dated and documented, so there is never a dispute about which bucket a feature belongs in. Third, read the data-rights clauses in your specific contract before you sign; the exact FAR/DFARS clauses control, and they occasionally differ from the boilerplate you expect.
Army SBIR is non-dilutive and IP-friendly by design: no equity, and you keep ownership of what you build. The government gets a protected, time-limited license to use it for government purposes — nothing more, as long as you mark and document your work properly. For the official framework, review the DoD SBIR/STTR program materials at dodsbirsttr.mil and the Army SBIR/STTR program. (This is general information, not legal advice — have counsel review your specific contract.)
