Verdant

Verdant's most defensible idea is not the permit workflow — it is that every answer has to carry its citation. Ordinance benchmarking compares your code against named peers (Portland, Seattle, Denver, Minneapolis, Sacramento in the homepage example) and each cell links to the source section, so a planner brings evidence to a commission instead of a summary. Plan review follows the same pattern: an ADU intake form validates heated floor area against an 800 sq ft detached-ADU cap, and review flags a 25 ft side setback as failing a 30 ft requirement with § 151.2 attached — 3 of 4 checks passed, 1 flagged with its citation. That is a real workflow, not a chat window over a PDF. Strengths: the modular structure (intake, plan review, constituent communication, report generation, ordinance research) is configured to your ordinances, workflows and forms rather than forcing your forms into someone else's template, and the platform is explicitly mapped to existing forms. Intake, review and decision are treated as one system, which means no re-keying between steps. It is browser-based with no on-premise install, which matters for small IT teams. The founding team has public service backgrounds, and the about page is unusually blunt about the problem — one-size-fits-all local government software that is expensive, confusing, and needs an engineer on staff to set up. Weaknesses to weigh honestly: this is a v0.1-era company. The changelog's only entry is July 3, 2026, when the marketing site launched, and the seed data puts it at 200+ applications across four cities. The AI model names behind the review and benchmarking are not disclosed anywhere in the available evidence, which makes it hard to assess accuracy ceilings or where your data goes. Nothing about integrations is documented in what we could reach, so if your department lives inside an existing GIS or ERP stack, that is an open question to raise in the walkthrough. Where it fits: small and mid-sized city planning departments digitising paper permitting, reviewers who want automatic citation flagging instead of manual code cross-referencing, and zoning officials who need peer benchmarking with a source link behind each number. Where it doesn't: private-sector developers and architecture firms managing their own submittals, state or federal permitting, large counties with deep ERP/GIS integration needs, and any team that requires a long reference-customer track record before signing. Treat the demo as a scoping conversation about your ordinances and forms — that configuration work is the product.