How we work

How a build works, and where you can stop it

If it isn't worth building, we'll tell you before you spend anything. If off-the-shelf software already does the job, you hear that in the first half hour.

How a build runs

Four gates, and you hold the exit at every one

  1. 1Scoping callCosts nothing
  2. 2See it workingBefore more money moves
  3. 3Stop anywhereKeep everything
  4. 4We stay if you want usCancel any time
Every stage is a priced stopping point, and what it produced is yours.
Fixed price in writing before work startsYour effort quoted up front, in hoursFixed quote for a catalogue tool: same or next dayCare plans optional, priced on the catalogue

The AI, plainly

Where AI does the work, and where it never does

AI does the production. Senior people spend their hours on the judgement. That's why the prices on this site look the way they do.

How the work is produced

The split

Stated plainly
The measurement, and the first draftsAI, senior-directed
The production work of a build: code, assembly, testsAI, senior-directed
What to build, and whether it is worth buildingA principal
The price and the scope you signA principal, in writing
Every line that shipsA named human accountable
Model training on your dataNever

If a firm won't tell you which of its work is human, ask why.

Data and security

Built by security people, which shows in the boring places

Access is least-privilege, revoked at the end of the engagement rather than when somebody remembers. Nobody buys on this. It matters on the day something goes wrong.

What this means in practice

Where your data sitsNamed in your quote, per project
Model training on your dataNever
Access modelLeast privilege
Access after handoverRevoked
File transferSecure share
Ownership of code and dataYours, in writing