Company profile · 3 min read
Verdant brings AI-supported permitting workflows to local government
Verdant provides a shared government workflow foundation and internal agents that gather context and support permitting review while staff retain decisions.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
Verdant is building an AI infrastructure layer for local government, starting with permitting. The fit is a public team with a high-volume workflow and enough authority to keep staff in control of decisions.
What it does
Verdant’s current site describes a system of record where rules, records and workflow context are available to staff and internal agents. Its first use case is permitting: agents gather context, check submissions and support review while government staff decide. Verdant homepage YC profile
The public YC profile says Verdant has processed 200+ applications, deployed in four cities and reached four paid deployments with an average close time of four weeks. These are company-reported commercial and activity figures, not an independent government-adoption study.
Why I’d look closer
Government software has a harder constraint than ordinary workflow software: the system must explain what happened, preserve records and fit a process that is accountable to citizens. Verdant’s current framing is useful because it keeps staff in the decision loop rather than presenting an autonomous permit decision as the product.
The founders’ backgrounds match the wedge. The YC profile describes Aidan Ng’s government and commercial-real-estate experience and Jason Yi’s prior local-government and legislative-tracking work.
What could make it the wrong choice
Local-government procurement is slow, jurisdiction-specific and hard to generalize. A buyer should ask how local rules are represented, how records are retained, how staff override a finding, how residents are notified, and what happens when a submission is incomplete or ambiguous.
The public sources do not provide pricing or a complete implementation plan. “Four cities” is company-reported and should not be treated as a universal deployment pattern.
My editorial take
I would shortlist Verdant for a local government with a specific permitting backlog and an internal owner who can define the rules and review the system. I would not start with “AI for government.” Start with one permit type, one queue and one auditable handoff. The product’s real promise is capacity without removing public accountability.
Cohort context
Verdant is listed in Summer 2026. In our 2026-09-18 directory snapshot, 1 of 232 listed companies in that cohort have YC’s primary industry label Government (0.4%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19T16:19:17.351Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Not observed in this response |
| H1 or H2 heading | Observed |
| Typed structured data | Not observed in this response |
| Docs/developer link | Not observed in this response |
| Pricing link | Not observed in this response |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
About the author
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.
First1000 ↗ · X ↗