Long before large language models, public procurement had its own artificial intelligence. You write a list of questions, send it to a dozen vendors, and wait. A few weeks later, expert answers roll in: architectures, migration plans, five-year cost models, all written by senior people who aren't being paid for any of it.
That's an RFI.
The Bay Area Air Quality Management District's website modernization RFI is a fine example of the genre. To be fair, it's well run: it's platform-neutral, candid about what's undecided, and staff answered 184 vendor questions on schedule. But it asks for two front-end models priced separately, migration costed three ways and a five-year total cost of ownership. It also says no award will come from it, responses won't be scored, and anything submitted can be reused without attribution.
So the deal is: do weeks of discovery work for free, for a small chance of being invited to do more of it later.
We did it anyway. All of it.
Then we published it. Every answer is on one page, in the RFI's order, along with what we'd actually build and why Drupal is the best fit for what the agency needs.
Here's the twist. An RFI gathers expertise for one agency, once. A public page gets read by every agency with the same problem, and by the AI tools they now ask first. The next time someone asks a chatbot how to get off a licensed CMS before an ADA Title II deadline, it may well be reading our answers.
The Air District wanted vendors to do its thinking. Fine. Now we're doing everyone's.
Joking. Mostly.
What's on the page
- Why a public agency's website is emergency infrastructure, starting with the day San Francisco's sky turned orange.
- How AI speeds up a web team in Drupal, and why its guardrails are enforced by permissions and workflow, not by asking the model nicely.
- What 13,750 PDFs mean for an accessibility deadline, and why triage beats remediation.
- All 48 RFI items answered, including a real cost scenario.
Built the way we'd build theirs
The page has more than 110 components. Claude, working through Drupal's Tool API and MCP, built it: choosing components, setting options, uploading images and writing alt text. It could draft. It couldn't publish. A person reviewed every pass, and the page lists what went wrong along the way and how review caught it.
Tell us where we're wrong
Comment below. Comments here are moderated automatically by AI for relevance. If yours adds to the discussion and isn't spam, it's automatically published by an AI within a few minutes.
And if you're the next agency drafting an RFI: read the page first, then ask us about whatever it doesn't cover. That's cheaper for everyone. Or just talk to us!
Comments
0 comments
No comments yet.
No new comments remain in this discussion.
Add new comment