From One Hub to Five: The Replication Map

A single transfer station is a good business. A repeatable template for building them is a platform. The difference is where most of the long-term value lives.

Why Detroit is Operation 1

Detroit is the marquee gap: the only top-10 U.S. metro without rail-served waste transfer capacity, on a Class I corridor, near major disposal capacity. It's the best place to prove the model—and the proof is what makes everything after it deployable.

The same structural test, four more times

Several Great Lakes and Midwest metros fail the same test Detroit does—real waste volume, Class I rail access, and no rail-served urban transfer:

• Cleveland — the closest Detroit analog on the Rust Belt rail backbone.
• St. Louis — major rail hub, no rail-served urban transfer.
• Indianapolis — rail-adjacent metro with weak waste infrastructure.
• Memphis — one of the largest rail hubs in the country.
• Kansas City — a comparable hub-and-gap profile.

Each one is a candidate Operation. The playbook is the same; only the local details change.

The template is the multiplier

Operation 1's standalone value is real but capped at single-asset multiples. Its larger value is as the template that makes Operations 2–5 deployable. A proven first asset plus a credible replication engine is what earns platform-level value—and a far deeper pool of strategic and infrastructure buyers.

One proven template. Five addressable markets. Build it once in Detroit, then run the same play across the corridor.