AI for City Hall: what YC wants and how to validate it
Original request by Gustaf Alströmer, Y Combinator. Source: YC Requests for Startups.
The request in plain English
Building permits take so long that some projects never get built, and city staff are buried in manual code checks and correction cycles. YC wants AI that clears that backlog, starting with permits and expanding to 311, public records, licensing, and inspections.
What YC's request says
- Permitting delays are long enough that some projects are never built.
- YC estimates that approving US building permits in 10% of the current time would give cities $16 billion a year in extra tax revenue.
- There are roughly 19,000 cities in the US.
- YC says companies it already funds are selling AI to government, and some are growing very fast.
Why now
Permit review is a document-heavy, rules-based process: check plans against zoning and building codes, flag issues, send corrections, repeat. That is work current AI handles well, especially when a human reviewer signs off on the final decision.
Cities also have a strong incentive to move. Faster permits mean more housing, more construction, and more tax revenue. That makes the ROI story concrete, which is unusual in government software.
How to sell to city hall
Start with the department that feels the most pain and has a measurable backlog. Permit review fits: there is a queue, a turnaround time, and a public that complains about both.
Small and mid-size cities often buy faster than large ones and are underserved by legacy vendors. Winning a handful and publishing the before-and-after turnaround numbers is the best sales asset you can have.
Three startup ideas to start from
Plan review assistant
Check submitted plans against zoning and code requirements and draft correction letters for a human reviewer to approve.
Applicant-side permit prep
Help builders and homeowners submit complete, compliant applications the first time, cutting correction cycles.
AI for 311 and records requests
Triage and answer resident requests and public records demands, the next step after permits.
How to validate it before you build
- Get one city's permit data: volume, average turnaround, and number of correction cycles.
- Shadow a plan reviewer for a day and time each step. Your product replaces the slowest ones.
- Run a parallel pilot where your tool reviews the same plans as staff, and compare results.
- Learn the city's purchasing threshold. Staying under it can turn a year-long procurement into a quick decision.
The founder trap
Underestimating local variation. Every city has its own codes and amendments. Build for configurability early, or each new city becomes a custom project.
IdeaCheck's take
Clear pain, measurable ROI, and a huge number of buyers. Sales cycles are the main risk; starting with smaller cities and the applicant side can speed things up.
Test your version
Check your idea against Hacker News
Building something in govtech? See what 28,000 Hacker News threads say before you commit.
Your first evaluation is free with Google sign-in.