Rollout

Start with the permit workflow already wasting time.

PermitLens is set up around the coordinator group, properties, and source checks that matter first. The pilot should prove less portal chasing before the rollout gets bigger.

Scope pilot Open demo

Team shape

How many people need shared visibility, ownership, and handoffs across the permit workflow.

Geographic scope

Which South Florida county or municipality cluster creates the most repeated portal-checking work today.

Data coverage

Which records the coordinator must prove first: permits, violations, lien signals, inspections, or property context.

Rollout support

Whether the first pilot is a single queue, one office, or a portfolio of active jobs already causing drag.

Start here

Focused rollout

Scoped pilot

We scope the first version around the properties, municipalities, and source checks already slowing the handoff-heavy workflow down.

Best when one office or coordinator group is already losing time to repeated property and permit checks. Start narrow, prove the workflow, then expand.

Targeted workspace: Shared visibility, owners, next actions, and permit context for the team actively running the first workflow.

County + municipal search: Search-backed access to permits, violations, lien-related signals, property context, and source coverage for the pilot surface.

Lean access control: Seats and role-based access for the people in the workflow now, instead of forcing a company-wide rollout on day one.

Pilot support: Rollout guidance around source coverage, queue ownership, and the repetitive portal work already causing operational drag.

Scope pilot Open demo

Use this when the goal is to fix one painful workflow first.

Expand here

Portfolio rollout

After pilot proof

We widen coverage after the first rollout is working cleanly, adding more teams, municipalities, and shared records into the same operating model.

Best after the first workflow proves itself and multiple teams need the same operating model across more properties or active jobs.

Cross-team workspace: Shared portfolio visibility across offices, coordinators, and project leads who need the same operating layer.

Broader record coverage: Search-backed access to property context, permits, violations, and lien-related signals across a wider municipal footprint.

Access + governance: Organization seats, role permissions, and a cleaner handoff model across multiple teams instead of shared logins and inbox forwarding.

Expansion support: Source planning, rollout sequencing, and workflow alignment as coverage expands across active jobs and teams.

Scope pilot Open demo

Use this when multiple teams need the same operating model.

Pilot proof

The first rollout needs a scorecard.

The pilot should prove a measurable change in the weekly coordinator workflow before pricing or coverage expands.

Time to prepare one property status packet before and after PermitLens

Weekly portal or source checks replaced by visible coverage rows

Permits with an assigned owner and next action instead of a spreadsheet note

Municipal source gaps discovered during the pilot and ranked for expansion

FAQ

The rollout questions worth answering before you start.

Do you publish a flat public price right now?

Not yet. PermitLens is still a sales-assisted pilot. Scope depends on team size, source coverage, and the workflow you want to prove first.

Can we start with one office or one use case?

Yes. That is the preferred rollout path. Start where permit operations are already creating drag, then widen coverage after the workflow proves out.

What changes the rollout scope most?

Usually the combination of source coverage, active job count, and how many people need shared access to the same follow-up workflow.