For agencies, counties and citiesNo coding required

Your agency’s apps,
built by your agency.

No coding required. The tools your counter staff, inspectors and caseworkers keep asking for — specified from what they already have, signed off by the people you choose, and shipped to web, desktop and phone on one OS.

Harbor County · Permits
1 · What you bring

Calls, emails, notes

Screenshots, links, a photo of the paper form. Drop in whatever you already have.

2 · The spec

One blueprint, signed off

Spec Studio reads all of it and draws one spec, every decision cited to where it came from. Nothing is built until it’s approved.

3 · Your app

Permits

App Factory builds it from the spec in Harbor County’s own brand — for web, desktop and phone.

Harbor County, the City of Wexford and Ridgeline Transit Authority are example agencies.
Your stack today

Your current stack is a spreadsheet.
None of it is yours.

Stale renewal dates. Owners who left in 2023. Feature requests nobody remembers submitting. It isn’t a vendor list — it’s a map of the decisions you’ve already lost leverage on.

  1. Renewals are trapsWhen a vendor raises rates or sunsets a feature, your data is their leverage.
  2. Feature requests stall in queuesVendors build for their biggest customers. Your workarounds become permanent.
  3. Audits are a screenshot jobThe auditor asks “who approved this?” and you screenshot twelve admin consoles.
The counter

Six desks have to see it.
They shouldn’t see it one at a time.

The application crosses zoning, plan review, fire, engineering and back to the counter — and it travels as an object, so only one desk can hold it at once. Nobody is being slow; the paper is. Keep every review. Stop passing the paper. And the person who filed it can finally see which desk it is on, without calling to ask.

Days waiting on the next desk0
Desks that have seen it0 of 6
Applicant can see itno
An illustration of one application. The days are the wait between desks, drawn, not measured — nothing here says a fire review takes less time.
Intakecounter+1dZoningplanning+6dPlan reviewbuilding+12dFirefire marshal+11dEngineeringpublic works+5dIssuebuilding official+2dthe queue, at 9 a.m.P-24119P-24119Fire review4 of 6 clearedyou are hereevery review kept. nobody waiting on an envelope.
Migrate · early access

It’s finally time to migrate
those 20-year-old Access databases.

The permit log, the code-enforcement tracker, the cemetery plot book — built in 2004 by someone who left in 2016, running on a PC behind the counter, holding residents’ names and parcels with no audit trail. Its tables become a real app’s database, its rows load after a dry-run preview — and not one row is ever sent to an AI model.

The county of the future

It runs on one OS.
It gets there one budget cycle at a time.

Two hundred and sixty vendor systems today, bought over thirty years by departments that never had a reason to talk. Each one leaves on its own renewal — inside the budget you already have — and what it did becomes an app you own. The systems of record stay, connected.

Year2026
Vendor systems260
Apps you own0
An illustration of one county over five years.
FINANCE/ERPGISCAD / 911COURTSUTILITY BILLINGPAYROLLELECTIONSRECORDSYOUR OS202620272028202920302031today: 260 vendor systemsone department, one appthe first budget cycleclerks are building nowGIS and finance stay, connectedone OS
The budget calendar

You decide in March
what you will need in November.

Forty renewals land across the fiscal year, each with its own auto-renew clock, and the money decision for all of them is taken once — before the year that needs them has happened. 24 of the 40 fall after the submission date, which means the thing a department discovers in October is a request for the year after next. One line item instead of forty is not a saving; it is the difference between deciding and guessing.

JulAugSepOctNovDecJanFebMarAprMayJunFISCAL YEARBUDGET SUBMITTEDeverything to the right of this line waits a yearan authorization that expires inside the yearOne line item · your own OSdecided once · built all yearwhat a department asks for in March can ship in March.
Everyone on the payroll

One county, five people.
Each one sees only their apps.

The permit clerk at the counter, the inspector on a site, the caseworker with a resident, the fleet supervisor in the yard, the records officer in the stacks. One app, one sign-in — and each person opens it to the apps that are theirs. A resident signs into the same app and sees exactly one thing: their own permit.

same county, five people
  1. A permit technician at the counter smiling as she talks a resident through an application
    Permit counter
    10 apps
    Kate, permit technician
  2. A building inspector in a hard hat on a site, phone in hand, looking across at the structure
    Inspections
    7 apps
    Luis, building inspector
  3. A county caseworker laughing gently in conversation with a resident across a table
    Human services
    9 apps
    Nia, caseworker
  4. A fleet supervisor in a vehicle yard on a call, half-smiling, trucks behind him
    Public works
    11 apps
    Dale, fleet supervisor
  5. A records officer between archive shelves holding a box, looking up as if she just found the file
    Records
    6 apps
    Priya, records officer
Harbor County, its people and its apps are examples.
Governance

Gates at every step in the development lifecycle.
Maximum control for highly regulated industries.

Choose the gates you want — the request, the spec, the build, security, production. Each one is enforced in the code, not in an administrative policy, and every decision lands in one trail you can hand an assessor, a council committee or a records request.

