Our work, in detail

Systems that businesses run on.

Five systems, and what each one changed. Client names are not published — most of this is internal software that runs somebody's operation, and that is not ours to advertise. What each one was, and how the work was arranged, is here.

Selected work

Our own venture

Venture platform product

A platform product we built and hold, taken from architecture through to production on our own account.

What changed
Built and held by us, to the same standard as any client build.

Client engineering

AI video management platform

Ingestion, storage and playback infrastructure for video, built to run continuously rather than to demonstrate.

What changed
Runs on the client's own premises, with no cloud dependency, and is owned outright by them.

Venture partnership

Business operating platform

Built with a founder who knew the industry: client records, automation and day-to-day operations in one system instead of four.

What changed
Four tools became one login.

Client engineering

Education program management

Programs, students and reporting for an education operator who had been running all three out of spreadsheets.

What changed
The spreadsheets were retired, and reporting came with it.

Client engineering

Healthcare compliance platform

A replacement for a legacy system in a setting where being audited is routine and losing a record is not an option.

What changed
A legacy system migrated rather than rewritten blind, with audit readiness as an architectural constraint.

How to read this

Three ways a thing here started.

A venture of our own is a company we built and hold. A venture partnership is co-built and co-owned with someone who brought the market. Client engineering is a system built for an existing business, paid for, and owned outright by them — we hold no stake in those and never ask to.

The category says how the work was arranged, not how carefully it was built. The standard is the same in all three, which is most of the point of arranging it this way at all.

Run one of ours

One of these is looking for someone to run it.

We build faster than we can take things to market. A venture that is built, works, and has nobody selling it is worth nothing — and that is a commercial problem, not an engineering one.

So we look for the other half: someone who can sell, hire and operate, coming in as a founder rather than an employee. You get equity, not a salary. We stay on as the technical side and keep building it. Which venture it is, and the state it is in, we will tell you in the first conversation rather than on a public page.

This is not a job posting and it is not for everyone. It suits someone who has run something before, knows a market well enough to have opinions about it, and would rather start with a working product than a deck.

You bring

  • Go-to-market — you know how this gets sold and to whom
  • The willingness to operate it day to day, not advise on it
  • Commercial judgement about pricing, positioning and who to hire first
  • A view on the market that you can argue for

You get

  • A founder's stake, agreed in writing before you start
  • A product that already exists and already works
  • Us as the permanent technical side, not a build and a handover
  • A say in what gets built next, because you are the one selling it

Which of these is you?

Whether you want something built, want to build one with us, or think you could run one of ours — the first conversation is the same, and a real engineer is on the other end of it.