Ninety minutes on your numbers. Not ours.
A working session where we build the model with you, using your store count, your shrink figure, and your current counting cycle. You leave with the spreadsheet whether or not you ever buy anything.
No slides. Bring whoever will be asked to sign off on the number.
Four things, in order.
The session exists because most RFID business cases are built on an industry average and a hopeful assumption. This one gets built on what you already know about your own stores.
Your baseline
Store count, average revenue per store, how often you count today, and how many hours it takes. Estimates are fine; we label them as estimates.
The leak
Where inaccuracy costs you now: lost sales on stock the system says you have, markdowns taken on the wrong items, and hours spent counting.
The model
We build it live, in front of you, with every assumption visible. If one looks wrong to your finance lead, we change it in the room.
What would prove it
The model ends with the number the POC would have to hit to be worth doing. That becomes the pilot's success criteria rather than a vague hope.
It is not a demo with a spreadsheet attached.
A demo shows you the software. A Payback Session works out whether the software is worth your time, which is a different question and usually the first one.
What makes the ninety minutes worth it.
Four numbers.
- Stores in scope and roughly what each one turns over in a year
- Counting cycle how often you count and what it costs you in hours or third-party fees
- Shrink and markdown as a percentage, even approximately
- Online orders fulfilled from stores, and how many get canceled after the fact
Three people.
- Store operations because they know what the count actually costs in practice
- Finance because they will challenge the assumptions, which is the point
- IT because the integration question tends to arrive late and change the timeline
Bring your numbers. We will bring the model.
If the model does not work in your favor, you will know in ninety minutes rather than after a procurement cycle.