TermModels & systemsAgentSoftware that can plan and take multi-step actions toward a goal, not only answer a question.Why CEOs care. An agent can change a record, move money, or write to a customer. Residual risk is operational, not editorial.
TermRisk & controlControl planeThe layer that decides which agents may act, on which systems, with what logs and kill-switch.Why CEOs care. This is how a board sees residual risk on software that acts. Without it, agent spend is unsupervised privileged access.
TermRisk & controlResidual riskThe risk that remains after controls — the number the board actually carries.Why CEOs care. Perfect safety is not on offer. The artefact is an accepted residual, with an owner, not a promise of zero incidents.
TermStrategy & capitalDual P&LOne page that shows AI cost takeout and AI revenue lift together, with residual risk noted.Why CEOs care. Spend is visible. Combined proof is not. Boards are starting to ask for both on the same page.
TermModels & systemsRAGRetrieval-augmented generation — the model is grounded in your documents at answer time.Why CEOs care. It is the usual pattern for ‘chat with our knowledge’. It reduces some hallucination; it does not create a system of record.
TermModels & systemsHallucinationA fluent answer that is not true, or not in the sources the system was given.Why CEOs care. Fluent error is more dangerous than an empty answer. High-stakes workflows need evaluation and a human gate, not a disclaimer.
TermPeople & operating modelRPARobotic process automation — scripted clicks on existing systems. Not an agent.Why CEOs care. Many ‘AI’ business cases are still RPA with a new label. RPA is brittle; agents are unsupervised if you let them be.
TermAPAC & policySovereign stackModels, cloud, and data that a jurisdiction can inspect, host, or refuse to let leave.Why CEOs care. In APAC this is a market-access question: China, and increasingly parts of ASEAN and the Gulf, will not share a single US-cloud stack.
TermModels & systemsFoundation modelA general model trained at scale, then adapted. The raw material, not the product.Why CEOs care. You rarely compete on training the base model. You compete on data, workflow, and control of how it is used.
TermModels & systemsFine-tuneFurther training of a model on your data so it behaves more like your domain.Why CEOs care. Expensive, easy to over-claim, and often beaten by good retrieval plus evaluation. Ask what residual risk it actually removes.
TermRisk & controlEvaluation (eval)A measured test of whether the system does the job — not a demo.Why CEOs care. Without evals, ‘it works’ is a vendor story. Evals are how residual risk is measured over time.
TermRisk & controlModel cardA short document of what a model is for, what it was trained on, and how it was tested.Why CEOs care. Becoming the nutrition label in procurement. Absence is itself a residual-risk signal.
TermRisk & controlRed teamAn adversarial test that tries to make the system fail, leak, or disobey policy.Why CEOs care. The adult version of ‘we tried it’. Buyers and AISI-style regimes expect evidence, not a slide.
TermModels & systemsGroundingForcing the answer to stay attached to retrieved or authorised sources.Why CEOs care. Grounding reduces some hallucination. It does not make the model a database, and it fails if the corpus is wrong.
TermModels & systemsContext windowHow much text (and now other media) the model can see at once.Why CEOs care. A bigger window is not a memory strategy. Cost and error rates still rise with dumped documents.
TermStrategy & capitalTokensThe units models read and write. The usual billable atom of inference.Why CEOs care. For agents, tokens per completed workflow is the TCO line, not tokens in the abstract.
TermStrategy & capitalInferenceRunning a trained model to produce an output. This is most of the bill after the pilot.Why CEOs care. Training headlines are rare. Inference is the operating cost. Agents multiply it.
TermData & infrastructureLatencyHow long the system takes to answer or to finish a step.Why CEOs care. Customer and trading workflows die on latency. A cheaper model that is late is not cheaper.
TermRisk & controlSLOService-level objective — the reliability bar you actually run to.Why CEOs care. AI features that miss the SLO of the host product (banking app, claims, trading) will be turned off, whatever the demo.
TermPeople & operating modelHuman in the loopA person must approve before the system acts — or after, depending on the design.Why CEOs care. A slogan unless you specify which actions, which people, and what happens when they are slow or wrong.
TermRisk & controlKill-switchA way to stop an agent or a class of agents immediately, without a release cycle.Why CEOs care. If you cannot stop it, you do not control it. Boards already understand this sentence from cyber and trading.
TermPeople & operating modelShadow AIStaff using public models with company data outside the official stack.Why CEOs care. The residual-risk you are not shown. Ban-only strategies usually fail; a sanctioned path plus monitoring is the adult version.
TermRisk & controlModel riskThe banking discipline for models that affect money, capital, or customers — now colliding with generative AI.Why CEOs care. Regulated groups already have a model-risk function. Generative and agentic systems often sit outside it. That gap is the story.
TermStrategy & capitalTCO (AI)Total cost of ownership: licences, inference, integration, evaluation, control plane, and people.Why CEOs care. Seat prices are the smallest line. Agents make inference and integration the real bill.
TermStrategy & capitalVendor mixThe deliberate use of more than one model and cloud, including a China or sovereign option where needed.Why CEOs care. Single-stack convenience is a concentration risk. APAC groups often need two stacks whether they want them or not.
TermAPAC & policyLicence to operateThe informal permission from regulators, buyers, insurers, and the public to keep using AI in the business.Why CEOs care. Lost faster than it is won. Policy is now a product constraint because counterparties will not wait for your home statute.
TermModels & systemsMixture of experts (MoE)A model architecture that routes each token to a subset of specialists, rather than activating every parameter.Why CEOs care. It changes the TCO story: more total parameters, less compute per token — if the serving stack can actually route.
TermModels & systemsDistillationTraining a smaller model to imitate a larger one.Why CEOs care. The usual path from a frontier demo to a cost the line will accept.
TermModels & systemsSmall language model (SLM)A compact model, often specialised, that can run closer to the data.Why CEOs care. On-prem, sovereign, and edge cases in APAC often need an SLM, not another frontier API.
TermModels & systemsMultimodalA system that reads or writes more than text — images, audio, video, documents.Why CEOs care. Claims, KYC, manufacturing, and clinical workflows are multimodal whether the vendor slide says so or not.
TermData & infrastructureEmbeddingsNumeric representations of text or images that make similarity searchable.Why CEOs care. This is the index behind ‘chat with our knowledge’. It is also a copy of your corpus in another form.
TermData & infrastructureVector databaseA store built to retrieve embeddings by similarity.Why CEOs care. Brand of database is secondary. Access control and freshness are the CEO questions.
TermData & infrastructureMCP (Model Context Protocol)A standard way for models and agents to connect to tools and data sources.Why CEOs care. A common plug is useful. An open plug without a control plane is a new attack surface.
TermModels & systemsTool useThe model calling an external function — mail, ERP, browser, payments — as a step in its plan.Why CEOs care. This is the line between answering and acting. Residual risk sits on the tool, not the paragraph.
TermData & infrastructureOrchestrationThe layer that sequences model calls, tools, and human steps into a workflow.Why CEOs care. This is where TCO, latency, and residual risk actually live — not in the model card.
TermStrategy & capitalModel routingSending each request to the cheapest or best-fit model that can do the job.Why CEOs care. The practical hedge against vendor mix and inference TCO.
TermRisk & controlGuardrailsFilters and policies that constrain what a model may take in or put out.Why CEOs care. Necessary, not sufficient. Guardrails without tool-gating will not stop an agent that can act.
TermRisk & controlPrompt injectionUntrusted text that instructs the model to ignore you and use its tools.Why CEOs care. Any agent that reads email, tickets, or the web can be instructed by that content.
TermRisk & controlObservability (AI)The ability to see traces, costs, evals, and incidents across model and agent runs.Why CEOs care. If you cannot see it, you cannot carry residual risk. The board will ask after the first incident.
TermAPAC & policyData residencyWhere data, embeddings, and logs are allowed to live — and who can compel access.Why CEOs care. In APAC this is often the binding constraint on a single regional product.
TermAPAC & policyData localisationA legal requirement that certain data not leave a jurisdiction.Why CEOs care. China, Indonesia, Vietnam, India and others already force product SKUs, not language packs.
TermData & infrastructureSynthetic dataData generated by a model to train or test another system.Why CEOs care. Useful when real data is scarce or sensitive. Dangerous when it quietly replaces ground truth.
TermModels & systemsRLHFReinforcement learning from human feedback — how many frontier models are steered toward preferred answers.Why CEOs care. It explains tone and refusal. It does not create a system of record or a control plane.
TermPeople & operating modelCopilot vs agentA copilot drafts; an agent acts. Do not fund one with the other’s risk language.Why CEOs care. Seat rollouts are copilots. Production workflows that change records are agents.
TermStrategy & capitalComplementary investmentThe process, data, and people spend without which model spend does not return.Why CEOs care. This is why Trailblazers out-earn Followers at the same model price.
TermStrategy & capitalSwitching costWhat it would take to leave a model, cloud, or copilot — data, prompts, evals, habit.Why CEOs care. Concentration is residual risk. Vendor mix is the hedge.
GuideConceptsPwC Global CEO Survey — value, workforce, confidenceHow peer chief executives describe AI value versus what they can show.
GuideConceptsTrailblazer versus FollowerBCG’s split is now a capital-allocation lens, not a culture slogan.
GuideConceptsThe agentic era, at CEO altitudeSoftware that acts, not software that answers. Trust becomes architecture.
GuideConceptsWhy evaluation is a management systemDemos do not Measure. Residual risk is unmeasured without evals.
GuideConceptsWork redesign, not ‘assistance’Value shows up when a role is redesigned. Assistance language hides that.
GuideConceptsLicence to operate is now a product inputBuyers, insurers, and the public will not wait for your home statute.
GuideConceptsGenerative is not the credit-score modelSame word ‘model’, different residual risk and a different control set.
GuideConceptsYour data, their weightsThe durable advantage is usually the workflow and the corpus, not the foundation model.
GuideInfrastructureWhat an enterprise control plane actually isIdentity, tool-gating, data scope, logs, evaluation, kill-switch. Not a chatbot admin page.
GuideInfrastructureAgents as principalsGive acting software the same identity discipline you give a contractor with system access.
GuideInfrastructureRetrieval is an access-control problemRAG without document-level permissions is a leak with a nice UI.
GuideInfrastructureThe evaluation harnessA standing test set and online monitor. Not a quarterly slide.
GuideInfrastructureTwo-stack reality in Asia PacificUS-cloud plus a China or sovereign path is often the honest architecture.
GuideInfrastructureInference cost as a controlThe control plane should cap spend the way it caps tools.
GuideCapital languageTransformation envelope versus line P&LSay which one you are running. Mixing them is how returns disappear.
GuideCapital languageHow to write a dual P&LSpend, cost takeout, revenue lift, confidence, residual risk, owner. One page.
GuideCapital languageOptions, not programmesFund the next proof, not the five-year platform, until the control plane exists.
GuideCapital languageUnit economics the line will ownCost per completed workflow. Not cost per seat, not cost per token.
GuideSecurity basicsAgents are a privileged-access problemIf it can call a tool, treat it like a contractor with production credentials.
GuideSecurity basicsPrompt injection, in one paragraphUntrusted text that instructs the model to ignore you and use its tools.
GuideSecurity basicsData egress and shadow AIThe residual risk you are not shown is usually a paste into a public model.
GuideSecurity basicsDesigning a kill-switch that existsOwner on the roster, tested path, class-level stop, a log. Not a vendor ticket.
GuideConceptsAI-native versus AI-enabledOne redesigns the work around models. The other bolts a copilot onto last year’s process.
GuideConceptsBuild, buy, or partnerThree ways to get a workflow into production. Most firms mix them without saying so.
GuideConceptsThe data flywheel, without the sloganUsage creates labelled traces; traces make the next model or retrieval set better; better systems get more usage.
GuideConceptsOpen weights versus closed APIsA cost, control, and residency choice — not a values debate.
GuideConceptsEvaluation as a productEvals are not a QA phase. They are the product the CEO can inspect.
GuideConceptsCompute and energy as a constraintTokens are not free. Clusters, power, and cooling now show up in capex conversations.
GuideConceptsTraining data and intellectual propertyWho may train on what — and who inherits the lawsuit.
GuideConceptsThe talent market is not the model marketYou cannot hire your way to a dual P&L, and you cannot skip complementary skill.
GuideConceptsUnbundling of enterprise softwareIf the interface is a prompt, the suite tax comes under review.
GuideConceptsFallback and graceful degradationWhat the customer sees when the model, the region, or the vendor is down.
GuideConceptsWhat ‘value’ is allowed to meanTime saved, cost out, revenue in, risk avoided — pick the unit before the programme.
1QuestionBoard questionsWhere does AI capital sit, and who can stop it?Is the budget a transformation envelope or a set of line P&Ls with a kill criterion?
2QuestionBoard questionsWhat residual risk do production agents carry today?Not the policy. The acting workflows: money, records, customers.
3QuestionBoard questionsCan we show cost takeout and revenue on the same page?The dual P&L. Activity is not a return.
4QuestionBoard questionsWhich standard do we claim when a buyer or insurer asks?NIST, IMDA, EU Act, or a private story?
5QuestionBoard questionsWhat happens in the first hour of an agent incident?Owner, kill-switch, customer and regulator path.
6QuestionBoard questionsAre we a single-stack firm in a two-stack region?China, and some ASEAN and Gulf buyers, will not share the US-cloud default.
7QuestionBoard questionsDoes the CEO personally own the AI decision?BCG: 72% now say they do. The board should hear whether that is true here.
8QuestionBoard questionsHow much of the workforce has been upskilled — and on what?Trailblazers train widely. Tool rollouts without skill are shadow AI.
9QuestionBoard questionsWhere does AI sit in the risk appetite statement?If it is silent, the firm has no agreed residual.
10QuestionBoard questionsWhich counterparties can already force our documentary pack?European buyers, insurers, banks, public tenders.
11QuestionBoard questionsWhat would we stop funding this quarter?A board that cannot name a stop has not allocated.
1QuestionELT questionsWho is the single owner of each acting workflow?Not the platform owner. The P&L owner who carries residual risk.
2QuestionELT questionsWhich two workflows consume this quarter’s capital?Concentration is the Trailblazer habit.
3QuestionELT questionsDoes every production agent have an identity and a kill-switch?Shared service accounts are unsupervised privileged access.
4QuestionELT questionsWhat is cost per completed workflow, not per token?Inference TCO hides in token dashboards.
5QuestionELT questionsWhere is shadow AI, and what is the sanctioned path?Ban-only strategies fail. Staff will paste into the public model.
7QuestionELT questionsHow does the China (or sovereign) stack report into the same ELT pack?A regional control plane that cannot see one P&L is not regional.
8QuestionELT questionsWho is paged when an agent acts outside policy?If the answer is ‘the vendor’, you do not own the residual.
9QuestionELT questionsWhat do we tell customers we automated — and what we did not?Disclosure is now a product and trust question.
10QuestionELT questionsWhich roles are we actually redesigning, not ‘assisting’?Assistance language hides operating-model change.
11QuestionELT questionsIs model risk extended to generative and agentic systems?Or does the MRM policy still assume a credit scorecard?
12QuestionELT questionsWhat is the vendor-exit path for the primary model?Switching cost is now a strategy item.
13QuestionELT questionsWhich data classes may never enter a public model?A short, enforced list beats a 40-page policy.
14QuestionELT questionsHow many hours did this ELT spend using the tools last month?Leaders who do not use the stack cannot allocate capital inside it.