First-seen date vs. announcement date: why the earlier one wins

Steel beams stacked in long rows in an outdoor industrial storage yard.

Most account intel in a rep's pipeline runs on the announcement date. A company puts out a release, an analyst covers it, a Google Alert fires, and the account lands in your queue. The problem is that the concrete has usually been poured for months by the time any of that happens.

A first-seen date is the date someone, or something, observed the ground change: pad graded, foundation poured, steel going up, yard expanding to hold new material. In facility footprint monitoring, that's the date a monthly pass over the site first shows the new structure where there wasn't one before.

What a first-seen date is

Think of it as a timestamp on a physical fact, not a communications decision. A VHR pass over a named account's site in March shows bare ground. The April pass shows a graded pad and foundation forms. First-seen is April, because that's when the change entered the record, whatever that record is built from, whether it's a monthly satellite pass or a site visit.

Compare that to the announcement date, which is set by a mix of legal review, investor relations scheduling, quarterly earnings calendars, and sometimes a groundbreaking photo-op timed for a local news crew. None of that has anything to do with when the capex started on the ground. It has to do with when the company decided it was ready to talk about it.

For a rep timing outbound, that gap is the whole game. If first-seen is April and the press release doesn't land until the Q3 earnings call in October, you've got six months where the account is in active expansion mode and every other rep working that territory is still reading last quarter's news.

First seen vs. press release date: why the gap is the point

The press release date tells you a decision has already been made and probably already been staffed. Procurement is further along than you'd like, the vendor shortlist may already exist, and the first calls into that account from competitors may have already happened, because somebody on their side of the fence saw the permit filing or the paving and worked it the same way you would have.

The first-seen date gives you the earlier edge. Physical activity on the ground confirms the capex is real weeks or months before the company is ready to confirm it publicly. That's the window where a call referencing the actual buildout, not the press release, reads as informed rather than reactive. "I noticed your Georgetown site added about 40,000 square feet of warehouse space starting back in April" lands very differently than "Saw your press release."

Building a dated capex event timeline

The useful version of this is a timeline, not a single date: first-seen, then whatever confirmation events follow, permit record, groundbreaking photo, press release, earnings call mention. Stacked up, that sequence tells you how long a company typically sits on expansion news before going public, which tells you how much lead time you're working with on the next site.

That's the structure behind a monthly account-level capex event feed built around named sites: each new pad, extension, or yard expansion gets a first-seen date, a rough size, and a location, so the trigger in your CRM is tied to when construction actually started, not when the company got around to saying so.

If you're still setting account alerts off press mentions, you're working the announcement date by definition, which means you're working the same lead everyone else in the territory just got. The first-seen date is the one nobody else has yet.

Worth checking what your top named accounts' sites look like this month, before the next earnings call tells you what you already should have known.

Start a pilot

← Back to the blog