Permitting Software for Contractors: 3 Steps for 2027

Start with the category, not the brand

Permitting software for contractors is a tool that tracks building permit applications, inspection milestones and expiration dates, and some products also prepare or submit the paperwork to a city or county.

TL;DR: Most small contractors should start with the jurisdiction's own portal plus a tracker that sits inside the job system they already use. Buy a submission-focused product only when filing across several jurisdictions is the bottleneck. Of the vendors below, only Projul publishes plan prices on its pricing page, so the other purchases start with a sales conversation.

Three categories cover most of the market. The first is the jurisdiction's own portal, which you often must use anyway. In Clark County, Nevada, a contractor needs a portal account before submitting, accessing or paying for permits. The second is a tracker inside a project or job-management tool. The third is an intake service that prepares and files applications for you.

Choose the category first, then compare vendors inside it. A tracker and a submission service solve different problems and are priced on different units, so comparing them directly produces a misleading answer.

Key Takeaways

• The jurisdiction portal is the baseline you cannot skip. Clark County's licensing page says a Citizen Access Portal account is required to submit, access or pay for permits.

• Projul is the only vendor here that publishes plan prices, and its tiers are set by user count.

• PermitFlow and Procore both route pricing through a sales conversation, and OnlyPermit's product page does not publish prices.

• PermitFlow's Procore app needs a Company Admin to install and a paid PermitFlow subscription to run.

• Reminders and exception routing are worth automating only where a named person owns each exception.

• A DIY stack in Zapier, Make or n8n can work, but you own retries, audit trails and access controls.

How we evaluated these tools

We reviewed each option's official pages in October 2026 and weighted six criteria before comparing them. Workflow fit carries the most weight, followed by jurisdiction coverage, because a tracker that cannot show the status of your city's filings is only a spreadsheet with a login.

We did not assign numeric scores to the vendors. Their published fields are too uneven to score fairly, since one shows full plan prices and another shows none, so the weights set the order of the questions and the profiles below apply them in prose. We also excluded several names that appeared in search results because we could not open an official vendor site for them this session.

Feature matrix

Read the matrix as what each vendor's own pages say, not as what a trial would show. PermitFlow is the only option whose pages describe submission, an inspection category and an app integration together. Projul's permit support is described as tasks and milestones, not as filing with an agency. OnlyPermit describes form filling and status updates but does not explain how applications reach the agency.

Where permit work breaks down

Small shops usually lose track in three places: a filed application that nobody confirmed, an inspection that must pass before work is covered, and a permit that expires while the job is still open. Projul's permit tracking guide, dated February 10, 2025, recommends a calendar reminder 60 days before expiration and warns against keeping permit details scattered across emails, text messages and sticky notes. That advice is tool-agnostic, which is the useful part, because the reminder works even before you buy software: Projul's permit tracking guide.

A proposed, configurable workflow for the expiration gap starts with a trigger: a permit record gains a new expiration date or inspection milestone in the tracker. The action creates a dated task in the job system, assigns it to a named coordinator and schedules a reminder 60 days before expiry. The output is a task with an owner and a log of each reminder. The prerequisites are an export or API access from the tracker, a job system that supports task assignment, and a written owner for each job. Human review sits in two places: the coordinator confirms each milestone against the jurisdiction's portal before anything is filed, and a person decides every extension. This describes a design, not a deployed system, and the product itself is at US Tech Automations.

For a broader view of how job tools handle scheduling alongside permits, see Housecall Pro vs Jobber for electrical contractors. For the bidding side of the same workflow, see best bid management software for contractors.

Pricing and what each option will show you

Pricing checked October 16, 2026. Projul lists 4 plans, according to Projul (2026), with user caps of 3, 10, 20 and unlimited.

Starter tier: $2,388 per year according to Projul (2026). Projul's Starter plan is the smallest entry point, and its pricing page says annual plans bill once a year with a Premium Support Package included, except on Starter. Monthly plans bill month to month and can be cancelled at any time, so a shop that expects to outgrow its user cap should compare the annual and monthly rows before committing.

Procore's pricing page, according to Procore, says there are no published prices and directs visitors to a custom quote. It says pricing depends on the products you need and the amount of construction you do, and that fees are charged annually per product. A small shop should ask for the one product it needs rather than a bundle.

