←  All case studies
Before Blackstone&
Case study / Banking & Financial Services

We turned a flood of AI ideas into investment decisions the bank could defend.

A global banking group had AI ideas coming in from 38 markets and no way to decide which deserved investment. We built and ran an innovation-lab front door: a hypothesis-driven loop that assessed every idea on desirable, feasible, and viable, killed most of them cheaply with written reasoning, and moved the rest toward funded delivery. The operating model was handed over and replicated beyond its original team.

1 in 10of AI ideas earned further investment; the rest were stopped early with the reasoning recorded
Client
A global banking group
Led by
Blackstone& founding team member, prior engagement
Engagement
Product leadership, Delivery
Sector
Banking & Financial Services
01 / Context

Lots of ideas, too much governance, no system

The global operations function of a banking group operating in 38 markets had more AI and automation ideas than it could process, and no structured route from idea to investment decision. Governance overhead stalled ideas regardless of merit.

Real operational pain sat behind the queue. In payment investigations alone, half a million cases a month required human intervention across the group, at roughly six minutes per case for the operators handling them and three for the checkers behind them.

02 / The Challenge

The fix could not be more governance

The job was to turn an unmanaged flow of AI ideas into defensible investment decisions, without adding yet another layer of governance to the process that was already the bottleneck.

The cost of doing nothing ran both ways: ideas with merit died in governance, and delivery effort went into ideas that were never feasible, desirable, or viable.

03 / The Approach

Hypotheses, experiments, and explicit kill decisions

We designed and ran an innovation-lab front door: a hypothesis-driven experimentation loop, from ideate and assess through business prototype, experiment, and test, ending in an explicit decision to kill, pivot, or persevere. Every idea was assessed on three questions, do they want this, can we do this, should we do this, with AI-specific tests under each: data readiness, model training, user trust in AI outcomes, return on investment, and scaling economics.

Rejection was a first-class outcome with written reasoning: a plausible test-automation case was killed because defect risk outweighed the efficiency benefit, while payment-investigation and repairs-and-exceptions cases proceeded. The loop was paired with customer research: pains, gains, and jobs-to-be-done analysis, and opportunity-solution trees with experiments designed per solution.

And it was built as an operating model, not a personal habit: defined roles, including an AI governance and compliance function, and a ceremony cadence culminating in a monthly deciding forum where stakeholders made the pivot, persevere, or kill calls. The model was adopted and run in practice, not left as a proposal.

04 / Outcomes & Impact

One idea in ten went forward

The front door ran at an average of three ideas a day. Roughly one in ten moved through to further investment. The rest were stopped early, with the reasoning recorded, before they consumed delivery effort.

The use cases that passed moved into scoped delivery: by January 2025 the repairs-and-exceptions case had a dedicated team onboarded and an AI and machine-learning feasibility study underway.

05 / Capability Transfer

The model outlived the person who built it

A dedicated team was stood up to run the front door for the global operations function, staffed to the roles the operating model defined. The pattern was later adopted by other AI labs across the group’s digital teams.

The operating model outlived the person who built it.

By the numbers
0 / day
AI and automation ideas entering the front door, on average, over the year
500,000
Manual payment-investigation cases a month, across 38 markets, behind one flagship use case
Replicated
The operating model was handed to a dedicated team and adopted by other AI labs across the group
How we made the call

The decisions behind the result

Anyone can list what was built. What matters to a buyer is the judgement: what we chose, what we rejected, and why.

Make rejection a first-class outcome, not a failure.
The front door’s credibility rests on defensible no decisions. A plausible test-automation case was killed because defect risk outweighed the efficiency benefit; killing nine ideas in ten cheaply is what makes the remainder fundable.
Assess AI ideas on AI-specific questions, not the bank’s generic governance.
AI ideas fail in AI-specific ways: data readiness, model risk, user trust in AI outcomes, scaling economics. Generic stage gates were the original bottleneck.
Buy evidence with experiments, not projects.
A hypothesis-and-experiment loop put cheap evidence before expensive builds, with kill, pivot, or persevere decisions made monthly on data.
Codify an operating model, not a personal triage habit.
A codified pattern with defined roles and a decision cadence could be handed over. It went to a dedicated team and was copied by other AI labs after the engagement ended.

* This case study reflects work delivered by a Blackstone& founding team member prior to the formation of Blackstone&. Client identity withheld; details generalised to protect confidentiality.

See yourself in this story?

Technology is the science. Partnership is the art. Let’s write the next one together.

Start a conversation →