Selling to Government: A Startup's Guide to Federal, State and Local Buyers

  1. Blog
  2. Demand & Channels

By Saroj Jha · November 5, 2026 · 10 min read

Sell to government by starting small and working with the buying rules, not against them. Win a first purchase below the thresholds where agencies can buy with less paperwork, sell through contract vehicles they already use, and line up the security authorization your product will need. Marketing’s job is to make you easy to find, easy to justify and easy to buy.

Government buying is slower than commercial buying, but it is written down. Agencies publish what they buy, how they buy it and who bought what. A startup that reads those rules has an advantage over one that treats the public sector like a big enterprise account.

This post is general information about marketing, not legal or contracting advice. Procurement rules change and vary by agency and state; check the current rules and talk to a contracting adviser before you bid.

Key takeaways

  • 1 Pick one level of government and one kind of buyer.
  • 2 Win a first purchase small enough to use simplified buying rules.
  • 3 Sell through contracts agencies already use, or through a partner who holds one.
  • 4 Plan your security authorization early, and claim only the status you hold.
  • 5 Make yourself findable with a public-sector page and peer references.

Why government is worth the effort

Government buyers are slow, but they are durable. A public body that adopts a product tends to keep it for years, and other public bodies copy what their peers use. One well-run city, agency or state can become a reference that opens dozens more.

The rules that make government slow also make it predictable. Purchasing thresholds, contract vehicles and security requirements are published. Award data is public. A startup can plan its entry path from written rules rather than guessing at an enterprise buyer’s unwritten ones.

The cost is time and patience. Expect longer cycles than commercial sales, paperwork before revenue, and security reviews that need planning months ahead. The steps below are about making that time count.

The framework at a glance

This guide works through five steps:

  1. Pick one level of government and one buyer.
  2. Start below the simplified thresholds.
  3. Sell through contracts agencies already use.
  4. Get the security authorization in order early.
  5. Be findable where public buyers look.

Figure 2 shows the federal purchasing thresholds and what each means for your first deal.

Step 1: Pick one level of government and one buyer

“The government” is thousands of separate buyers. Choose one level and one kind of buyer.

Figure 1 Four public-sector levels and a typical first path
  1. Federal Who buys Agencies, through contracting officers, with program staff as the users Typical first path A small first purchase, a pilot, or sales through a reseller that already holds a contract
  2. State Who buys State agencies, often through a central procurement office Typical first path Responding to requests for proposals (RFPs), or selling through a cooperative contract
  3. Local Who buys Cities, counties, special districts Typical first path Smaller purchases with local rules, cooperative contracts, referrals between nearby governments
Show the four levels as a table
Level Who buys Typical path for a startup
Federal Agencies, through contracting officers, with program staff as the users A small first purchase, a pilot, or sales through a reseller that already holds a contract
State State agencies, often through a central procurement office Responding to requests for proposals (RFPs), or selling through a cooperative contract
Local Cities, counties, special districts Smaller purchases with local rules, cooperative contracts, referrals between nearby governments
Schools and colleges Districts and universities See my guide to selling EdTech to school districts

Source: AAJ’s framework.

Example Co., step 1 Fictional

Example Co. sells permit-tracking software. Cities are its users, so it picks local government first, starting with mid-sized cities in two states where a neighboring city is already a customer.

Step 2: Start below the simplified thresholds

US federal agencies can buy small amounts with much less process. From October 1, 2025, the micro-purchase threshold rose from $10,000 to $15,000, and the simplified acquisition threshold rose from $250,000 to $350,000.[1] Below those amounts, the paperwork and the competition requirements are lighter.

Figure 2 The federal purchasing thresholds
$15,000 $350,000
  • Zone Range What it means for a first deal
  • Simplest buying Below $15,000, the micro-purchase threshold The least paperwork
  • Simplified procedures From $15,000 to $350,000, the simplified acquisition threshold Lighter paperwork and competition requirements
  • Full process Above $350,000 Far more process

From October 1, 2025 (previously $10,000 and $250,000).

Source: Federal Acquisition Regulation inflation adjustment, Federal Register, August 27, 2025[1]. The scale starts at zero.

For a startup, that suggests:

  • Price a first deal that fits. A pilot or a first-year license under the simplified threshold is far easier for an agency to approve than a multi-year enterprise deal.
  • Make the program team your champion. The people who will use the product make the case; the contracting officer makes the purchase. Market to the first and make the second’s job easy.
  • Have your paperwork ready. To bid on federal contracts directly, a company must register in SAM.gov, which also assigns a Unique Entity ID.[2]

State and local governments set their own thresholds and rules. Look up the purchasing rules for each target state or city before you price.

