Field notes: the plant that grew a fourth silo and nobody at corporate noticed

There's a plant I keep coming back to in conversations with BD folks at equipment makers. It's ordinary enough to be a template, which is exactly why it's worth describing. Call it a mid-size drum plant, the kind sitting on a county road outside a growing metro, doing maybe 200,000 tons a season. Three silos for years. Then, sometime between one paving season and the next, a fourth one shows up.
Nobody called the regional sales rep. Nobody filled out a capital expenditure survey. The plant just got bigger, because the owner had DOT work lined up and needed the storage to stage mix overnight without idling the drum. That's the whole story from the plant's side: a logistics decision, made on the ground, with zero intention of signaling anything to anyone upstream.
From the OEM's side, it's a different story. A fourth silo on an existing plant is one of the cleaner tells you'll get that an operator is scaling, and scaling operators are the ones who replace load-out conveyors, upgrade baghouses, and eventually swap the whole plant when the drum can't keep pace with the new storage capacity sitting next to it. If you sell capital equipment into this space, that plant just moved from "steady account, revisit in three years" to "active growth account, worth a call this quarter." And the only reason anyone at corporate found out was a rep driving past it on the way to a different job.
That's the pattern worth naming: silo and hopper counts change quietly, at the plant level, for reasons that have nothing to do with telling the market anything. Nobody at a batch plant is issuing a press release when they pour a new silo foundation. There's no permit database that rolls up cleanly across counties and states, and even where permits exist, a silo addition doesn't always trigger the kind of filing that shows up in a public records search. The information exists. It's just sitting on a gravel pad in a county you don't have a rep assigned to.
Multiply that one plant by a territory of eighty or a hundred facilities, and you start to see why "staying on top of the territory" usually means a rep's memory, a spreadsheet that's eighteen months stale, or a trade show conversation that happened to come up. None of those scale, and all of them miss the plants that are too small to be on anyone's radar until they're suddenly bidding on a highway contract and need a new drum plant by spring.
Looking at every plant in a territory on the same schedule, every year, catches that kind of change directly: the silo count or stockpile footprint shifts, and you see it without waiting for someone to mention it over coffee. That's the whole premise behind Asphalt Plant Mapping, which locates plants across a region from imagery and tracks that configuration pass over pass, so a fourth silo shows up as a flagged change instead of a rumor.
It won't tell you why the plant added it, whether it's RAP storage, overflow capacity, or prep for a bigger drum next year. That part still takes a phone call. What it does is tell you where to make that call first, instead of working a list alphabetically and hoping you hit the growing accounts before a competitor does.
The plant with the fourth silo is still out there, by the way, running three shifts most weeks. Somebody's going to sell them a bigger drum plant eventually. The only open question is who gets there first.
If your territory has one of these plants sitting unflagged right now, that's worth finding out before the next paving season starts.