See It Work · Book 12 · The Agentic Enterprise · Chapter 10
The board cares about revenue, not tokens
The most common measurement mistake: using IT metrics (tokens, uptime) to justify a business transformation. The board cares about revenue, margin, risk, speed, and competitive position — not tokens. The fix is a seven-metric executive dashboard that connects agent activity to enterprise value, on one page, every quarter.
The full detailed chart. Condensed for print legibility in the book; shown here at full size.
Report tokens and latency to the board and you've described technology, not value — and the program looks like a cost center. Report business outcomes and it looks like what it is: a value engine worth funding.
Enterprise map · measuring valueready
What this means for you
A seven-metric, one-page dashboard reports business value, not IT metrics. What this means for you: your agent program reads as the value engine it is, not a cost center — because you put revenue, margin, and speed in front of the board instead of tokens and uptime, and that's what keeps it funded and growing.
Agent value reframed from IT metrics to enterprise value:
Measuring Value
the board cares aboutrevenue · margin · risk · speed
nottokens or uptime
the dashboardseven metrics, one page
cadenceevery quarter
Seven metrics, one page, every quarter — if you need forty slides, you are describing technology, not value.
For the technical reader — the command, and how to verify it yourself
# one line · you do not need to run this see walkthrough
see walkthrough # -> agent value measured in revenue, not tokens
Full step-by-step is in Appendix RX: Hands-On Demonstrations in the book.
ⓘDeterministic demonstration. The conversation is a faithful dramatization of the exercise; the receipt is the artifact it produces — the same every time, because the system is receipted. (Representative of the demo's structure; the production page renders the captured run.) No output here is fabricated. A live "run it yourself" mode is coming.