Ask ten procurement professionals what "tail spend" means and you'll get eight different answers, usually involving some version of "the small stuff at the bottom of the spend report." That description is accurate in a narrow sense but operationally useless — because the definition of tail spend you adopt determines what's in scope for your savings program, and getting that boundary wrong has direct financial consequences.
We've worked through this question with enough procurement teams at Proculr that we've developed a specific, defensible definition that we use consistently. I'll share it, explain why it's drawn where it is, and then address the categories that create disagreement.
The Standard Definition — and Its Problems
The conventional definition of tail spend is the bottom tier of suppliers by spend volume — typically the 80% of suppliers that collectively represent 20% of total spend, the inverse of the Pareto principle. If you have 400 active suppliers and 80 of them account for 80% of your spend, the other 320 are your tail.
This definition has intuitive appeal but two structural problems. First, it's percentage-based rather than dollar-based, which means it says different things for different organizations. For a company with $50M in indirect spend, the tail might represent $10M. For a company with $500M in indirect spend, the same percentage definition produces $100M in tail spend — an order of magnitude larger in absolute terms but the same in relative terms. Your savings target is a dollar figure, not a percentage.
Second, the supplier-count definition doesn't capture maverick spend — purchases made outside any contract or approved supplier, often on p-cards or expense reports, that don't appear in your supplier master at all. Maverick spend can represent 10-20% of total indirect spend for organizations without strong purchase-order compliance. If you define tail spend only by suppliers-in-the-system, you're systematically excluding a significant chunk of the real problem.
A More Useful Definition
Here's the definition we use at Proculr, and the one I'd recommend: tail spend is all indirect spend that has not been through a procurement review, a competitive event, or contract negotiation in the past 24 months, regardless of supplier size or spend volume.
This shifts the definition from "small supplier" to "unmanaged spend." The key word is "unmanaged" — spend that exists outside active procurement oversight, regardless of how it got there.
Under this definition, tail spend includes:
- All purchases below your organization's purchase requisition threshold (typically $5K-$10K for mid-market companies)
- Auto-renewed contracts where no renegotiation has occurred since the original signing
- P-card purchases and expense reimbursements for recurring vendor relationships
- Spend with suppliers who were once strategic and have since dropped below active management thresholds
- New vendor relationships initiated by departments without procurement involvement
And explicitly excludes:
- Direct materials (even small-volume components that are part of the bill of materials — these have a different management model)
- Regulated spend categories where the vendor selection process is driven by compliance rather than commercial optimization
- Spend with suppliers currently in active contract negotiation or RFP process
Why the 24-Month Clock Matters
The 24-month review threshold is not arbitrary. Market conditions for most indirect spend categories move meaningfully over a two-year period. A SaaS contract negotiated in 2022 may have been at market rate then but is likely above market now as the category has matured and competitive pricing has shifted. A facilities maintenance contract renewed without competitive review for three years running has absorbed multiple annual price increases that may or may not track what a renegotiated rate would produce.
The 24-month threshold says: a contract or vendor relationship that hasn't been reviewed in two years should be treated as unmanaged, even if it was fully managed at origination. The clock resets when procurement runs a competitive event, renegotiates rates, or does a documented market rate review — not just when a renewal auto-executes.
We're not saying every contract needs a full RFP every two years — that's not the right process for all categories. But the distinction between "reviewed by procurement in the last 24 months" and "renewed automatically" is exactly the gap that creates price drift. Tail spend management means closing that gap systematically.
Where Organizations Get the Definition Wrong
Two common mistakes produce meaningfully different savings targets.
Including direct materials in tail spend scope. Some organizations define their "tail" broadly to include small-dollar component purchases within the bill of materials. This inflates the apparent tail spend number and creates false confidence in the savings opportunity. Direct material spend requires supply chain continuity considerations that don't apply to indirect spend — you can't run a 3-bids-and-a-buy competitive event on a critical component with a six-month lead time. Including it in tail spend scope produces an unrealistic savings target and distracts from the real opportunity.
Excluding high-value but infrequent indirect spend. A consulting engagement at $150K every 18 months might not appear in your regular tail spend analysis because it's project-based and high-dollar. But if it's never been through a competitive process — or if the same firm has been retained for three consecutive engagements without a market check — it meets the functional definition of unmanaged spend. The 80/20 supplier-count definition would put this in the "strategic" bucket because of spend volume, but our activity-based definition puts it squarely in scope.
Setting the Savings Target
Once you have a consistent definition, the savings target becomes much more tractable. The general range for realized savings from a systematic tail spend program is 8-18% of the in-scope spend, with the range driven primarily by how long the spend has been unmanaged and how competitive the relevant categories are.
A category where vendors have been auto-renewing with 3-5% annual price increases for four years without a market check tends to sit 12-20% above current market rates. A category where spot purchases are made without any approved supplier framework has even more variance, because without a contracted rate there's no price anchor at all.
The 8-18% range is deliberately wide because it depends on the specific categories in scope, the geographic concentration of suppliers, and how competitive the relevant markets are. We'd rather give you a range grounded in the mechanics of why tail spend is overpriced than a specific number that implies false precision. What you should expect is that the savings are material — typically 1.5-3% of total indirect spend — and that the opportunity grows with each year the spend stays unmanaged.
Making the Definition Operational
A definition is only useful if it translates into a classification you can actually run. For most mid-market companies, operationalizing the activity-based tail spend definition requires pulling together three data sources: the approved supplier list with contract dates and last-review dates, the AP transaction history including p-card and expense data, and the purchase requisition log with approval routing history.
When these three sources are joined, the tail spend picture usually looks larger than expected — because spend flowing outside the purchase order system through p-cards and expense reimbursements has often never been visible in any single place. That expansion of the visible tail is actually good news, not bad: it means the savings opportunity is larger than a supplier-list-based analysis would suggest.
The definition you use shapes the program you build. Start with "unmanaged" as the criterion, not "small," and the tail spend program addresses what's actually costing money.
