Pilot playbook

How to run a 14-day digital loyalty pilot

A day-by-day plan for testing a digital loyalty card with real staff and customers while measuring only what the pilot can actually prove.

Updated September 15, 20268 minute readWritten and reviewed by StayLoyal

A useful loyalty pilot tests operations before it tests growth. In two weeks, a business can learn whether customers understand enrollment, whether staff can run the scanner during checkout, and whether the reward rules survive real questions.

Fourteen days usually cannot prove long-term retention or incremental revenue. It can produce the implementation evidence needed to decide whether a longer measured rollout is worthwhile.

Before day 1: write the pilot brief

Choose one program, one location, one accountable owner, and a start and end date. Write down the qualifying action, reward, exclusions, staff roles, customer enrollment fields, and how mistakes will be corrected.

Define success thresholds before seeing the results. Use operational thresholds the system can measure, such as whether the QR is displayed, whether staff use the scanner, and whether customers successfully save passes.

One program and one location
Named pilot owner and trained staff
Approved customer-facing terms
Counter QR placement
Baseline and success criteria
A plan for support and incident escalation

Days 1–2: launch quietly

Start during staffed hours when the owner or manager can observe. Ask a small number of customers to scan, complete enrollment, and save the pass. Watch where they hesitate without collecting more personal information than the program needs.

Have staff practice scanning, adding progress, undoing a mistake where allowed, and explaining the reward. Fix operational confusion before increasing promotion.

Days 3–5: stabilize the counter workflow

Review failed enrollments, device mix, staff access, and scanner errors. Move the QR if customers cannot see it or if scanning blocks the payment line.

Keep a short issue log with the time, device, location, symptom, and resolution. Do not record customer secrets or full pass identifiers in an informal document.

Days 6–10: observe normal usage

Once the mechanics are stable, let the program run without constant coaching. This is when the business learns whether the workflow fits a normal shift rather than a founder-led demonstration.

Check whether every trained shift records loyalty activity consistently. A high number of issued passes with no later staff actions may indicate a scanner or training problem—not necessarily a customer-retention problem.

Days 11–14: review and decide

Summarize activation, staff usage, customer pass issuance, loyalty actions, corrections, and any redemptions. Separate observations from interpretation.

Choose one of three outcomes: continue unchanged for a longer measurement period, revise the program and repeat a bounded pilot, or stop because the workflow does not fit the business.

Use a defensible scorecard

StayLoyal can report product activity. It cannot, by itself, prove a physical visit, purchase value, contribution margin, or incremental lift. Those outcomes require reconciliation with the merchant’s own point-of-sale or financial records.

Metric	StayLoyal can observe?	What it tells you
Passes issued	Yes	Enrollment completed and a membership was created
Wallet saves	Yes, when authorized	A pass save flow was authorized for a platform
Stamps and redemptions	Yes	Authorized staff recorded loyalty actions
Staff/location activity	Yes, when configured	Where and by whom actions were recorded
Store revenue	No	Requires POS or financial data
Incremental repeat visits	Not by itself	Requires a baseline and identity-matched comparison
Customer satisfaction	No	Requires direct, consented feedback

Protect the customer relationship

Tell customers what information the program collects and why. Collect only what the business needs to operate the loyalty relationship, protect access to the merchant workspace, and use separate consent for marketing messages where required.

A loyalty pilot is not permission to upload contacts into unrelated outreach tools or send promotional messages without the consent required by the relevant channel and jurisdiction.

What a successful pilot earns

The output of a good pilot is confidence in the operation: customers can join, staff can run it, the reward can be honored, and the merchant can interpret the activity accurately.

Longer-term business impact should be measured after that foundation works. Avoid turning two weeks of product activity into an unsupported promise about retention or revenue.

Primary and supporting sources