Vendor profiles

PermitFlow

Vendor facts: PermitFlow's home page describes an AI platform for construction and trades, with agents for intake, research, submission, coordination and issuance. PermitFlow's contact page names 3 product categories according to PermitFlow (2026): Permitting, Inspections & Closeouts, and License & Registration Management. Its audiences include home services contractors, commercial contractors, home builders, developers and architects. The only purchase path on the pages we opened is a demo request, and neither page publishes a price.

Its Procore integration page says the embedded app manages the building permit process from inside Procore, with an in-app permit log, expiration alerts and automated reminders. The same page says installation requires Company Admin status and a paid PermitFlow subscription, and that the app installs through Procore's App Marketplace (PermitFlow's Procore integration). It does not say which research and submission steps run inside Procore.

Our read: PermitFlow fits contractors and developers who file across several jurisdictions and want someone else to carry the paperwork. Its main limitation is that the pages do not name the jurisdictions it covers, so ask for that list in writing. Implementation starts with admin access and a paid subscription, so confirm both before a pilot.

Procore with the PermitFlow app

Vendor facts: Procore's pricing page does not mention permits. The permit path we found runs through PermitFlow's app in Procore's Marketplace, not through a native Procore permit module.

Our read: This option fits firms that already run every job in Procore and want permits in the same system. The limitation is cost structure: the permit app is a second contract on top of Procore, so price both together. If you do not already use Procore, this is the wrong entry point, and PermitFlow on its own is the simpler comparison.

Projul

Vendor facts: Projul's permit guide says you can create tasks for each permit milestone, assign them to the right person, attach permit documents to the project and build permit milestones into the project timeline. The guide is written by Projul, so treat it as the vendor's own description. Projul's pricing page does not list permit tracking as a plan feature.

Our read: Projul fits small shops that run jobs in a schedule-driven tool and want permit milestones next to the work. Its pages describe tasks and milestones, not filing with a jurisdiction, so it does not replace a submission service. If you are comparing job tools more broadly, Automate's estimating software guide for electrical contractors covers the adjacent workflow.

OnlyPermit

Vendor facts: OnlyPermit describes an AI-powered platform that identifies the permits a project needs from its location and project type, fills in forms, stores documents and sends status updates and deadline alerts. Its product page says the tool serves small residential and large commercial projects, names no integrations and no jurisdictions, and does not mention pricing (OnlyPermit product page).

Our read: OnlyPermit fits builders who want help identifying permits before a project starts. The limitations are the missing submission explanation and the absence of published pricing, which means you cannot model cost or data access before a sales call. Treat it as a candidate to evaluate in writing, not a default.

Jurisdiction portals: Clark County and St. Paul

Clark County, Nevada: Clark County lists 4 contractor requirements before filing according to Clark County, Nevada (2026). The county says contractors need an active Nevada State Contractor's License, an active Multi-Jurisdictional Business License number, a Citizen Access Portal account, and that the account must be linked to the contractor's license number.

St. Paul: The city's PAULIE platform, according to City of Saint Paul (2026), provides a secure, mobile-friendly way to submit and track applications, and the page was last edited July 1, 2026.

Our read: These portals are not purchases, but you pay for them in staff time, so they are the baseline every other option must beat. A portal records the filing, but it does not give your crew a task list with owners, which is why most shops still need a tracker.

When NOT to use US Tech Automations: if you file in one or two jurisdictions and only a handful of permits a year, the city portal plus a dated calendar reminder is simpler and cheaper to run. If your job system already supports permit milestones, configure those first rather than adding a second tracker. If your real need is preparing and filing applications across many jurisdictions, a dedicated intake vendor such as PermitFlow is the more direct purchase, provided you accept quote-based pricing.

Who this is for

• A shop filing in one or two jurisdictions: start with the portal and a tracker, and skip submission software until the volume justifies it.

• A firm already running jobs in Procore: evaluate the PermitFlow app first, because it keeps permits in the system you already use.

• A builder or developer filing across many jurisdictions: pilot an intake service and ask for the jurisdiction list in writing before signing.

