Starting the Conversation
In the previous lesson, you explored the seven professional domains where institutional knowledge is most at risk. Now the question becomes practical: how do you actually use everything you have learned in this chapter when you sit down with a potential client, an internal sponsor, or a sceptical colleague?
Every deployment begins with a conversation, and the quality of that conversation determines a great deal about what follows. The frameworks you have learned -- the two-platform landscape, the four monetisation models, the five maturity levels, the seven domain profiles -- are not abstractions. They are vocabulary. They give you precise language for discussions that would otherwise devolve into vague promises about "AI transformation."
Qualifying the Conversation
The most common mistake in enterprise AI conversations is proposing a solution before understanding the context. The maturity model from Lesson 6 is your qualification tool.
| Maturity Level | What They Need | What You Offer |
|---|---|---|
| Level 1 (Awareness) | Education | A briefing, not a proposal |
| Level 2 (Experimentation) | Direction | A pilot scope with clear success criteria |
| Level 3 (Integration) | Governance | A deployment plan with measurement framework |
| Level 4 (Optimisation) | Optimisation | Cross-functional coordination strategy |
| Level 5 (Transformation) | Partnership | Strategic advisory on competitive positioning |
A Level 1 organisation does not need a deployment proposal. They need someone to explain what domain agents are and why they matter. Presenting a technical architecture to a Level 1 audience is the fastest way to lose the conversation.
A Level 3 organisation does not need education. They have already run pilots. They need help scaling from departmental success to enterprise governance. Offering them an introductory briefing wastes their time and your credibility.
Qualification before proposal. Always.
Framing Value for the Stakeholder
Different stakeholders respond to different value framings. The monetisation models from Lesson 5 are not just pricing structures -- they are communication tools.
| Stakeholder | Framing That Resonates | Why |
|---|---|---|
| Sales leader | Success-fee economics | Aligned incentives -- they pay only when the agent delivers measurable results |
| HR director | Subscription with policy governance | Predictable cost, compliance assurance, institutional memory preservation |
| CFO | License with ROI projection | Capital expenditure framing, data sovereignty, total cost of ownership |
| IT leader | Platform comparison (Cowork vs Frontier) | Architecture fit, integration requirements, security model |
| CEO | Maturity model positioning | Strategic competitive advantage, organisational transformation roadmap |
The sales leader who hears "subscription pricing for an HR tool" will disengage. The same sales leader who hears "you pay 15% of the additional revenue the agent generates, nothing if it generates nothing" will lean forward. Same technology. Different conversation.
The Knowledge Question
Before you discuss platforms, before you select a monetisation model, before you identify the domain -- you need to answer one question with enough precision that everything else follows:
Whose expertise, encoded in what form, available to whom, operating under what constraints?
This is the knowledge question. It is the starting point for every deployment conversation, whether the deployment is internal or external. Break it down:
- Whose expertise? -- Which professional's institutional knowledge are you encoding? The senior analyst? The lead architect? The compliance officer?
- In what form? -- Agent instructions? Decision trees? Workflow automations? What structure captures the expertise most faithfully?
- Available to whom? -- The expert's immediate team? The entire department? External clients? The answer shapes governance requirements.
- Under what constraints? -- Regulatory boundaries? Data sensitivity? Domain-specific risk tolerances? The constraints determine the deployment model.
If you cannot answer these four sub-questions, you are not ready to discuss platforms, pricing, or architecture. The knowledge question comes first.
Putting It Together
A deployment conversation that uses these frameworks follows a natural sequence:
- Qualify -- Assess the organisation's maturity level. Determine what they need (education, direction, governance, optimisation, or partnership).
- Identify -- Ask the knowledge question. Whose expertise? In what form? For whom? Under what constraints?
- Frame -- Match the value proposition to the stakeholder. Use the monetisation model that resonates with their role and concerns.
- Position -- Place the deployment on the platform landscape. Cowork for team-level, knowledge-worker-led deployment. Frontier for enterprise-wide, executive-sponsored transformation.
- Scope -- Map to the appropriate domain profile. Use the domain sections (Chapters 17--29) as the deployment guide.
This sequence works whether you are proposing a deployment to your own organisation, pitching a consulting engagement, or evaluating a vendor's claims. The frameworks are the same. The conversation changes based on your role in it.
What Comes Next
Chapter 15 opens the blueprint. It describes what a Cowork plugin looks like from the inside -- the technical architecture that carries your expertise into enterprise operation. The strategic vocabulary you built in this chapter becomes the foundation for the practical deployment that follows.
Try With AI
Use these prompts in Anthropic Cowork or your preferred AI assistant to explore these concepts further.
Prompt 1: Personal Application
I need to have a conversation about deploying AI agents in my
organisation. Here is the context: [describe your organisation's
size, industry, current AI usage, and the stakeholder you would be
speaking with]. Using the five-level maturity model, what level is
my organisation at? What type of conversation should I prepare --
education, pilot proposal, governance plan, or something else?
What you're learning: How to apply the maturity model as a practical qualification tool. The AI will help you assess your specific organisational context and recommend the right conversation approach, preventing the common mistake of proposing solutions before understanding readiness.
Prompt 2: Framework Analysis
Compare how you would frame the value of a domain agent to a CFO
versus a sales leader. The domain is [choose: finance, sales &
marketing, supply chain, product management, people & operations,
legal & compliance, or innovation]. For each
stakeholder, identify: which monetisation model to lead with, what
metrics to highlight, and what objection to prepare for. Explain why
the same deployment requires different conversations.
What you're learning: How to adapt your communication strategy to different stakeholders using the monetisation models as framing tools. This exercise builds your ability to have the right conversation with the right person, rather than delivering a one-size-fits-all pitch.
Prompt 3: Domain Research
Walk me through answering the knowledge question for a specific
deployment scenario. The organisation is a mid-sized law firm with
50 lawyers. They want to improve contract review efficiency. Answer
each part: Whose expertise would you encode? In what form? Available
to whom? Under what constraints? Then explain how the answers to
these four questions determine the platform choice, monetisation
model, and deployment approach.
What you're learning: How to use the knowledge question as the foundation for every deployment decision. This exercise demonstrates that platform selection, pricing, and architecture all follow naturally from answering "whose expertise, in what form, for whom, under what constraints" with enough specificity.