Capabilities

What we actually build

We are a small studio that ships production software. The work below is live and in daily use. Client names and product names are omitted on purpose — that discretion is part of what clients engage us for, and it is written into our Terms of Engagement.

Media pipelines

Systems that move large media files from the person who shot them to the place they are published, with the approvals in between. We build these on a strict no-proxy rule: bytes travel from the client device straight to storage, and the backend only brokers permission — it never touches the file itself. That keeps cost flat as volume grows and removes an entire class of failure. Delivered as an Android uploader plus a web workflow app over Google Drive, with an object-storage fallback.

Client portals and billing

Request intake, project tracking and invoicing in one portal, with a live payment gateway behind it and an admin side for the team running the work. Built on managed Postgres and object storage, deployed continuously, with the payment integration tested against real transactions rather than sandbox stubs.

Learning platforms

Curriculum-bound tutoring systems for schools — a chat tutor that answers within the syllabus and declines everything outside it, a scrolling study feed, and practice sets. The interesting engineering is the guardrail: an offline evaluation harness scores each change against a labelled dataset before it ships, and model routing is switched over the air per grade, so quality and cost can be tuned without shipping a new app build.

Records and document systems

Optical character recognition, classification and question-answering over large document archives — the kind of work where an institution has thousands of scanned pages and no index. Built to run locally when the material is sensitive enough that it should not leave the building.

Integration coordination

Where a client already owns the product and needs someone to hold the integration together, we act as specialised coordinator for their integration module — owning the interface contracts, the release gates and the handover between the teams either side of it, and staying reachable for support once it is live. This is a named, ongoing role rather than a project with an end date. Enquiries for this work come through the Contact page like any other.

How we work

Specification first, then a written plan, then implementation gated by tests — with a code review before anything reaches a client's production environment. Every engagement is scoped and quoted individually; we do not publish a rate card, because the honest number depends on the work. Ask us and you will get a written proposal.