Selected work

Custom software case studies you can open and use

Most of our work sits under NDA, so instead of a wall of logos here are two products written up whole — a two-sided marketplace where the payment is held between both sides, and a platform running made-to-order production. Each one says what the business problem was, what was genuinely hard inside it, what it cost and how long it took. Then it hands you a demo to open on sample data.

2
products we can show whole, start to finish
2
of them open as a demo you can use right now
19
engineering problems written up, not glossed over
Two-sided marketplace app · Creator economy

Marketplaces where the money sits in the middle

A marketplace with two sides, a payment held between them, and an AI studio that bills by the generation. The hard part is never the catalogue — it is deciding, in code, the exact moment money and files change hands.

What was hard

  • The order is a state machine, and money is one of the states
  • The payment provider is the source of truth, not the phone
  • Delivered work has to be worthless until it is paid for
4 months
from kickoff to a working product
173
end-to-end tests, 24 suites
21
data models behind it
  • NestJS 11
  • Prisma 7
  • PostgreSQL
  • Flutter
  • React 19
  • Socket.IO
  • FFmpeg
Read the caseLive demo inside

Walk a deal from the first message to a delivered file, on sample data.

Creator feed in the marketplace app, with an order button
Made-to-order production platform · Medical manufacturing

Operations platforms where every order is one of one

Made-to-order production has no catalogue and no reorder button. Every item is built for one person from measurements a computer takes off a scan, and the system has to hold that thread from the first appointment through manufacturing, delivery, and the remake eighteen months later.

What was hard

  • The record has to be a photograph, not a mirror
  • Work does not stop because the network did
  • Access is not a role, it is a scope
8 months
and still building — the largest system we run
13
flow families, from intake to remake
2,053
automated checks across its three repositories
  • React
  • TypeScript
  • PostgreSQL
  • Offline-first sync
  • Computer vision
  • TWAIN scanners (Plustek A320L and others)
  • Scope-based access
Read the caseLive demo inside

Sign in and run an assessment end to end — survey, scan, markup — on sample data.

Order board in the operations platform, with production stages

And everything we cannot show

Most of what we build belongs to somebody else and stays behind their name. That is the honest reason this page is short rather than a grid of logos — and the reason the two products here are ours, so we can open them all the way up. If your project is closer to something we cannot publish, ask on a call: we will say what we did, in what shape, and where the line is.

Tell us what you are building

What building one of these costs

Every price on this site is for a named scope with a result, not an hourly rate — so the number does not move while we work. Pick the one closest to what you need and the page will tell you what is included and, more usefully, what is not.

What people ask before asking for a case study

The awkward ones, answered plainly.

Both cases are products we built and still run, which is exactly why we can open them all the way up — the demos, the numbers, the parts that went wrong. Client work is the majority of what we do and almost all of it sits under NDA, so it cannot appear here in any honest form.

The class of problem, the engineering decisions and the anonymised numbers — which is what these two write-ups are. On a call we can go a good deal further verbally about work we cannot publish, and we will say plainly where the line is rather than hinting.

Not the client repositories, for the same reason you would not want us showing yours. What we can do is walk you through a suite of tests on a call, or write you a small piece of the thing you are asking for as a paid first step — which tells you more about how we work than any repository tour would.

Closer in shape than in industry. If money moves between two parties, if records must stay true years later, if people work where the network does not reach — that is the same problem wearing different clothes. If your product is a game, a trading engine or anything where frame rate or microseconds decide, we will tell you it is not our trade.

Yes. Both demos open in the browser on sample data with no sign-up, no form and nothing to install. Break them if you can — that tells you more than a slide would.