One search across 13,000 state and local portals.
samsearch is an AI platform for state, local and education procurement. It crawls 13,000 state, local and education procurement portals, reaching around 50,000 buying agencies across all 50 states. That covers state governments, counties, cities, school districts, universities, and transit and utility authorities.
Search in plain English. Read a summary instead of a bid package. Be told when an addendum moves a date. Get the bids worth your time pushed to you.
Book a DemoThe SLED problem is not depth. It is scatter.
Federal work is hard because the packages are long. State and local work is hard because there is no single place it is published.
There is no SAM.gov for SLED
Every state runs its own system. Most large counties and cities run another. Districts and universities often run a third. A long tail of authorities post a PDF to a web page and nothing else.
No shared format, no shared taxonomy
Jurisdictions do not agree on categories, and most have no notion of a NAICS code. The same requirement is described a dozen ways across a dozen portals.
Registration walls, one per portal
Several sources require an account before you can even see a package. samsearch maintains that access so your team does not have to keep fifty logins alive.
One feed, with the source attached
Bids are normalised into consistent fields and indexed for semantic search. Each record keeps its jurisdiction and its portal, so every result is traceable back to where it was published.
Bid documents, read before you open them
A SLED package is shorter than a federal one and just as disqualifying. The conditions that rule you out are rarely in the summary.
The whole package, on arrival
Specifications and drawings. Bid forms and pricing sheets. Insurance, bonding and licensing conditions. Prevailing wage schedules. Everything is read as it lands.
A summary you can decide from
Scope, quantities, place of performance, key dates and the terms that most often disqualify a bidder. Written in plain English, before anyone opens a document.
The conditions that decide it
Bonding thresholds, insurance limits, local preference rules, licensing requirements and mandatory pre-bid attendance. These are pulled out as fields, not left inside a PDF.
Cited back to the page
Every extraction points to its document and page. You verify a citation rather than trusting a summary, which is what makes it usable on a real bid decision.
Addenda are tracked, and you are told
State and local addenda move deadlines and change scope exactly as federal amendments do. They are published with far less ceremony.
An addendum on a county solicitation is often a replacement PDF. No summary of what moved, posted to a portal you would have to remember to check. Teams find out the due date changed when they submit late.
What happens on an addendum
- The package is read again
- It is diffed against the previous version
- Changed fields are listed, not buried
- Tasks carrying old dates move with them
- Everyone watching the bid is notified
Fields compared
- Bid opening and question deadlines
- Pre-bid meeting date and attendance
- Quantities and specifications
- Bonding and insurance requirements
- Award criteria and evaluation method
Why it matters more here
- Windows are short, often two to three weeks
- Addenda land late in the window
- Portals rarely email non-registered vendors
- A missed addendum can void a bid outright
Every bid graded against your profile
Fill in a company profile once. Every new bid across 13,000 portals is read and scored against it, continuously.
Scored with its reasoning
Each recommendation carries a fit score and a plain-English reason citing the passage it came from. You can disagree with it, which is the point.
Territory applied first
State, jurisdiction type, named agency and place of performance are filtered before scoring. A service radius is a hard constraint, not a preference.
Local advantage recognised
Many jurisdictions weight or reserve awards for in-state, in-county or local vendors. Where you have a presence, that is a scored advantage and the grading knows it.
Licences and certifications matched
State contractor licences, DBE, MBE and WBE status, and prequalification where a jurisdiction requires it. Matched against what each bid actually asks for.
Saved searches that qualify before they email you
Across 13,000 portals and 50,000 agencies, a keyword alert is unusable. Qualification happens before the email is sent.
Save a search per territory
Most teams run one saved search per state or service area rather than one that returns everything. Keywords, a plain-English description, or your whole profile.
Every source is watched
New bids across all 13,000 portals are picked up continuously, and their documents processed rather than just their titles.
AI drops the weak matches
Each candidate is graded against your profile and territory. What survives is a shortlist, not everything that contained your keyword.
A digest you can act on
Daily or weekly, with the score and the reason on each item, and links straight to the bid rather than to a search page.
What is covered
- Jurisdictions
- All 50 state governments
- Counties and parishes
- Cities, towns and villages
- School districts, K-12
- Universities and community colleges
- Transit, water, port and housing authorities
- Portals aggregated
- BidNet Direct
- Bonfire
- Periscope
- OpenGov Procurement
- Ionwave
- DemandStar, Bid Express and the long tail
- On every record
- Jurisdiction and issuing department
- Source portal, so it is traceable
- Due date, question deadline, pre-bid meeting
- Set-aside and local preference requirements
- Bonding, insurance and licensing conditions
- Addendum history
- Derived by samsearch
- Plain-English package summary
- Extracted conditions and requirements
- Fit score with its reasoning
- Addendum diff history
- Cooperative vehicle, where one applies
Why teams search SLED at all
The market is larger than federal in aggregate, and it behaves nothing like it.
Less competition per bid
A county solicitation is seen by the vendors who happen to watch that county. The same work federally would draw a field several times larger.
Local preference is a real edge
Many jurisdictions weight or reserve awards for local vendors. If you have a physical presence somewhere, that is a structural advantage federal work does not offer.
Faster cycles, smaller packages
SLED solicitations are often a fraction of the length of a federal RFP. Awards come in weeks rather than quarters, which suits teams that cannot carry a nine-month capture.
No federal registration to start
Most jurisdictions run their own vendor registration and do not require a SAM.gov UEI. SLED is where many companies win their first public-sector contract.
Co-op vehicles multiply one win
A contract awarded through a co-operative purchasing organisation can be used by other members without recompeting. One award can serve many buyers.
The work recurs
Facilities, transportation, food service, IT support and maintenance renew on predictable cycles at every jurisdiction. That makes the pipeline forecastable.
Frequently Asked Questions
What is SLED procurement?
Where are state and local contracts published?
How many state and local sources does samsearch cover?
Does samsearch summarise state and local bid documents?
Does samsearch track addenda on state and local bids?
Can I ask questions about a bid document?
How is SLED different from federal contracting?
Can I search state and local alongside federal?
Can I filter to my state, county or city?
Will I get alerted when a matching bid is posted?
How quickly do new state and local bids appear?
Do you cover cooperative purchasing contracts?
Do I need a federal registration to bid on state and local work?
Can samsearch help write the bid response?
Who uses samsearch for state and local contracts?
See your territory in one feed.
A demo runs against your service area and your capabilities, not a prepared example.