Step 3: Sell through contracts agencies already use

Many public buyers prefer to buy through contracts that have already been competed, because it saves them months.

  • Federal: the GSA Multiple Award Schedule. A long-term, government-wide contract with pre-negotiated terms. Getting on it takes time and has ongoing compliance obligations, so many startups sell through an authorized reseller that already holds a schedule first.
  • State and local: cooperative contracts. Groups such as NASPO ValuePoint run cooperative contracts that eligible public entities can buy from, usually without running a fresh competition of their own.[3]
  • Resellers and partners. Government-focused resellers and systems integrators already hold contracts and relationships. A partner can be the fastest first route.
Figure 3 Three routes to a first sale
  • Your own contract (GSA MAS) — Slower to get, broad reach.
  • A cooperative contract (e.g. NASPO ValuePoint) — State and local buyers.
  • A reseller or integrator — Fastest start.

Source: AAJ’s framework.

AI companies selling through the GSA schedule (August 2025) Real example

In August 2025, GSA announced government-wide “OneGov” agreements with two AI companies, both bought through its Multiple Award Schedule.

  • OpenAI, August 6, 2025: ChatGPT Enterprise for “a nominal fee of $1” per participating federal agency for one year.[4]
  • Anthropic, August 12, 2025: Claude for Enterprise and Claude for Government for $1 per participating agency, for up to one year, across the executive, legislative and judicial branches. GSA noted that Claude for Government “supports FedRAMP High workloads”.[5]

These are the terms announced at the time, not current pricing. Two lessons carry over to smaller companies: use a contract vehicle agencies already buy through, and make the first purchase so easy that approval is a formality.

Marketing’s job here is to make it obvious, on your public-sector page, which contracts and partners a buyer can use to buy you.

Step 4: Get the security authorization in order early

For cloud software, security authorization often decides whether you can sell at all.

  • Federal cloud: FedRAMP. The program authorizes cloud services for federal use. Its newer 20x approach describes “a new approach to cloud security assessment and authorization”, and it has run pilots at the Low and Moderate impact levels.[6] Check fedramp.gov for the current classes and timelines before you plan.
  • State and local: GovRAMP. Formerly StateRAMP, it rebranded as GovRAMP in February 2025 and aims to “unify cybersecurity frameworks across all levels of government”.[7]

Agencies check your status on the FedRAMP Marketplace, described by FedRAMP (as of November 5, 2026) as “a searchable and sortable database of Cloud Service Offerings (CSOs) that have achieved a FedRAMP designation”.[8] It shows three designations: Ready (an accredited assessor has attested to the offering’s security and the program office accepted the readiness report; valid for one year), In Process (actively working toward authorization) and Authorized.[8] Use exactly the designation the Marketplace shows on your public-sector page. “FedRAMP Ready” and “FedRAMP Authorized” are not the same claim.

Figure 4 FedRAMP Marketplace designations
  1. 1 Ready Assessor attested; valid one year
  2. 2 In Process Working toward authorization
  3. 3 Authorized Completed and maintained

Claim only the one you hold.

Source: FedRAMP, About the Marketplace[8].

You don’t need these to start conversations, but buyers will ask. Put your current status, and your plan, on your public-sector page. Never imply an authorization you don’t hold.

Step 5: Be findable where public buyers look

Government buyers research vendors much as other buyers do, plus a few public-sector habits:

  • A public-sector page: who you serve, relevant compliance status, the contracts and partners to buy through, and named government customers (with permission).
  • Peer references: public servants trust what other agencies have done. A case study from a neighboring city or a similar agency is worth more than any ad.
  • Associations and events: state and local government associations and their conferences, where buyers and users meet.
  • Public data: award data shows who bought what. Federal spending is published on USAspending.gov, which helps you find agencies that already buy your category.

Example Co., step 5 Fictional

Example Co. publishes a case study with its first city, written with the city’s permit office. It presents with that city’s staff at the state municipal league conference. Three nearby cities ask for demos; two buy through a cooperative contract the first city pointed them to.

Figure 5 How one city becomes three
  1. 1 Example Co.’s first city A case study, written with the city’s permit office
  2. 2 The state municipal league conference Example Co. presents with the first city’s staff
  3. 3 Three nearby cities Ask for demos
    • 4 Two of them buy
    • Through a cooperative contract the first city pointed them to
    • Three city customers

Fictional

Example Co. is fictional (Step 5). Cities copy their neighbors.

