Reads contracts and delivery performance together, so a supplier drifting out of terms is a conversation before it is an invoice.
earlier warning
to the Scan's evidence — before any scope
to a system in production, not a pilot
modeled targets · not client results · timings are CRFT's standard engagement
The contract is a PDF in a folder. Performance is in the ERP. Nobody joins them until a renewal or a dispute, so price creep and slipping lead times accumulate quietly for quarters.
Where the Scan startsWith your contracts, delivery history and where price creep has gone unnoticed.
Four lines, the same four on every system we build. Where they fall is what makes this one different from the last one.
The signals it works from. Typically connects to Contract storage, ERP, Accounts payable and Quality records.
The calls it makes on its own, unattended, every time it runs.
Into the tools the work already lives in.
A category manager runs the supplier conversation. The system supplies the position; it does not hold the relationship.
The same four legs as every CRFT engagement — written for this system rather than in general.
We take a sample of contracts and reconcile them against what was actually invoiced and delivered. The size of the gap in that sample sets whether this is worth building at all — and sometimes it is not, which is a finding worth having for the price of the Scan.
Scope follows contract legibility. Structured terms are quick; scanned PDFs mean extraction is the first leg.
It reconciles historically before it monitors forward, so the first output is a number you can take to a supplier, not an empty dashboard.
Each dispute resolved teaches it which deviations are real and which are noise in your categories.
Warning time before a term breach becomes a cost, and recovered spend against contracted terms.
Five inputs, a published price, a report in 48 hours. Decide with numbers — then own what gets built.