Proposed business-license intake workflow
Discuss whether a separately approved pilot should evaluate new business-license applications, document requirements, and existing department handoffs.
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.
Business-license review requirements
Document the jurisdiction's actual license categories, applicant records, staff reviewers, approval responsibilities, and existing systems. Renewals, notifications, fee calculation, and production workflows are not implemented.
Confirm buyer and vendor permissions
Any records access, third-party export, payment processor, transfer method, vendor interface, or system mapping must be separately authorized, implemented, and independently verified.
Separate proposed requirements from implemented capabilities
The public website shows an illustrative fictional-data preview only. No working product, deployed integration, production security control, customer result, savings estimate, or implementation schedule is claimed.
Review a separately scoped jurisdiction pilot
Discuss the illustrative workflow, your actual requirements, and the purchasing approvals your jurisdiction determines.
Discuss a proposed pilot