# Dave Serrano, Operations Manager at Kestrel Builds — read of Permit AI, May 22 2026

> 14 years in construction ops, currently managing project pipeline for a 22-person GC doing residential remodels and light commercial in the Denver-Boulder corridor.

## How I got here

My boss forwarded me a LinkedIn post last week. One of his college buddies shared it with the caption "finally someone built this." I ignored it for three days. Then we got our third resubmission rejection of the quarter on a ADU job in Jefferson County and I Googled "permit rejection software" out of frustration at 7am before my commute. This page came up second. I clicked it then, read half of it on my phone in the parking garage, and came back to finish it on my laptop.

## What I clicked first

The headline "Stop Losing Weeks to the Permit Office" is fine, generic, every SaaS page says something like that. What stopped me was this line in the problem block: "A single absent site plan addendum or an incorrect setback calculation can pause a $400,000 project." That is specific. That is not marketing copy written by someone who has never been to a permit counter. That is written by someone who has watched a superintendent stand around for six weeks over a missing addendum. So I kept reading.

## Where I paused

The Greg Hatfield quote: "My permit coordinator quit last spring and I dreaded learning the process myself. Permit AI stepped in and honestly I do not think I need to rehire that role."

I stopped on that for a minute. Because that is a real thing that happens. Our permit coordinator left in 2023 and we backfilled the role in 45 days because we had no other option. If this tool actually covers what that person was doing, that is not a $199/month conversation. That is a $55,000/year headcount conversation. The claim is big enough that I want to stress-test it rather than dismiss it.

## What I distrusted

"94% first-submission approval rate across all packages generated in beta."

Beta. That word is doing a lot of work in that sentence. How many packages is that? Fifty? Five hundred? Spread across how many jurisdictions? Denver has different rejection patterns than rural Jefferson County. Los Angeles is a completely different universe. A 94% rate across beta users who are probably self-selecting motivated early adopters in friendly jurisdictions is not the same as 94% across the full chaos of US municipal permitting. I am not calling it a lie, I just cannot evaluate it without knowing what "beta" actually means in numbers.

Same issue with "47 min average time from scope upload to complete package." Average across what scope complexity? A bathroom remodel is not a commercial buildout. I would want to know what the ceiling looks like, not the average.

The "$3,200 estimated average value recovered per project" line has no methodology attached to it anywhere on the page. That number could be real or it could be someone's back-of-napkin math. I do not know and they did not show me.

## What would convince me

One thing specifically: a jurisdiction I have been burned by recently. Give me a Jefferson County, Colorado test run. Show me the actual form it generates, the checklist it scores, the code sections it cites. I want to look at a real output and compare it to what I know that office actually wants. I do not need a case study PDF with a logo. I need to see the artifact.

Second thing: tell me what happens when it gets it wrong. Is there a correction workflow? Do I eat the resubmission cost alone? Is there any accountability on their end? The page describes RFI correction-response drafting which is interesting but I would want to know if that is an admission that they expect some failure rate.

## What I'd ask in an email reply

1. The 94% first-submission rate: how many packages is that based on, which jurisdictions, and do you track the failures and what caused them?

2. Jefferson County, Colorado is notoriously inconsistent about their energy compliance requirements depending on which reviewer you get. Does your database account for reviewer-level variance, or just the official published requirements?

3. If I upload a scope and your package gets rejected, what is my recourse? Do you cover the resubmission cost, help fix it for free, or is that just on me?

## Verdict: curious-enough-to-reply

The pain is real and this page actually describes it accurately, which is rarer than it should be. The claims need scrutiny but they are not obviously made up. I would send the questions above and ask for a test run on a live jurisdiction before committing to anything.

---
*Memo by skeptic persona, generated 2026-05-22. Studio breaks own self-grading loop.*