Client deck · Slides 26–49

Client deck, Part 2: template

Slide 26 [Client name]: [use case name]

Slide text

AI control plane assessment readout. Replace every [bracketed prompt] and label illustrative numbers.

Prepared for [sponsor name, title] | Prepared by [lead architect] and [engagement lead] | [Month Year]

Speaker notes

Part 2 starts here. Build a copy of this section in your own deck for each client and use case. Each slide’s notes name the template in the guide that feeds it (T1 to T13). Leave this guidance out of the speaker notes in the deck you send to the client.

Slide 27 What this readout covers

Slide text

[Adjust to the time you have: 60 minutes covers all eight parts.]

1. The use case

Its goals, its scope and its stages

2. How the assessment ran

Six steps from discovery to a funded first phase

3. What discovery found

The assets the use case depends on

4. The value at stake

Business case and KPIs

5. What it must do

Requirements, security and autonomy by tier

6. Recommended architecture

North star, how it works, and its realization

7. A phased plan

Value at every milestone, quick wins first

8. Decisions

Owners and decisions for the next 90 days

Template.

Speaker notes

Template. Replace every bracketed prompt with the client’s content and label illustrative numbers. Keep the eight parts. Shorten any of them to fit the meeting.

Slide 28 [Use case] from [trigger] to [end state]

Slide text

[One sentence: who uses governed agents to do what, and the result for the business.]

THE CHALLENGE

[The chain of manual, risk-sensitive steps today, and what the delays and errors cost. Two or three sentences in the client’s own words.]

[Slow]

[How long it takes today]

[Costly]

[Cost or revenue lost]

[Risky]

[Compliance or safety exposure]

THE TARGET STATE

[Target state: the orchestrator and the specialist agents, the systems they reach, and the decisions people keep. The control plane makes every step governed, observable and auditable.]

SCOPE

TRIGGER

[Event that starts the process]

END STATE

[What is true when it is done]

USERS

[User groups]

SYSTEMS OF RECORD

[Systems the process runs on]

OUT OF SCOPE

[What this assessment excludes]

Template: fill from T1 (use case at a glance).

Speaker notes

Template. Replace every bracketed prompt with the client’s content and label illustrative numbers. Fill from template T1. Use the client’s own words for the challenge, and keep the target state to what people keep and what agents do.

Slide 29 Six steps from discovery to a funded first phase

Slide text

Each step produces a template in the assessment toolkit and a part of this readout.

STEP 1

Frame

Which use case, which goals, how much value?

Choose one priority use case, agree its goals and scope, and write the value hypothesis.

Templates T1, T2

STEP 2

Discover

What exists today, and how well does it perform?

Inventory the applications, data, integrations, agents, models, identities, policies and infrastructure the use case touches, and baseline its KPIs.

Templates T3, T6

STEP 3

Define

What must be true for it to work, safely?

Capture business, functional, data, integration, non-functional and operational requirements, and the security and compliance controls for every layer.

Templates T4, T5

STEP 4

Design

What does good look like, and how is it realized?

Draw the vendor-neutral north star for the use case, tell a day in the life, trace how the components work together, then realize it with MuleSoft Agent Fabric and Informatica.

Templates T7, T8, T9, T10

STEP 5

Phase

How does value arrive at every milestone?

Sequence the use case with the four phases of the plan, quick wins first, and put KPIs, ROI and business value on every milestone.

Templates T11

STEP 6

Decide

What should the client decide?

Present the findings and the plan, agree who owns what once the agents are live, secure the decisions for the first 90 days, and log risks, assumptions and next steps.

Templates T12, T13

WORKSHOPS

Executive framing

Process and systems

AI estate inventory

Data and master data

Requirements and security

Architecture

Value and phasing

Readout

FIVE WEEKS [Week 0: prepare • week 1: frame • weeks 1–3: discover • week 3: define and design • week 4: phase • week 5: decide]

