Building a named-account watchlist that actually catches expansion

Steel beams stacked in rows at an industrial storage yard

Most territory lists get built once, at the start of a quarter, off a firmographic export. Revenue band, employee count, SIC code, done. Then the list sits untouched until the next planning cycle, and whatever happened to those accounts in between (a new plant, a leased yard, a second shift's worth of parking added) never makes it into the CRM until a rep stumbles on it by accident or a press release surfaces six months late.

A named-account watchlist built for expansion tracking has to work differently from a standard target account list. You're not filtering for "fits our ICP." You're filtering for "this account physically grows its footprint when it's doing well," and then you're checking that footprint on a schedule.

Pick accounts that actually run physical capex

Firmographic filters tell you who's big. They don't tell you who's building. Start instead from a narrower question: does this account operate owned or leased facilities that expand when the business expands? Manufacturers, cold storage and logistics operators, data center operators, food processors, auto suppliers, anyone running a yard or a plant floor all qualify. A SaaS company with 2,000 employees and one leased office in Austin doesn't, no matter how well it scores on your normal ICP model.

Once you've got that narrower pool, rank by capex signal rather than company size: multiple existing sites (a company with four plants is more likely to add a fifth than one with a single HQ), any public language in earnings calls or investor decks about capacity expansion, and industries where your product specifically sells into new-site buildouts. This is the list that should feed your territory, not the generic 200-account spreadsheet handed down from marketing ops.

Build one record per site, not one per company

A named account with six facilities needs six rows, not one. Each site record should carry the address, approximate parcel size, what's currently built on it, and the date you last checked it. That date field matters more than people think. Without it, "monitoring" an account means someone remembers to Google the company name occasionally, which isn't monitoring, it's hoping.

This is also where most CRM-based account plans fall apart. A CRM stores who you talked to and what they said. It has no field for "the lot behind Building 3 was empty in March and has a foundation poured by June." That's a different kind of record, tied to a location and a date, not to a contact or an opportunity stage.

Check the list monthly, not at renewal time

A watchlist that only gets reviewed at QBR time is a quarterly list wearing a monthly-sounding name. Expansion doesn't wait for your planning cycle. Permits get pulled, pads get graded, and new buildings get framed between your check-ins, and by the time the account shows up in a press release or a job posting for "plant manager, new facility," a competitor's rep already called on it.

Run a standing monthly pass over the watchlist, even a short one, asking one question per account: has the footprint changed since last month. A list of fifty accounts takes an afternoon to check this way, as long as the source shows site-level change rather than announcements after the fact.

That's the specific gap Capex Signals is built to close: a monthly, account-level feed of facility footprint growth, tied to a dated location rather than a press release, so the watchlist you built gets refreshed with ground-truth change instead of secondhand news.

If your territory already has the capex-heavy accounts named, the next step is just getting their site footprints checked on a schedule instead of left for the next press release to surface.

Start a pilot

← Back to the blog