Atlas Business Management
Government IT Services/Technology Procurement/Business Advisory
AboutServicesManaged ITWeb DevelopmentProductsBuild a QuoteAdvisoryContractsBlogContact
government it

How Government Agencies Actually Buy Software

A vendor-neutral walkthrough of how public-sector software purchases really happen — the thresholds, the paperwork, and where deals stall.

The United States Capitol building photographed from the plaza beneath a streaked, overcast sky

Public-sector purchasing looks arbitrary from outside and rigid from inside. It is neither. It is a set of rules designed to prevent favouritism, and once you can see the rules, the process becomes predictable — including the parts where it reliably gets stuck.

This is written for both sides of the table: agency staff who have inherited a purchase, and vendors who keep losing on process rather than merit.

The dollar threshold decides almost everything

Before anything else, the value of the purchase determines the path. Exact figures vary by jurisdiction and change over time, so treat these as shape rather than gospel and confirm locally:

  • Micro-purchases. Small buys a cardholder can make directly, with minimal process. Fast, and the reason so much shadow software exists in government.
  • Simplified acquisition. A middle band requiring quotes and some competition, but not a full solicitation. This is where a great deal of agency IT actually gets bought.
  • Full competition. Above the simplified threshold, expect a formal solicitation, published evaluation criteria, and a timeline measured in months.

The single most useful question at the start of any public-sector conversation is "which band is this in?" Everything downstream follows from the answer.

Contract vehicles exist to skip the slow path

A contract vehicle is a pre-negotiated agreement — terms, and often pricing, already competed. Buying through one lets an agency skip much of the solicitation process because the competition already happened.

This is why vendors care so much about being on them, and why agency staff should ask early whether a vehicle already covers what they need. It is frequently the difference between a six-week purchase and a nine-month one. We keep a plain-language breakdown on the contract vehicles page.

The people involved, and what each one wants

Purchases stall when a vendor talks to one of these and ignores the rest.

  • The program office. Has the problem and usually the budget. Wants the thing to work.
  • The contracting officer. The only person who can actually obligate funds. Wants a defensible, compliant file. Not a gatekeeper to route around — the person who makes the purchase legal.
  • IT and security. Must assess the system before it touches the network. This is where unprepared vendors lose months.
  • Finance and legal. Fiscal year, funding colour, and terms. Their calendar is not negotiable.

Where purchases actually stall

  1. Security review. The vendor cannot produce a security package, an authorization, or answers about data residency. This is the most common cause of delay by a wide margin.
  2. Accessibility. Section 508 conformance is a legal requirement, not a nice-to-have, and "we are working on it" is not an accessibility conformance report.
  3. Terms nobody can sign. Standard commercial clauses — automatic renewal, binding arbitration, unilateral term changes — that a government entity is not permitted to accept.
  4. Fiscal-year timing. Money that expires, or a purchase that misses the window and waits a year.
  5. Unclear requirements. A statement of work vague enough that bids are not comparable, forcing a restart.

If you are the buyer

  • Confirm the threshold and whether an existing vehicle covers it before writing anything.
  • Bring security and accessibility in at requirements stage, not after selection. Late findings kill deals that were otherwise done.
  • Write requirements as outcomes with measurable acceptance criteria, not a feature list copied from one vendor's brochure — that invites a protest.
  • Ask every vendor for their accessibility conformance report and security documentation in the solicitation, so it is not a surprise later.
  • Plan for the fiscal calendar. Work backwards from when funds expire.

If you are the vendor

  • Have the security and accessibility documentation ready before the first meeting. This is the cheapest competitive advantage available.
  • Find out which vehicles the agency already uses, and whether you can be reached through one.
  • Talk to the contracting officer early and respectfully. They will tell you what the file needs.
  • Price consolidated. Agencies would rather issue one order than eleven, which is much of the value in a single consolidated catalog quote.
  • Understand the fiscal year better than your competitors do.

None of this is exotic. It is a process with published rules, and the parties who read them win disproportionately. If you are scoping something now, the guide to choosing a contract vehicle covers the next level of detail.

Working through a purchase and want a second opinion? We do this daily.