Red flags: you need published prices before any sales conversation; you expect a tool to file in a jurisdiction the vendor never names; or your "permits" are site safety permits such as hot work or confined space, which belong to a permit-to-work category rather than building permits.

Worked example: 18 open permits

Illustrative numbers, not customer data: take an electrical shop with 18 open permits across 4 jurisdictions, where each permit has 3 inspection milestones, which leaves 54 dates to watch (18 × 3). If a coordinator checks each permit's status once a week at 5 minutes per permit, that is 90 minutes of status checks a week (18 × 5). In a proposed workflow, a milestone entering a 60-day window triggers an SMS through Twilio, and a failed or undelivered message returns an error_code on the message record, as described in Twilio's Message resource. If 2 of those 54 messages in a month return an error code, the coordinator makes 2 follow-up calls, which is 3.7% of the 54 messages (2 ÷ 54) needing a human. The review point sits on the errors, not on every reminder, and the workflow reminds people but does not file anything. The prerequisites are a milestone-date export or API feed from the tracker and a sender number with recipient consent.

Common mistakes and a decision checklist

Common mistakes to avoid:

• Buying a submission service for a shop that files two permits a year.

• Assuming "AI" means the software files with every jurisdiction; get the named list in writing.

• Pricing a tool from its demo page and forgetting the required base subscription, as with the PermitFlow Procore app.

• Skipping the expiration reminder because the portal shows a status.

Three decision steps:

1. Count your filings per year and the jurisdictions they span. If the count is low and the jurisdictions are few, stop at the portal and a dated reminder.

2. Decide whether the bottleneck is filing or tracking. Tracking points to a job-system tracker such as Projul, and filing points to an intake service such as PermitFlow.

3. Ask each vendor in writing for its jurisdiction list, the price at your volume, the admin rights and subscriptions required, and the export path for milestone dates.

Building it yourself or buying

The realistic alternative for many shops is stitching triggers and reminders together in Zapier, Make or n8n. Those tools can keep run histories, retry failed steps, branch on errors and produce audit evidence when configured. The buyer still designs and owns observability, idempotency so a retry does not send a second reminder, escalation paths, access controls and maintenance when a portal changes its form. That is a fair trade for a shop with one technical owner and a short list of jurisdictions.

A proposed US Tech Automations design could configure the same trigger-and-reminder pattern with three differences: per-jurisdiction rule sets, escalation to a named coordinator when a send fails, and a stored log of each reminder for later review. Its prerequisites match a DIY build: milestone exports or API access, a consented sender account, and a human owner for every exception. Those differences matter only if your jurisdictions and crew make them necessary.

Frequently asked questions

Do I need permitting software for a few permits a year?

Usually not. The jurisdiction portal plus a dated reminder 60 days before expiration covers a small volume, which is the same advice Projul's guide gives.

Does PermitFlow publish prices?

No. On the pages we opened, PermitFlow offers a demo request and no plan prices, so treat its cost as quote-based until you receive a written proposal.

Does Procore handle permits natively?

Not on the pricing page we opened, which does not mention permits. The permit path we found runs through PermitFlow's app in Procore's Marketplace, which requires Company Admin rights to install.

Can a city portal replace permitting software?

For filing, often yes, because the portal is usually the required channel. For tracking crew tasks and milestones across jobs, the portal alone does not give you owners and task lists, so you still need a tracker.

Is a DIY stack in Zapier, Make or n8n enough?

It can be for a short list of reminders, as long as one person owns retries, error handling and access controls. Those tools support run history and error branches when you configure them.

Bottom line

Pick the category before the vendor. For a small shop, the portal plus a dated tracker is the default, and an intake service makes sense only when filings across jurisdictions are the real bottleneck. Projul is the one option here with published tiers, PermitFlow and Procore require quotes, and OnlyPermit publishes no pricing, so get the jurisdiction list and the price in writing before you compare them side by side. To see how US Tech Automations configures this reminder-and-escalation pattern, see how US Tech Automations configures this.

Sources:

• Projul pricing

• Projul permit tracking guide

• PermitFlow contact page

• PermitFlow Procore integration

• Procore pricing

• OnlyPermit product page

• Clark County, Nevada licensing requirements

• City of Saint Paul construction permits

• Twilio Message resource