The queue at the counter is the visible part.
Intake on paper, plan review by email, inspections in a spreadsheet, and an applicant who has to telephone to find out where anything is. None of it is anyone’s fault; none of it was designed.
Bought by cities, counties and regulatory agencies.
At risk One department is holding this past target. Surfaced on a dashboard rather than discovered when the applicant calls a council member.
What the work produces
- One case, from counter to certificate
- Intake, routing, review, inspection and issuance in one record rather than five systems and an email thread.
- Departments that can see each other
- Fire, planning and public works working the same queue, with the hold that is costing time visible before it becomes a complaint.
- Applicants who stop ringing
- Status they can check themselves, and a notification when something actually changes.
- Inspections captured in the field
- On a phone, offline if the signal is bad, synced when it is not.
Also in this category: Permit intake and plan reviewInspection scheduling and field captureCode enforcement case trackingBusiness licensing and renewalsPublic-facing status lookup
Limits
What we will not do.
Stated before a solicitation rather than after an award, because finding this out late is expensive for both of us.
- We will not rebuild your finance system to take a payment. We integrate with whatever you already use to collect money.
- We do not write your code or your ordinances into the software as though they will never change. Fee schedules and review rules are configuration, because they move.
- If a commercial permitting product fits your process without you reshaping the department around it, buy the product. Several are good.
Questions a buyer asks
Can this integrate with our GIS?
Yes. Parcel, zoning and overlay data being available at intake is usually what makes the rest work, and most entities already have the GIS.
What about payment processing?
We integrate with whatever the entity already uses rather than introducing a new merchant relationship, which is a procurement of its own.
How long does a permitting build take?
It depends on how many departments and review types are in scope. One review path is a matter of weeks; a whole department is longer and is better done in stages so something is in use early.
How do you contract with a public entity?
Through whatever vehicle the entity uses: direct award under the bid threshold, competitive solicitation, an interlocal or cooperative contract, or as a subcontractor to a prime. We will tell you which we are eligible for before you spend evaluation time on us.
Where does the software run?
In the entity’s own cloud accounts, under the entity’s own contracts. We are given scoped access during the build and it is revoked at handover. That keeps the data inside your perimeter and means nothing depends on us continuing to exist.
Who owns the code?
You do. Source is delivered to your repository under a license permitting unrestricted use, modification and resale, with documentation written for whoever inherits it. There are no seat licenses and nothing switches off if the relationship ends.
What about accessibility?
Anything public-facing is built to WCAG 2.1 AA and tested with a keyboard and a screen reader before handover, not after a complaint. Say in the solicitation if you need a VPAT and we will produce one.
What about records retention and open records?
Anything we build that holds public records is built assuming those records will be requested. That means exportable, searchable, and able to produce a defensible set for a request — designed in rather than added later.
School district systems Data and systems integration Records and document automation