Everything in this series has been an argument. This is the checklist.
You can adopt every formula in Field Note No. 2 and still lose, if the actual budget conversation next quarter is still "how many tokens did we use." Metrics change what you can measure. Budgets change what gets funded. This note is about the second one — five steps, in order, closing the argument this series has been making since No. 1.
Freeze the vanity metric. Don't kill it.
Token count still matters for capacity planning — keep tracking it. Stop reporting it as a success metric in anything that reaches a budget conversation. The distinction is the whole move: measure it, don't lead with it.
Establish one real baseline
Pick a single pilot process and measure it properly, before automation touches it.
Route before you scale
Put a router in front of the pilot before expanding it to a second process.
Govern before you multiply
Vault the credentials, scope the approvals, wire the audit trail — before the second and third processes get added, not after the first incident.
Multiplying an ungoverned pattern multiplies its cost, not just its value.
Report outcome budgets next quarter
Take the four numbers and the dashboard shape below, and put them in front of finance instead of a token count — not as an experiment, as the actual budget ask.
Where this leaves you
Tokenmaxxing is dead. This is what replaces it, five steps at a time — not a slogan, an actual sequence a real architect can run, starting with whichever step your organization hasn't taken yet.