For contractor teams centralizing permit operations across active municipalities.
Permit portfolio dashboard
Portal connections
Alerts and tasks
Team permissions
Best when one team needs a command center now.
Pricing
Seat pricing for teams that share permit work.
Project managers, coordinators, renewals desks, and field crews need the same operating picture. The pricing model should reflect that instead of turning portal noise into a billing event.
01
No per-permit tax for noisy municipal data.
02
No fake enterprise packaging just to get basic rollout help.
03
Start with the team that feels the pain first, then expand deliberately.
For multi-office firms rolling out shared workflows, billing controls, and connector expansion.
Everything in Core
Priority connector roadmap
Custom onboarding
Portfolio reporting
Best when connector depth and rollout support become the limiting factor.
What is in the product
Four layers matter. Everything else is implementation detail.
The product has to keep the portfolio, the connector truth, the team model, and the daily workflow lined up in one system.
01
Portfolio control
A shared dashboard, one lifecycle, clear owners, and a visible next step on every permit.
02
Connector operations
Connection coverage, sync health, and a straight answer on which municipal data can be trusted.
03
Team access
Seats, roles, and cleaner handoffs between PMs, coordinators, and field crews.
04
Operational workflows
Permit detail, inspections, tasks, and setup that match the way a contractor office actually works.
Rollout posture
Buy the first shape of the rollout, not the fantasy version.
Permit software becomes real when one team depends on it every day. That is the bar to hit first.
Start with the office, coordinator group, or municipality cluster already wasting time on status reconciliation.
Use one shared lifecycle and one ownership model before adding more seats, markets, or connector work.
Move to Growth when rollout support and connector depth become the actual bottleneck, not because the pricing page says you should.
FAQ
The questions worth asking before rollout starts.
Why price per seat instead of per permit?
Because permits are handled by teams, not by one person. Seat pricing matches shared ownership better than charging you for every noisy record in a portal.
Is the Growth plan only for enterprise teams?
No. It is for teams that need more rollout help, more connector coverage, or more structure across offices and jurisdictions.
Can we start with a focused rollout?
Yes. That is the sensible way to do it. Start with the municipalities causing the most drag, then expand from there.