Evolve-or-Die.AI is structured as a single argument that compounds across twenty chapters. Part One establishes the landscape. Part Two builds the Leadership Intelligence Stack one intelligence at a time, then resolves who owns the operating system. Part Three applies the stack to the specific roles of the C-suite.
The pivot is Chapter 10. The first nine chapters build the six intelligences. Chapter 10 answers the question those chapters raise: if every leader must hold all six, who builds the system that lets them, and how does the whole C-suite develop the capability rather than concentrating it in one person. Everything after Chapter 10 is application.
In 1975 a Kodak engineer built the first digital camera. His managers understood exactly what it was, and chose not to release it. Kodak invented the technology that killed it. The pattern is not about technology. It is about operating models, and it repeats in every transition. Recognising where you stand is the first act of leadership.
Chapter 1. What the AI Era Is Actually Doing to Organisations
AI does not create structure. It amplifies the structure that already exists. The budgets are real, the intent is genuine, and the results are close to nothing, because the workflows are unchanged and the workforce is unprepared. AI compounds alignment where it exists, and fragmentation where it does not.
Chapter 2. Why This Disruption Is Different From Web and SaaS
For the internet and for SaaS, most organisations got away with absorbing the change into what they already did. For AI they will not. Every previous technology changed how information moved between people. AI changes who, or what, produces the information in the first place. That distinction changes everything.
Chapter 3. The Leader Who Will Not Survive This Transition
Every leader who reaches the C-suite does so by building a dominant style, and the organisation slowly reflects that style back at them. The agreement compounds. The blind spots compound. What the AI era exposes is the leader whose career was built on capabilities AI can now replicate.
Chapter 4. Human Intelligence: What Only You Can Bring
This is where the stack begins. Judgment under uncertainty, ethical reasoning, lived experience. The irreplaceable layer every other intelligence sits on, examined for what it actually requires of a leader once AI can replicate so much of the rest.
Chapter 5. Artificial Intelligence: What the System Brings
There is a difference between understanding AI and understanding what AI means for how you lead. The first is for specialists. The second is the leadership matter: how AI changes the flow of intelligence, the workforce, the risk architecture, and the geopolitical ground across US-led and China-led ecosystems.
Chapter 6. Orchestration Intelligence: Leading the Mixed Workforce
The newest discipline in the stack. It did not exist five years ago. Leading a team today is not leading humans who use tools. It is governing a mixed workforce of humans and agents: knowing which capabilities belong to which, and building workflows that combine both without losing accountability or human authority.
Chapter 7. Business Intelligence: When Numbers Move Faster
No organisation has ever had more data. The AI era did not create a data problem. It created an interpretation problem. Business Intelligence is a lagging indicator: it tells you what already happened. At AI-era pace, a business that looks healthy on today's dashboard can already be structurally compromised.
Chapter 8. Portfolio Intelligence: Products, Services, Competitive Intel
What to build, buy, bundle, or kill, when the competitive picture refreshes faster than the planning cycle. The discipline of holding a portfolio under a market that no longer waits for the annual review.
Chapter 9. Cultural Intelligence: The APAC Advantage
Cultural Intelligence is not an APAC skill. It is a universal leadership discipline the AI era has made more urgent, because AI scales cultural risk. The APAC vantage point is the credential: navigating cultures, geographies, and ownership structures from inside, not as a footnote.
Chapter 10. The Chief Intelligence Officer: Who Owns the Operating System
The pivot of the book. The quarterly review spends eighty per cent of its time on what already happened. If every leader must hold all six intelligences, who builds the architecture that lets them, and how does the whole C-suite develop the capability rather than concentrating it in one person.
Chapter 11. The Orchestrator Architecture: Leading Humans and Agents as One System
The orchestrator structure is already operating inside organisations that have deployed AI at scale, whether or not they have named it. The agent operates within boundaries the leader sets; the leader holds final accountability. Name it and govern it deliberately, or it compounds in the wrong direction.
Chapter 12. Orchestrating Intelligence Across the Organisation
How the Intelligent Leader connects intelligence across every function at once, by building the operating system rather than redrawing the org chart. The architecture of where intelligence lives and how it flows, learned by breaking it first: intelligence cannot live inside the agent that happens to use it first.
Chapter 13. Governing Intelligence You Did Not Build
Most of the intelligence an organisation runs on arrives from outside: licensed models, analyst data, third-party research you cannot audit from the inside. The defensive floor is keeping bad intelligence out. The ceiling most leaders never reach is deliberately importing adversarial intelligence as the error-correction layer your own system cannot provide.
Chapter 14. Market, Demand and Account Intelligence
Where the book turns from architecture to application, starting where the money and attention already sit: the go-to-market engine. Pipeline is the tip of the iceberg, the part above the waterline. The two thirds below is the intelligence that produced it, and most organisations have no visibility into it at all.
Chapter 15. Channel, Partner and Talent Intelligence
Why these functional intelligences sit below the universal six, and what happens to the go-to-market engine when they are fragmented, siloed, or absent. Coverage, capability, and the people, human and agent, who actually execute.
Chapter 16. The CEO: Governing the Intelligent Enterprise
The board listens politely, asks about this quarter's margins, and defers. Eighteen months later a competitor who invested is operating at a cost base you cannot match. The argument the CEO must be able to make clearly, specifically, and without apology, to a board that instinctively resists every long-cycle investment.
Chapter 17. The CMO: When AI Knows Your Customer
The stack applied to marketing, where AI now reads the customer faster and broader than any team. How the CMO stays the authoritative voice on the customer instead of being displaced by the data, the platform, or the tool that knows the buyer better than the brief ever captured.
Chapter 18. The CHRO, CFO, CIO and COO: Intelligence at the Operational Core
The four leaders at the operational core each optimise for their own function, their own metrics, their own commitments. Why that is rational, why it makes cross-functional transformation stall, and how the stack applies across all four without asking any of them to stop doing the job they were hired to do.
Chapter 19. Building the Intelligent Enterprise: A 90-Day Architecture
The strategy is approved and the roles are named. Then the first 90 days arrive and one question matters: what do we actually do tomorrow morning? The evidence-led sequence that separates transformation that compounds from transformation that collapses. The diagnostic comes first. Always.
Chapter 20. The Intelligent Leader: Building the Architecture
Gaudí did not optimise the building in front of him. He designed the one that needed to exist, then let it outlast him. The inversion the whole book has been building toward: the Intelligent Leader does not optimise what exists, they design what needs to exist, and build the architecture first.
Organisational intelligence is not a property of a framework or a model. It is a property of the institution's ability to maintain coherent judgment under structured disagreement about what the framework is telling it. The Afterword documents how the book was produced: human and artificial intelligence operating as a system to produce something neither could produce alone. Not a disclosure. A demonstration.