The method
Five phases. One named framework each. The first four put the loop in place. The fifth is the loop, run continuously — that is Guardian.
The five phases
What was promised when you signed. What is actually live. Who still owns it. A one-page reconstruction of the original business case mapped against today's usage.
The five places value is leaking — across coverage, signal, compliance, workflow, and renewal. Each scored by impact and ease. The output is a top-five list, not a hundred-item backlog.
Three things move at once: configuration of the platform, ownership across teams, and the operating cadence. Configuration is the easy part. Ownership and rhythm are where the gap lives.
Four to six monthly numbers your CFO can sign. The set is picked together in week one — not a fixed five, because what moves the board at an automotive Tier-1 is not what moves a medical-devices CFO. The default starting set: disruption avoidance, compliance exposure, time-to-resolution, procurement leverage, working capital.
Monthly working sync. Quarterly board-style review with CPO and CFO. Half-yearly training cycle. Annual renewal-readiness brief. Same template, every time. Value compounds only if someone protects it.
Where most of the work lives
The majority of my engagements run on Prewave. The single biggest value lever I see again and again is BIRS — the Business Interruption Risk Score. Most teams have BIRS enabled but treat it as a number on a dashboard. The high-value move is to wire BIRS into the procurement decision flow: which suppliers do you single-source on, which buffer-stock decisions does the score actually drive, which contracts get force-majeure language strengthened, which suppliers get a second source named for them.
Kärcher and Hilti are the public benchmarks. Both have used the BIRS discipline to build a continuous business-interruption mitigation function and have publicly attributed material avoided cost to it. The same playbook is replicable across DACH automotive, machinery and consumer goods supply chains.
Beyond BIRS, the recurring Prewave configuration work: tightening alert thresholds across 200+ risk categories and 400+ languages to cut noise; activating the Action Platform so tier-2 alerts produce workflow steps, not emails; aligning the LkSG module to the BAFA evidence requirement, not just the report template.
Compliance → business value
The compliance modules in Prewave — and the equivalents in Sphera, Resilinc, Exiger — are most often deployed as compliance theatre: file the report, pass the audit, file the next report. The same supplier-diligence data set, redirected, is a procurement asset. It consolidates the supplier book, sharpens force-majeure clauses, retires underperforming relationships and de-risks single-source dependencies. Compliance pays for itself when it informs sourcing decisions, not only regulator filings.
Across the rest of the stack
Network digital twin actually drilled down to part-and-site level for the top critical suppliers. The fifty-plus risk scores calibrated to a smaller, business-relevant set so the team stops drowning. Weather and lane feeds wired into daily planning.
Tolerance levels tuned per supplier tier so automated due diligence stops escalating every signal. Item-level mapping wired into the sourcing decision. Sanctions and beneficial-ownership refresh aligned to the regulatory calendar.
ESG question pack realigned to LkSG and the forthcoming CSDDD mandatory fields. The pre-built mitigation workflows turned on. Supplier 360 wired to procurement so risk grade informs supplier-of-record decisions.
EventWatchAI thresholding to keep the 104-million-source firehose actionable. Multi-tier mapping driven from your bill of materials rather than the standard supplier survey. War-room collaboration moved from "during a crisis" to a standing monthly cadence.
How the loop maps to services
Phases 1 and 2 of the loop. Fixed scope, three to four weeks. You end with the Value Leak Map and a clear recommendation on whether the platform stays, expands or goes. The most common door into Guardian.
Phases 3 and 4. Eight to twelve weeks. Named owners, a working Value Ledger, an activated workflow that survives my exit. Most Activations roll directly into Guardian.
Value Training in two tracks — User and Management. Practical workshops, run once or recurring inside Guardian.
AI Value Sprint. Same loop applied to AI initiatives, four to six weeks, with extra attention on data readiness and metric design. The Sprint is the door; Guardian is the home.
The destination
Phase 5 of the loop, run continuously. A fractional Value Realization function for your team. Monthly sync, quarterly board review with the CPO or CFO, vendor escalation, training cycles, renewal preparation. The point of every other module is to land you here.
What you keep
Every engagement leaves your team with a working operating cadence, a documented playbook, and a Value Ledger they update themselves. Guardian keeps that system honest, current and compounding. Strategy is part of the work when it helps — the edge is in the operating cadence that turns it into a board-ready number, every month.