# Derek Fuentes, Director of Operations at Pinnacle Solar — read of Solar AI, May 6, 2026

> 9 years in solar, started as a field tech in Phoenix, now running ops for a 22-person installer doing around 80 jobs a month. My ops coordinator of four years just quit and I'm realizing how much permit knowledge walked out with her.

## How I got here

Googled "solar permit package automation" on my lunch break last Tuesday. We're in the middle of staffing a replacement for Joanna and I am not interested in training someone from scratch on 14 different AHJ quirks in Maricopa County alone. This page showed up third. I clicked it, skimmed for about seven minutes, and then had to go back to a site visit.

## What I clicked first

The line "permit packages auto-assembled to local AHJ specs" in the hero grabbed me immediately. That is the actual problem. Not proposals -- permits. I can train a rep to build a decent proposal in a week. I cannot easily train someone on why MCESD wants single-line diagrams formatted differently than the City of Tempe. So that phrase made me read further.

The stat "38% faster permit submission" made me slightly suspicious but I kept going.

## Where I paused

The Linda K. quote: "Permit submissions used to take my ops coordinator two full days per job. Now she queues them in about an hour and the AHJ is not kicking them back for missing documents."

I stopped here because that is extremely specific and matches a real pain I know. Two days per job is not an exaggeration for a complex install. The "kicking them back" detail is right -- that is what actually kills your schedule, the resubmission cycle, not the initial submission. Whoever wrote that quote either coached a real ops person really hard or that person actually said it. I want it to be real.

## What I distrusted

"3,200 US jurisdictions" is a number I have seen on at least three other software vendor pages. I have no way to verify it and it has become a kind of magic number in this space that I suspect gets padded. What I actually care about is: do you have Maricopa County Environmental Services, City of Chandler, City of Mesa, and Town of Gilbert, and are those templates current as of this quarter. "3,200 jurisdictions" tells me nothing about that.

Also the reply-rate claim: "Reply rates on AI-triggered sequences run 3 to 4 times higher than manual check-ins." That is a bold number and there is zero sourcing. Three to four times compared to what baseline? Industry average? Their own customers' manual average before switching? I have seen vendors say things like this and mean "we compared to one rep who never followed up."

The testimonials are first-name-last-initial, city, company name. Marcus T. That format is a choice. It is also the format you use when testimonials are either composited or the person asked to stay semi-anonymous. I would feel better with a LinkedIn link or a "Book a reference call" option.

## What would convince me

Show me a live demo with a real AHJ I can name. Not a scripted screen recording with a fake jurisdiction called "Springfield County." Let me type in "City of Mesa, AZ" and watch what package it generates. If that package is actually close to what my ops coordinator built by hand, I am sold on that feature alone.

For the follow-up sequences: give me one real campaign with open rates, reply rates, and the actual send cadence. Not aggregated stats -- one anonymized but detailed example. "Day 1, subject line X, 42% open rate. Day 4, subject line Y, 18% reply." That would tell me whether the AI is writing something a homeowner actually responds to or just noise with good timing.

## What I'd ask in an email reply

1. Your page says AHJ templates update automatically when requirements change. How do you find out an AHJ changed its requirements -- do you have staff monitoring this, or is it self-reported by customers after a kickback?

2. We're on JobNimbus and Aurora. When a proposal closes in Solar AI, what exactly pushes back to JobNimbus -- just status, or the full document? And does it create the permit stage in our pipeline or do we still do that manually?

3. What happens to our permit templates if we cancel? Can we export the AHJ package logic we've built up, or does that live only inside your system?

## Verdict: curious-enough-to-reply

The permit automation angle is real and the page actually explains the mechanism rather than just claiming outcomes. I have enough specific questions that a 20-minute demo call would either close me or disqualify this, and that is more than I can say for the last two tools I looked at.

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