Dataset · Buying agencies

Every agency that buys — and the context that decides whether they buy from you

The agency record is the spine of the platform. Every signal, contract, contact and purchase order hangs off one of them, which is why a signal arrives already knowing the budget, the fiscal calendar, the incumbent, and the person who owns the line.
Agencies that actually buy
100K+
Record per agency, name variants resolved
1
States covered
50 + DC
Residents at the small end
~3,000

One record, everything attached to it

A name and a population is a mailing list. What makes an agency record worth anything is the money, the calendar, the incumbents and the people, kept in one place and refreshed together.

  • Name variants resolved, so one agency is one record
  • Fiscal year start, because it decides when to call
  • Every other dataset joins here, not the other way round

record: agency

County
name
Sumter County, Florida
population
145,300
fiscal_year_start
October 1
budget_fy27
$612,000,000
contracts
37 active · 4 expiring within 180 days
contacts
18 verified · 2 appointed this year
open_signals
6
coop_vehicles
Sourcewell, state term contract
Built from: adopted budget FY27, board minutes, award register, staff directory

The six kinds of buyer

SLED is not one market with one sales motion. Each type has its own governing body, its own calendar, and its own reason for buying — which is why the record carries the type and you can filter on it.
  • State agencies

    Departments, authorities, boards and statewide programs, each publishing its own budget and award records.

    Typically buys

    Enterprise systems, statewide services, large infrastructure programmes.

    What makes it different

    Longest cycles and the biggest contracts — and state term contracts other agencies can buy from without running their own RFP.

  • Counties

    Boards of commissioners or supervisors, plus sheriffs, clerks, health departments and public works.

    Typically buys

    Public safety, roads and bridges, ERP and permitting, health services.

    What makes it different

    Often the budget of record for everything rural inside their borders, so one win covers a wide area.

  • Cities & towns

    Councils and their departments: utilities, police and fire, parks, planning, public works.

    Typically buys

    Utilities and metering, fleet, body cameras, websites and permitting.

    What makes it different

    The most numerous type and the most talkative — council minutes are where the earliest signals surface.

  • K-12 school districts

    School boards with published agendas, plus facilities, technology, transportation and nutrition departments.

    Typically buys

    Devices and networks, facilities and HVAC, buses, security, food service.

    What makes it different

    Capital work runs on bonds and installs in the summer, so the buying conversation starts a year ahead.

  • Higher education

    Universities, community colleges and their system offices, each with several buying centres.

    Typically buys

    Research and campus IT, facilities, housing, athletics, procurement services.

    What makes it different

    More than one budget holder per campus, so the right contact matters more here than anywhere else.

  • Special districts

    Single-purpose bodies with their own boards: water, transit, ports, libraries, fire protection, drainage.

    Typically buys

    Treatment and SCADA, fleet and rolling stock, specialised equipment.

    What makes it different

    Easy to miss because they sit on no city or county list — and often the actual buyer for the category.

What the record carries

Four groups of fields. Identity tells you who they are; the other three tell you whether, when, and through whom they will buy.

Identity

  • name · aliases
  • type
  • state · county
  • population | enrollment
  • website · portal

Population and enrollment are the honest proxy for budget size when a budget is not published.

Money

  • fiscal_year_start
  • adopted_budget
  • spend_by_category
  • purchase_orders
  • coop_vehicles

The fiscal calendar is the most underused field here. It tells you which month the conversation is actually open.

People

  • procurement_officers
  • department_heads · cio
  • board_members
  • email · direct_line
  • appointed_at · verified_at

Contacts live on the agency, not in a separate list, so they age with the agency rather than silently going stale.

Activity

  • open_signals
  • contracts · expires_at
  • open_solicitations
  • incumbent_vendors
  • meeting_cadence

This is the join to every other dataset. Follow an agency and these are what change under you.

How far down coverage goes

Down to towns and districts of about 3,000 residents. Most mid-market vendors find their next ten deals well below the metros.

Texas, as a worked example

Agencies tracked
7,336
Counties covered
100
Sectors represented
26
Projects tracked
880
Browse the Texas directory

How a record stays true

Agencies change quietly. Nothing announces that a director left or a budget was adopted — it just appears in a document.

  • DailyNewly published documents are pulled in daily, so a field changes within days of the meeting that changed it.
  • FYBudgets roll when the agency adopts them, not on a calendar year we impose.
  • NewAppointments and departures surface as their own signal types, so a contact change reaches you rather than waiting to be noticed.
  • SrcEvery populated field traces to the document it came from.

What the agency record makes possible

Four things in the platform that only work because the record exists and stays current.
  • Meeting prep

    A briefing written from live data: contracts, incumbents, recent signals, and what to lead with.

    Agency Profile
  • Look-alike search

    Find agencies that resemble your best customers on type, size, budget and vendor mix.

    List Builder
  • Territory planning

    Cluster nearby agencies into routes, so a day of visits is planned around who is actually in play.

    Pipeline
  • Account enrichment

    Your CRM accounts filled in with budgets, contacts and renewal dates, syncing both ways.

    Integrations

Questions about agency coverage

An entity that runs its own procurement and publishes its own records: roughly 100,000 of them, each counted once, so a city is one agency. We follow the departments, boards and school sites beneath each one, because that's where signals surface, but we don't count them as buyers. The buying agencies are the ones that carry a full record.

Down to towns and districts of about 3,000 residents. Coverage thins where an agency publishes little, and the record shows you which fields are missing rather than filling the gap with an estimate.

All 50 and the District of Columbia. Each state has a public directory page showing the agencies, projects and signals we hold for it, browsable before you sign up for anything.

Contacts carry the date they were last verified, and appointments and departures surface as signals in their own right — so a change reaches you rather than sitting in a field that quietly went stale.

Because the sales motion differs. A school district buys on a bond and installs in the summer; a special district has its own board and appears on no city or county list. Filtering by type is usually the first cut a territory plan makes.

Yes. Build a segment in List Builder and push it to HubSpot or Salesforce in one click, or export CSV. Lists refresh daily and add new agencies that match your filters on their own.

All FAQs

Start finding government buyers today.

Signals from 100,000+ state, local and education agencies, months before the RFP. Free to start.

No credit card required