The short version
- Government overall: 22 months on average for technology purchases, with scope changes alone adding about seven months (Gartner, survey of 1,120 executives).
- Cities and counties: 3–9 months for small jurisdictions buying under the bid threshold; 9–18 months for anything that needs an RFP and a council vote.
- K-12: most districts take 6–11 months from identified need to signed contract; add a school year if a pilot is required.
- Higher ed: departmental deals close in 3–9 months; campus-wide systems take 12–18.
- Utilities: 6–18 months at public power and co-ops; 12–24 months and more at investor-owned utilities, driven by the rate-case calendar.
- What shortens it: being in the budget before the RFP, cooperative contracts, and giving buyers the references and documentation they say they lack.
Sales cycle length by segment
Ranges are first qualified conversation to signed contract, for a purchase large enough to need a formal approval. Search the table by segment or keyword.
Showing all 9 segments
| Segment | Typical cycle | Why it takes that long | Fastest path | Source |
|---|---|---|---|---|
| Small cities and townsUnder ~50,000 residents; special districts behave similarly | 3–9 months | Purchases often sit under the formal-bid threshold; one department head and a city manager can decide; council approval is a single agenda item. | Quote under the small-purchase limit, or a cooperative contract the city can piggyback on. | Pulse RevOps smart-city playbook (6–12 months for small cities); SaasDash |
| Mid-size and large cities50,000+ residents; anything over the bid threshold | 9–18 months | Budget request in one fiscal year, RFP in the next; IT security review; council or committee vote; protest window. | Get into the adopted budget before the RFP is written; be the incumbent's reference-checked alternative. | Pulse RevOps (9–15 months mid-market, 18–24 top-50 cities); Civic IQ (9–18 months) |
| CountiesBoards of commissioners or supervisors; sheriff, health, elections and public works buy separately | 9–18 months | Multiple elected officials with their own budgets; purchasing often centralized in a county procurement office; capital items tied to the CIP. | Department-level pilots paid from operating funds, then a board-approved contract in the next budget. | Civic IQ procurement guide; NationGraph (6–18 months) |
| State agenciesExecutive-branch departments and statewide IT | 12–24 months | Legislative appropriation, statewide procurement rules, formal RFPs with scoring committees, and the longest protest and contract-review steps. | Statewide or NASPO ValuePoint contracts that let agencies order without a new solicitation. | Gartner (22-month average for government technology); SaasDash (6–18 months for state agencies) |
| K-12 school districts~13,000 districts; July 1 fiscal years almost everywhere | 6–12 months, 12–24 with a pilot year | Decisions follow the school calendar: evaluate in fall and winter, budget in spring, buy in summer. A classroom pilot adds a full school year. | Enter the evaluation in September–January so you are in the budget adopted in spring; supplemental tools under the bid threshold move fastest. | EdWeek Research Center survey of 223 leaders (37% take 6–11 months; 22% take 12–17); Tyton Partners (2024 cycles ran 30% longer than 2023) |
| Higher educationPublic universities follow state codes; private campuses set their own | 3–9 months departmental; 12–18 months campus-wide | Departments and colleges hold their own budgets and can buy below threshold quickly; enterprise systems (ERP, SIS, LMS) go through central IT, procurement and often a board. | Sell to a dean or department first, then expand; cooperative contracts (E&I, state higher-ed contracts) skip the RFP. | SaaS Hero (3–9 month departmental cycles); Starbridge higher-ed guide |
| Public power and co-op utilitiesMunicipal electric, water and gas systems; rural electric cooperatives | 6–18 months | Boards meet monthly, budgets follow the city or co-op fiscal year, and engineering staff are small, so one champion carries the deal. | Pilot in one department, reference from a peer utility, then a board-approved contract; APPA and NRECA events shorten trust-building. | Read the Impact (plan 6 months to pilot); Pulse RevOps water KPIs (specs written 6–18 months before bid) |
| Investor-owned utilitiesLarge electric and gas IOUs under state regulation | 12–24 months; 18–36+ for rate-case-funded programs | Spending must be approved in a rate case; pilots are run by innovation teams and then re-sold to operations; NERC CIP and vendor-risk reviews add months. | Time outreach to the rate-case cycle and get written into the next filing; a 6-month pilot followed by an 18-month contract is a realistic plan. | Pulse RevOps energy playbook (12–24 months); Read the Impact (6 months to pilot, 18 to contract); Energy Central (12–48 months at large IOUs) |
| Federal civilian and defenseFor comparison | 18–36 months | FAR rules, FedRAMP and CMMC requirements, and appropriations that arrive late in the fiscal year. | GSA schedules, SBIR/OTAs and teaming with an incumbent prime. | SaasDash; Starbridge (12–36 months) |
K-12 in detail: the EdWeek distribution
The most specific public data on any SLED segment comes from an EdWeek Research Center survey of 223 district and school leaders (June 2025), who were asked how long a district-wide purchase takes from identified need to signed contract.
Showing all 6 ranges
| Time from identified need to signed contract | Share of districts |
|---|---|
| Under 3 months | 7% |
| 3–5 months | 16% |
| 6–11 months | 37% |
| 12–17 months | 22% |
| 18–23 months | 13% |
| 2 years or more | 6% |
Two things follow. First, more than half of districts (59%) take six to seventeen months, so a vendor who first meets a district in February will usually not see revenue until the following school year. Second, supplemental and classroom tools move faster than district-wide platforms: roughly a third of districts buy survey and quiz tools in under three months. Tyton Partners' annual survey of K-12 company executives found 2024 cycles ran about 30% longer than 2023 as ESSER funds expired, a reminder that the ranges move with the funding climate.
Where the months go
Gartner's public-sector buyers described three stages (exploration, vendor engagement, contracting) that each take three to twelve months. Mapped to how a city or district actually operates, the timeline looks like this.
Showing all 5 stages
| Stage | When | What you can do |
|---|---|---|
| Need identifiedDepartment head flags a gap, audit finding or end-of-life system | 12–18 months before award | Be the vendor that educates; this is where 'lack of specific information from the provider' causes Gartner's delays. |
| Budget requestLine item added to the operating budget or capital plan | 9–15 months before award | Help the champion write the justification and a realistic cost estimate. |
| Budget adoptedCouncil, board or legislature approves the spending plan | 6–12 months before award | Read the adopted budget; funded items are public buying signals. |
| Solicitation drafted and postedRFP, RFQ or bid; or a cooperative-contract purchase instead | 3–6 months before award | If you are not already known to the evaluators, your odds drop sharply. |
| Evaluation and awardScoring committee, demos, references, negotiation, protest window | 1–3 months | Have government references ready; Gartner found 68% of buyers blame delays on missing vendor information. |
What actually shortens the cycle
- Enter before the budget is adopted. Agencies publish their intent 6–18 months before any RFP, in budget requests, capital plans, council minutes and strategic plans. A vendor who is in those conversations is shaping the requirements; one who arrives at the RFP is responding to a competitor's.
- Pick the procurement path, don't just accept it. A purchase under the small-purchase threshold, a cooperative contract (Sourcewell, OMNIA, NASPO ValuePoint, TIPS, E&I) or a statewide contract can cut a 12-month RFP cycle to a few weeks. Our procurement thresholds by state page lists the limits.
- Remove the information gap. In Gartner's survey, 68% of government buyers blamed delays on a lack of specific information from the vendor. Public-sector references, security documentation, pricing that fits the agency's contract vehicles and a clear implementation plan all remove months.
- Work the calendar. 46 states and most districts start the fiscal year July 1; the budget that funds your deal is written the previous winter. Our fiscal-year calendar shows the windows.
- Keep the pipeline full enough to wait. With cycles this long, the only way to hit a quarterly number is to have started the conversations a year earlier. That is the arithmetic behind outsourced B2G business development: steady first meetings today become closings in two to four quarters.
How we use these numbers
When Kensington Sales Group plans a government outbound program, we size the pipeline backwards from the client's segment: roughly 9–18 months for cities, counties and K-12, 12–24 for states and investor-owned utilities. The first meetings a BDR books in month one are the deals that close at the end of the following fiscal year, so we measure the program on qualified meetings and pipeline created, and set closing expectations against the ranges above. See how many meetings a B2G SDR books per month for the other half of the math.
Method and sources
Ranges combine published survey data (Gartner 2022; EdWeek Research Center 2025; Tyton Partners 2023–2024) with practitioner benchmarks published by government sales-intelligence and GTM firms (Civic IQ, Starbridge, NationGraph, Pulse RevOps, SaasDash, Read the Impact, Energy Central), each linked in the table. Where sources disagree we show the overlap. Figures are for the United States and were checked on November 7, 2026. Corrections: sales@kensingtonsalesgroup.com.
Cite or share this data
Free to reuse with attribution: "Kensington Sales Group, SLED Sales Cycle Length by Segment (2026), kensingtonsalesgroup.com/resources/sled-sales-cycle-length.html".