Common mistakes

  • Targeting “the government”. Thousands of separate buyers follow different rules. Pick one level and one buyer type.
  • Pricing the first deal like an enterprise contract. A first-year deal above the simplified threshold brings far more process. Start smaller.
  • Marketing only to the contracting officer. The program team that will use the product makes the case. Win them first.
  • Claiming an authorization you don’t hold. “FedRAMP Ready” is not “FedRAMP Authorized”. Use exactly what the Marketplace shows.
  • Skipping partners. Resellers and integrators with existing contracts can get you in years earlier than your own contract vehicle.
  • No public-sector page. Buyers who find no government customers, compliance status or buying route assume you’re not ready.
  • Underestimating time. Plan cash and staffing for long cycles, and treat early pilots as the investment they are.

A checklist before your first government bid

  • I’ve chosen one level of government and one buyer type.
  • The company is registered in SAM.gov, if selling federally.
  • The first offer is priced to fit the simplified buying rules where possible.
  • I know which contract vehicles, cooperative contracts or partners a buyer can use.
  • I know our security authorization status and plan, and state them accurately.
  • A public-sector page lists customers (with permission), compliance status and how to buy.
  • I’ve looked up past awards in our category on USAspending.gov or the state’s procurement site.

How to measure progress in government sales

  • Pilots started and converted to paid contracts.
  • Time from first meeting to purchase order, split by whether an existing contract was used.
  • Reference customers willing to speak or co-present, and referrals between public bodies.
  • Inbound from the public-sector page and associations against outbound.
  • Security authorization milestones against plan, since they gate larger deals.

Examples from different fields

The path is the same, a small first purchase, existing contracts and the right authorization, but the buyer and the proof differ. These examples are fictional and illustrative.

AI startup selling document-processing to a federal agency. The program office wants faster case processing; the contracting officer wants a small, low-risk buy. Start with a pilot priced under the simplified acquisition threshold, run on non-sensitive documents, with a measured result (hours saved per case). Be ready to explain how the model is evaluated and where data is processed, and plan the FedRAMP path before production.

EdTech company selling to a state education agency. State agencies often buy through RFPs or statewide contracts that districts can then use. One statewide contract can open many districts, so the marketing investment goes into proposal-ready proof: outcomes data, accessibility conformance and the student-data agreement.

GovTech SaaS for city permitting. Cities copy their neighbors. Win one well-known city, publish the case study with its staff, present together at the state municipal league, and list the cooperative contract other cities can buy through.

Cybersecurity vendor selling to states and counties. Security authorization and references from other public bodies decide. Show your GovRAMP status, offer a short assessment for one agency, and, where a state runs a cybersecurity grant program, plan outreach around its timeline.

MedTech or health-data company selling to public health departments. Expect long procurement and strict data agreements. Lead with interoperability with the department’s existing systems and with what data you never touch. Pilots often come through grant-funded projects, so track the grant calendar.

Hardware or drone company selling to public-safety agencies. Buyers will check where components are made and whether the product meets agency rules on approved suppliers. Put that information up front, alongside demonstrations for the agency’s operators.

What changes by stage?

  • Seed — One level of government, pilots below the simplified threshold, SAM.gov registration, a reseller or partner if one fits.
  • Series A — A public-sector page, case studies, cooperative or schedule contracts, a security authorization plan.
  • Series B — A dedicated public-sector team, contract vehicles of your own, and the authorizations your largest buyers require.

If you want me to look at your own funnel, positioning and channels, my Growth Audit ends with three prioritized fixes and a 30-day action plan.

Related on AAJ

References

The superscript numbers in the article match this list.

  1. Federal Acquisition Regulatory Council. “Federal Acquisition Regulation: Inflation Adjustment of Acquisition-Related Thresholds.” Federal Register 90, no. 164 (August 27, 2025). Effective October 1, 2025. govinfo.gov
  2. U.S. General Services Administration. “Entity registration.” SAM.gov. Accessed November 5, 2026. sam.gov
  3. NASPO ValuePoint. “About.” Accessed November 5, 2026. naspovaluepoint.org
  4. U.S. General Services Administration. “GSA Announces New Partnership with OpenAI, Delivering Deep Discount to ChatGPT,” news release, August 6, 2025. gsa.gov
  5. U.S. General Services Administration. “GSA Strikes OneGov Deal with Anthropic,” news release, August 12, 2025. gsa.gov
  6. FedRAMP. “FedRAMP 20x.” Accessed November 5, 2026. fedramp.gov
  7. GovRAMP. “StateRAMP Announces Rebrand to GovRAMP,” February 14, 2025. govramp.org
  8. FedRAMP. “About the Marketplace.” Accessed November 5, 2026. fedramp.gov

More in Sales & Pipeline

Part of the Sales & Pipeline hub - see all 38 resources on this topic.

Also useful in Industry Playbooks.