Permitting delay feels free because nobody invoices you for it. No line item says "three weeks lost to a correction cycle" — the cost hides in four other places, and companies that never total it systematically underinvest in the boring machinery (checklists, portal sweeps, signature chasing) that prevents it. Here's the model. Run it with your numbers once and the boring machinery starts looking cheap.
The four buckets
1. Cash cycle. Most residential deals pay out on milestones tied to install completion and PTO. Every delay week pushes final payments right while your costs (equipment already purchased, payroll) sit spent. The carrying math is simple: (revenue outstanding per job) × (your cost of capital, weekly) × (delay weeks) × (jobs in pipeline). At any real pipeline size, weeks of float across dozens of jobs is a permanent loan you're making to your own process.
2. Cancellation risk. This is the bucket that kills quietly. Every week between signature and energization is a week for buyer's remorse, a competing knock, a family emergency, or a financing expiration — and a canceled late-stage deal forfeits acquisition cost, design and permit spend, and sometimes restocking. The industry-wide pattern is well established (faster processes cancel less — it's part of why instant permitting measurably matters, with NREL clocking roughly two weeks saved per job in adopting jurisdictions). Model it as: (your cancellation rate among delayed jobs − rate among on-time jobs) × (sunk cost per cancellation). If you don't know those two rates, that's finding number one.
3. Crew utilization. Install crews are a fixed cost consuming schedule whether permits arrive or not. Permit slippage creates the whipsaw: idle days when approvals bunch up late, overtime when they land all at once, and reschedule cascades that burn coordinator hours and homeowner goodwill. The stabilizer isn't faster cities — it's predictable intake, which is a first-pass-approval problem more than a jurisdiction problem (the rejection post is really a crew-utilization post wearing a compliance costume).
4. Referral drag. Homeowners forgive weather; they don't forgive silence and slippage. The referral engine that makes solar economics work runs on "that was easier than expected" — and every unexplained delay week taxes it. Hard to put on a spreadsheet, easy to see in review scores by cohort.
Where the recoverable weeks live
The uncomfortable, liberating finding when teams actually timestamp their pipeline: the city's queue is usually the smallest controllable bucket. The recoverable weeks are internal latencies — plan sets waiting on internal review, corrections unread in portals, utility documents awaiting signatures, inspections nobody scheduled, permits quietly aging. Each is a one-to-five-day leak; a pipeline has all of them at once. You can't fix what you don't timestamp, which is the entire argument for stage-level tracking: not reporting for its own sake, but finding which of the four buckets your particular leaks drain into.
That's the honest pitch for tooling, too. TexPTO exists because the delay cost model above is invisible in a spreadsheet and obvious on a stage-timestamped pipeline: it shows where every job's days actually went, alarms the silent states, and turns "permitting feels slow" into "signature latency costs us X days per job — fix that first."
FAQ
What does a week of delay cost per job? Run the four buckets with your numbers — carry on outstanding revenue, marginal cancellation risk, utilization whipsaw, referral drag. Most operators who do land on a figure that makes a permitting coordinator hire look obviously cheap.
Isn't the city the bottleneck? Sometimes — Texas caps municipal review at 45 days — but timestamped pipelines usually show internal and signature latency as the larger recoverable share.
What's the single fastest fix? Same-day customer signatures on utility documents, then a daily portal sweep for corrections and deficiencies. Both cost process, not money.
How do we get the data to run this model? Timestamp every stage transition on every job for 90 days. The model computes itself from there.
Sources
- NREL SolarAPP+ performance findings (measured time savings from faster permitting): https://txses.org/solarapp/
- Texas municipal review framework: The 45-Day Rule
Framework, not financial advice. The numbers that matter are yours — the model is only as honest as the timestamps behind it.