Micro-Purchases and Purchase Cards: The Fastest First Federal Sale for SaaS
By Philip Luca — Founder of GovExpress; prior domain experience at Bloomberg Government and GovWin IQ.
Most federal buying runs through solicitations, evaluation panels and contract vehicles. A small slice doesn’t. Below the micro-purchase threshold, an authorized federal employee can buy a commercial product with a government purchase card, often without a formal competition. For a software company with a low-priced subscription, that can be the shortest route to a first federal customer.
This guide explains what a micro-purchase is, how purchase cards work, which commercial license terms block these deals, and how to make your product easy to buy this way.
What a micro-purchase is
The FAR defines the micro-purchase threshold in Part 2 and sets out the rules for using it in Part 13. Purchases at or below the threshold can be made without soliciting competing quotes, as long as the buyer considers the price reasonable and spreads purchases among qualified suppliers where practicable.
The threshold is adjusted for inflation every five years. The adjustment that took effect on October 1, 2025 raised the base micro-purchase threshold from $10,000 to $15,000 and the simplified acquisition threshold from $250,000 to $350,000. Some purchases carry different limits, including lower ones for work covered by construction and service contract labor rules, and higher ones for certain contingency and emergency buys. The FAR is also being rewritten through the Revolutionary FAR Overhaul, and many agencies now apply the new text by class deviation, so check the current FAR and the agency’s own policy before you plan a deal around a number.
Two rules matter for pricing:
- The threshold applies to the purchase, not your list price. A three-year prepaid subscription, setup fees and add-on seats all count toward the same purchase.
- Splitting is prohibited. A buyer can’t break one requirement into several smaller card transactions to stay under the threshold. If your annual price sits above the line, don’t suggest monthly charges as a way around it.
How the purchase card works
Most micro-purchases are made with a government purchase card issued under GSA’s SmartPay program. The cardholder is a federal employee with a delegated, written authority and a single-purchase limit set by their agency, which can be lower than the threshold.
From your side, a card purchase looks much like any business card transaction. You accept the card, charge it and deliver. A few differences:
- The buyer may need you in SAM.gov. Registration isn’t always required for a micro-purchase, but many agencies prefer or require it, and you’ll need it for anything larger. See our SAM.gov registration guide.
- Sales tax usually doesn’t apply. Purchases on a centrally billed government purchase card are generally exempt from state sales tax. Make sure your checkout can remove it, or invoice manually.
- IT purchases get extra review. Many agencies route software purchases, even small ones, through their CIO office for security, privacy and accessibility review before the card is used. The card makes the sale fast; the internal review sets the actual timeline.
License terms that block card purchases
The most common reason a card purchase stalls isn’t price. It’s the clickwrap. A federal employee generally can’t bind the government to commercial terms that conflict with federal law, and agency counsel will flag them. The usual problems:
- Open-ended indemnification. A clause requiring the customer to indemnify you can conflict with the Anti-Deficiency Act.
- Automatic renewal. A subscription that renews and charges the card without a new purchase decision can commit funds that haven’t been obligated.
- Governing law and venue. Disputes with the federal government are resolved under federal law and its own forums, not the state courts named in your terms.
- Unilateral changes. Terms that let you change pricing or conditions by posting a new version on your website generally won’t bind the government.
GSA has published standard language that modifies commercial supplier agreements for these issues, and FAR clause 52.212-4 sets the baseline terms for commercial purchases. A short federal addendum, or a version of your terms that removes or overrides these clauses for government customers, can save weeks.
Security and accessibility still apply
A small purchase isn’t exempt from the agency’s security and accessibility obligations. Depending on how your product handles federal data, the agency may ask about:
- Cloud authorization. A cloud service that stores or processes federal data may need a FedRAMP authorization before the agency can use it at scale. Be precise about your status: a self-attested security questionnaire or a commercial audit report isn’t the same as a FedRAMP authorization, and federal reviewers will treat them differently.
- Accessibility. Section 508 applies to the information and communication technology the agency buys, whatever the dollar value. Have a current Accessibility Conformance Report ready. See Section 508 and VPATs for software companies.
If the answer to the security question is “not yet,” a micro-purchase pilot that keeps federal data out of your product, or limits it to public information, may still be possible.
Making your product easy to buy this way
A practical checklist:
- Offer a plan that fits under the threshold. A single-team annual plan priced below the current micro-purchase threshold, with no required add-ons, is easiest to buy.
- Publish a federal terms addendum. Address indemnification, auto-renewal, governing law and unilateral changes in advance.
- Accept cards without sales tax. Confirm your billing system can mark a customer tax-exempt.
- Prepare a short security and accessibility packet. A one-page data handling summary, your ACR and an accurate statement of your authorization status answer most CIO-office questions.
- Register in SAM.gov. It removes one reason to say no, and you’ll need it once the account grows. Pick your NAICS codes while you’re there.
- Plan the next step. When usage outgrows the threshold, the agency will need a different route: a simplified acquisition, a GSA Schedule order, or another contract vehicle. Line it up before the renewal comes due.
Micro-purchases won’t build a large federal business on their own, but a handful of active teams inside an agency gives you references, usage data and a reason for a larger buy. To see what else stands between your company and federal buyers, score your company’s federal readiness.
Related reading
- How to Sell Software to the Federal Government: The Complete 2026 Guide for ISVs
- GSA Schedule for SaaS Companies: Is It Worth It, How Long, and What Does It Cost?
- Federal Contract Vehicles for Software Companies: GWACs, IDIQs, BPAs and Where to Start
- SAM.gov Registration for Software Companies: A Step-by-Step Guide
- Glossary: SAM.gov · GSA Schedule · FedRAMP
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.