How work gets delivered here, in nine promises you can check.

Nine commitments about how work gets delivered here. Not a diagram with four arrows in it: promises specific enough that you can tell, at the end, whether each one was kept — which is the only reason to publish a process at all. Each carries what it is for, and how you check it.

The nine

• You get the diagnosis before you get the invoice — we read your books first, and you keep the findings whether or not you hire us.
• Something is in production in the first two weeks. Not a mockup: a thing handling real traffic or real calls.
• 21 days from access, not from signature. Miss it on anything unflagged at kickoff and the build fee comes back.
• No big reveals. You see it weekly, including the weeks it is ugly.
• Every claim we publish for you has a test behind it. If the site says 24/7, something must answer at 3am.
• Access is enforced at the data, not in the screens. Ask us to impersonate a low-privilege user in front of you.
• You own it — repository, database, prompts, evals, domains and every third-party account in your name.
• The numbers we report are ones you can re-run, with the query printed beside them.
• We tell you when the answer is not us, and do not quote for it.

The one we have broken

Commitment eight, on 2 September 2026, against our own flagship client: we published a figure that read a blank database field as a zero. The client caught it inside the hour, because the query was printed next to the number. That is commitment eight doing the only job it has, and the correction is on the outcomes ledger and the case study rather than quietly patched out.