Five industries.
One architecture.
The first of these was built for a grocery loyalty programme, so people ask whether it only works for groceries. It doesn’t. Every one of these is the same shape: a moment your customer spends waiting, work prepared inside it, and a person who says yes before anything happens. Only the configuration changes — pick an industry and watch the object rebuild.
- the wait
- A shopper opens the app to plan the weekly shop and spends anywhere between five and forty minutes browsing. The app gives nothing back for that time.
- what gets assembled
- The week ahead read from the household calendar, a basket drafted against the usual brands and the dietary rules, and one approval to review — not thirty decisions.
- the boundary
- It can prepare a basket. It cannot buy, substitute or redeem. The retailer keeps the ledger and every consequential action.
- what gets measured
- Minutes returned per shopper per week, completion of the wait, basket-review rate, and zero unapproved actions.
Where does your customer already wait? What could be ready by the time they look? Who signs it off? And how would you know it worked? Answer those four and the journey is most of the way built — the industry only decides what gets prepared.
Working versions of these exist, prepared for named businesses and shared privately with the person they were written for. The versions here are stripped of every client name on purpose.