From Machine Learning to Generative and Agentic AI
Examine how machine learning, generative AI and agents change financial work, and the data, governance and operating choices that determine their value.
This book follows AI from machine learning and data infrastructure through lending, fraud, insurance, customer service, wealth management, trading, research and payments. Generative AI and agentic workflows extend that foundation into new forms of financial work.
The analysis connects applications to organizational choices: workflow design, human review, sourcing, model risk, security, regulation and strategy. Named cases, documented evidence and chapter exercises give readers material to evaluate those choices.
Chapter exercises ask readers to evaluate a real institution, state their evidence, design a workflow and defend a recommendation. Reflection questions examine the limits of the chapter’s methods and arguments.
Read a representative chapter, then explore its guided workflow exercise online.
From Opportunity Prioritization to Operating Model and Vendor Strategy
The complete chapter, including frameworks, cases, regulatory context, a practitioner perspective, an applied exercise and references.
Read sample chapter →AI in Financial Services: From Machine Learning to Generative and Agentic AI
A guided agentic strategy snapshot and implementation roadmap, supported by reflection questions and two decision frameworks.
Read workflow exercise →Chapter 18’s Autonomy Spectrum classifies a deployment once chosen and Chapter 20’s Suitability Ladder classifies the work. This matrix chooses. It scores candidate opportunities across four axes, and it is built to resist the failure most visible in the survey evidence, which is collapsing risk into a single number. The second failure, funding a tool for a process nobody intends to redesign, sits outside the matrix for the reason given below, and is tested separately.
Axis One: Value at Stake. Value is decomposed into three factors and never estimated as a single figure: the value per unit of work, the volume of units, and the share of that value the institution can realistically capture. The third factor is where most business cases inflate. A process that consumes 40,000 hours a year does not release 40,000 hours of value, because the released time is distributed in fragments across many people, and fragments convert to value only where a role is redesigned or a queue clears. Scoring the capture rate explicitly forces the question of what happens to the time, and it is the axis on which a business case should be rejected most often.
Axis Two: Structural Feasibility. Four conditions are scored separately: whether the data the agent needs exists and is of adequate quality, whether the process is describable well enough to specify, whether the integration surface is reachable, and whether the work passes the reversal test set out in Chapter 20. An opportunity that scores well on three and fails on one fails outright. Feasibility is closer to a conjunction than to an average, and a matrix that averages the four will keep recommending the use case whose data does not exist.
Axis Three: Consequence of Error, scored as three separate quantities. Severity, reversibility, and detectability are not the same thing and collapsing them into a risk score destroys the information a designer needs. A high-severity error that is instantly detectable and cheaply reversible is a manageable proposition. A low-severity error that is undetectable and accumulates is the one that produces a remediation program three years later. Detectability deserves particular weight in agentic work for the reason the opening vignette established: agent output is more coherent than unaided work even when it is wrong, so the reviewer’s ability to spot an error is lower than the institution’s intuition suggests.
Axis Four: Strategic Fit and Reuse. This axis asks whether the opportunity builds a capability the institution will use again. An integration layer, a break taxonomy, an evidence-pack standard, or an escalation architecture built for one use case and reusable across ten is worth materially more than its own business case shows.
Bank of America’s stated criterion of scale and reuse across some 3,000 processes is this axis expressed as policy, and it is the axis that distinguishes a portfolio strategy from a collection of pilots.
Scoring and the four quadrants. Score each axis from one to five, then plot value at stake against structural feasibility, using consequence of error to set the governance tier and strategic fit as the tiebreaker within a quadrant. High value and high feasibility are the quick wins that should be sequenced first and used to build the reusable assets. High value and low feasibility are the moonshots, which belong in a separate multiyear track with the feasibility blockers named as their own projects. Low value and high feasibility are the traps: they are easy, they get built, and they consume the delivery capacity that the quick wins needed. Low value and low feasibility are discards, and a portfolio that cannot name what it discarded has not run a prioritization.
When the matrix misleads. The matrix scores the opportunities someone thought to list, and in most institutions the list comes from whoever attended the workshop. It also has no axis for the variable most strongly associated with realized returns in the survey evidence, which is willingness to redesign the workflow, because that is a property of the organization and not of the opportunity. An institution that scores a portfolio honestly and then funds the winners without redesigning anything will land in the 63 percent of organizations not reporting a positive earnings contribution from artificial intelligence. Score the opportunities, then ask separately whether the business units in question are prepared to change how the work is done, and treat a negative answer as disqualifying regardless of the score.
Prioritization selects the process. This method designs it, without code, at a level of detail a business audience can argue about and a technology team can build from. It runs in five steps and produces a diagram with four lanes: human, agent, system, and fallback.
Step One: Stage Decomposition. Break the process into stages at the level where the output of one stage is a thing a person could inspect. Too coarse a decomposition hides the handoffs where failure occurs; too fine a decomposition produces a diagram nobody reads. The test of the right granularity is whether each stage has a nameable output and a nameable owner.
Step Two: the Role Allocation Test. For each stage, three questions decide the lane, and all three must be answered before the stage is assigned. Is this task inside the demonstrated capability frontier for this model on this institution’s data, established by measurement rather than by analogy to a similar task? If the agent performs it and gets it wrong, can the reviewer detect the error from what the reviewer will actually see? Does the reviewer have the authority and the time to act on a detected error? A stage that fails the second question belongs in the human lane whatever the model can do, because a review that cannot detect an error is a control in name only.
Step Three: Handshake Specification. For every boundary crossed between lanes, specify what passes, in what form, with what completeness guarantee, and what the receiving lane does when the handshake is incomplete. This is where most process designs are silent and most implementations fail. A handshake specification names the fields, the evidence attached, the confidence representation if any, and the explicit statement of what the sending lane did not check.
Step Four: the Fallback Lane. The fourth lane exists because the first three describe the process working. It carries what happens when the agent cannot proceed, when a system is unavailable, when the handshake fails validation, and when volume exceeds capacity. Each fallback names who absorbs the work and at what service level.
A process design without this lane is a design for the good case, and in a regulated process the bad case is the one carrying the statutory deadline, the customer who is already unhappy, and the volume spike that arrived on the day the upstream system was unavailable.
Step Five: Instrumentation and KPI Placement. Metrics are placed at the handshakes. End-to-end cycle time tells an institution that something has changed and never where. Measuring at each boundary yields the stage-level data needed to move the human-agent line later, which is the point of drawing the line explicitly in the first place. Place at minimum: volume and latency at each handshake, the rate at which each handshake fails validation, the rate at which the reviewer changes the agent’s proposal, and the rate at which changed proposals turn out to have been right.
When the method misleads. A swimlane assumes the process is knowable in advance and stable enough to draw, which holds for reconciliation and fails for an investigation that goes where the evidence leads. The deeper limitation sits in the human lane. Drawing a review box does not create review, and the experimental evidence in this chapter shows oversight failing precisely on the large errors it was placed there to catch. A diagram that shows a human reviewing every agent output satisfies a governance committee and tells that committee nothing about whether the errors that matter will be found. The honest use of this method is to place the reviewer where the second question in Step Two has been answered affirmatively, and to say plainly where it has not.
Exercises within the chapters support workflow design, opportunity assessment and institutional analysis.
Chapter questions ask readers to defend decisions and examine the limits of the methods used.
Frameworks connect opportunity selection, human-agent coordination, sourcing, governance and operating choices.
Institutional cases and endnotes let readers examine the evidence behind the book’s analysis.
Each chapter provides sources and reading for deeper study. Supporting appendices are being finalized.
Faculty can request an inspection copy and enquire about materials for their intended course or programme.
Public evaluation: read the chapter, workflow exercise and framework examples online.
Purchaser resources: resource packages and downloadable access will be confirmed when sales open. Purchaser access is not yet active.
Faculty resources: ask the Press about inspection copies and currently available teaching materials. Restricted resources require faculty verification.
Considering this book for a course? Request an inspection copy or ask about student and faculty resources. Include your institution, role and intended teaching use.
Follow ongoing developments across AI, business, and the specialist publications.
Explore the briefings →Explore related finance, investment and risk titles in the FutureCentral Press catalogue.
Browse the catalogue →