GovSpend AI Search | Juan Huaco

5
GovSpend modules in one question: 29K+
bid sources behind the answers (2025): 2M+
public meetings transcribed in 2025: 2
places to ask: the platform and Slack

How it started

GovSpend's search was built the way data platforms usually are: keywords and filters. Powerful once you know the schema, slow when you only know the question. In November 2025 the platform launched AI Search, a chat where you ask in plain language, available to any user with the GovSpend AI permission on their subscription. I worked on it as a developer alongside the team that shaped it.

The problem

A seller knows what they want to find: which agencies in their territory bought from a competitor last year, which contracts expire soon, what a district said in a meeting about a purchase. Turning that into the right combination of modules, filters and date ranges is a different skill, and while the intelligence lives across datasets, the person still has to search, filter, compare and connect the dots by hand.

The approach

You ask in plain language. AI agents on GovSpend's MCP server search the five modules, meetings, bids, contacts, contracts and purchase orders, and the open web if you want it, with your profile as context by default. The answer is a table of the top results with a link to every record and, since December 2025, a line on why each one is there. Follow-up questions refine it, and saved searches can be listed, run, created and exported from the same chat.

Every result is a record you can open

On procurement data, a confident wrong answer is worse than none, because nobody notices. So the answer is not a paragraph: it is a table of records, each with a link into GovSpend and a line on why it is relevant. The language layer decides what to search and what to show first; what it shows is always something you can check.

One server behind every door

In February 2026 GovSpend's release notes said AI Search was now powered by a new MCP, crediting it with better stability, more datasets and faster responses. A webinar recap on its blog that June adds that the MCP server, the one external assistants connect to, helps power AI Search and the Slack app, though neither needs MCP access to use. One backend, three ways in: the platform, Slack, or your own assistant.

Three doors, one server: GovSpend says its MCP server, the one external assistants connect to, helps power AI Search and the Slack app, and that since February 2026 a new MCP is behind AI Search. What it searches: the five GovSpend modules and, if you want, the open web. Sources: the product page, a webinar recap on its blog and the release notes.

Your profile is the context

The question 'are there open bids relevant to me?' only works if the system knows who you are. AI Search uses the customer profile, territory, products, market, as context by default, so short prompts still get specific answers; a toggle turns it off for generic ones, and a filter picks GovSpend only, the open web, or both.

On screen · tap to enlarge

The Help Center article: AI Search, powered by an MCP server built so AI agents can search across GovSpend.

What comes back: a table of the top results, a link to every record and the reasoning behind them.

On govspend.com/ai: natural-language prompts across all modules and the open web, powered by the custom MCP server.

Try it here

Three questions from GovSpend's public docs and blog, taken apart: which words pick the module, the topic, the place and the time, and what shape the answer comes back in.

moduletopicplacetime

Module: Contracts
Source: GovSpend
Profile: On by default: territory, products, market
Returns: A table of the top results, a link to each record, and why it is relevant
Follow-up: “Who are the incumbents on those?”

The questions are GovSpend's own examples. The breakdown is illustrative: how the agent resolves them is the product's business.Read the AI Search guide

What's next

AI Search keeps changing: launch in November 2025, relevance explanations in December, the move to the new MCP server in February 2026, Slack in June. Today any user with the GovSpend AI permission on their subscription has it in the platform's left menu. GovSpend's 2025 review said it would reach Slack, Copilot and wherever teams already work; Slack came first.

Nov 2025
AI Search launches: plain-text prompts across all modules, in a chat
Feb 2026
Moves onto the new MCP server: more datasets, faster responses
Jun 2026
Available from Slack, no technical setup
Sep 2026· now
Available to every user with the GovSpend AI permission

Stack

MCP Protocol
AI agents
Chat UI

Public sources

All projects