Brand-Name Justifications for Software Companies: When an Agency Can Name Your Product

Sooner or later a federal buyer will tell you they want your product by name. Maybe their team already runs it, maybe it integrates with a system nothing else supports, maybe they tried the alternatives. Wanting a product is not enough to buy it, though. Federal rules start from the position that requirements describe a need, not a brand, and an agency that names one product has to justify that choice in writing.

This guide covers the rules for naming a product in FAR 11.104 and 11.105, the link to FAR 6.302-1, the separate rules for GSA Schedule orders in FAR 8.405-6, and what all of it means for a software company on either side of a brand-name requirement. It is written for founders and capture leads, and it complements our guide to sole-source awards.

---

The default: describe the need, not the product

FAR 11.105 sets the rule. Agency requirements shall not be written to require a particular brand name, product, or a feature of a product, peculiar to one manufacturer, in a way that excludes products made by other companies, unless all of the following hold:

1. The brand, product or feature is essential to the Government’s requirements, and market research indicates that other companies’ similar products, or products without the feature, do not meet, or cannot be modified to meet, the agency’s needs.
2. The restriction is supported on paper. Either the authority to contract without full and open competition is supported by the required justification and approval under FAR 6.302-1, or, under simplified acquisition procedures, the basis is documented in the file (FAR 13.106-1(b)) or justified (FAR 13.501).
3. The documentation or justification is posted for acquisitions over $25,000 (FAR 5.102(a)(6)).

The bar is high, and it is meant to be. The burden is on the agency to show that nothing else will do, not on other vendors to show they are as good.

FAR 11.105 then points elsewhere for two common buying routes: Multiple Award Schedule orders follow FAR 8.405-6, and orders under indefinite-quantity contracts follow FAR 16.505(a)(4).

---

Brand name or equal

There is a middle path between an open performance specification and a single named product. FAR 11.104 allows a brand name or equal purchase description. It names a brand as a reference point and must also list the salient physical, functional or performance characteristics that an “equal” product has to meet to be acceptable for award.

Two parts of FAR 11.104 matter here:

• Performance specifications are preferred, because they encourage offerors to propose innovative solutions. Brand name or equal descriptions may be advantageous under certain circumstances.
• Brand name or equal is for firm requirements. It is meant for cases where the salient characteristics are firm requirements.

For a software company, the salient characteristics are the whole contest. If they describe what the buyer actually needs, such as a supported data standard, an integration, a security authorization or a deployment model, any product that meets them can win. If they are copied from one vendor’s feature list, they work like a brand-name requirement with extra steps.

---

Why naming a product closes competition

FAR 6.302-1 treats a purchase description that specifies a particular brand name, product or feature peculiar to one manufacturer as other than full and open competition, regardless of the number of sources solicited.

That last phrase is the one software companies often miss. An agency may solicit five resellers to supply your product, and those resellers may compete hard on price. That is competition between sellers of one product. Competition between products is closed, so the action needs the same kind of justification and approval as any other limit on competition. Our sole-source guide covers what a justification contains and how approval rises with contract value.

Under simplified acquisition procedures, FAR 13.106-1(b) lists brand name among the circumstances in which a contracting officer may solicit from one source, with the reasons documented in the file.

---

Brand names on GSA Schedule orders

Much federal software is bought off the GSA Schedule, and Schedule orders are exempt from FAR Part 6. They have their own rule in FAR 8.405-6, and it is explicit about brands:

A brand name item, whether available on one or more schedule contracts, is an item peculiar to one manufacturer.

So a Schedule order that names your product is a restricted order even if a dozen resellers carry it on their schedules. FAR 8.405-6(b) applies the same test as FAR 11.105: the brand, product or feature must be essential, and market research must show other products do not meet, or cannot be modified to meet, the need.

The paperwork scales with the order’s estimated value:

Estimated value	What FAR 8.405-6 requires
Above the micro-purchase threshold ($15,000), up to the simplified acquisition threshold ($350,000)	The contracting officer documents the basis for restricting consideration to an item peculiar to one manufacturer.
Above the simplified acquisition threshold	A limited-sources justification with the contents listed in FAR 8.405-6(c), including the market research done among schedule holders and a best-value determination.
Above $25,000	The documentation or justification is posted with the request for quotation on GSA eBuy, after screening for proprietary data, unless a listed exception applies.

