Spend leakage is rarely the result of one bad decision. It is the accumulation of small ones, none of which look urgent on their own.
A supplier raises prices by three percent on a repeat order and no one renegotiates because the order is routine. Two business units pay different rates for the identical item because neither can see what the other is paying. A contract renews automatically because the renegotiation deadline passed unnoticed. Individually, each of these is a rounding error. Across a year, across thousands of line items, they compound into a number that surprises finance when it finally surfaces.
Why the quarterly spend review catches it too late
Most organizations still find leakage through a periodic spend analysis: someone exports a year of purchase history, builds a pivot table, and compares prices across suppliers and business units. This works, eventually. It also means the leakage has already happened by the time anyone sees it. The analysis is forensic, not preventive.
What changes with continuous benchmarking
The alternative is checking every price against a live benchmark at the moment it is proposed, not months later in a retrospective report. That requires two things most spend analyses do not have: a benchmark that updates continuously as new awards land, and enough item-level coverage that "we did not have data on that category" stops being the excuse leakage hides behind.
This is the specific gap dmp’s benchmarking module is built to close — comparing every proposed price against current data before the negotiation closes, not after the invoice arrives.