Optimizing the Enterprise in the AI-Native Era, Volume 3

Your platform needs 8.69% of your tables. The other 91% is a three-year project nobody can defend.

Ashgrove Group has 2,140 tables across eleven source systems. Its 68 priority decisions need 186 of them.

That single change of question — from "what data do we have?" to "what do our decisions need?" — is the largest cost lever in platform design, and everything in this book is downstream of it.

The number this book is written around

Ashgrove's platform costs $4.17 million a year and supports decisions worth $18.6 million. That is 22.40% of the value it enables — defensible, but not obviously so. This book answers the three questions that follow with arithmetic rather than argument: would buying it as a service cost less, which decisions cost more to support than they return, and how many more decisions must it carry before the ratio becomes comfortable.

What you will be able to do

• Reconcile the four tiers — DATA, INFORMATION, KNOWLEDGE, DECISION — with the seven build layers, once, so the whole organization stops arguing about which "layer three" it means
• Score sixteen capabilities against evidence rather than impression, and find that the groups scoring 1 are exactly the groups with no named owner
• Choose technology with a weighted matrix whose minimums eliminate, and discover when the choice is not a technology choice at all
• Answer buy versus build with all five costs, including the three that are borne by other teams and never appear on the slide
• Size the platform from decision volume: 5.2 cores where a data-volume rule of thumb says 237
• Allocate cost honestly — half of it is joint and always will be — and compute marginal and total cost per decision
• Secure a system where no component is breached and the composition still discloses
• Write exit criteria that a stage cannot be declared complete four times against

Every number was produced by running the code

Two runnable models and thirty-nine check chains bind every figure in this volume to a single data sheet. Two of those chains tie it to Volumes 1 and 2 — change the earlier company's revenue and this book fails immediately. The chains caught real errors during writing, and the book says which ones.

Reads on its own

Chapter 33 reproduces everything this volume depends on: the tier × layer map, the complete Ashgrove data sheet, and the four results from Volumes 1 and 2 that the platform arithmetic rests on.

Fourteen chapters, ten self-test questions each with explained answers. Five appendices including the capability matrix with a blank version to fill in for your own organization, and a 182-term glossary shared across the series.