Stop estimating. Count it.
Thirty days in your stores, on your stock. We bring the readers, install them, establish what your inventory accuracy actually is today, run Clarity Store against it, and hand you the difference in writing. No hardware cost, no license fee, no commitment, no rip-and-replace.
Open to multi-location retailers in apparel, footwear, and other inventory-intensive categories.
A number you can take to your board.
Most inventory business cases are built on an industry average and a hopeful assumption. This one is built on a count of your own stock, taken twice, by the same people, in the same stores. Whatever the POC shows is yours to keep, whether or not you buy anything.
Your baseline accuracy
What your stock file says versus what is physically on the floor, measured at item level before anything changes. For most retailers this is the first time they have seen the real figure.
The accuracy delta
The same measurement at the end of the 30 days, taken the same way, so the movement is attributable rather than asserted.
Hours returned
Counting time before and after, per store, per cycle. The operational saving is usually the part that funds the rollout.
A rollout model
What the pilot numbers imply across all your stores, built on your store count and your revenue, not on ours.
Four moves, and only one of them is ours.
The POC is deliberately small. It runs in one or two stores, on stock you already tag or that we tag for the pilot, and it uses your own colleagues rather than a visiting team. If it only works when we are standing there, it has not been proven.
Scope
A specialist walks the stores, then we agree the departments and the one question the pilot has to answer. Store format, SKU density, and antenna placement are not copy-paste, and the survey is what stops that becoming a surprise later.
Baseline
Your team counts the pilot stock the way they do today. That count, against your stock file, is the number everything afterwards is measured against.
Run
Clarity Store goes live in the pilot stores. Your colleagues cycle count on handhelds, and the item-level record updates as they walk. Roughly four weeks of ordinary trading.
Readout
We recount, compare, and present. One session, your stakeholders, the real figures, including anything that did not improve.
Nothing, and it ends when you say so.
A proof of concept that comes with a contract attached is not a proof of concept. We supply and install the readers, the platform runs at no license cost for the pilot period, and you own none of it until you decide to. Nothing you already run gets switched off.
The honest version of the ask.
A pilot fails on the boring things: nobody owned it, the stores were never told, the baseline was never taken. Here is what we need from you, stated plainly enough that you can decide now whether it is worth your quarter.
Five things, one of them a person.
- A named owner who can get a decision made
- One or two stores, and the departments inside them
- Access to your stock file for the pilot SKUs
- An hour of store-team time for handheld training
- Somebody from IT for the integration conversation
The rest of it.
- A site survey of the stores before anything is installed
- Readers, antennas, and handhelds, supplied and installed
- Clarity Store configured for your pilot scope
- Integration to your ERP or WMS for the pilot data
- Training your team can repeat without us
- A named implementation lead, not a ticket queue
- The baseline, the recount, and the written readout
Readers you already own get used rather than duplicated, and anything missing we supply for the thirty days. How the pilot stock gets tagged is settled at the survey, before anyone commits to a date.
Not every RFID commitment is the same shape.
A pilot can look like a step worth skipping, and it is an expensive one to skip, because the work a pilot does still has to happen. It just happens after you have signed, at your cost, on your timeline. Here is where that difference shows up.
The cost moves, it does not vanish.
- Timelines quoted in weeks that arrive in months
- Use cases assumed generically, with no site survey
- Hardware billed from the day you sign
- Integration complexity discovered after deployment
- Associate adoption treated as your problem
- No accuracy baseline before the rollout starts
The same work, before the money.
- Thirty days, scoped in writing before we begin
- Your actual stores surveyed before any commitment
- Readers, installation, and platform at no cost
- Integrations scoped and built during the pilot
- Training embedded in the deployment, not bolted on
- A documented accuracy result before you sign anything
Someone ran this exact pilot first.
Lager 157 started with three stores and one counting cycle, and used what came back to decide what to do next.
The questions we get every time.
Who qualifies?
What is the catch on "free"?
Do we have to tag our whole assortment?
Does this replace our ERP or WMS?
Do we have to buy hardware to run the pilot?
Who sees our data?
What happens at the end of the thirty days?
Tell us what you want proven.
The more specific the question, the better the pilot. "Prove our accuracy is worse than our stock file says" is a good one. So is "prove our colleagues will actually use it."
Delivery picks it up
The same people who would run your pilot.
Scoping call, about an hour
Stores, departments, systems, and the question the pilot answers.
You get a written pilot plan
Scope, dates, what each side owns. You decide from there.
If it can be proven in thirty days, what is the six months for?
Every month spent evaluating is another month of phantom inventory, canceled online orders, and stock counted by hand. Thirty days is a short argument. Bring us the stores and the question, and we will bring you the number.