Case studies
What we’ve built, and what kind of work it was.
Every case study is labelled for what it is. We never present a demo as a client, or a plan as a result.
All case studies
- Our own productRestaurants · shops · general tracking
VisionOps: what happens on the floor
One overhead camera and a small computer on site that turn a floor into data: how long each table, seat or display is in use, how many people pass through, and in a restaurant, when each table is seated, served and cleared. The video stays on site; only event data leaves.
- Edge vision engine
- Zone studio
- Table state machine
- Service dashboard
- Our own ventureDigital products · e-commerce
WovenQR and FormeQR
Two QR artwork brands where the pattern of the code itself forms a customer’s logo, initials or name. Both run on one generation engine we built, with separate storefronts, checkout and protected delivery.
- QR generation engine
- Two storefronts
- Checkout and delivery
- Marketplace service
- Worked example · made-up brandE-commerce
Alder and Fern: an online tea brand
A one-minute interactive walkthrough of a typical e-commerce build. A made-up tea brand goes from four tools that disagree, through the 7-day Diagnostic, to a joined-up pipeline with live dashboards, win-back lists and anomaly watch.
- Diagnostic findings
- Data pipeline
- Dashboards
- Win-back list
How we label our work
Four kinds of case study
- Our own venture
- Businesses we build and run ourselves, on the same tools and standards we use for clients.
- Our own product
- Products we design and build in-house, then install for clients. We say plainly how far along each one is.
- Worked example · made-up brand
- Builds on realistic, made-up data, so you can see exactly how a project works without anyone’s private figures.
- Client work
- Work for clients, published only with their written permission and only with results they have signed off.