Savings Realization & Leakage Tracker

The problem this kills

You negotiated the prices. You reported the savings. Then the year closes and finance asks the question every procurement lead dreads: can you prove it?

The honest answer is usually no. The "savings" lived in a slide deck, not in the invoices. Somewhere between the signed contract and the accounts-payable run, the old price kept getting paid - on a stray PO, a forgotten supplier portal default, a line item nobody re-mapped. That gap between negotiated and realized is called leakage, and most teams have no systematic way to see it. So savings get reported, then quietly evaporate, and the credibility of the whole procurement function takes the hit.

Spreadsheets don't fix this because they can't reconcile a register of promised savings against thousands of invoice lines, period by period, while keeping a clean audit trail of what was checked and approved. You end up either trusting the number or rebuilding the analysis by hand every quarter.

What you'll build

A private web app for your team that:

• Imports your savings register - each initiative with old price, new price, effective date, expected volume, and whether it's a cost reduction or cost avoidance.
• Imports actual invoiced prices from your AP/ERP export (or a Google Sheet / CSV if you have no integration yet).
• Computes realized savings per item and period: (old price - actual price) x actual volume, aligned to each initiative's effective date.
• Flags leakage - lines where you're still being billed the old price, or above the new contract price - so you can chase them before quarter-end.
• Routes every figure through a human validation gate - finance/procurement reviews the methodology and evidence, and nothing counts as "achieved" until validated.
• Reports validated realized savings on a dashboard by category and quarter, with CSV export and a shareable report.

What's inside the Implementation Plan

• It starts by interviewing you about your business. Before a single line of code, the plan has the AI agent ask about your current process, your ERP and AP exports, your real field names and SKU/category conventions, your volumes, and your messy edge cases - then it tailors the data model and rules to your world. This is not a generic template you have to bend to fit.
• A clear definition of done and an architecture diagram you can actually follow.
• Step-by-step build instructions, each ending in a ready-to-paste prompt.
• The cost-reduction-vs-avoidance distinction baked into the model, so the two never get blended into one misleading number.
• Effective-date alignment so a January contract doesn't get credited for December invoices.
• A "No API yet?" fallback that runs the entire tool off Google Sheets / CSV imports and exports clean CSV in the exact columns your system expects.

The governance it includes (this is the point)

• Login so only your team can open the tool.
• Row-level security so each organization only ever sees its own data.
• A complete audit trail - who imported what, who validated which figure, and when.
• A hard human-in-the-loop approval gate - the tool computes and the AI drafts the realized-savings figure, but a person reviews the methodology and evidence and approves before it's ever reported as achieved.
• Duplicate guards - an initiative-plus-period key for savings figures and the invoice line id for actuals, so the same input can't be double-counted.

Who it's for

Procurement leads and category managers who report savings to leadership, and the finance partners who have to stand behind those numbers. If you've ever had a "validated savings" conversation turn awkward, this is for you - and you don't need to write code to build it.

You've got this - paste the first prompt and let the agent interview you.