FAR Part 12 for Software Companies: Selling Your Product as a Commercial Product
By Philip Luca — Founder of GovExpress; prior domain experience at Bloomberg Government and GovWin IQ.
Many software founders assume that selling to the government means building something to a government specification, under government rules, with government accounting. For most commercial software, it doesn’t. Federal acquisition law prefers to buy what the market already sells, and FAR Part 12 is the set of rules for buying it that way.
If your product is sold to companies today, the most important question in your first federal deal is whether the government will buy it as a commercial product. This guide covers what that means, what it changes for you, and where software companies still get caught.
What counts as a commercial product
The FAR defines “commercial product” and “commercial service” in FAR 2.101. (Before late 2021 both were covered by a single term, “commercial item”, which you’ll still see in older documents and in conversation.) In plain terms, a product is commercial if it’s of a type customarily used by the general public or by non-governmental entities for non-governmental purposes, and it has been sold, leased or licensed to the general public, or offered for sale, lease or license.
A few points matter for software:
- “Of a type” is broad. The product doesn’t have to be identical to what you sell commercially. Minor modifications made for the government can still leave it commercial.
- Offered counts, not just sold. A product that’s offered to the public can qualify even before it has many customers, though a buyer will want evidence that the offer is real.
- COTS is a subset. Commercially available off-the-shelf (COTS) products are commercial products sold in substantial quantities in the commercial marketplace and offered to the government without modification. A standard SaaS subscription bought as-is often fits that description.
- Services can be commercial too. Implementation, training and support that you sell commercially at catalog or market prices can be commercial services.
Whether a particular purchase is commercial is the contracting officer’s determination, usually based on the agency’s market research. You don’t certify it yourself, but you can make it easy to reach.
Why the government prefers commercial
Federal statute directs agencies to prefer commercial products and services where they meet the need, and FAR Part 10 requires agencies to do market research to find out whether they do. Answering a sources sought notice or RFI with a clear description of an existing product is one of the most direct ways to feed that research. If the agency concludes early that a commercial product will do, the requirement is more likely to be written so a product like yours can compete.
What changes when you’re bought as commercial
Buying under FAR Part 12 changes the deal in ways that favour a product company.
Fewer clauses. Commercial contracts use a short, standard set of provisions and clauses instead of the long lists found in other contracts. The core ones are FAR 52.212-1 (instructions to offerors), 52.212-2 (evaluation), 52.212-3 (representations and certifications, most of which you complete once in your SAM.gov registration), 52.212-4 (contract terms and conditions) and 52.212-5 (the statutes and executive orders that apply). Agencies often use the Standard Form 1449 for commercial solicitations and awards.
Fixed-price contracts. For commercial acquisitions, agencies generally use firm-fixed-price contracts or fixed-price contracts with economic price adjustment. That matches how software is priced already. Our guide to federal contract types covers the exceptions.
No certified cost or pricing data. Commercial products and services are exempt from the requirement to submit certified cost or pricing data. You may still be asked for information that shows your price is fair and reasonable, such as your commercial price list, published pricing or recent sales at comparable volumes, but you aren’t opening your cost accounting to the government.
Simpler procedures. The FAR lets agencies combine the synopsis and solicitation into a single notice for commercial buys, and allows simplified procedures for commercial acquisitions above the ordinary simplified acquisition threshold. That can make a commercial buy faster than a comparable non-commercial one.
Your license terms mostly carry over
FAR 12.212 says the government acquires commercial computer software under the licenses customarily provided to the public, to the extent those licenses are consistent with federal law and otherwise meet the government’s needs. For the Department of War (DoW), DFARS 227.7202 takes a similar approach. In practice, your standard license or terms of service is the starting point.
The qualification matters, though. Some terms common in commercial agreements don’t bind a federal agency, and the FAR says so directly:
- Open-ended indemnification. An agency can’t agree to indemnify you for an unlimited or undetermined amount. FAR 52.212-4 makes such terms in a commercial agreement unenforceable against the government.
- Governing law and venue. Disputes with the government are governed by federal law and run through the Contract Disputes Act, not your chosen state courts.
- Automatic renewals and unilateral changes. An agency generally can’t commit funds it hasn’t appropriated, so auto-renewal language and terms you can change by posting a new version on your website don’t work the way they do commercially.
Our guide to software license terms in federal contracts goes through these in more detail. The practical step is to keep a version of your terms that’s already been cleaned of the provisions a contracting officer will strike.
Where software companies still get caught
- A heavily customised build. If the government is paying you to develop something new to its specification, the purchase may not be commercial, and the contract will carry the full set of non-commercial clauses. Keep custom development separate from your standard product where you can.
- No public evidence. A contracting officer has to document the commercial determination. A public price list, published documentation and commercial customers make that easy. A product that’s only ever been sold through bespoke enterprise deals is harder to show.
- Security requirements still apply. Commercial status doesn’t waive security requirements. A cloud product may still need FedRAMP authorization or an agency ATO, and DoW work involving CUI can bring CMMC requirements. A vendor’s claim about its own controls is self-attested. Buyers increasingly look for an assessment or authorization they can verify.
- Clause text in flux. The FAR is being rewritten under the Revolutionary FAR Overhaul, and agencies have been adopting revised part text through class deviations. Read the clauses in the solicitation in front of you rather than relying on numbers from an older contract.
Getting bought as commercial
Federal buyers who can acquire your product as a commercial product can also buy it through the same routes they buy other commercial software: open-market purchases, micro-purchases on a purchase card, and orders against vehicles such as the GSA Schedule. To see which agencies already spend the most in your category, use the free GovExpress Target Finder. To see how ready your company looks to federal buyers, score your company’s federal readiness.
Related reading
- Federal Contract Types for Software Companies: Fixed-Price, T&M, Cost-Type and IDIQ
- Software License Terms in Federal Contracts: What Agencies Can’t Sign
- Sources Sought and RFIs for Software Companies: Why Answering Early Shapes the Contract
- Micro-Purchases and Purchase Cards: The Fastest First Federal Sale for SaaS
- Glossary: GSA Schedule · FedRAMP · ATO
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.