Illustrative plan. Compress or stretch it to the client’s pace. Templates T1 to T13 are in the guide Assessing an AI Control Plane Project.

Speaker notes

Template. Replace every bracketed prompt with the client’s content and label illustrative numbers. Keep the six steps. Replace the week plan with the dates you actually ran and the workshops you held.

Slide 30 What [the process] depends on today

Slide text

[One sentence on how discovery ran.] The full inventory is in the assessment report (templates T3a to T3h).

[#]

systems of record

[#]

agents: [orchestrator and specialists]

[#]

models, routed by policy

[#]

MCP tools to publish

[#]

master data domains

[#]

policies and controls to enforce

[Finding 1: headline]

[Evidence: what discovery showed, where and how often.]

[Finding 2: headline]

[Evidence.]

[Finding 3: the AI estate today]

[Agents, models, gateway, registry, cost visibility.]

[Finding 4: headline]

[Evidence.]

Template: fill from T3 (asset inventory) and the discovery workshops.

Speaker notes

Template. Replace every bracketed prompt with the client’s content and label illustrative numbers. Fill the counts from the asset inventory (T3a to T3h). Keep four findings, each with evidence the client will recognize. One should describe the AI estate today (registry, gateway, cost visibility, agent quality).

Slide 31 Every asset the use case touches, by layer

Slide text

[From the asset inventory: what exists, what must be built, and what each agent may reach.]

SYSTEMS OF RECORD

[System 1]
[role • phase]

[System 2]
[role • phase]

[System 3]
[role • phase]

[System 4]
[role • phase]

[System 5]
[role • phase]

[System 6]
[role • phase]

MASTER DATA

[Domain 1]
[golden record • issues]

[Domain 2]
[golden record • issues]

[Domain 3]
[golden record • issues]

[Reference data]
[source]

[Sensitive data]
[handling]

MCP TOOLS & APIs

[tool_1 • tool_2]
[system • scope]

[tool_3]
[system • scope]

[tool_4]
[system • scope]

[tool_5]
[system • scope]

[tool_6]
[system • gated write]

AGENTS & TIERS

[Orchestrator]
[Tier • role]

[Agent 1]
[Tier • mode]

[Agent 2]
[Tier • mode]

[Agent 3]
[Tier • mode]

[Agent 4]
[Tier • mode]

[Agent 5]
[Tier • mode]

MODELS

[Frontier LLM]
[tasks • terms]

[Failover LLM]
[provider]

[Small model]
[hosting]

[Embeddings]
[endpoint]

Routing policy
[rule]

POLICIES & CONTROLS

[Write gate]
[conditions]

[Content rule]
[routing]

[Authorization rule]
[check]

[Data rule]
[models • regions]

PII masked
before every prompt

[Cost limit]
[per outcome]

Template: fill from T3a to T3h.

Speaker notes

Template. Replace every bracketed prompt with the client’s content and label illustrative numbers. One chip per asset, with its role and the phase in which it is needed. Keep six columns; the colors match the architecture slides (systems of record grey, data green, tools teal, agents blue, models violet, policies orange).

Slide 32 Each stage of [the process] and the systems it touches

Slide text

STAGE

PEOPLE

AGENT

CONTROL PLANE

MCP / API

SYSTEM OF RECORD

OUTCOME

[Stage 1]

[Human step]

[Agent 1]
[Tier • mode]

[MCP tool / API]

[System of record]

[Stage 2]

No human step

[Agent 2]
[Tier • mode]

[MCP tool / API]

[System of record]

[Stage 3]

[Human step]

[Agent 3]
[Tier • mode]

[MCP tool / API]

[System of record]

[Stage 4]

No human step

[Agent 4]
[Tier • mode]

[MCP tool / API]

[System of record]

[Stage 5]

[Human step]

[Agent 5]
[Tier • mode]

[MCP tool / API]

[System of record]

[Stage 6]

No human step

[Agent 6]
[Tier • mode]

[MCP tool / API]

[System of record]

Enterprise AI control plane: registry • AI gateway (LLM, MCP, A2A) • policy • agent identity • evaluation • cost • observability

[Outcome: from X to Y, with people keeping every accountable decision]

Template: fill from T1. Amber = human decision. Blue = agent and autonomy tier. Every call passes through the control plane.

Speaker notes

Template. Replace every bracketed prompt with the client’s content and label illustrative numbers. Fill from template T1 (stages). For each stage give the human step (or none), the agent and its tier, the MCP tool or API, and the system of record. Delete a stage if the process has five.

Slide 33 Expected business outcomes and KPIs

Slide text

[Illustrative for a client with [volume] a year. Replace with the client’s own baseline during discovery.]

EXPECTED BUSINESS OUTCOMES

[Capacity released]

[How the solution delivers it]

$[X]M

[volume × unit × value]

[Revenue protected]

[How the solution delivers it]

$[X]M

[volume × unit × value]

[Utilization]

[How the solution delivers it]

$[X]M

[volume × unit × value]

[Cost or risk avoided]

[How the solution delivers it]

$[X]M

[volume × unit × value]

[~$X a year released or protected, before platform, model and change costs]

KEY PERFORMANCE INDICATORS

KPI	Baseline*	Target (12 months)
[KPI 1]	[Baseline]	[Target]
[KPI 2]	[Baseline]	[Target]
[KPI 3]	[Baseline]	[Target]
[KPI 4]	[Baseline]	[Target]
[KPI 5]	[Baseline]	[Target]
[KPI 6]	[Baseline]	[Target]
Agent evaluation pass rate	[Baseline]	[Target]
Governed AI traffic	Not measured	100%
AI cost per [outcome]	Not measured	Within target

*Baselines and values are illustrative until measured during discovery.

Speaker notes

Template. Replace every bracketed prompt with the client’s content and label illustrative numbers. Fill from templates T2 (business case) and T6 (KPIs). Show the formula under each value so finance can check it. Keep the three control-plane KPIs at the bottom of the table.

Slide 34 Requirements that shape the design

Slide text

[Number] requirements in the register (template T4). These are the ones the architecture turns on.

Business

[BR-01] [Requirement that shapes the architecture]
[Must • phase]

[BR-02] [Requirement that shapes the architecture]
[Must • phase]

[BR-03] [Requirement that shapes the architecture]
[Must • phase]

[BR-04] [Requirement that shapes the architecture]
[Must • phase]

Functional

[FR-01] [Requirement that shapes the architecture]
[Must • phase]

[FR-02] [Requirement that shapes the architecture]
[Must • phase]

[FR-03] [Requirement that shapes the architecture]
[Must • phase]

[FR-04] [Requirement that shapes the architecture]
[Must • phase]

Data & integration

[DR-01] [Requirement that shapes the architecture]
[Must • phase]

[DR-02] [Requirement that shapes the architecture]
[Must • phase]

[DR-03] [Requirement that shapes the architecture]
[Must • phase]

[DR-04] [Requirement that shapes the architecture]
[Must • phase]

Operations

[OR-01] [Requirement that shapes the architecture]
[Must • phase]

[OR-02] [Requirement that shapes the architecture]
[Must • phase]

[OR-03] [Requirement that shapes the architecture]
[Must • phase]

[OR-04] [Requirement that shapes the architecture]
[Must • phase]

Template: fill from T4.

Speaker notes

Template. Replace every bracketed prompt with the client’s content and label illustrative numbers. Pick the four requirements per column that most shape the architecture. Each keeps its ID, priority and phase from the register.

Slide 35 Security at every layer, autonomy by tier

Slide text

Zero-trust controls on every call,⁹⁰ and a tier for every agent that sets how much it may do on its own: earned on evidence, and lowered automatically when something goes wrong.

Users