How long does it take to sell software to a government agency?

Commonly nine to eighteen months from first conversation to signature, driven by the annual budget cycle, security review, and procurement timelines. Purchases under the small-purchase threshold or through an existing contract move much faster.

Do government agencies require SOC 2 for software purchases?

Many do, and more ask for it every year. Some states also require a standardized security assessment. Expect a detailed security questionnaire even where no formal attestation is mandated.

Can an agency buy software without a bid?

Yes, when the purchase falls under its small purchase threshold, when it buys from a cooperative or state term contract, or when a documented sole source justification applies.

Who is the real decision maker for a government software purchase?

Usually the department manager who owns the problem and the budget, but IT and procurement can each stop the purchase. All three need to be addressed.

Guide

How to sell software to government agencies

State and local agencies buy software through a longer path than commercial buyers: a department identifies a need, funding is requested in the annual budget, IT and legal review security and data terms, and procurement runs a competitive process or uses an existing contract vehicle. Deals commonly take nine to eighteen months from first conversation to signature. The way to shorten it is to be involved while the need is being defined and the budget request is being written, not after the request for proposals posts.

The money decides the timeline

Unless a purchase fits under a small-purchase threshold or an existing contract, it needs a budget line. Departments build requests months before the fiscal year starts, finance consolidates them, and the council or board adopts the budget. A request that misses that window waits a year.

This is why the most valuable conversation is the one that happens while a department manager is drafting next year's request. At that stage you are helping define the scope and the number instead of responding to someone else's version of both.

Four ways in

Software rarely arrives through one door. Know which of these applies before you invest in a pursuit.

Under the small purchase threshold — a department buys a limited subscription directly, often as a pilot.
Competitive procurement — a published request for proposals with weighted evaluation criteria and a formal committee.
Cooperative or state term contract — an existing competitively awarded vehicle the agency can buy from directly.
As a subcontractor or module under an incumbent system integrator already holding the contract.

Security and data review will happen

Expect a security questionnaire, questions about where data is hosted and who can access it, and contract language covering data ownership, breach notification, retention, and what happens at termination. Agencies increasingly ask for a recognized security attestation such as SOC 2, and some states require a standardized assessment before purchase.

Public records law is the part commercial sellers miss. Data in your system may be subject to disclosure requests, and the agency needs to be able to produce it. Records retention schedules may also require exports the agency can keep after the contract ends.

Pilots are useful and dangerous

A small paid pilot inside the purchasing threshold is a legitimate way to prove value and build the internal case for a budget request. It also produces the reference an agency's peers will ask for.

The risk is a pilot that never converts because no one owned the budget path. Agree at the start on what success means, who will sponsor the funding request, and which fiscal year it lands in. A pilot without that agreement is unpaid product feedback.

Sell to the department, prove to IT, close through procurement

Three groups have to be satisfied and they care about different things. The department manager cares about the operational problem. IT cares about security, integration, and support burden. Procurement cares about a defensible process and clean contract terms.

Losing any one of them stalls the deal indefinitely. Map all three early, and give the department sponsor the material they need to answer the other two on your behalf when you are not in the room.

Last reviewed August 2026

How Hank automates this

Hank reads the budget approvals, board minutes, and capital and strategic plans published by cities, counties, districts, and state agencies, so you hear about a funded technology need while it is still being scoped. It names the staff contacts to reach and, once a solicitation posts, extracts the requirements and evaluation criteria.

Book a demo

Common questions

Related guides

The government fiscal year buying cycle

How cooperative purchasing contracts work

Who to call at an agency before the bid posts

What is Hank?

Hank is how companies find, pursue, and win state and local government work. Every day it reads tens of thousands of sources — agency portals, board packets, budget approvals, capital plans, meeting minutes, and expiring contracts published by cities, counties, school districts, and state agencies — and surfaces what matters to your service lines in real time, often months before a solicitation posts. When the solicitation does post, Hank breaks it down into scope, key dates, submission requirements, evaluation criteria, and compliance items, names the people at the agency to contact, and drafts a first-pass proposal from your own past work. Every signal, contact, document, and pursuit stays in one place your team works out of.