Approval of a justification above the simplified acquisition threshold also rises with value under FAR 8.405-6(d). Up to $900,000, the contracting officer’s certification serves as approval unless agency procedures require more. From $900,000 to $20 million, the activity’s advocate for competition approves. Above that, approval moves to the head of the procuring activity or a senior designee, and above $90 million (above $150 million for the Department of War, NASA and the Coast Guard) to the agency’s senior procurement executive.

Two more details matter for software sold through blanket purchase agreements. The documentation or justification has to be completed and approved at the time the requirement for a brand-name item is determined. And a justification is required at the order level when the BPA did not include one or its justification does not cover what the order needs. When only part of an order is brand-name, the documentation and posting rules apply only to that part.

Thresholds change by rule and inflation adjustment, so confirm the current figures in the FAR before relying on them.

---

What this means for a software company

If a buyer wants your product by name, help them build the record honestly. The test is whether your product, or a specific feature of it, is essential and whether market research shows alternatives do not meet the need. Concrete, checkable facts carry that test: integrations with systems the agency already runs, data formats, security authorizations, existing deployments and the cost of switching. Marketing claims do not. A justification built on claims a competitor can disprove invites a challenge. Our guide to sources sought notices and RFIs covers how market research reaches vendors.

If you see a brand-name requirement for a competitor’s product, read the posted documentation. On a Schedule order above $25,000 it is posted on eBuy with the request for quotation, and other brand-name justifications are posted under FAR 5.102. The justification states the features the agency says are essential. If your product meets them, say so early, with evidence, to the contracting officer. A brand name or equal description is an open door if you meet the salient characteristics, and a strict brand-name requirement is only as strong as the market research behind it. Our guides to bid protests and organizational conflicts of interest cover the formal routes when informal ones fail.

If you sell through resellers, a brand-name requirement for your product may still be competed among the resellers who carry it. Know which partners hold your product on their schedules and contracts, and keep pricing consistent across them. Our guide to federal resellers covers the channel.

If your product is the reference in a brand name or equal description, the salient characteristics are where you win or lose. Characteristics that describe real requirements protect the buyer and favor a product that meets them well.

---

A brand-name checklist

• Know the test. Essential to the requirement, and market research shows nothing else meets or can be modified to meet the need.
• Give buyers checkable facts, not adjectives, when they ask why your product is the right one.
• Watch eBuy and posted justifications in your category to see which products agencies are naming.
• Read the salient characteristics in every brand name or equal solicitation, and answer them point by point.
• Map your reseller coverage so a brand-name order for your product has more than one place to land.
• Read the current rule text. Thresholds are adjusted over time, and the FAR is being rewritten under the Revolutionary FAR Overhaul, so section numbers and wording may move. Confirm the rules in your solicitation and get advice from counsel on contract questions.

---

The short version

• Requirements describe needs, not brands. FAR 11.105 allows a named product only when it is essential and market research shows nothing else will do.
• Brand name or equal keeps the door open. FAR 11.104 requires salient characteristics that any equal product can meet.
• Naming one product closes competition between products, no matter how many resellers are asked to quote.
• Schedule orders have their own rule. FAR 8.405-6 treats a brand name item as peculiar to one manufacturer even when many schedules carry it, with documentation, posting on eBuy and approvals that scale with value.
• The justification is public. Read your competitors’ and make sure yours rests on facts.

---

Where this fits

A buyer’s case for naming your product is only as strong as the facts behind it, from your security posture to your registration and federal track record. It helps to know how your company looks across the categories federal buyers review before a contracting officer has to write it down. Score your company’s federal readiness to see where you stand.

---

Related reading

• Sole-Source Awards for Software Companies: When an Agency Can Buy Without Competing
• GSA Schedule for SaaS Companies: Is It Worth It, How Long, and What Does It Cost?
• Blanket Purchase Agreements for Software Companies: How GSA Schedule BPAs Work
• Federal Resellers for SaaS Companies: How the Channel Works and How to Choose One
• Sources Sought and RFIs for Software Companies: Why Answering Early Shapes the Contract