How we built iPermit a contractor portal that bends to permit work, not the other way around

iPermit, an ARCXIS company, expedites building permits across hundreds of US cities. We engineered the custom contractor portal and the controlled integrations that run it — built for the operational exceptions off-the-shelf software can't absorb.

ClientiPermit (ARCXIS)

EngagementBuild + ongoing

LiveiPermit Pro Portal

iPermit Pro contractor portal on desktop and mobile

Hundreds

of US cities & counties served

ARCXIS

-backed — the nation's #1 inspection & engineering company

ServiceTitan

integrated — a request auto-creates a mirrored job

24/7

contractor portal access, from any device

01The Context

Pulling a building permit is slow, manual, and different in every city.

iPermit has spent decades taking that pain off contractors' hands — a start-to-finish permit-expediting service that began in Los Angeles and now reaches hundreds of cities and counties under the ARCXIS umbrella. HVAC, plumbing, and construction crews hand off the paperwork and get back to the job.

The product at the center of that is the iPermit Pro Portal: contractors order permits and track every job from new to pending to scheduled to completed, 24/7, from any device. AppMakers USA engineered that portal and the integrations behind it.

02The Challenge

In permit operations, the "small exceptions" turn out to be the whole business.

Every jurisdiction, trade, and job type carries its own rules, routing, approvals, and special cases. On paper those look like edge cases; in practice they are the work. A configuration that looks like a clean fit in a demo starts to crack the moment real permit workflows — exception routing, contractor-specific handling, approval variations — pile up.

On top of that, the contractor-facing experience needed real usability: clean forms for complex permit submissions, dependable status, and integrations that don't drop job data. The system had to be flexible where the business is, and rock-solid where the data flows.

03The Approach

A custom portal for the exceptions, a controlled layer for the integrations.

We built the contractor portal as a custom application with its own backend, so the operational exceptions live in code that can flex — not in brittle configuration. Around it we engineered a controlled integration layer into iPermit's systems, so data moves predictably between the portal and everything it has to talk to.

That includes a ServiceTitan integration: a contractor requests a permit from a link, and the job is automatically mirrored into iPermit's software with its data carried across — no re-keying, no lost details.

Contractors

+ ServiceTitan request link

→

iPermit Pro Portal

custom app + own backend — exceptions live here

→

iPermit systems

via a controlled integration layer

One predictable path in, one custom system that can flex, one controlled path out.

04The Hard Problem

The hard part wasn't the screens. It was making releases safe.

The deeper a single platform gets customized to absorb a real operation, the more fragile it becomes: staging and production blur, debugging visibility drops, and it gets dangerously easy to affect live data while testing. QA overhead balloons because every "small" change can ripple through the whole operation.

So we moved the contractor experience onto a custom application we could actually engineer around — with a clean staging-to-production path, real failure visibility, and a controlled integration boundary.

Everything jammed into one rigid platform

Heavy customization made staging and production blur together
Minimal debugging visibility; poor change tracking
Easy to affect production while testing
QA overhead ballooned on every small change

Custom portal + controlled integration layer

Clean staging-to-production release process
Real visibility into failures, predictable behavior
A controlled boundary between the portal and backend systems
Cleaner UI built for complex permit submissions

The result

The contractor experience became more usable and far more predictable, and releases stopped being a gamble. The exceptions that define permit work now live where they can be reasoned about — in a system engineered for them.

Forcing a complex operation into off-the-shelf software — and feeling it crack?

Get a Free Project Estimate →

05The Proof Is Live

It's in production, run by a national permitting operation.

ipermitpro.com · Permit Analytics● Live

iPermit Pro — Permit Analytics dashboard built by AppMakers

The Permit Analytics dashboard we built — contractors and admins track throughput in real time. 42,285 permits submitted and 39,038 completed through the portal (shown in iPermit Pro, per iPermit).

Built by AppMakers USA for iPermit

Live product

iPermit Pro Portal

The custom contractor portal in production at ipermitpro.com — order permits and track every job from new to completed, 24/7, from any device, across hundreds of cities.

Visit the live portal →

Named client

iPermit · an ARCXIS company

A decades-old permit-expediting operation backed by the nation's #1 inspection and engineering company — not a logo on a wall, a real business running on the system.

See iPermit Pro →

AppMakers builds this kind of operational backbone as custom web applications with the integrations behind them.

06Outcomes

What the rebuild actually delivered.

A portal contractors rely on

24/7 ordering and job tracking across hundreds of US cities — with tens of thousands of permits submitted and completed through it (per iPermit).

Releases that stopped being a gamble

A clean staging-to-production path with real failure visibility replaced brittle, hard-to-debug configuration.

Integrations that hold

A controlled layer — including ServiceTitan — moves job data without re-keying or dropped details.

Is your business running despite your software?

If the exceptions that make your operation valuable are the same ones breaking your tools, you need a system engineered around them. We build that — and stay to run it with you.

Get a Free Project Estimate →