Every number we publish, and the command that reproduces it.

Fifteen figures. Each one names the client it belongs to, or names us, and each one carries the query, command or report that reproduces it. Four of them are things that went wrong, three of those four in our own work, and three more are live jobs that have not yet produced a number worth claiming. A page of only wins is an advertisement.

The three rules of this page

• Every row names who it belongs to. No “a leading contractor in the Mid-Atlantic” — if a client has not agreed to be named, the figure does not appear at all.
• Every row carries the thing that reproduces it: a query, a shell command, or the exact report and filter inside the client’s own system.
• The failures sit in the same list, in the same type, rather than in a footnote.

What is on it

Results for a named client, including $18,465 of approved roofing work that the client’s own CRM credited to the wrong channel, and 50 inbound leads arriving through 10 labelled doors that did not exist in June 2026. Invariants that hold on every deploy: 244 of 244 database tables forcing row-level security, 1,016 of 1,016 pages carrying a unique title and h1, 283 of 283 cold-email claims re-asserted against captured evidence. Defects caught, including 1,050 customer records readable by a sales rep through four reporting views that ignored row-level security, and 370 of our own pages failing WCAG 2.4.1 at Level A.

Including the one a client caught

On 2 September 2026 we published a figure stating a roofing client had produced three jobs from the internet in twenty-one years. It came from a lead-source column blank on 57.7% of their jobs and on 90.8% of their biggest year. The client caught it inside the hour, because the query was printed beside the number. It is on the ledger rather than quietly patched out.