What shipped, what broke, what it cost.

A working log rather than a newsletter. Entries record what shipped, what failed in production and why, which customer conversation changed a decision, and the numbers attached. It is written for the reader who wants the unedited version of how an AI agency actually operates week to week.

What goes in an entry

• The change that shipped, and the reason it was prioritised over the alternatives.
• Production incidents, with the root cause rather than a euphemism.
• Revenue and pipeline movement, stated as numbers.
• A decision that was reversed, and what the reversal cost.

Why publish the failures

A log that only records wins is marketing wearing a diary's clothes, and it is useless to the operators reading it for pattern-matching. The failures are where the reusable lesson is: the eval case nobody thought of, the integration that silently stopped syncing, the pricing experiment that lost trust faster than it gained margin.

Cadence

Written weekly, published without editing passes. Anything genuinely confidential to a customer is either omitted or anonymised to the point where the lesson survives and the identity does not. Where a number is estimated rather than measured, the entry says estimated.