Two tiers, in order of weight. The platform work carries the most engineering and shows the least. The studies show everything and carry no client data.
Our strongest work is the work we cannot show. Ordering and operations platforms for quick-service restaurant and hospitality brands across the USA and Canada — high order volume, per-location complexity, and systems that are not allowed to stop.
An NDA can be arranged before a technical discussion. Under one, we can go through architecture, integration detail and specific problems directly.
A service that gathers data from many sources, makes it consistent, and hands it to other systems in a usable shape. A different continent and a different problem shape from the platform work — which is what shows it was not one lucky contract.
The work that proves the most is the work we are least able to publish.Why the order is this way
Below are studies we built ourselves, to show in the open how we think about problems we normally meet under contract. They are labelled conceptual because they are — no clients, no real data, no claimed results. Websites for local businesses are a separate, productised offer and live on the Digital Basics page.
The operator problem from the platform work, studied in the open: orders, products, inventory, integrations and system health in one view rather than five tools.
A mobile product study around a single number — a recovery score — and the evidence behind it: stages, duration, weekly trend and the two changes most likely to help.
What we draw on day one of a Day 1000 system: clients over a REST API, business logic and authentication behind it, a relational database of record, queues, and the external services every real system ends up depending on.
We would rather show less than claim more.On what we publish
