Day 0
Choose the store set
Start with stores that represent normal pressure, including at least one location that creates morning follow-up today.
Stage 5 - Most aware
Implementation
How Tillzen Gets Implemented Without Replacing the POS
Implementation should feel small at first. Pick a focused store set, choose the closeout gap to measure, keep the POS in place, and use real closeouts to prove whether the packet becomes cleaner by Day 14.
Buyer wants to know what work changes before agreeing to a pilot.
Days 1-3
Find the first pattern
Look for missing proof, vague reason quality, sign-off before evidence, owner confusion, or review bottlenecks.
Day 14
Read out the decision
Use packet quality, adoption, unresolved exceptions, and reviewer follow-up to decide the next rollout step.
Setup
Define complete before stores change behavior.
Implementation starts by naming the fields a reviewer needs, not by asking stores to adopt a broad new system all at once.
- Store, date, shift, drawer, safe, and manager identity.
- Expected cash, counted cash, proof state, and sign-off.
- Variance reason, owner, status, and resolution path.
- Reviewer follow-up fields the readout must measure.
Enablement
Training stays tied to one daily routine.
The first implementation goal is not a large transformation project. It is getting managers to submit a packet that can answer for itself the next morning.
- Show what a complete packet looks like.
- Use one messy closeout as the example.
- Make missing proof visible before review.
- Keep feedback close to the store routine.
Pilot proof standard
The page should move the buyer toward one real closeout.
Close to action. Needs specificity, risk reduction, proof, and a clear pilot path.
Concierge setup
Focused first stores
No POS replacement
Daily review rhythm
Day-14 decision
Questions
Common Decision Questions
How long does implementation take?
The first implementation pass is designed around a 14-day pilot, with Day 0 baseline setup and a focused readout by Day 14.