From large delivery teams to agentic delivery.
A Fortune 500 bank's global IT leadership decided to change how the bank builds software: from large onshore and offshore teams to a lean, agentic lifecycle, from business requirements through to running in its cloud. A senior SNT engineer worked inside the bank's IT leadership as the onsite AI architect for a global IT services firm, shaped the strategy, designed a requirements agent and designed the first business platform to be built the new way.
What the work covered
The strategy
A foundation, not a pilot: seven agents across the software lifecycle, built from shared parts with security built in, certified before production and introduced to teams like new colleagues. A draft for discussion with the bank’s IT leadership.
A requirements agent
The first of the seven. It takes an analyst from a one-line idea to a requirements document in the bank’s format, grounded in past approved projects, with the analyst approving every change. Designed by our engineer, built by the vendor’s team and piloted on one project.
An alternatives document hub
For the IT team in the bank’s asset management arm: private-markets PDFs from hundreds of fund managers, read, checked and published in one pipeline, with people handling only the exceptions. Designed and costed, with a proof of concept built.
The numbers
Design targets and estimates from the design work, not results.
- 7 → 1
- seven manual steps in the document process, redesigned as one automated pipeline (design)
- 95%
- of documents handled with no person touching them (design target)
- Days → minutes
- to act on a capital call, down from 5 to 7 business days (design target)
- ~$0.9M
- a year of operations effort saved (estimate in the business case)
- 7
- lifecycle agents in the strategy, from requirements to release
- 4 × 1 month
- the requirements agent: four engineers built it in about a month, then piloted it
How the work was done
- 01
The decision
The bank wanted its own agentic lifecycle rather than handing its software delivery to a vendor’s platform: its data stays in its own cloud, it owns the logic, and every step can be shown to regulators.
- 02
Requirements first
Good requirements in, so coding agents have something precise to build from. The requirements agent was the first agent designed, built and piloted.
- 03
One platform, designed for agents
The alternatives hub was the first business platform designed the new way: every figure quotes its source, every result must add up, and anything uncertain goes to a person.
- 04
Coding agents carry the build
The work began on a vendor platform built around a coding assistant, then moved to evaluating coding agents for the build itself as they matured.
- 05
What it means for you
The same path works for any firm whose delivery rests on large teams: start with one valuable platform, design it for agents, and let coding agents carry the build.
Designed for a regulated bank. Data stays inside the bank’s own cloud, the bank owns the logic, every extracted figure quotes its source text, and every step is traceable for an audit. A person approves every requirements change and every exception.
See it, then talk to us
This was advisory and design work by our engineers, not a Built with Claude build. Ask us how the same path would work for your team.