Documentation
Seat Management Model
The first commercial version is built around organization-level subscriptions and seat-aware access control.
Seat Management Model
PermitLens is sold to contractor teams, not to isolated individual users.
Core billing assumptions
- One organization owns the subscription.
- One active subscription represents the product plan.
- Stripe quantity represents paid seats.
- Invites and active memberships should not exceed paid seat count.
Why this matters
Permit work is shared by design.
Permit status, reworks, inspections, and connector triage are not one-person jobs. The access model has to reflect the way a contractor office actually operates or the billing model will fight the workflow.
What this avoids
- Charging teams more just because a portal emits more records
- Pretending every user is an independent buyer
- Letting invites and active access drift away from what was actually purchased
Previous Getting Started
Understand how the Astro marketing site and Next.js product app fit together in the PermitLens monorepo.
Support Need a rollout conversation?
When the product questions turn into operational questions, move it into a live demo and implementation plan.