The 6-week pilot: from your inbox to your number
One lane. Read-only access to the inbound emails you already receive. At the end: a verified figure for how much buffer that lane can safely release — proven against what actually landed. If the number isn't there, we both walk away, and you keep the report.
What we need from you
A forwarded or connected mailbox for one lane (about an hour of setup), a contact who knows the lane, and thirty minutes a week. No IT project. No supplier or forwarder involvement — they never log in to anything.
Week by week
We connect the inbound mailbox for your chosen lane. Nothing changes for your suppliers or forwarders.
Epoch reads the confirmations, revisions, and forwarder updates already in the mail flow and rebuilds arrival truth at PO line level.
Reconstructed dates vs the dates in your ERP vs what actually arrived. The first deviation report lands on your desk.
Buffer analysis: the days you hold vs the days the lane's real variability requires at your service level.
The projection is back-tested against actual arrivals. Your team checks the receipts — literally.
You get your number: euros releasable, carrying cost saved per year, and a rollout plan if you want one.
The questions you'd ask anyway
Messy is the point. Epoch is built for revised dates buried in reply-chains, mixed shipments, and naming errors — the exceptions other systems ignore.
Read-only mail access, EU hosting, GDPR-compliant processing. Your IT team gets the documentation before anything connects.
Simple: if the six weeks don't produce a number worth taking to your CFO, you don't pay. You'll have the exact fee before the intro call ends.
