A small team, a lot of agents, and a person on every decision that matters.

Example plan, not a quote
    1. 01

      Brief

      One conversation with you. We write the spec, and you approve it before anything is built.

      A person decides at this step.
    2. 02

      Build

      Agents work from the spec, each task on its own branch.

      Agents do this step.
    3. 03

      Test

      Tests, accessibility checks and screenshots run on every change.

      Agents do this step.
    4. 04

      Review

      Every pull request must pass CI. Security, payments, auth and data changes wait for a person.

      A person decides at this step.
    5. 05

      Ship

      You get the product, the repository and the evidence behind each claim.

      A person decides at this step.

    Five rules we hold ourselves to

    1. 01

      The spec comes first

      Each product starts from a written spec and a short list of principles. Agents build from the spec, and a change to the spec is a decision someone signs.

    2. 02

      Every repo tells agents how to work

      Instructions for coding agents live next to the code: how to run it, what never to touch, and which checks must pass before a pull request.

    3. 03

      “Shipped” needs evidence

      We separate “written”, “tested”, “merged” and “released”, and record evidence for each one: test runs, screenshots, receipts. When we got this wrong, we wrote down why.

    4. 04

      People keep the risky decisions

      Plans, destructive commands, payments, data models, auth and releases wait for a person. Routine changes merge once every check passes.

    5. 05

      Spend is visible

      Agent work has a cost estimate before it starts and caps per run, so a project budget stays a budget.

    What we do

    You work directly with the people who design and build your product. We use agents to go further, not to stay out of the room.

    Start a project