Permitting software your jurisdiction can actually afford.
PermitDesk is a proposed fixed-price pilot for cities and counties evaluating permit intake, document review, and department routing. The preview below is illustrative sample data, not a working production application. Every capability requires a separately scoped and approved implementation.
Offered by JS Technology Solutions, Inc. The sample figures and workflow below are illustrative. No production customer, implemented system, or performance result is represented.
From application to the right desk, without the paper shuffle.
A proposed jurisdiction-approved pilot could evaluate these four workflow stages. The stages are not an existing production implementation.
Intake
Discuss whether an approved pilot should assess online intake, staff-entered submissions, and the jurisdiction's actual document requirements.
Classify & check
Identify whether staff-reviewed permit types and document checklists belong in the separately agreed pilot scope.
Route
Map existing department handoffs and determine which routing or fee-related requirements, if any, should be evaluated.
Track & decide
Define the status information staff need to review. Permit and licensing decisions remain with authorized jurisdiction personnel.
A preview of the proposed pilot.
The proposed workflow centers on two views: a permit-queue dashboard showing routing and missing documents, and an application view with the file, completeness check, and fee.
August 2026 · Intake summary
Sample workspace| Permit / license type | Received | Complete | On-time | Open |
|---|---|---|---|---|
| Building permits | 418 | 94% | 61 | |
| Business licenses | 306 | 88% | 72 | |
| Trade permits (elec/plumb) | 281 | 97% | 18 | |
| Sign permits | 142 | 95% | 14 | |
| Special event permits | 137 | 85% | 52 |
Application · Residential addition, 214 Oak Street
Missing documentIllustrative sample figures and interface only. No working PermitDesk application, production portal, implemented fee engine, or live jurisdiction data is represented.
Workflow requirements to evaluate with your jurisdiction.
Online application intake
A pilot could assess application intake requirements. No working public intake portal is represented as deployed.
Application classification & completeness
Discuss permit categories, document checklists, and the staff review required for any future implementation.
Cross-department routing
Identify the jurisdiction's actual departments, handoff rules, approvals, and any proposed routing requirements.
Fee calculation
Any fee-related requirement must be separately scoped against the jurisdiction's approved fee schedule. No fee engine exists today.
Status tracking & notifications
Evaluate what status information authorized staff and applicants would need. No notifications or applicant portal are represented as implemented.
Inspections scheduling
Inspection scheduling would require its own separately approved requirements and implementation. No scheduling system is represented as existing.
Staff retain every permitting decision.
The public page illustrates a possible future intake workflow. No implemented AI classification, automated routing, document analysis, or applicant assistant exists today.
Completeness on arrival
Any completeness-review workflow would depend on separately approved permit checklists, authorized records, and jurisdiction staff review.
Classification and routing
Potential classification and department-routing requirements must be defined and approved before implementation. No automated workflow is deployed.
Plain-language applicant guidance
Applicant communication would require an agreed review process and a separately built implementation. No applicant assistant or measured savings is claimed.
Any future automation, audit logging, or data-handling controls require separate scoping, buyer approval, and verification. Permit and licensing determinations remain with jurisdiction staff.
Evaluate your existing systems before scoping a pilot.
No finance, GIS, land-management, payment, API, or file-transfer connection has been deployed. Every possible mapping requires jurisdiction and vendor authorization, security review, and separate implementation.
Potential integrations require verification
A jurisdiction and its existing vendors must confirm whether an authorized export, mapping, or API is available. No connector or production integration is represented as deployed.
Any data exchange, access permission, security control, cost, and implementation timeline must be separately scoped and verified.
Explore the workload: Building permit intake · Business licensing · Plan review & document validation · Citizen self-service portal. Or read the pilot purchasing guide and the technical docs.
Practical resource: permit correction lists and applicant follow-up.
Define and verify security controls before any jurisdiction data is used.
Access control, data handling, logging, hosting, and review evidence are proposed pilot requirements, not implemented or independently verified production controls.
Applicant-data protection
Data minimization, access restrictions, and record logging must be separately designed, approved, and verified before any production data is processed.
Full audit trail
Audit-log requirements, retained events, reviewer access, and record-retention periods must be defined and independently verified for any future pilot.
Security-review ready
The jurisdiction determines its actual security questionnaire, review evidence, required approvals, and whether any proposed implementation is acceptable.
Humans hold the controls
Any future pilot must retain issuance, denial, applicant communication, and other government decisions with authorized jurisdiction staff.
Your data stays yours
Encryption, hosting, data ownership, export formats, model-use restrictions, and disposal must be separately agreed and verified before implementation.
Built to not lose an application
Monitoring, response handling, application tracking, and reliability requirements would require separate approved implementation and verification.
A permitting rollout sized for your jurisdiction.
The proposed 60-day pilot has a published fixed price. Potential later subscription pricing is illustrative and requires separately agreed scope, implementation, purchasing review, and jurisdiction approval.
- Separately approved scope
- Buyer rules always apply
- No implementation is assumed
- Potential intake requirements
- Staff-reviewed document checks
- Potential department routing
- Scope and controls agreed separately
- Scope defined after any pilot
- Potential plan-review requirements
- Additional approvals required
- Implementation priced separately
- Scope defined after any pilot
- Department requirements reviewed
- Buyer-directed security assessment
- Separate implementation agreement
No measured customer outcomes, staff-time savings, return on investment, or implemented production capabilities are claimed.
Two ways in, shaped around your purchasing rules.
A fixed-price pilot
The proposed $7,000 fixed-price pilot covers a separately agreed 60-day scope. Your jurisdiction alone determines its purchasing process, approvals, documentation, and whether any purchase is permitted.
Scope a pilotA direct subscription
Any later subscription requires a separately agreed implementation scope, independently reviewed security requirements, and the jurisdiction's own purchasing authorization. No vendor certification, insurance, or references are represented.
Request a quoteExplore a pilot for applications like yours.
A short walkthrough of the proposed pilot and sample workflow for your permit and license mix. No commitment.
Request a demoStraight answers.
Does a production application or automation exist?
No production PermitDesk application, intake portal, automated classification, fee calculation, or inspection scheduler is represented as existing. The page illustrates a proposed pilot only.
Are third-party integrations already available?
No. Every possible system connection, export, permission, field mapping, and security control requires separate authorization, implementation, and verification.
How should we compare existing platforms?
Evaluate your existing tools against your own documented intake requirements. A proposed PermitDesk pilot is not represented as a replacement for any existing system.
Who determines the purchasing process?
Your jurisdiction alone determines the applicable purchasing process, approvals, documentation, and whether a proposed pilot can be considered.
When could a pilot begin?
Timing depends on your documented requirements, purchasing approvals, data permissions, security review, and separately agreed implementation scope. No launch timeline is promised.
What does the proposed pilot price include?
The published $7,000 price is for a separately agreed 60-day pilot scope. No production application, integration, security control, or recurring service is included unless explicitly agreed.