If you had to put a number on it, a government sale usually takes six to eighteen months from first real contact to signed contract, and a complex or enterprise procurement runs eighteen to thirty-six months or longer. A 2022 Gartner survey that vendors keep quoting puts the average government and education technology cycle at 22 months, while federal IT guidance commonly quotes 12 to 24 months.
The reason those numbers sit so far apart is that the length is not one thing. It is a small purchase made on a purchase order next to a multi-year enterprise software program running through a formal competitive solicitation, and the second one can take four times as long. Everything below breaks the range into the pieces you can actually plan against: how long each stage takes, which factors stretch it, and what a vendor controls.
Table of Contents
- How Long a Government Sales Cycle Usually Takes
- Why Government Sales Cycles Take Longer
- Fiscal-year budgets decide when money can move
- Competition is a legal requirement, not a sales tactic
- Security and privacy review adds a separate queue
- Accessibility and legal review are mandatory
- Many people have to agree
- The handoff to the contracting office
- Protest and rebid risk
- What is structural and what is avoidable
- How Long a Government Sales Cycle Usually Takes by Stage
- What Changes the Timeline Most
- How to Plan a Realistic Government Sales Timeline
- Common Reasons a Government Deal Gets Stuck
- Frequently Asked Questions
- Is a 9-month government sales cycle normal?
- How long does government procurement usually take?
- Are government pilots faster than full contracts?
- Does a higher government contract value always mean a longer sales cycle?
- How can a vendor reduce delays in the public procurement process?
- What is the rule of 2 in government contracting?
- Conclusion
How Long a Government Sales Cycle Usually Takes
A typical government sales cycle runs about six to eighteen months end to end, which is roughly three to five times longer than a comparable private-sector software deal. Complex procurements stretch that to eighteen to thirty-six months, and anything touching sensitive data, physical infrastructure or a multi-agency rollout can push past three years.
Here is how the duration changes with the procurement pathway, which is the single biggest lever you have.
| Procurement pathway | Typical duration | What drives the length |
|---|---|---|
| Informal pilot, demo or proof of concept | 3 weeks to 3 months | Staff availability and an informal agreement to try it; usually no money moves |
| Micro-purchase or small purchase | 1 to 3 months | Value stays under the agency threshold that requires competition |
| Purchase through a cooperative contract vehicle | 3 to 6 months | The vehicle is already competed, so the agency just needs internal approval and a task order |
| Sole-source or single-source award | 4 to 8 months | Writing a justification, an approval chain, and sometimes a public notice period |
| Full competitive RFP or RFQ | 9 to 18 months | Solicitation drafting, mandated public comment, proposal window, evaluation panel, award |
| Major enterprise or multi-year program | 18 to 36+ months | Security authorization, integration with legacy systems, legal review, executive sign-off |
Notice how the same product can be bought three different ways. A city that buys a permitting system through an existing cooperative agreement moves in months; the same city running a formal RFP for the identical scope will spend a year on the process alone.
If you have seen wildly different answers to this question, that is not noise. The number one organic result for this query is a Reddit thread in r/agency where agency owners report closing in a week, and others report cycles that run for years. They are usually talking about different pathways, and often about whether the contract was signed or merely agreed in principle.
Why Government Sales Cycles Take Longer
Most of the delay comes from a handful of institutional requirements, and each one is there for a reason. Knowing which are structural and which are just poor project management saves a lot of frustration.
Fiscal-year budgets decide when money can move
Public money can only be obligated inside an approved budget. The federal fiscal year runs October 1 to September 30, while many state, local and school entities run July 1 to June 30. A need that is approved and funded in the fourth quarter of the fiscal year waits for new money in the first quarter, which quietly adds three to six months to an otherwise finished deal.
Competition is a legal requirement, not a sales tactic
Above certain values, an agency must publish a solicitation and accept competing proposals. That sets a floor under the timeline, because public comment periods, question deadlines and evaluation windows cannot be compressed by a vendor who wants the award. Thresholds differ by jurisdiction and move over time; Texas raised its municipal sole-source threshold to 100,000 dollars from 50,000 before 2023, and California school districts use a separate figure of 119,100 dollars that adjusts with inflation each year.
Security and privacy review adds a separate queue
Software touching citizen data, utility systems or health information gets reviewed on its own timeline. Expect to answer architecture questions, supply audit reports, and sometimes submit to a formal authorization process. Two to six months is common, and it happens in parallel with procurement rather than before it.
Accessibility and legal review are mandatory
Federal and most state buyers require Section 508 accessibility conformance for anything user-facing, plus legal review of terms, liability and data-handling clauses. Vendors that cannot answer accessibility questions quickly tend to lose weeks in the Q&A period.
Many people have to agree
A program office may support the purchase while the IT department, finance, legal, procurement and an elected official or board all have a say. Consensus building is slow by nature, and calendars conflict. Every additional approver adds weeks rather than days.
The handoff to the contracting office
Once a requirement moves from the end user to the acquisition shop, you lose direct access and often lose information with it. The contracting officer owns the schedule from that point, and their workload, not your urgency, sets the pace.
Protest and rebid risk
Public contracts can be challenged, which makes agencies cautious. A cautious agency builds in evaluation time and rarely skips a step, even when the step looks like padding from the outside.
What is structural and what is avoidable
Fiscal calendars, required competition, security review and protest exposure are structural. Treat them as fixed costs of doing business. Avoidable delay comes from selling before a budget exists, arriving after requirements are written, missing a stakeholder who can stop the deal, and proposing only at the RFP stage instead of shaping the requirement earlier.
How Long a Government Sales Cycle Usually Takes by Stage
Here is the stage-by-stage view most teams find useful, with what you can do while the agency works through its own steps. The vendor action column matters as much as the duration, because most of the calendar is not yours to compress.
| Stage | Typical duration | What you can do while waiting |
|---|---|---|
| Discovery and problem validation | 1 to 4 months | Document the current process, cost of doing nothing, and who feels the pain daily |
| Buying authority and budget check | 1 to 3 months | Map the end user, the budget owner and the person who signs; confirm a funded line exists |
| Pilot, RFI or business case | 2 to 6 months | Run a scoped pilot with written success criteria and a date on the calendar |
| Procurement path and solicitation | 2 to 5 months | Get onto the right vehicle early; prepare a compliance matrix before the solicitation issues |
| Proposal response and evaluation | 2 to 4 months | Answer every question in writing, keep the compliance matrix current, avoid late surprises |
| Due diligence and security review | 1 to 4 months | Pre-clear audit reports, architecture diagrams and data-flow documentation |
| Negotiation and legal review | 1 to 3 months | Know which terms are negotiable; flag liability and indemnity positions early |
| Approval, award and kickoff | 1 to 4 months | Confirm signature authority and the effective date; ask for the performance timeline in writing |
A few terms worth knowing before you read the table. An RFI is a request for information, usually used to size the market, and it rarely leads to an award. An RFQ asks for pricing against known requirements. An RFP asks for a technical approach plus price, evaluated either lowest price technically acceptable or best value. A sole source skips competition and needs a written justification, usually because only one product meets the requirement.
A cooperative contract vehicle is an existing competed agreement, such as NASPO ValuePoint, OMNIA Partners, Sourcewell or a GSA schedule, that lets an agency buy from an approved list without running its own solicitation. Buying through one of those is usually the fastest legal route available to a new vendor.
What Changes the Timeline Most
Contract value is the factor people expect, and it matters, but it is not the only one. Ranked by how much they actually move the number, these are the levers that matter.
- Buying method. A vehicle purchase can take three months where an RFP takes fifteen. Establish the pathway before you build a forecast.
- Number of approvers. Each added layer typically adds three to six weeks. Count them before the kickoff meeting, not after.
- Data sensitivity. Anything touching health, financial or utility data pulls in a formal security review, adding one to six months.
- Legacy integration. Work against a mainframe, an on-premises system or a proprietary standard turns a software sale into a professional services project with a different calendar.
- Agency maturity. A shop with an experienced acquisition team and a current procurement plan moves faster than one building the process as it goes.
- Local content and labor rules. Prevailing wage, local hiring or domestic content requirements can reshape staffing and pricing, and take time to sort out.
- Fiscal and political uncertainty. A funding freeze or an election cycle can push a signed deal past the end of the year regardless of readiness.
Consider a city replacing its parking citation and payment system. If the current vendor holds an expiring contract, the city’s own procurement staff, and the replacements already sit on a vehicle, the sale can be structured and signed inside six months. The same project run as a formal competitive RFP, integrating with the city’s legacy citation database and handling payment card data, is a twelve to eighteen month job with a security review in the middle.
Same product, same buyer, very different calendar. The first one is a task order; the second is a program.
How to Plan a Realistic Government Sales Timeline
Planning a government timeline is mostly about sequencing your own work against a calendar the agency controls. A workable method has eight moves, and you can start the first three before anyone asks you for a proposal.
- Map the buying authority. Name the end user, the budget owner and the signature authority. If you cannot name all three, you do not yet have a deal.
- Confirm the procurement pathway. Ask which threshold applies and whether a vehicle is an option. This single answer can move your forecast by a year.
- Work backwards from the fiscal calendar. Find out when the budget was or will be approved and when the fiscal year turns. In 2026, a request that misses the funding window waits a full cycle.
- Set stage-gate dates. Assign a target date and an exit condition to each stage, so a stalled deal shows up as a missed gate rather than a slow drift.
- Keep a compliance checklist from day one. Build the matrix before the solicitation exists so you can fill it from evidence you already have.
- Prepare evidence early. Audit reports, accessibility conformance statements and data-flow diagrams take weeks to assemble. Start them at the pilot stage.
- Assign owners with real authority. Someone needs to answer procurement questions, and someone else needs to answer technical ones. Confusion between those roles is how deals stall quietly.
- Build one contingency. Decide in advance what happens if the deal misses the fiscal year: a deferral, a phased scope, a multi-year structure, or an unsolicited proposal under FAR Subpart 15.6 for federal buyers.
Here is the milestone template I would use to keep a forecast honest.
| Milestone | Target date | Exit condition | Owner |
|---|---|---|---|
| Authority confirmed | Month 2 | End user, budget owner and signer named | Account lead |
| Pathway chosen | Month 4 | Threshold and vehicle decision documented in writing | Account lead |
| Pilot complete | Month 7 | Success criteria met, sponsor willing to advocate | Solutions lead |
| Compliance package ready | Month 9 | Matrix, audit reports and accessibility statement complete | Operations |
| Proposal submitted | Month 12 | All mandatory items delivered before the deadline | Bid manager |
| Earliest realistic award | Month 15 | Confirmation from the contracting officer | Account lead |
One cost worth modelling: a full RFP response can absorb hundreds of staff hours across solution engineers, compliance and legal. If you enter a solicitation cold, you are spending that effort with no influence on the requirements. Vendors who engage before a specification is written do not just answer the question better; they are frequently the only bid that matches what was actually asked for.
Common Reasons a Government Deal Gets Stuck
Most stalled public-sector deals share a small number of causes, and each has a specific fix. Here is what to look for and what to do about it.
- You sold before a budget line existed. The agency agreed the problem was real but had no funded line to buy from. Fix: ask which budget the money would come from before you invest in a pilot, and target a funding cycle rather than a calendar year.
- A required stakeholder was never in the room. IT security, finance or legal had not seen the project and objected later. Fix: build the stakeholder list during discovery and meet each one before the pilot ends.
- You entered at the RFP stage. Requirements were already written without you. Fix: get in earlier, even with a standard presentation, so your language appears in the specification.
- You treated a pilot as procurement. The pilot succeeded, nobody owned the follow-up, and the momentum leaked away. Fix: define the procurement pathway and a decision date in writing at the start of the pilot.
- Security review was underestimated. Fix: send your architecture and audit documentation during the pilot rather than after the award notice.
- Everything depended on one champion. That person changed roles or left. Fix: build a second sponsor and a relationship inside the acquisition shop, not just the program office.
Sometimes the honest answer is that the opportunity is finished. If the agency has committed its budget elsewhere, the incumbent holds a vehicle position with years remaining, or the sponsoring official has left, keep the relationship and move on. Chasing a dead cycle costs more than it wins.
Frequently Asked Questions
Is a 9-month government sales cycle normal?
Yes, nine months sits close to the middle of the range and is common for a formal competitive procurement of mid-sized software or services. Anything under six months usually means a purchase through an existing contract vehicle or a value below the competitive threshold. Anything past eighteen months points to a complex program with security review, integration work or a fiscal-year delay built in.
How long does government procurement usually take?
It depends almost entirely on the pathway. A micro-purchase or small purchase can finish in one to three months, a cooperative contract vehicle purchase in three to six, a sole-source award in four to eight, and a full RFP in nine to eighteen. Federal IT procurements are commonly described as taking 12 to 24 months, while a broader government and education technology average sits near 22 months.
Are government pilots faster than full contracts?
Pilots move faster because little or no money moves. A pilot can run in three weeks to three months because it often uses existing staff time and a letter of intent rather than a procurement instrument. The catch is that a pilot is not a contract, so it creates momentum rather than revenue. Agree the procurement pathway and a decision date in writing before the pilot begins, or it tends to end quietly.
Does a higher government contract value always mean a longer sales cycle?
No. Value matters because it usually pushes a purchase above a competitive threshold, but the pathway matters more than the number. A modest purchase through an existing cooperative contract vehicle can close faster than a large one run through a formal RFP with security review and multi-agency approvals. Judge each opportunity by its pathway, approval count and data sensitivity rather than by contract value alone.
How can a vendor reduce delays in the public procurement process?
You cannot compress the agency’s calendar, but you can remove your own delays. Confirm the procurement pathway early, meet the stakeholders who can stop the deal, prepare your compliance package before the solicitation issues, and get onto a contract vehicle where one fits. Working backwards from the buyer’s fiscal year and agreeing stage-gate dates internally keeps surprises out of the schedule.
What is the rule of 2 in government contracting?
It is not a legal rule, just shorthand that circulates among vendors. People use it loosely to mean that in public-sector sales you should expect roughly two years from first conversation to signed contract, or that you need two years of runway in your plan. Treat it as a planning assumption rather than a fact, then replace it with the range for your specific buyer and pathway.
Conclusion
Plan for six to eighteen months on a typical government sale, and eighteen to thirty-six for anything complex, then adjust hard for the procurement pathway. Before you commit to a close date, verify five things: which procurement method applies, who holds the buying authority, when the budget window opens, how the agency will evaluate proposals, and the earliest realistic approval date from the contracting officer.
Get those answers and the timeline writes itself. Skip them and you are forecasting on hope.
