Baseline
What was messy before the pilot
Morning follow-up minutes, missing proof asks, vague variance notes, unresolved owner count, and the store set being tested.
Stage 5 - Most aware
Sample pilot readout
What a Tillzen Pilot Readout Should Show by Day 14
A pilot should end with a decision document, not a vague demo recap. The readout should show whether real stores created cleaner closeout records and whether the next rollout step is worth taking.
Buyer is close to action and wants to know exactly what the pilot produces.
Day-14 view
What changed in the record
Cleaner packets, earlier proof gaps, clearer ownership, manager adoption, and fewer closeouts sent back for context.
Decision
What to do next
Expand, narrow, coach, extend, or stop from evidence instead of enthusiasm for a polished product tour.
Readout contents
The readout should compare baseline to Day 14.
The strongest readout separates operational quality from software preference. It should make the current closeout gap visible, then show whether Tillzen helped pilot stores leave reviewable records.
- Annualized time value from reduced follow-up.
- Proof gaps by store and business date.
- Unresolved exceptions with owner and status.
- Adoption and manager burden signals.
Rollout logic
A good readout names the next move.
The final recommendation should be practical. Some stores may be ready to expand, some may need coaching, and some fields may need a narrower pilot before broader rollout.
- Expand when packets are cleaner and adoption is stable.
- Coach when the same reason or proof gap repeats.
- Extend only when evidence is promising but incomplete.
- Stop when the current gap is not painful enough to change.
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.
Day 0 baseline
Days 1-3 first insight
Days 4-10 exception pattern
Days 11-14 packet quality
Final rollout decision
Questions
Common Decision Questions
What should a pilot readout include?
It should include baseline friction, day-14 packet quality, proof gaps, unresolved exceptions, adoption, time value, and a recommendation to expand, narrow, coach, extend, or stop.