Tail spend: how a Fortune Global 500 industrial group took back control without breaking the user experience.

Why tail spend is the silent issue of indirect procurement

In most organisations, tail spend represents 20% of the value of indirect purchasing but 80% of the transactions. It is the historical blind spot: too fragmented to deserve a category strategy, too high in line count to be handled case by case by category managers.

Three things happen when it is left as is.

1. The user waits. Six months for an employee to get an ergonomic mouse because the request goes through a full sourcing cycle. Five months for a lab to receive a basic consumable because the supplier is new and onboarding took six follow-ups. On paper, the process is respected. In real life, the team stops using procurement.

2. Maverick spend explodes. When the official channel takes five months to deliver an €80 item, the user takes out a personal card, buys on Amazon, and runs an expense report. It is rational from their point of view. At group scale, it represents thousands of euros a day of spend that escapes any negotiation, any data, any compliance.

3. Transaction cost exceeds purchase cost. Creating a supplier, processing an €80 invoice, handling an expense report, archiving, controlling. The administrative cost of a tail transaction routinely exceeds the value of the purchase itself. The organisation pays twice: once for the buy, once for the process.

The point is therefore not just to "save on tail". It is to give time back to the teams, smooth the experience, and stop wasting in transactional overhead what is supposedly saved in sourcing.

The marketplace: the right tool, under conditions

Amazon Business is built exactly for this case. The catalogue covers 99% of the everyday tail need (consumables, light IT, furniture, supplies, basic lab equipment). The user experience mirrors consumer Amazon, so users know how to use it without training. Prices are competitive and continuously benchmarked. ERP integration via punchout keeps PO, three-way match, and clean data.

The client wanted exactly this mix: take back control (data, compliance, price) while improving the experience (lead time, ergonomics, simplicity). On that double objective, the marketplace is a coherent tool.

On one condition: deploy it as a transformation programme, not as a SaaS module.

My mandate

On the Amazon Business EU side, I led the deployment with this group across 30+ EMEA sites. The contract existed, the tenant was live, adoption was at zero. Six months later, maverick spend on the covered categories was cut in half and the user experience had flipped.

What I found on the ground

The classics of unmanaged tail spend, at scale:

• A procurement policy written before the marketplace era, silent on tail, full of grey zones.
• No shared list of which categories must go through Amazon Business and which fall outside.
• Category managers either reluctant (loss of control) or quietly relieved (less noise), with no shared narrative.
• Users still routing through expense reports because it was faster.
• IT integration done at minimum: SSO ok, punchout ok, three-way match with holes.

The tool was working. What was missing was a deployment thought through as a programme.

The four conditions for a marketplace to deliver on its promise

A marketplace does not create compliance by its mere presence. It needs four pillars, executed in parallel from the first site.

1. A clear, shared, quantified business case. Before any deployment, we put the numbers on the table: current tail spend volume, share in maverick, transaction cost per line, average lead time, expected savings on price and on process. Not a marketing slide: a document finance signs off on. Without that document, the programme gets challenged at every steering committee, and the first deployment hurdle kills it. With it, we have an objective anchor when IT pushes another priority or when a category manager wants to pull a category out of scope.

2. A visible C-level sponsor. On this engagement, I asked CPO and CFO to co-sponsor the programme on the record, with a quarterly review. Any tail spend initiative shrinks the perceived territory of certain category managers and adds workload to IT. Without a sponsor able to arbitrate above both, the project stalls in three months. Sponsorship has to be visible at every site kickoff: video message, named accountabilities, quantified objective.

3. Written and signed use cases. Each tail category is mapped into three buckets: in scope for Amazon Business, out of scope (covered by an existing contract or a category team), and grey zone to arbitrate. The document is reviewed and signed by category managers. From that point, the question is no longer "should this go through Amazon Business?" but "is this category on the list?". This single document removes half the friction and gives users a clear answer.

4. A real, site-by-site hypercare phase. Hypercare is where most digital projects die quietly. On this rollout, we ran an 8-week cycle per site: a named local champion, weekly office hours, a single escalation point to procurement ops, daily tracking of orders bypassing the punchout, and a closing checkpoint with the site lead before declaring full go-live. Crucially, hypercare was used to test the use cases written at the previous step against real conditions. A miscoped category gets caught in hypercare, and that is when the list gets adjusted, not three months later.

It is the combination that produces the result. A sponsor without a business case is a slogan. A business case without use cases stays theoretical. Use cases not tested in hypercare turn into false dogma. Hypercare without a sponsor runs out of oxygen at the second site.

What it changed for the client

Six months after the first wave, maverick spend on the covered tail categories was cut in half. An employee who needed an ergonomic mouse had it within 48 hours. A lab that needed a routine consumable ordered it in the morning. Category managers stopped handling €80 tickets and moved back up to the categories that actually drive savings. Finance got auditable data on a perimeter that had been opaque for years.

Amazon Business was the technology that made the experience possible. The business case, the sponsor, the use cases, and the hypercare are what turned a signed contract into a tail spend programme that holds.