SAVINGS VERIFICATION
A performance engagement only works when both sides know what counts as a saving, what is excluded, and how changes in headcount, pricing and scope are handled.
The written statement of work should define the pre-engagement spend baseline, applications or vendors in scope, licence quantities, unit pricing, renewal dates and the measurement period.
Actions already approved or contractually committed before the engagement should be identified up front so they are not incorrectly attributed to the engagement.
An identified opportunity is not automatically a realised saving. A realised saving should require evidence that the customer's actual cost, committed spend or renewal obligation decreased under the agreed measurement rules.
Material changes in employee count, acquisitions, divestitures, product scope or vendor pricing should be normalised or treated under the rules agreed in the statement of work.
The customer validates business need before licences are removed, reassigned or downgraded. Technology Spend Optimizer produces review recommendations; it does not automatically execute those changes.
Where savings come from a renewal or commercial negotiation, the contract should define the comparison basis, such as the supplier's like-for-like renewal proposal, prior unit price or another agreed benchmark.
Evidence can include invoices, executed order forms, billing exports, licence counts or other agreed records. The exact evidence standard belongs in the customer contract.
The commercial agreement should specify how disputed savings are reviewed and resolved. Website examples and calculator outputs do not override the signed agreement.