Enterprise permitting suites, paper and email, or a lean system: choosing permitting software for smaller jurisdictions

Option 1: Enterprise permitting platforms

Platforms in the Accela, Tyler EnerGov, and OpenGov class offer broader land-management and community-development capabilities that can include permitting, planning, code enforcement, and licensing. If your jurisdiction needs integrated workflows across many divisions, a broader enterprise suite may be the better fit.

The trade-off is scope. An enterprise implementation can involve a formal procurement, dedicated agency project staff, and a larger implementation effort. For a smaller jurisdiction focused on application intake and routing, that broader scope may exceed the immediate problem being solved.

Option 2: Paper, email, and spreadsheets

The status quo in many small and mid-size jurisdictions is not a legacy system; it is no system. Applications arrive at the counter, in the mail, and as email attachments. Someone sorts them, someone walks them between departments, and a spreadsheet, or a very experienced clerk, tracks where everything stands.

To be fair to it: there is no software cost, no procurement, no training, and no vendor. For a very low volume of simple permits, with stable staff who know the process cold, it genuinely works.

The costs are just paid elsewhere. Applications get lost or sit unnoticed in an inbox. Incomplete submittals are discovered weeks in, after a reviewer finally opens the file. Applicants call and visit the counter because it is the only way to learn their status. And leadership has no metrics: no turnaround numbers, no backlog visibility, no way to know whether this month is better or worse than the last. The process also lives in a few people's heads, which becomes a real problem the day one of them retires.

Option 3: A lean, purpose-built system

The third option is software scoped to the core of the permitting and licensing job and nothing else: online intake, completeness checking, classification and routing, fee calculation, status tracking, and inspections scheduling. This is PermitDesk's approach.

For a smaller jurisdiction, much of the practical burden can sit in intake and shuffle: applications arriving in inconsistent shapes, incomplete submittals caught late, files walked between departments by hand, and staff time burned on status calls. A lean system attacks exactly that, uses AI to do the checking, classifying, and applicant guidance (with every determination left to staff), and connects to the finance, GIS, and records systems you already run instead of replacing them. Setup is measured in weeks, pricing is published and flat, and the pilot is priced to fit under most small-purchase thresholds, so trying it does not require a formal solicitation.

What a lean system deliberately does not do is replace an enterprise suite's breadth. It is not a full land-management platform, a code-enforcement case system, or a planning module. If you need those in one integrated package, you are shopping in option 1.

When each one fits

An enterprise suite is the right call when...

• You are a large city or county with high volumes, many divisions, and complex land-management needs beyond permitting.
• You have the budget, the project staff, and the appetite for a broader implementation, and you want one integrated platform for community development.
• Your process requirements genuinely need deep, agency-specific configuration across planning, enforcement, and permitting together.

Staying on paper and email is defensible when...

• Your volume is very low, your permit types are simple, and turnaround is genuinely not a complaint from applicants or the council.
• Your staffing is stable and the institutional knowledge is not at risk.
• There is truly no budget line, even a small one; software you cannot pay for does not help you.

A lean system is the right call when...

• Your pain is concentrated in intake, completeness, routing, and status, and applicants and staff are feeling it.
• A broader enterprise implementation is out of proportion to your size, or has already been considered and shelved.
• You want to keep your existing finance, GIS, and records systems and add a working front door, not run a replacement project.
• You want to prove it on real applications before committing, on a budget a department head can approve.

How to evaluate, whatever you choose

A few questions cut through any vendor's pitch, ours included: Can we see it run on our own permit types before signing? What exactly happens to an incomplete application, and who finds out? Where does our data live, can we export all of it, and what happens at contract end? What does the AI decide on its own, and what does it merely propose? And what is the all-in cost through go-live, not just the license line? PermitDesk's answers to the security, data-ownership, and AI-boundary questions are published on our trust page; hold every vendor to the same standard.