Start a build

Your next product, built by people who run their own.

We are a product studio. Strategy, architecture and engineering, with AI where it earns its place.

Who we are

A studio that ships, then stays to help you run it.

We take an idea to a running product with a small senior team, and nothing gets handed to a delivery layer on the way. Twenty five years of building software sits behind that, most of it carrying somebody else's name.

Two of the products are ours. They are how we know the work holds up, because we are the ones who get paged when it does not.

Built for ourselves

The same signature check, running in your browser.

The SolidHooks dashboard listing webhook deliveries, each row showing status, source, destination, connection, attempts, latency and response code.

Sign waitingVerify waiting

SolidHooks receives inbound webhooks, verifies the signature, stores the raw payload and retries until your endpoint acknowledges it. The line above is this page building an event of its own and putting it through the same HMAC-SHA256 check, in your browser, as you scroll.

The Flagship application sign-in screen: terminal ID, work email and password fields beside an aerial photograph of a stacked container yard.
flagship.africa

The other one moves steel.

Flagship automates bonded terminal operations: gate in and gate out, stacking, customs examinations, demurrage invoicing, waybills and payments. A container yard does not tolerate a bad deploy, which makes it a useful thing to build against.

Track record

Most of what we have built carries someone else's name.

Twenty five years of product work, and the majority of it belongs to the companies we built it for, under agreements that keep them off pages like this one. So here is the part we can show you, and the ground the rest of it covered.

Ours, in production

  • SolidHooks

    Inbound webhook infrastructure. Receives, verifies, stores and retries until your endpoint acknowledges it. 10,000 deliveries a month free, 8 attempts on paid plans, backoff from 5s, AES-256-GCM at rest.

  • Flagship

    Bonded terminal operations for African ports. Yard, customs, demurrage invoicing and payments.

  • Novatickets

    Ticketing for live events, built and run in house.

Where the rest of it lived

  • Logistics and bonded terminals
  • Ticketing and live events
  • Payments
  • Developer infrastructure
  • Developer education

If your sector is not on that list, it is usually still the same problem underneath: something that has to be correct every time, under load, without a person watching it.

Three commitments, and no account managers.

We start with the smallest version that could be real.
Not a prototype and not a deck. Something with a URL, a database behind it, and a person who can break it.
The people who design it are the people who build it.
A small senior team, working directly with you. Nothing is handed to a delivery layer, because that is where the intent gets lost.
We stay on after launch.
We run our own products in production, so we build yours the way something gets built when the person writing it is also the person who gets paged.
An open notebook and the edge of a keyboard under a single desk lamp at night.

Where AI belongs

Not every product needs a model, and the ones that do usually need less of one than the demo suggested. We work out what the model is actually for, what happens when it is wrong, what it costs at scale, and which parts stay deterministic. Then we build that. We also build with AI ourselves, which is part of how a team this size ships this much.

  • Product strategy and architecture
  • AI architecture and integration
  • Product engineering
  • Operations after launch

Bring us the one you cannot get built.

Start a build

Your delivery log is on the left.