What changed
HUD posted the Automated Permitting Systems Demonstration NOFO (CFDA 14.506, opp PDR-2600-DC-029O, closes 07/13/2026) — federal money explicitly funding demonstrations of local permitting automation (FACT, grants.gov/362362). Parallel: FHWA's ADCMS program funds digital construction-management adoption through FY2026 (FACT, grants.gov/348923).
Why now
The grant-application angle is dead (NOFO closes in 2 days), but the NOFO itself is the signal: the federal government has concluded local permitting is a bottleneck worth appropriating money to fix (FACT). HYPOTHESIS: most sub-10k-population jurisdictions still take permits on paper/PDF because incumbent e-permitting vendors cannot economically onboard them; AI-assisted solo development plus a fee-funded (free-to-town) model changes that unit economics.
Converging signals
(1) HUD demonstration money for permitting automation; (2) FHWA ADCMS money for construction digitization; (3) a permanent forced-filer class — contractors and homeowners compelled by local ordinance to file permits, millions per year (inference on volume); (4) proven fee-funded precedent in adjacent gov-payments (court e-filing convenience fees, and MyGovernmentOnline's technology-fee model).
Customer pain
Contractors lose half-days driving to town hall to drop off paper applications, checks, and plan sets, and cannot see status; town clerks/building officials re-key everything and field status calls. HYPOTHESIS — no complaint-thread evidence was provided in the input; pain is inferred from the paper workflow itself and from HUD deeming it grant-worthy.
Who pays
The contractor/applicant pays a per-filing convenience fee ($10–$25) added at submission, exactly like online court and utility payments. The town pays nothing, which removes the procurement budget objection. Secondary payer later: the town, for add-ons (inspection scheduling, reporting).
Solved today
Paper/PDF-email in the long tail; incumbents (Tyler EnerGov, OpenGov/ViewPoint, Cloudpermit, iWorQ, CitizenServe, GovPilot) serve mid-size cities at $5k–$50k+/yr; MyGovernmentOnline already runs a fee-funded model out of a Louisiana planning commission; contractors in bigger metros use PermitFlow (VC-backed, contractor-side).
Why current solutions are bad
Incumbent pricing and implementation overhead don't clear at a 1,500-person town's volume, so nobody sells to them; MyGovernmentOnline is regionally concentrated and dated; PermitFlow doesn't give the town a portal. The bottom ~10k jurisdictions are structurally unserved (inference).
Proposed product
A hosted permit-intake portal per town: configurable form mirroring the town's existing paper application, plan-file upload, card payment of permit fee + convenience fee, e-signature, a simple review queue for the building official, status emails to the applicant, and CSV/PDF export matching the town's records format. AI-assisted setup: OCR the town's paper form and fee schedule to generate the portal config in hours.
MVP version
One town live: their actual permit form digitized, Stripe payment splitting permit fee (to town) and convenience fee (to founder), clerk-side queue with approve/deny/needs-info, applicant status page. No GIS, no plan review tooling, no integrations. 30 days of build.
30-day build
Build MVP; simultaneously recruit 2–3 pilot towns through the founder's fire-service/municipal network (fire marshals and building officials overlap heavily in small towns); get one signed adoption letter. Pull the HUD grantee list when awards publish to identify demonstration partners worth contacting.
60-day build
First town live and processing real permits; document time-saved and contractor uptake; produce a one-page case study; begin outreach through the state municipal league newsletter and county building-official associations.
90-day revenue plan
3–5 towns live. Math check (inference): a 3,000-person town issues perhaps 100–300 permits/yr, so $15/filing yields only $1.5k–$4.5k/yr/town — revenue is real but scale requires dozens of towns or an upsell ($99–$299/mo town-paid tier for inspections/reporting). First revenue ~day 90–120.
Distribution path
Direct outreach to building officials/clerks (they answer the phone in small towns), state municipal leagues, county/state building-official association meetings, and word-of-mouth between neighboring towns. No scalable self-serve channel — this is town-by-town ground game (honest weakness).
Pricing hypothesis
$10–$25 convenience fee per filing paid by applicant; free to the town. Later: town-paid $99–$299/mo tier for inspection scheduling, code-enforcement, and annual reporting. Undercuts incumbents by not asking the town for money at all.
Technical difficulty
Low-moderate: forms, file upload, payments, queue, notifications — squarely in the founder's fast-prototyping strength. The hard part is per-town configuration variance; mitigate with the OCR-to-config pipeline. Payment split (town's fee vs. founder's fee) needs Stripe Connect-style handling.
Legal / regulatory risk
Real but manageable: some states require permit fees be set by ordinance, and a convenience fee may need council authorization or must be structured as the applicant's optional online-payment surcharge; card-surcharge rules vary by state. Handling town funds requires clean remittance. Not licensure — the founder needs no certification (so not heavy_compliance) — but each state's fee statutes need a check before entering.
Platform dependency
None that can deplatform the product: the counterparty is the town itself, payments via Stripe (replaceable). No app store, no scraping, no third-party portal.
Founder fit
High: per-filing government-paperwork monetization is his proven ELDT model; fire-service background gives instant credibility with small-town building/fire officials, who are often the same office; recycling/industrial ops background means he speaks contractor. Key structural difference from ELDT, scored honestly: in ELDT the portal already existed and he automated into it — here he must get a government to ADOPT his portal, which is a sale, not just an integration.
Breakout potential
~19,000 municipalities (inference), 50-state replication, and natural expansion into inspections, business licenses, rental registration, and code enforcement on the same rails. If HUD demonstrations publish favorable findings in 1–2 years, they become free federal marketing for exactly this category.
Final recommendation
PILOT, don't fully commit: the HUD NOFO validates the problem but the grant angle itself is dead. Spend 30–45 days and modest capital getting 2–3 towns from the founder's fire-service network live on an MVP. The decisive test is not the tech — it's whether a town adopts within ~60 days of first contact and whether contractors tolerate the fee. If adoption cycle exceeds ~90 days per town, kill it and keep the rails for a filer-side (contractor-paid, no-town-adoption-needed) permit-prep product instead.
Next action
This week: list 10 small towns where the founder personally knows the fire marshal/building official; call three and ask exactly how permits are filed today and who would have to say yes to an online intake portal that costs the town nothing. When HUD announces 14.506 awards, pull the grantee list from grants.gov/USAspending and contact grantees as demonstration technology partners.