Skip to main content

series · 6 essays

The AI Ledger

Enterprise AI has spent two years priced like a promotion, not a product. These six essays follow the money as that phase ends: what the subsidy actually covers, what the invoice looks like when it arrives, and what a team should measure once it does.

The essays build one ledger. The subsidy gets itemized first, from twenty-six days of real usage data, and then the industry-wide invoice arrives. The accounting discipline follows: count verified outcomes, not tokens or generated output. From there the argument turns practical. An afternoon of tooling makes the measurement automatic, owning the learning loop keeps you from paying for intelligence twice, and the closing essay asks where the saved hour actually goes.

Read them in order; each essay assumes the numbers from the one before it. The order is the argument's, not the calendar's, which is why The AI Operating Ledger sits third despite publishing first. That essay also closes The Agentic SDLC series. This is the thread that follows the money instead of the workflow.

reading order

The essays

  1. 01
    The Subsidy, Itemized
    10 min read

    The baseline: twenty-six days of Claude Code, $2,556 of API-priced work against a $200 subscription, and what the gap actually buys.

  2. 02
    The Agent Era Gets an Invoice
    12 min read

    The turn: Build, WWDC, and two confidential S-1 filings land in two weeks, and the agent becomes the interface just as the pricing gets real.

  3. 03
    The AI Operating Ledger
    11 min read

    The discipline: enterprise AI enters its accounting phase, and the winners measure verified outcomes, not generated output.

  4. 04
    The Instrument and the Ledger
    8 min read

    The instrument: the hand-built June ledger becomes an afternoon of tooling, built by the very thing it measures.

  5. 05
    Paying for Intelligence Twice
    9 min read

    The second invoice: AI workflows shed valuable learning exhaust, and owning the loop beats renting it back.

  6. 06
    Where the Saved Hour Goes
    13 min read

    The dividend: AI can hand engineers real time back, and history says unallocated capacity gets absorbed unless someone decides where it goes.

supporting reads

Around the spine