How precise is "roughly how big" in a monthly capex read?

A partially erected steel-framed building structure silhouetted against a clear sky.

If you've pulled a competitor's new distribution center into a forecast call, you've said some version of "it's a big build, maybe 200,000 square feet." That number came from somewhere. Usually it came from a press release, a permit filing, or a LinkedIn post from the GC. All three show up months after the pad was graded. If you're sizing the event off overhead imagery instead, the question that actually matters is how tight that "roughly" is, and what it's doing the math on.

What "roughly how big" actually means

A satellite or aerial image at 0.5 meter ground sample distance (GSD) means each pixel covers about 50 centimeters on the ground. That's enough resolution to trace the outline of a new slab, a tilt-up wall going up, or a yard extension month over month and get a reasonably clean footprint polygon. It is not enough to read a stamped drawing, confirm clear-height, or tell you whether the shell is single-story or has a mezzanine.

So when a feed reports a footprint size, it's reporting the outline area at the pixel resolution it was shot at, not an engineering takeoff. A 150,000 sq ft estimate on a tilt-up warehouse means the visible slab footprint measures out to roughly that, rounded to a band, not that someone cross-checked it against the building permit. For an SDR, that's usually the right level of precision. You're deciding whether this account just crossed a threshold worth a call, and whether the scale of the build matches what your rep in that territory is hearing on the ground.

The other variable is cadence. A monthly pass means the gap between "first bare earth" and "first detected" is weeks, not the single day the dirt moved. Footprint size at first detection is often smaller than the final build, because construction isn't done yet. The number that matters more than any single snapshot is the trend: pad cleared this month, slab poured next month, walls up the month after. Watching footprint growth across that sequence tells you whether the account is still pouring capex into the site or whether the build has stalled, which is a signal in itself.

Footprint growth as a proxy for spend, not a substitute for it

Square footage from overhead imagery is a size proxy, not a budget number. A 100,000 sq ft cold storage shell and a 100,000 sq ft flex warehouse cost very different amounts to build, and nothing in an RGB image tells you refrigeration spec versus dry storage. What the imagery does give you, reliably, is the thing a press release can't: the footprint existed, it grew by a measurable amount, and it was first visible on a specific date at this address. That's a dated, located fact you can put in a call note before the account's own comms team has drafted theirs.

For a sales team working named accounts, that's usually the trade worth making. You give up the false precision of a specific dollar figure and get a verified event tied to a real site, weeks or months ahead of the public announcement. Treat the size estimate as a rough band (small addition, mid-size expansion, major new build) and let the date and the growth curve do the heavy lifting on urgency.

If you're deciding whether to work this into your territory process, the monthly account-level feed is built around exactly that trade-off: a footprint size estimate accurate enough to triage by scale, tied to a first-seen date accurate enough to beat the trade press. It won't give you a construction budget. It will tell you that something real is being poured at an account you're already watching, and roughly how much of it, before anyone outside that company has said a word about it publicly.

Start watching the footprints on your named accounts instead of waiting for someone else's announcement to tell you capex already happened.

Start a pilot

← Back to the blog