The neighborhood regular
Orders from the same few local pizzerias a few times a month. Has tried chain loyalty apps and dropped them, the pattern behind the research above.
No product, no pattern, no agreed model. I set the design vision for Slice Rewards, took it from a blank page to launch, and turned a flat start into a measured lift in repeat purchases.
One rule anyone can repeat, and a pizza that fills as you order.
5 chapters · 6 min readIndependent pizzerias were losing regulars to chains with loyalty apps.
A network-wide program for 16,000 shops that still feels simple.
Took it from a blank page to one rule and shipped it. When launch came in flat, I found why and fixed it in the flow.
Repeat purchases up 4–9% by Q2, statistically significant.
Open any bet for what I believed and the signal that proved it right or wrong.
Customers were ordering from Domino’s, Papa John’s and Pizza Hut, which rewarded them for ordering again. Independent shops had nothing, and retention of Slice’s power users had dropped 5%.
Slice decided to fund the reward itself, on a fixed launch date before the investor pitch. In interviews, people who’d tried chain programs named three reasons they quit: confusing rules, slow progress, and not knowing when they had a reward. Each became a constraint: one rule, a head start, and telling people the moment they earn.
Behind every order, a regular deciding where to go.
Orders from the same few local pizzerias a few times a month. Has tried chain loyalty apps and dropped them, the pattern behind the research above.
Runs a family pizzeria up against chain loyalty apps. Wants a program, but not the cost of pizzas earned elsewhere, or the time to run one.
{{ ch.q }}
I worked with Creative and Marketing to align illustration, color and motion, so the campaign could use the product as-is. The TV spot was built on the screens I designed: order status, the Home tracker and the celebration.
The App Store listing leads with the same Home tracker, as “America’s biggest pizza rewards program.”






{{ b.t }}
{{ b.t }}
{{ pp.t }}
{{ pp.t }}
My principle{{ b.pr }}
{{ b.el }}{{ b.cap }}
{{ pp.t }}
{{ ch.result }}
“{{ ch.quote }}”
{{ ch.who }}WhyConfusing rules were the top reason people quit chain programs, so every surface got one job and one message.



Wireframe, then a $25 photo pitch, then a points bar. The bar read as a progress meter, not pizza; the pie won.





A photo pie looked appetising but hid progress at small sizes. An illustrated pie kept it legible from 1 to 8.





From an upsell (“spend $15”) to a plain confirmation that this order counts.




WhyPeople quit over rules they couldn’t follow, so the tab explains the program without adding rules.
Your Rewards leads with the pie and the one number that matters, then tip cards that slide: how to earn, what you get, what counts. How it works answers the questions from research in a collapsible FAQ, so the rule stays one line.
Four moments, one message: you’re closer to a free pizza.
{{ pp.t }}
{{ ch.mo.cap }}
The same moments and motion, in the shipped flows. Each flow starts where people already were: web customers coming into the app, developing users mid-habit, and members cashing in.
{{ ch.flowSum }}
The three cases that mattered most: a pizza that costs more than the reward, a refund that takes a point back, and a reward about to expire.










Eight tokens, one wordmark, three bursts and a pie with ten states. Every Rewards surface, from the Home module to Congrats, was built from these parts and specced for iOS and Android.
WhyThe pie had to read the same on a small Home module and a full-screen Congrats, so every surface was built from one kit.








Launch is the first experiment. Name the riskiest assumption, and instrument for it.