How a mid-size city should buy permitting & land-management software

Permitting and land-management is one of the most frequently replaced and most failure-prone systems a city operates. A 50,000-to-300,000-resident jurisdiction usually has no internal software-evaluation function, buys this system once a decade, and lives with the consequences in the form of permit backlogs that frustrate residents, builders, and elected officials alike. This guide is the shortlist-and-scoring process we'd run for a city of that size — opinionated on purpose, because a neutral checklist that refuses to take positions is what produces a 200-line requirements matrix nobody can act on.

The single most important decision you will make is not which vendor you pick — it is how honestly you scope what you actually need before you talk to anyone. Most failed permitting procurements were lost at requirements definition, not at the demo.

Start with a requirements checklist you can defend

Separate requirements into must-haves and nice-to-haves before any vendor sees them, and keep the must-have list short enough that a majority of credible vendors can clear it. A bloated must-have list doesn't get you a better system; it gets you a sole-source justification for whichever vendor wrote the spec.

For a mid-size city the genuine must-haves are: configurable permit-type workflows your own staff can edit without a change order; a self-service applicant portal with online payments; electronic plan review (EPR) for commercial work; a mobile inspection app that works offline in the field; tight GIS/parcel integration; and open, documented APIs so you are not held hostage at renewal. Treat instant/automated approvals for simple permit types, contractor licensing, and pre-built reporting as differentiators, not gates.

Score on a weighted rubric, not a gut feel after the demo

Demos reward showmanship. A weighted scoring rubric, filled in by the same three or four people for every vendor against the same scenarios, is the discipline that keeps a slick presentation from beating a better-fit product. We weight five dimensions: fit-to-workflow (30%), implementation risk and references (25%), total cost over seven years (20%), integration and data portability (15%), and vendor viability (10%).

Make every vendor run your scenarios, not their canned demo: intake a commercial tenant-improvement permit, route it through two department reviews, fail an inspection, and reissue. You learn more from watching a vendor configure one real workflow live than from an hour of slides.

Pricing-band guidance

Public bid tabs and awarded contracts make this category unusually transparent on price. For a mid-size city, expect annual subscription in roughly the $120k–$350k range depending on modules and population, with one-time implementation typically landing at 0.8x–1.5x of first-year subscription. Be skeptical of any bid where implementation is priced far below that band — it usually means the configuration work has been deferred into costly change orders later.

Insist on seeing the renewal escalator in writing. A modest annual subscription with a 7%–10% uncapped yearly increase is more expensive over a seven-year horizon than a higher starting price with a 3% cap.

Implementation-risk flags

The flags that most reliably predict a troubled permitting implementation: a vendor who will not give you references at your population band and permit volume; a proposed timeline under six months for a full multi-department replacement; data migration treated as the city's problem rather than a scoped deliverable; and a configuration model that requires the vendor for every workflow change.

Ask each finalist for two references that went badly and what they changed. Vendors worth buying from can answer that question. The ones who insist every deployment was flawless are the ones whose reference checks you should pursue hardest.