Sourcing Event Pipeline & Savings Tracker: See the Whole Portfolio and the Savings You've Actually Banked

The problem this kills

Ask a procurement team "how much did we save last quarter?" and watch the scramble. The answer lives in six places: a master RFQ tracker that one analyst maintains, a few category buyers' personal spreadsheets, a slide deck someone built for the last business review, and a couple of email threads where a savings number got "agreed." Nobody is quite sure which figure is real, what baseline it was measured against, or whether finance would actually sign off on it.

Meanwhile the pipeline itself is invisible. Leadership can't see how many sourcing events are in flight, who owns each one, which ones are stuck, or what the active portfolio is worth. Two buyers run competing RFQs against the same supplier in the same category without realizing it. A "$2M savings" claim turns out to be a cost avoidance against a quote nobody negotiated, sitting right next to a hard, banked cost reduction — and they're added together as if they're the same thing.

The result is the thing that quietly erodes a CPO's credibility: savings that can't be defended. A sourcing portfolio deserves to be one governed system of record — every event visible, every savings number traced to a baseline and a methodology, and validated by a human before anyone reports it as delivered.

What you'll build

A simple internal web app for your procurement team. You enter or import your sourcing events — name, category, owner, current stage, baseline spend, target savings, achieved savings, and the key milestone dates. Each event flows across a kanban board by stage (your real stages: Intake → RFQ → Negotiation → Award → Implemented, or whatever yours are) and also lives in a filterable table you can slice by owner, category, or quarter.

When a buyer claims savings, they don't just type a number. They record the baseline (and where it came from), the savings type (cost reduction vs. cost avoidance), the methodology, and the achieved amount. That claim sits as unvalidated until a procurement lead reviews and approves it — only then does the savings count toward the portfolio. The dashboard rolls everything up: total pipeline value, realized savings by category and by quarter, validated vs. claimed, and a flag on any project that's gone stale. The tool warns you when two open events target the same category and supplier, exports the whole pipeline to CSV, and emails a scheduled summary to leadership.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — your real sourcing stages and how events move between them, where your projects live today, your exact category taxonomy and project-ID convention, how you define and source a baseline, how you draw the line between cost reduction and cost avoidance, who is allowed to validate savings, and the messy exceptions (multi-year deals, phased awards, savings that slip a quarter). It reads a short tailored spec back to you and waits for your thumbs-up before building anything — so the board, the savings rules, and the dashboard match your sourcing process, not a generic template.

From there it walks the agent through the data model, the import, the kanban board and table, the savings-capture form with mandatory baseline and methodology, the lead's validation gate, the portfolio dashboard, the stalled-project alerts, and the duplicate-supplier-per-category warning. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path that imports your pipeline from a Google Sheet / CSV and exports a clean CSV in the columns your finance team and business reviews expect — so you can build and run the whole thing this afternoon, with no integration to any e-sourcing suite.

The governance it includes (this is the point)

Reported savings are only as good as the controls behind them, so the controls aren't optional. The plan builds in login so only your procurement team can use the tool, row-level security so you only ever see your own organization's pipeline, a complete audit trail of who changed which savings figure and who validated it, a hard human-validation gate so a claimed savings number is never counted as delivered until a procurement lead approves the baseline, methodology, and achieved amount, and duplicate guards keyed on project ID — plus a warning when two open events chase the same category and supplier.

Who it's for

Procurement leads, sourcing managers, and CPO-office analysts who manage many sourcing events across a scattered set of spreadsheets and are tired of rebuilding the savings story for every business review. If you can describe your sourcing stages and how you decide a savings number is real, you can build this.

You've got this — start with the plan, paste the first prompt, and answer the interview. You'll have your pipeline on a board and your first defensible savings number on the dashboard before the afternoon's out.