Skip to content

From an idea to a shipped product, built with AI.

We build our own products this way, in the open. The same team, and the same way of working, is available for yours — from the first conversation to a product your customers use.

How it works

Four stages, and you can stop after any of them.

  1. DiscoverWhat the product is for, who it is for, and what the first version has to do. We come out of this with a scope you can say no to.
  2. Prototype, not startedA version you can click through in days rather than months, so the argument about what it should do happens against something real.
  3. Build, not startedThe production product, with tests and continuous integration, accessible and working on a phone from the first screen.
  4. Launch and hand over, not startedDeployed, documented, and yours: the code, the accounts and the deployment. No part of it stays locked to us.

What we have built this way

Our own products, in the open, with public code and public CI — so the claim is checkable rather than a reference we picked. The same way of working is what you get.

What you are left holding

The end of a project is a handover, not a dependency. This is what arrives.

  • A repository you own

    On your account from the first commit, with the history, the tests and the pipeline that built it.

  • A deployment that runs itself

    Continuous integration and a deploy on merge, so shipping a change is a pull request rather than an event.

  • Tests that mean something

    Not coverage for its own sake: the tests that would have caught the bugs we actually hit while building it.

  • Documentation for the next person

    How it is built, why it is built that way, and what to do when it breaks — written for whoever inherits it, including you.

  • Accessible and responsive from the start

    WCAG AA, working on a phone, in both light and dark. Retrofitting any of those costs more than doing them.

  • No lock to us

    Your accounts, your domains, your keys. If you never speak to us again, the product keeps running.

Who it is for

  • Founders with an idea and no engineering team yet.
  • Small teams who need a second product built without pausing the first.
  • People who know exactly what their industry needs and need it built.

Questions

Tell us about your idea

What you are trying to build, and who it is for. We will tell you what we would do first.

Start the conversation