Building permits vs. satellite imagery for sales trigger events

Permit filings have been the default trigger-event source for named-account outbound since someone first scraped a county website into a spreadsheet. They're public, they're usually free, and they feel like ground truth because they come stamped by a government office. The problem shows up the first time you call on one.
Why permit data lags the real trigger
A building permit gets filed before anything happens on the ground, often a year or more before it does. Then it sits in a municipal review queue through revision cycles, utility sign-off, maybe a zoning variance that drags for months. By the time the record hits whatever aggregator feeds your CRM, the account may have already scaled the project down, resubmitted under a different parcel, or shelved it for a budget reason nobody logged anywhere public.
That's the filing that gets coded correctly. Permit quality varies hard by county and parish, categories get miscoded, additions get filed against the wrong parcel number, and a lot of real capex, yard paving, staging-area buildout, equipment pads, never generates a permit an aggregator can parse at all. You end up with a trigger list that's long on noise and short on the one fact you need: is this account spending money on a site, right now.
Permit filing vs. ground truth, on a real account
Run the comparison on a real project and the gap is obvious. The permit says foundation, 40,000 square feet, filed Q1. The ground says nothing got poured for five months, then a pad went in closer to 28,000 square feet, then a second phase showed up as a separate amendment six weeks later that never appears tied to the original filing. If your alert fired off the original permit date, you called in month one on a project that didn't break ground until month six, then missed the real expansion because it landed in a different record entirely.
For an SDR working a named-account list, that timing mismatch is the whole game. A call that opens with "I saw your permit" six months after the fact sounds like every other vendor pulling the same public record. A call that opens with the fact that a building went up this month, at this site, sounds like someone watching the account instead of a database.
Sourcing the trigger from the footprint instead of the filing
The alternative is to stop pulling the trigger date from paperwork and pull it from the site. A monthly satellite pass over a named account's facility list shows a new pad, a cleared staging yard, or a lot extension the same month it physically shows up, regardless of whether a permit was ever filed, misfiled, or filed under an LLC you'd never connect to the parent company. There's no review queue to wait on and no parcel code to untangle. The building is either bigger than it was last month or it isn't.
This doesn't replace permit data for everything. A filing still tells you project scope and stated intent, which is useful for sizing a deal or writing the call. But as a trigger date, a permit is filed before the money moves and the ground gets touched. A footprint change is dated after the money already moved, once the pad or slab is sitting there to be seen.
Capex Signals runs that comparison monthly against a named-account list, new construction, extensions, and yard growth at the site level, tied to the month it was first seen and a rough size, so the trigger date is when the concrete got poured, not when the paperwork got stamped.
If permit lag has been costing you the first call on accounts that are spending right now, it's worth watching the ground instead of the docket.