Case studies
Frustration. Pattern.
Solution. Outcome.
Every study follows the same four beats. Read them in any order. You'll start recognising your own business inside a few.
Feedback · Multi-site restaurant group
We replaced a £4,500-a-month feedback platform.
A central operations team relied on a guest feedback service costing roughly £4,500 a month, and it might have to go. A couple of people asked a simple question. Could we do something really lightweight with AI instead?
Integrations · Adventure centre
We found the staff were the integration layer.
Bookings lived in one system. The details were re-entered into another to build the group's programme, a third scheduled the team, and finance needed it all again for the invoice. Even adding a new user meant phoning support.
Integrations · Restaurant group finance
We stopped Finance being a human pipe between two systems.
Finance needed data from an old restaurant system to arrive in a new finance platform in a very particular form. The route involved too much handling, too much checking and too much chance for a tiny inconsistency to become somebody's afternoon.
Forecasting · Hospitality operations
We made a forecast less clever and far more useful.
An early forecasting engine hit around 11% MAPE. Engineering leaders were close to awe. A regional manager and a store user were completely confused.
Operations · Multi-site hospitality
One labour report became the foundation for five tools.
A modest labour deployment report answered one question. Were shifts staffed the way they were planned? It was filed away as finished.
Restraint · Restaurant group
Our best answer was not building anything.
A request came in for a site to let people check gift-card balances. Perfect little app territory, and satisfying to build.