# SBIR Phase III Commercialization for Super Intelligence Federal Contracts

Super intelligence SBIR Phase III commercialization allows small businesses to transition federally funded artificial intelligence research into non-SBIR procurement contracts without recompeting. In 15 U.S.C. 638(r)(4), agencies possess statutory authority to issue sole-source awards while contractors retain 20-year data rights protection. Understanding this commercialization pathway enables technical teams to scale operational machine learning models across federal agencies.

Source: https://fast.io/resources/super-intelligence-sbir-phase-iii-commercialization-contracts/
Author: [Tom Langridge](https://fast.io/authors/tom-langridge/)
Last reviewed: 2026-10-12

## How SBIR Phase III Commercialization Operates for Federal Super Intelligence

Many federal contractors assume that moving an artificial intelligence prototype from research into production requires competing across open agency solicitations, assembling complex cost volumes, and risking the loss of proprietary algorithm designs. In reality, Congress established a direct statutory mechanism that bypasses competitive procurement entirely. In 15 U.S.C. 638(r)(4), federal agencies and prime contractors are directed to issue Phase III awards relating to technology, including sole source awards, to the SBIR and STTR award recipients that developed the technology, to the greatest extent practicable and without further competition.

Super intelligence SBIR Phase III commercialization refers to the process where a small business transitions federally funded AI research from Phase I or II into sole-source procurement contracts funded with non-SBIR dollars, retaining 20-year SBIR data rights protection under Title 15 U.S.C. 638.

Technical founders and contracts managers encountering this terminology must understand the governing executive policy. President Donald Trump signed Executive Order 14434, titled "Inaugurating the Era of Super Intelligence," on September 29, 2026. Under Section 2(a), executive departments and agencies use the terms "Super Intelligence" and "SI" in place of "Artificial Intelligence" and "AI" across official correspondence, public communications, websites, reports, policy documents, and other non-statutory documents within the executive branch.

Because SI also designates the International System of Units and the sacroiliac joint, federal documentation spells out Super Intelligence (SI) upon first appearance.

Section 2(b) of Executive Order 14434 explicitly provides that nothing in that section requires the alteration of previously issued regulations, Presidential actions, contracts, grants, or other historical documents. Under Section 2(b) of EO 14434, existing Phase I and II contracts and their historical data rights markings remain legally unaffected. Active awards, past deliverables, and technical documentation do not require retroactive modification or terminology changes.

The legal scope of the term appears in Section 3(a) of the order. Under Section 3(a), the terms "Super Intelligence" and "SI" mean the technologies and systems encompassed by the term "artificial intelligence" as defined in 15 U.S.C. 9401(3). That statute, enacted under the National Artificial Intelligence Initiative Act of 2020, defines artificial intelligence as a machine-based system that can, for a given set of human-defined objectives, make predictions, recommendations, or decisions influencing real or virtual environments.

Because Section 3(a) ties federal Super Intelligence directly to 15 U.S.C. 9401(3), the federal phrase names the operational machine learning models, neural networks, computer vision pipelines, and automated reasoning tools in active use today.

This administrative designation differs fundamentally from research vocabulary in commercial computing. Frontier research laboratories, including Meta Superintelligence Labs, Microsoft's MAI Superintelligence Team, and Safe Superintelligence Inc., use superintelligence (spelled as one compound word, abbreviated as ASI for artificial superintelligence) to describe a hypothetical system that exceeds human expertise across nearly all cognitive domains. That hypothetical system does not exist today. Federal SI is an administrative label for operational machine learning technology, whereas lab ASI remains a distant research target.

Policy development remains in progress. Section 3(b) of Executive Order 14434 directs the Assistant to the President for Science and Technology to submit proposed legislative language for a federal definition of SI to the President within 60 days of the order, which falls on November 28, 2026. As of October 2026, no statutory definition of SI exists. What the proposed language will recommend, and whether Congress will enact new legislation, remains pending. Furthermore, Section 4(c) establishes that the order creates no right or benefit enforceable at law or in equity against the United States, directing internal agency procedures rather than creating private rights for contractors.

A major blind spot among commercial tech companies is failing to recognize that SBIR Phase III awards are procurement contracts rather than research grants. While Phase I grants or contracts assess technical feasibility and Phase II awards fund prototype development using agency SBIR set-aside funds, Phase III awards represent operational procurement. They are funded entirely by non-SBIR capital, such as agency operational budgets, working capital funds, weapons system program offices, or commercial enterprise accounts.

There is no statutory dollar limit on an SBIR Phase III award. A Phase III contract can range from a modest technical evaluation to a multi-year program of record worth tens of millions of dollars. Because the initial Phase I and Phase II competitions satisfy federal statutory competition requirements, agencies possess the legal authority to award follow-on Phase III contracts on a sole-source basis directly to the innovative firm.

## The Three Legal Prerequisites for Sole-Source Phase III Contracting

Under the Federal Acquisition Regulation (FAR), government contracting officers typically operate under strict mandates to maximize full and open competition. Awarding a sole-source contract normally requires drafting a detailed Justification and Approval (J&A) document under FAR Part 6, demonstrating that only one responsible source can satisfy agency requirements.

For SBIR Phase III awards, Congress created an explicit statutory carve-out. Federal contracting officers can award sole-source SBIR Phase III contracts without opening a competitive solicitation when the procurement satisfies three core legal prerequisites:

* **1. Derivation, Extension, or Completion:** The proposed Phase III work must derive from, extend, or complete technical efforts conducted under a prior Phase I or Phase II SBIR or STTR funding agreement. The technological connection can be broad; it does not require an identical statement of work, but must demonstrate a clear technical lineage from earlier funded research.
* **2. Non-SBIR Funding:** The contract must be funded using operational, procurement, research, development, test, and evaluation (RDT&E), or mission appropriations from agency program offices, rather than small business research set-aside allocations.
* **3. Small Business Size Eligibility at Inception:** The contractor must have satisfied small business size standards at the time of the original Phase I or Phase II award. A business that outgrows small business size thresholds, graduates from the program, or undergoes a corporate acquisition remains eligible to receive sole-source Phase III awards.

The statutory authority for this mechanism resides in 15 U.S.C. 638(r)(4). In 15 U.S.C. 638(r)(4), federal agencies and prime contractors are directed to consider an award under the SBIR or STTR program to satisfy all applicable federal competition requirements, including sections 3201 through 3205 of title 10 (formerly the Armed Services Procurement Act) and 41 U.S.C. 3301 (the Competition in Contracting Act).

Because the original Phase I or Phase II award was selected through a competitive, peer-reviewed evaluation process, that competition satisfies federal competitive requirements for all subsequent work deriving from the innovation.

When executing an SBIR Phase III contract, contracting officers do not prepare a standard FAR Part 6 J&A for full and open competition. Instead, they document the sole-source justification by citing statutory authority under Title 10 U.S.C. 3204(a)(5) for defense acquisitions or Title 41 U.S.C. 3304(a)(5) for civilian agency acquisitions, which permit other than competitive procedures when a statute expressly authorizes or requires that an acquisition be made through another entity.

The Small Business Administration (SBA) SBIR Policy Directive reinforces this mandate. Under Section 6 of the Policy Directive, federal agencies that require the technology developed under an SBIR award are directed to award Phase III work to the SBIR firm to the greatest extent practicable. If an agency contemplates procuring the technology from another vendor or running a new competition, the contracting officer must notify the SBA and the original SBIR awardee in writing before issuing the solicitation.

This legal framework enables federal agencies to deploy artificial intelligence and data fusion capabilities rapidly across operational units. Under an SBIR Phase III contract vehicle facilitated through GSA, Praeses secured a five-year contract with an initial ceiling value of $79 million to deploy data fusion and AI analytics across the federal government. The single-award vehicle allows Air Force Global Strike Command and other eligible federal agencies to acquire operational data fusion solutions directly, demonstrating how agencies convert earlier small business research into large-scale enterprise contracts.

## Protecting Model Weights and Algorithmic Data Rights Under DFARS 252.227-7018

When small businesses transition machine learning models into federal production contracts, protecting intellectual property is paramount. In conventional federal contracting, work developed with government funding often defaults to Government Purpose Rights or Unlimited Rights under FAR 52.227-14 or DFARS 252.227-7013 and 252.227-7014. Under Government Purpose Rights, the government can disclose technical data and software to outside parties, including commercial competitors, after a five-year window. Under Unlimited Rights, the government can publish algorithms or hand them to rival defense primes immediately.

SBIR Phase III commercialization provides a powerful shield against intellectual property loss. Under the SBA SBIR Policy Directive and DFARS 252.227-7018 ("Rights in Technical Data: Small Business Innovation Research Program"), technical data and software generated under any SBIR or STTR award receive specialized "SBIR Data Rights."

SBIR data rights provide a 20-year protection period from the date of contract award. During this 20-year window, the federal government receives a limited license to evaluate, test, and use the software and technical data internally. The government is strictly prohibited from releasing, disclosing, or licensing the protected data outside the government, and cannot use the data for manufacturing or competitive re-procurement without the contractor's explicit written permission.

For companies developing advanced machine learning models and automated systems, SBIR data rights cover core intellectual property assets:

* **Model Architecture and Source Code:** Proprietary neural network designs, loss functions, custom CUDA kernels, and algorithmic orchestration scripts developed under the program.
* **Trained Weights and Checkpoints:** The numerical parameter tensors produced during pre-training, domain fine-tuning, or alignment. Model weights represent technical data and computer software documentation protected under DFARS 252.227-7018.
* **Training and Evaluation Datasets:** Proprietary synthetic data generation pipelines, curated instruction datasets, human feedback annotations, and benchmark evaluation suites created under the contract.
* **Interface Specifications and Embeddings:** Custom vector embeddings, retrieval indices, and API schemas connecting the model to operational databases.

To preserve SBIR data rights, contractors must strictly comply with mandatory data marking requirements. Under DFARS 252.227-7018(f) and FAR 52.227-20, every deliverable containing protected technical data or software code must carry the exact statutory SBIR Data Rights notice. The notice must specify the contract number, the name of the contractor, and the expiration date of the 20-year protection period.

Delivering unmarked code, documentation, or weight files is a severe compliance failure. Under federal acquisition rules, if a contractor delivers technical data to the government without restrictive markings, the government may treat the deliverable as having Unlimited Rights after a notice and cure period.

A primary advantage of Phase III commercialization is the rollover provision. Whenever a contractor receives a follow-on Phase III award, newly generated technical data developed under that Phase III agreement receives its own 20-year protection period from the date of the new award. This creates a rolling intellectual property perimeter as the technology evolves across successive federal task orders.

The following table compares SBIR data rights with conventional federal intellectual property categories:

| Data Rights Category | Governing Clause | Government Disclosure Authority | Commercial Competitor Access | Statutory Protection Duration |
| :--- | :--- | :--- | :--- | :--- |
| **Unlimited Rights** | DFARS 252.227-7013 / FAR 52.227-14 | Unrestricted public release | Full access; government may re-compete | Indefinite; no confidentiality |
| **Government Purpose Rights** | DFARS 252.227-7013 / DFARS 252.227-7014 | Internal government and defense missions | Allowed under non-disclosure terms | 5-year default period, then converts to Unlimited |
| **Limited Rights (Data) / Restricted (Software)** | DFARS 252.227-7013 / DFARS 252.227-7014 | Internal agency use only | Strictly prohibited without consent | Indefinite for privately funded assets |
| **SBIR Data Rights** | DFARS 252.227-7018 / SBA Policy Directive | Internal government testing and operational use | Strictly prohibited; government cannot re-compete | 20 years from award date for all funded technical data |

## Managing SBIR Phase III Transition Records and Model Assets in Fast.io

Transitioning an artificial intelligence prototype into an operational Phase III procurement contract requires organizing hundreds of administrative, legal, and technical records. A successful Phase III effort generates Phase I and Phase II technical reports, commercialization plans, Statements of Work (SOWs), DD Form 254 security specifications, data rights assertion tables, model cards, training run manifests, and subcontractor non-disclosure agreements.

When research teams store these critical documents across local engineering drives, scattered email threads, and consumer cloud accounts, configuration control breaks down. A contracts administrator might submit a draft statement of work that omits statutory SBIR sole-source references, or an engineering team might deliver a model checkpoint without mandatory DFARS data rights markings, creating severe audit and intellectual property vulnerabilities.

Centralizing transition dossiers, proposal files, and governance records inside dedicated [shared workspaces](/product/workspaces/) gives contracting teams a structured single source of truth.

Fast.io workspaces provide org-owned environments where project leads, contracts managers, and technical teams coordinate Phase III deliverables:

* **Granular Access Permissions:** Grant access per organization, workspace, and share through member roles. Prime contractors can share specific deliverable folders with agency contracting officers or government technical points of contact while restricting proprietary labor rate models, unredacted cost proposals, and foundational weight repositories to authorized staff.
* **Per-File Version History:** Every draft statement of work, technical justification, and data rights assertion maintains complete version history automatically. Team members can track iterative changes across negotiation cycles, compare revisions, and restore earlier document versions if required.
* **Detailed Activity Log:** Fast.io provides a detailed activity log that records changes across workspace files, documenting who uploaded, modified, or shared transition documentation. This provides operational visibility over sensitive procurement files.
* **Metadata Views for Solicitation Management:** Federal acquisition documents, Broad Agency Announcements, and Contract Data Requirements Lists (CDRLs) often span hundreds of pages. [Metadata Views](/product/document-data-extraction/) turn unstructured contract documents into a live, queryable database. Teams describe required extraction fields in natural language, and the system extracts contract numbers, deliverable milestones, submission deadlines, and security markings into a sortable spreadsheet view without manual OCR rules.
* **Integrated E-Signatures for Teaming Agreements:** Subcontractor non-disclosure agreements, teaming agreements, and Phase III commercialization commitment letters can be prepared and sent directly from the workspace using [e-signature](/product/e-signature/). The platform supports sequential or parallel signer routing, optional one-time passcodes per signer, and files executed agreements with tamper-evident audit certificates directly back into the contract folder.

Fastio runs on cloud infrastructure partners, including Google Cloud Platform and Cloudflare, that are certified to industry-leading security standards. Files remain protected with encryption in transit and at rest.

Organizations can evaluate the platform through a 14-day free trial on monthly plans, which requires a credit card.

| Plan Tier | Monthly Billing | Workspaces Included | Storage Included | Monthly AI Work Credits |
| :--- | :--- | :--- | :--- | :--- |
| **Starter** | $9.99 per month | 5 workspaces | 250 GB | 100,000 credits |
| **Business** | $49.99 per month | 50 workspaces | 5 TB | 600,000 credits |
| **Enterprise** | $199.99 per month | 200 workspaces | 25 TB | 3,000,000 credits |

## Step-by-Step Transition Roadmap from Phase II Prototypes to Phase III Procurement

Securing an SBIR Phase III award requires deliberate commercialization planning long before a Phase II contract concludes. Contracting officers in operational program offices frequently manage heavy acquisition workloads and may not be familiar with SBIR Phase III authorities. Technical founders must guide agency stakeholders through the sole-source transition process using a disciplined five-step roadmap:

### 1. Identify the Operational Transition Sponsor Early

Phase III funding does not come from agency SBIR program managers; it originates from operational program managers who hold acquisition budgets to solve mission-critical problems. Begin transition discussions at least six months before Phase II performance ends.

Identify Program Executive Offices (PEOs), operational command leads, or civilian division chiefs whose operational requirements align with your machine learning capabilities. Present the technology not as an experimental research project, but as a de-risked operational tool that directly addresses an existing mission requirement.

### 2. Map the Phase III Statement of Work to Prior Technical Lineage

Draft a concise Statement of Work (SOW) or Performance Work Statement (PWS) that clearly documents the technological connection between the proposed Phase III effort and your prior Phase I or Phase II awards.

The statement of work must explain how the new tasks derive from, extend, or complete the algorithmic pipelines, data fusion architectures, or model training workflows funded under prior SBIR agreements. Establishing this explicit technical lineage provides the Contracting Officer (CO) with the legal basis required to justify sole-source procurement under Title 15 U.S.C. 638(r)(4).

### 3. Supply the Contracting Officer with an SBIR Phase III Justification Package

Contracting officers are often reluctant to execute sole-source awards without clear regulatory documentation. Prepare a standardized Phase III Acquisition Package for the agency contracting office containing:

* **Executive Summary:** A clear explanation of the operational requirement and the technical solution.
* **Technical Lineage Summary:** Contract numbers, awarding agencies, Phase I and Phase II completion dates, and topic titles proving prior SBIR competition.
* **Statutory Sole-Source Reference:** Explicit citations to Title 15 U.S.C. 638(r)(4), SBA SBIR Policy Directive Section 6, and Title 10 U.S.C. 3204(a)(5) or Title 41 U.S.C. 3304(a)(5).
* **Sample Sole-Source Memorandum:** Template language explaining that prior competitive selection under the SBIR program satisfies all CICA competition requirements, eliminating the need for a FAR Part 6 J&A.

### 4. Select the Optimal Contract Vehicle

Collaborate with the contracting officer to determine the most efficient procurement vehicle for the Phase III award:

* **Direct Stand-Alone Contract:** A direct C-type or firm-fixed-price procurement contract issued directly by the operational agency.
* **Task Order Under Existing Vehicles:** Issuing a task order under an existing government-wide acquisition contract (GWAC), GSA Multiple Award Schedule, or agency IDIQ vehicle.
* **Assisted Acquisition Services:** Working through an agency assisted acquisition office, such as GSA Federal Acquisition Service (FAS) or FEDSIM, to execute the award on behalf of the sponsoring program office.
* **Prime Contractor Subcontract:** A major defense or aerospace prime contractor can award an SBIR Phase III subcontract directly to your firm. In 15 U.S.C. 638(r)(4), federal prime contractors are directed to issue Phase III subcontracts to SBIR recipients to the greatest extent practicable.

### 5. Audit Deliverables and Affix Mandatory Data Rights Legends

Before delivering any software code, technical documentation, model weights, or training data to the government, conduct a thorough compliance audit. Verify that every deliverable bears the exact SBIR Data Rights legend specified in DFARS 252.227-7018(f) or FAR 52.227-20.

Confirm that the marking includes the current contract number, company name, and correct expiration date reflecting the 20-year protection period. Maintain an internal registry of all marked deliverables to support future commercial licensing and follow-on federal contracting.

Because procurement decisions involve formal legal interpretations, contractors should coordinate with their contracting officer and legal counsel when structuring Phase III solicitations and data rights assertions.

## Frequently asked questions

### How does an agency award a sole-source SBIR Phase III contract for super intelligence technology?

Federal agencies award sole-source SBIR Phase III contracts under the statutory authority of Title 15 U.S.C. 638(r)(4), which directs agencies to issue Phase III awards to the original SBIR firm to the greatest extent practicable. Because the initial Phase I and Phase II awards were competed competitively, the procurement satisfies the Competition in Contracting Act. Contracting officers cite Title 10 U.S.C. 3204(a)(5) or Title 41 U.S.C. 3304(a)(5) to execute the contract without requiring a separate full-and-open Justification and Approval document.

### Do SBIR data rights protect proprietary AI model weights in Phase III contracts?

Yes. Under DFARS 252.227-7018 and the SBA SBIR Policy Directive, SBIR data rights protect all technical data generated under an SBIR funding agreement, including source code, model architectures, training algorithms, and neural network model weights. The federal government receives a license to evaluate the system internally but cannot release the weights outside the government or use them to compete follow-on procurements for a 20-year protection period, provided the contractor applies the mandatory SBIR marking.

### How does Executive Order 14434 affect ongoing SBIR Phase II and Phase III awards?

Executive Order 14434 does not modify existing contracts or data rights. Section 2(b) explicitly provides that nothing in the order requires the alteration of previously issued contracts, grants, or regulations. Historical contracts, proposal documentation, and technical data markings retain their original validity. Under Section 3(a), Super Intelligence adopts the statutory definition of artificial intelligence in 15 U.S.C. 9401(3), so the order introduces an administrative term rather than changing technical evaluation baselines.

### Can a federal agency other than the original SBIR funding agency award a Phase III contract?

Yes. Any federal agency can award an SBIR Phase III contract, regardless of which agency funded the original Phase I or Phase II research. For example, a small business that developed an AI algorithm under a Department of Defense SBIR Phase II contract can transition that technology into a Phase III sole-source procurement with the Department of Homeland Security, the Department of Energy, or civilian agencies.

### Must a company remain a small business to receive an SBIR Phase III commercialization award?

No. While a company must meet small business size standards at the time of the original Phase I or Phase II award, there is no size restriction at the time of Phase III award. A business that grows beyond small business size thresholds, or that is acquired by another entity, remains eligible to receive sole-source Phase III contracts derived from its prior SBIR work.

### What distinguishes federal Super Intelligence from artificial superintelligence in research laboratories?

Federal Super Intelligence (two capitalized words, abbreviated as SI) is an administrative label for existing operational machine learning systems defined in 15 U.S.C. 9401(3). Research superintelligence (one compound word, abbreviated as ASI) describes a hypothetical future system that exceeds human expertise across nearly all cognitive domains, which does not exist today. Commercial laboratories pursue artificial superintelligence as a research goal, whereas federal SI names operational models in active use.

## Sources

- [Cornell Law School: Legal Information Institute (15 U.S.C. 638)](https://www.law.cornell.edu/uscode/text/15/638): In 15 U.S.C. 638(r)(4), federal agencies and prime contractors are directed to issue Phase III awards relating to technology, including sole source awards, to the SBIR and STTR award recipients that developed the technology.
- [PR Newswire: Praeses GSA Phase III SBIR Contract](https://www.prnewswire.com/news-releases/praeses-secures-gsa-phase-iii-sbir-contract-to-accelerate-ai-powered-data-fusion-across-federal-government-302892859.html): Under an SBIR Phase III contract vehicle facilitated through GSA, Praeses secured a five-year contract with an initial ceiling value of $79 million to deploy data fusion and AI analytics across the federal government.

## About Fast.io

Fast.io provides shared workspaces where people and AI agents work on the same files, with built-in semantic search and citation-backed chat over what they hold. Agents reach it through a remote MCP server, a REST API at https://api.fast.io/current/, and a command line client published on npm as @vividengine/fastio-cli. MCP setup is at https://mcp.fast.io/docs: Claude and most MCP clients connect to https://mcp.fast.io/mcp/tools, ChatGPT to https://mcp.fast.io/mcp/operations, and coding agents to https://mcp.fast.io/mcp/code.