Selected work
The problems we take on.
A cross-section of the work we do — the constraint that shaped each engagement, the decision that unlocked it, and what changed for the team that has to run the result.
Every case below is an illustrative example until our first client-approved studies are published. No client is named, and no figure is claimed.Ask what we can show you
Case studies
What a finished engagement looks like.
Newest first. Open a card for the long version.
Example Example One platform for a fleet of regional sites
Consolidated a set of country sites onto one publishing platform with shared components, so a campaign ships once instead of once per market.LogisticsExample An assistant that answers from the manual
A retrieval assistant grounded strictly in a support team's own documentation, where every answer links back to the paragraph it came from.Support toolingExample A pattern library two product teams could share
Replaced two diverging interface kits with one tokenised library and the documentation around it, so a new screen starts from agreed parts.Healthcare softwareExample A marketplace rebuilt around its sellers
Rewrote listing, search and payouts as separate services with clear contracts, so a seller's changes appear in the storefront without a nightly job.MarketplaceExample Field work that survives a lost signal
An offline-first job app for maintenance crews: work orders, photos and sign-off captured on site and reconciled the moment a connection returns.Field service
Questions
About the work on this page.
How we choose projects, what a written case study contains, and what to do when the one you need is not here yet.
How do you choose which work to take on?
We take work where the constraint is technical and the person who decides is reachable — a team that can answer in the same week we ask. The sector matters far less than that.
When a project needs a larger team than ours, or a specialism we do not have, we say so on the first call and, where we can, point you to someone who does.
What does a case study here contain?
The starting constraint, the decisions we made and why, the parts we built, and how the system was handed over. Screens and diagrams where they explain something a paragraph cannot.
No percentages and no growth curves: we publish outcomes a client has agreed to in writing, and until then we describe the work rather than score it.
Can we see work that is not published?
Often, yes. Some engagements stay under NDA, but we can usually walk you through the architecture, the repository layout and the handover documents on a call.
Tell us which of the four disciplines sits closest to your problem and we will bring the nearest example we are allowed to show.
Next step
Bring us the one that is actually hard.
Describe the constraint in plain language — the deadline, the system you cannot replace, the team you have. We will tell you honestly whether we are the right studio for it, and what the first two weeks would look like.