turn a gate on in watch mode first —
see what it would have blocked
  1. D. WhitcombeCounty administrator · sponsor
    APPROVEDrequest · 08:12
    New app
  2. R. AdeyemiBuilding official
    APPROVEDspec rev A · 09:41
    Spec sign-off
    A clerk asked for it.
    A clerk can’t approve it.
  3. J. ParkIT applications · any 1 of 3
    APPROVEDhand-off to build · 10:05
    Build
  4. Latest scan 11:240 critical · 0 high
    CLEAREDsecurity posture · 11:30
    Security
    no scan yet? blocked.
    no scan is not a clean scan.
  5. L. Moreau · T. BishopCISO · Records manager
    APPROVED · 2 OF 2commit e92a41d · 14:06
    Production
    e92a41d is approved.
    f30c118 has to ask again.
Governance auditEvery governance decision in your org, in one trail you can hand an auditor.
TimeGateResultWhoWhat
08:12New appClearedD. WhitcombePermits request, sponsor approved
09:41Spec sign-offClearedR. Adeyemispec rev A
10:52SecurityBlocked—release held: no completed scan
11:30SecurityClearedscan 11:240 critical, 0 high
14:06ProductionClearedL. Moreau, T. Bishopcommit e92a41d, 2 of 2
14:31ProductionBlockedS. Okonjocommit f30c118 has no approval
People and apps are examples. Gates are off until your agency turns them on.
Evidence, not assurances

Resident data never leaves quietly.
Every crossing gets a receipt.

We do not hold your ATO and we will not pretend to. What we hand the people who do is evidence: declare your regime and the platform fails closed — resident data may go only to a destination you approved under a written agreement, what goes to an AI model is redacted first, and every crossing is receipted before the call, in a chain that shows if anyone edits the past.

Governance, in the product

Your approval committee,
built into the software.

Org HQ ▸ Governance. Four screens your compliance officer will actually open.

Org HQ ▸ Governance ▸ Gates
Every lifecycle gate — its governor, approvers, and enforcement — in one registry.
New app
Spec sign-off
The rule: Before anything is built, at least 2 of these people must approve the spec.
Who can approve: Dr. A. Rahman · K. Osei · J. Tran
Kept in the loop — Notified of every request and decision — they don’t approve.
Changes save automatically.
Security posture — block a production release while serious findings are open
Security scan — approve running a scan or pen testOff
Org HQ ▸ Governance ▸ Approvals Inbox
PendingHistory
Waiting on your decision (3)
Bed Board — launch to production1 of 2 approved
commit a41f9c2 · requested by R. Patel · 13:58
Optional comment…
RejectApprove
OR Schedule — schema changeadds a column
Credentialing — access changegrant to 4 West managers
Org HQ ▸ Governance ▸ Audit
Every governance decision in your org in one trail you can hand an auditor.
Category ▾From dateActor, gate, app, or summary…
14:31ProductionBlockedb7e0d13 · no approval
14:06ProductionCleareda41f9c2 · M. Lee, S. Grant
11:30Security postureCleared0 critical, 0 high
10:52Security postureBlockedno completed scan
09:41Spec sign-offClearedspec rev A · K. Osei
Org HQ ▸ Governance ▸ Data Boundary
Your data boundary
Everything below is measured, not scored.
Regime packsHIPAAAdd regime
Enforce the boundaryEnforcing — regulated data fails closed
Approved destinations — The only places data may go.
AI model · dedicatedBAA on file
Email deliveryBAA on file
Disclosure ledger — every receipt, what left and where it went →
you can’t approve your own request · an approval covers one exact commit, once
any one · at least N · all of them — you set the quorum
hand this to your auditor
declare HIPAA and it fails closed by default
Gates are off until your organization turns them on; the people, apps and times here are examples.
Real software

Build an app once.
Ship it to every device.

One build becomes a web app at your own .gov address, a signed desktop app, and native apps on both phones. No second codebase, no separate mobile team — which is the only way an inspector in a crawl space and a clerk at a counter end up looking at the same record.

One version, four placesEvery surface comes off the same build, so the web, the desktop and both phones cannot drift apart. The commit is the version.
An ordinance changes in MarchThe affected app is re-specified, re-tested and re-shipped inside the week — every surface at once, because they all come from one build.
No second codebaseThe phone apps are rendered natively from the same app, not hand-written twice. Nobody maintains a separate mobile team to keep them in step.
The desktop app is signed and notarized for macOS and runs the app’s own surface in a native window. Permits and Harbor County are examples.
The new economics of public work

Nobody understands a permit counter
like a permit counter.

Not us. Not the incumbent vendor whose contract renews whatever happens. Public-sector software has always been built by outsiders and sold to the people who take the complaints. This inverts it: built by the office that runs the counter, and installed by the county next door — arriving in their seal, on their OS.

01You build itThe routing tool your inspectors made because the vendor’s list view never knew which two stops were on the same street.
02It worksProven on your parcels, your inspectors, your re-inspection rate — the kind of evidence no procurement demo can fake.
03The county next door installs itIt arrives in their seal, on their OS, governed by their gates. Your price, your revenue — when the marketplace opens.
The marketplace is not open yet — this is where it goes. Harbor County, the City of Wexford and Inspection Router are examples.

See your own stack first.

The free stack assessment maps your vendors, your spend, your overlap, and the five-year rent-vs-own curve — on your numbers, before anyone asks you to believe anything on this page.