CFO-sponsored working-capital diagnostic
Finance wants to know whether duplicate inventory is material enough to justify remediation funding.
Proof required: Capital exposure, recoverable range, carrying-cost drag, and report ownership.
Pilot archetypes
Three buyer committees, three proof requirements.
CIO / SAP migration readiness review
IT and master-data teams need a safe backlog before S/4HANA, ERP consolidation, or MDG scope is approved.
Proof required: CSV-first data readiness, no write-back, confidence tiers, and governance review path.
Operations / procurement leakage review
Plants and buyers need to know whether duplicate records are causing search friction, emergency buys, or supplier fragmentation.
Proof required: Duplicate-family priority, supplier alias context, site/store visibility, and Open Findings review.
Short demo video storyboards
The three clips every serious buyer should be able to watch.
Demo 01 - Upload and map
Show a buyer how a SAP, Maximo, Oracle, or generic CMMS export is mapped before the engine runs.
File selected -> field readiness -> currency interpretation -> owner confirms mapping.
Demo 02 - Findings and CFO view
Show the first executive screen after a diagnostic completes.
Exposure signal -> duplicate groups -> confidence tiers -> CFO command view.
Demo 03 - Governed review path
Show what remains after the active session ends and why downloads are session-scoped.
Source purge -> Open Findings -> dashboard report history -> next remediation decision.
Production note: these are the approved storyboards for short branded video assets. Until final media is published, they make the demo sequence explicit for buyers and implementation teams.
Pilot checklist
What a credible first pilot must include.
A weak pilot contains only easy duplicates. A strong pilot includes known duplicates, known non-duplicates, incomplete fields, currency variation, ERP aliases, and enough rows to test both value and restraint.
Catalog file10K-100K rows preferred, with item description at minimum; unit cost, quantity, plant, manufacturer, and MPN improve value proof.
Truth samplesInclude 30-50 known duplicates and known non-duplicates to test both recall and restraint.
Owner groupFinance, procurement, maintenance, CIO/data governance, and site operations should all review the report.
Decision gateApprove remediation only after Tier 1 evidence and high-value Tier 2 groups are reviewed by owners.
Enterprise trust posture
Proof controls buyers expect before they upload operational data.
Source purge
Uploaded source files are purged after report generation; summary metrics and Open Findings remain.
No ERP write-back
The diagnostic creates evidence for review. It never changes, deletes, merges, or overwrites ERP records.
Local currency
Reports display money in the user's selected or country-derived currency, while USD remains the base audit calculation.
Audit trail
Report ownership, access, quota, and feedback events are retained for governed review.
Session downloads
Excel, Word, PDF, and CSV downloads are available only in the active generation session.
Open Findings
Browser findings remain available without retaining the original source catalog rows.