In the previous lesson, you assessed your organisation's readiness using the five-level maturity model. Now you need to know where to apply that readiness. Part 3 of this book is organised around seven enterprise deployment domains, and each one represents a specific type of expertise that is currently locked inside individual professionals. Understanding these domains tells you where the deployment opportunities are -- and which section to prioritise when you are ready to build.
These seven were not chosen to be comprehensive. They were chosen because they represent the clearest cases where three conditions converge: the domain expertise is highly specific, encoding that expertise is currently difficult, and the connector infrastructure exists to make production deployment practical. They are also the domains where professionals most consistently identify the same underlying problem: institutional knowledge that is valuable to the organisation but unavailable beyond the individual who holds it.
Before examining each domain individually, it is worth understanding what they share. Every organisation has knowledge that exists only in the heads of its most experienced people. When the senior analyst retires, when the lead counsel changes firms, when the top sales performer leaves -- the organisation loses not just a person but a body of judgment, pattern recognition, and contextual understanding that was never documented.
This is institutional knowledge lock-in. It is not a technology problem. It is a knowledge transfer problem. The analyst's understanding of which data sources to trust under which conditions. The lawyer's sense of which clause patterns are genuinely dangerous in which jurisdictions. The HR director's memory of which policy exceptions are routinely granted and why. None of this is written down. All of it is valuable.
The seven domains that follow are where this problem is most acute -- and where the deployment frameworks from this chapter can address it.
Domain
Section
Chapters
Core Expertise at Risk
Finance and Banking
II -- Office of the CFO
17--21
Analyst judgment on data trust, risk calibration, regulatory materiality, Shariah compliance, banking regulation
Sales, RevOps & Marketing
III -- The Growth Engine
22
Qualification heuristics, signal recognition, outreach personalisation, campaign optimisation
Supply Chain & Procurement
IV -- Product & Value Chain
23
Vendor judgment, three-way match expertise, logistics optimisation, demand forecasting
Product Management
IV -- Product & Value Chain
24
Discovery-to-delivery synthesis, roadmap prioritisation, user research pattern recognition
People & Organisational Operations
V -- People & Efficiency
25--27
Policy intent, exception logic, process documentation, institutional memory, cross-agent integration
Legal & Compliance
VI -- Legal & Compliance
28
Clause pattern recognition, jurisdictional risk assessment, contract lifecycle management
Innovation & Intrapreneurship
VII -- The Innovation Lab
29
Lean methodology judgment, hypothesis design, venture creation with AI acceleration
Five chapters -- the largest section in Part 3. The expertise at risk here is not the ability to run a financial model -- any competent analyst can do that. The expertise at risk is the senior analyst's understanding of which data sources to trust under which conditions, the banker's calibration for which risk signals actually predict credit events versus which are noise, and the CFO's judgment about which regulatory requirements are material versus which are compliance theatre.
Chapter 28 builds the foundational finance agent for FP&A and valuation. Chapter 29 extends it into intent-driven financial architecture -- agents that reason about strategic intent, not just data retrieval. Chapter 30 deploys across the full range of CA and CPA practice areas: audit, tax, advisory, and client service. Chapter 31 provides the most comprehensive treatment of Islamic finance AI in any curriculum -- 26 SKILL.md files across seven jurisdiction overlays covering Murabaha, Ijarah, Sukuk, Takaful, and Zakat. Chapter 32 addresses banking-specific regulation: IFRS 9 expected credit loss models, Basel III/IV capital adequacy, and AML/KYC financial crime prevention.
A new analyst joining a finance team can learn the tools in weeks. Learning which numbers to believe takes years.
Lead qualification, pipeline management, outreach personalisation, CRM data enrichment, and campaign performance analysis. The expertise at risk is the top performer's qualification logic: the signals, heuristics, and pattern recognitions that distinguish a prospect worth pursuing from one that will consume resources without converting. Every sales team has someone who "just knows" which leads are real. That knowledge is the deployment target.
Chapter 34 builds agents that scale this judgment across the entire go-to-market organisation -- from prospecting and ICP matching through pipeline forecasting to cross-channel campaign optimisation and revenue attribution.
End-to-end supply chain management -- from vendor selection and purchase order management to invoice reconciliation and logistics optimisation. The expertise at risk is the experienced procurement manager's understanding of which suppliers are reliable under which conditions, how to structure a three-way match for complex multi-line POs, and which demand signals from the sales pipeline actually predict inventory requirements versus which are noise.
Chapter 24 deploys agents across vendor management, automated RFQ processing, duty and compliance, and demand forecasting that integrates sales pipeline data with inventory planning.
Discovery to delivery -- from user research synthesis through feature specification to roadmap prioritisation and stakeholder communication. The expertise at risk is the senior product manager's ability to synthesise customer feedback, technical constraints, business priorities, and market signals into a coherent decision about what to build next. That synthesis is the most valuable thing a product manager does, and it is the hardest to transfer.
Chapter 25 builds agents that transform product management from reactive coordination into proactive strategic capability -- using frameworks like RICE and WSJF for priority scoring, automating user research thematic analysis, and generating sprint updates and release notes.
Three chapters covering the infrastructure that determines whether an organisation can execute consistently at scale. The expertise at risk spans three layers: the HR director's understanding of the intent behind policies and the exceptions routinely granted (Chapter 26), the operations leader's knowledge of which processes actually run the business versus which are documented but ignored (Chapter 27), and the integration layer that connects all domain agents into a coherent agentic office (Chapter 28).
When someone asks "Can I work from another country for three months?" the written policy says no. The experienced HR professional knows that the answer is actually "yes, if you follow this informal process that has worked for the last four cases." That gap between written policy and institutional practice is the knowledge at risk.
Chapter 28 is the integration chapter -- it connects the domain agents from Chapters 17 through 27 into a workplace AI layer that knows your organisation's people, projects, terminology, and priorities.
Contract lifecycle management, legal operations, regulatory compliance monitoring, jurisdiction-specific risk assessment, and IP protection. The expertise at risk is the experienced lawyer's understanding of which clause patterns are genuinely dangerous in which contexts. A standard non-compete clause might be enforceable in one jurisdiction and meaningless in another. A data processing agreement might be compliant in Europe and insufficient in California. The senior lawyer carries this jurisdictional map in their head.
Chapter 33 gives significant treatment to Legal Operations Agents -- the emerging practice of deploying AI specifically within legal department workflows. The governance principle in this domain is non-negotiable: certain decisions must always involve a qualified attorney regardless of how accurate an agent becomes.
The culmination of Part 3. Chapter 29 asks what happens when the capability to build, deploy, and govern domain-specific AI agents is applied not to optimising an existing enterprise, but to creating a new one. It combines Lean Startup methodology, Design Thinking, and Agile with AI-accelerated execution -- for both the intrapreneur within a large enterprise and the founder building from scratch.
The expertise at risk is the experienced venture builder's judgment about which hypotheses to test, which MVPs to build, and which market signals indicate a genuine opportunity versus a mirage. Chapter 29 draws on domain agents from across the entire curriculum and shows how an AI-native startup is structurally different from a traditional one.
Although each domain has unique expertise types, the deployment methodology is the same across all seven. Every domain deployment follows the same pattern:
This is why Part 3 can address seven different domains with a consistent framework. The expertise changes. The methodology does not.
Most professionals reading this chapter will recognise their work in one or two of these domains immediately. Some will find themselves at the intersection of multiple domains -- a compliance officer who also manages HR policy, a sales leader who also handles financial reporting, a product manager who also runs procurement processes.
If your work does not map neatly to any single domain, that is normal. The domain sections (Chapters 17--29) are designed to be read selectively. Read the section closest to your expertise first. The deployment patterns you learn there will transfer to any adjacent domain.
If your work falls entirely outside these seven domains, the frameworks still apply. The maturity model, the monetisation models, the platform comparison -- all of these are domain-agnostic. The seven domain sections simply provide the most detailed deployment guides for the domains where the infrastructure is most mature.
Use these prompts in Anthropic Cowork or your preferred AI assistant to explore these concepts further.
What you're learning: How to map your own professional expertise to the domain framework. The AI will help you identify knowledge you carry unconsciously -- the judgment calls and pattern recognitions you make automatically that a new colleague would take months to develop.
What you're learning: How to distinguish between domain-specific expertise types while recognising the common deployment methodology. This analysis builds your ability to evaluate any domain through the institutional knowledge lens.
Part 3 is organised around seven enterprise deployment domains chosen because they represent the clearest cases where domain expertise is both highly specific and currently difficult to encode, and where connector infrastructure makes production deployment practical. All seven domains share a single underlying problem: institutional knowledge lock-in -- valuable expertise held by individual professionals that is unavailable to the organisation as a whole.
📋Quick Reference
Access condensed key takeaways and quick reference notes for efficient review.
Free forever. No credit card required.
Ask