Every supplier on the list is an interface: a contract to manage, invoices to process, a relationship to maintain, a risk to monitor. Multiply a fragmented base by the cost of each interface and rationalization sells itself: consolidating hundreds of suppliers down to a manageable set, invoicing monthly, removes real administrative cost before a single price moves.
And yet the naive version of the exercise destroys value. The list gets shorter by cutting whoever is small, and whoever is small is often the specialist: the niche supplier with the better part, the local responsiveness, the innovation the big generalist will never bring. Rationalization done by spreadsheet sort order trades innovation for tidiness.
A structure, not a shorter list
The better outcome is architectural. Master vendors and partnership suppliers hold the tier-1 position: the contract, the service level, the consolidated invoice, the single interface. Proven niche suppliers do not get cut; they get placed, as managed tier-2 under the tier-1 network.
Done well, this is genuinely positive-sum. The buyer keeps the specialist capability with a fraction of the interfaces. The master vendor's management fee is real, and the model carries it explicitly, so consolidation wins on net interface cost, not on hope. The tier-1 partner builds a deeper, more defensible relationship. And the niche supplier gains something it could never reach alone: a route to elevate, and to cross-sell its capability across the tier-1 partner's whole network. Each participating supplier wins, and the buyer wins most.
Who goes where is a modelling question
The hard part is not deciding to re-tier; it is deciding who belongs where. Capacity, coverage, performance history, criticality, switching cost and price all interact, and gut feel handles perhaps a dozen suppliers before it starts guessing. Encoded as constraints, the same question becomes scenario work: which tier structure holds the award together, what does each promotion or demotion cost, where does a niche supplier, promoted to a managed Challenger in the event, sharpen the whole field. And because the model is written for your base, code-on-the-fly rather than configured from a template, the tier structure fits your reality instead of a reference architecture, with your team supported to carry it forward.
Even inside a strategic nomination, the tail of the category deserves the same treatment: re-opened, aggregated where it can be leveraged, and routed through the structure rather than around it.
The question to ask
A target number of suppliers is a starting point. A tier structure with named roles and a route for specialists to grow is a sourcing strategy, and the number falls out of it. Bring us your supplier list and we will model the tier structure on it.
