A proposed fixed-price permitting-intake pilot
Discuss an illustrative permitting workflow and a separately scoped $7,000, 60-day pilot. Your jurisdiction determines every purchasing requirement, approval, and documentation obligation.
Proposed scope only. Illustrative proposed pilot only. No working PermitDesk application, public intake portal, production AI workflow, payment connection, third-party integration, or implemented security control is represented as existing. Every production capability requires a separately scoped, buyer-approved implementation.
Define the proposed scope
A proposed pilot can evaluate one jurisdiction-approved permit or license workflow, subject to actual staff requirements, available records, data permissions, and a separately agreed implementation plan.
Your jurisdiction decides how it may purchase
Your purchasing team alone determines the applicable process, required approvals, documentation, and whether a pilot purchase is permitted. A quote or purchase order is available only if your jurisdiction confirms that its own rules allow it.
No purchasing exemption, contract vehicle, guaranteed eligibility, or production implementation is represented.
Evaluate the actual public preview
The public homepage contains an illustrative fictional-data preview. It is not a working PermitDesk application, connected jurisdiction portal, implemented integration, or measured customer result.
Verify production requirements separately
Data access, security controls, buyer and vendor permissions, integrations, implementation work, acceptance criteria, and any future subscription must be separately reviewed and approved.
Review a separately scoped jurisdiction pilot
Discuss the illustrative workflow, your actual requirements, and the purchasing approvals your jurisdiction determines.
Discuss a proposed pilot