About PermitFoundry
A new company asking a careful
buyer to take a chance.
We know what that costs you. So this page is not a story about us — it is the set of commitments you can hold us to, the mechanism behind our claims, and the name of the person who answers when you write.
Why permitting
The bottleneck is the software,
not your staff.
Housing and small-business timelines in this country run through building departments, and building departments run on software that was designed before drawings were digital. The people are not the constraint. A plan reviewer who has to export a sheet set, mark it up in a second product, and retype comments into a third is not slow — they are being asked to do integration work by hand, every day, forever.
That is a software problem with a software fix, and it is unglamorous enough that it has been left alone. We would rather build the unglamorous thing well than sell an adjacent one loudly.
Cities of 25k–150k
Big enough to need real plan review, small enough that the incumbents ignore them.
Plan review first
We started at the hardest part rather than bolting it on last.
Both sides of the counter
The applicant's experience is part of the city's cycle time, not a separate product.
How we build
Configuration over code — as an engineering decision, not a slogan.
Every jurisdiction is different, and the industry's answer has been to fork the product per city. That is what turns a rollout into eighteen months and an upgrade into a project. Our answer is that your differences are data.
01
Your rules are configuration
Permit types, checklists, fee schedules, workflows, roles, and branding are entered, versioned, and reversible — not compiled. No development cycle sits between contract and go-live.
02
One codebase, every tenant
Nobody runs a private fork. Every city gets the same fixes in the same week, and an upgrade is not a line item in your budget.
03
No connector we do not own
Plan review is ours. Where we integrate — your IdP, your GIS, payments — the integration is documented, tested, and named in the contract.
04
Accessibility in the component, not the audit
Labels, focus order, and non-colour status live in the shared component library, so conformance is a property of the system rather than a remediation project.
Our commitments
Four things you can check without asking us.
Each one is a promise that a competitor could keep and mostly does not. That is the whole positioning, and it is verifiable from this website.
Pricing stays published
Tiers, implementation, add-ons, escalator cap. If we change them, the old rate card stays online with its date.
See the rate cardSecurity posture stays public
Mechanisms named, certifications dated, and a written statement of what we do not hold.
Read the postureAccessibility is conformance, not intent
WCAG 2.2 AA with a published VPAT that names its own exceptions — including on this website.
See the VPATEvery claim carries a receipt
If a number appears on this site, its source appears with it. If we cannot cite it, we do not print it — including on this page.
See the research
Design partner program · 2026–2027
We would rather earn a reference than print a logo wall.
We are taking a small number of design partners — jurisdictions willing to put one permit type into production early and tell us where it hurts. It is a real commitment on both sides, priced accordingly, and it is how the product gets shaped by an actual counter rather than by our assumptions.
Ask about the design partner programWhat you get
- Pilot pricing, fully credited toward year one.
- Direct line to the people writing the code, not a ticket queue.
- Your workflow requirements shape the configuration surface everyone else gets.
- Rate protection for the initial term.
What we ask
- One permit type in real production, not a sandbox.
- An hour every other week with the staff who actually use it.
- Permission to share anonymized cycle-time results.
- Candour when something is worse than what you had.
Placeholder · needs a real fact before launch
Reference customers
This block stays empty until a partner jurisdiction agrees in writing to be named. No logos, no unattributed quotes, no “trusted by hundreds of cities.”
Placeholder · needs a real fact before launch
Team
Names, roles, and relevant background go here when we are ready to publish them. We will not state a headcount we do not have.
How to reach a human
No contact form maze, no chatbot, no gatekeeper.
Write to us and a person who works on the product answers — usually the same day, always within one business day. If you are evaluating and need a document rather than a conversation, say so and you will get the document.