How to sell software to government agencies

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.