Field notes

What it takes to put AI on the books.

Short pieces on the work itself: AI spend that doesn't reconcile, baselines nobody wrote down, attribution rules that decide the answer, and the arguments a finance team actually has about all three. Published as they're written.

More AI code isn't more product

AI coding tools add far more code than finished software, and the rest waits in review. What two studies show, and what to check before buying more seats.

The token is the wrong unit for AI ROI

Benefit doesn't arrive per token, so token cost against return isn't the ROI question. Why the initiative is the unit, and where token cost belongs.

Getting to AI ROI in six weeks

A week-by-week plan for answering 'what did the AI spend return?' before the board meets: what you can and can't prove in six weeks.

Keeping the record in a spreadsheet for now? Start from the free AI ROI tracker template, an Excel workbook laid out on the rules these pieces argue for.

Read these in a reader: subscribe to the RSS feed.