Upskilling Finance Teams: From Analysts to Builders

Most finance teams have crossed the first threshold with AI: people use it. They draft with it, summarise with it, ask it questions. That is useful, and it is also where most teams stop. The value that actually moves the needle, the automated reporting, the governed onboarding, the workflows that give analysts their week back, comes from a different capability: the ability to build. The real goal of AI upskilling for finance teams is to move people from using AI to building with it.

That shift does not happen by buying more licences or running a one-off lunch-and-learn. It happens when you deliberately build capability on your own workflows, with the governance a financial institution requires baked in. It is the work we do on our financial services programmes, and this is how to think about it before you commit a team to it.

From using AI to building with it

The distinction matters because the two capabilities have very different ceilings. A team that uses AI gets faster at individual tasks. A team that builds with AI changes how the work itself runs: they automate the reconciliation, not just speed up their own copy-paste; they ship the onboarding flow, not just answer one case quicker. The first is a personal productivity gain. The second is an operational one, and it compounds.

The barrier is rarely intelligence or appetite. Finance professionals are already analytical and already work with systems and data. The barrier is that nobody has shown them the build patterns, the scoping discipline, and the governance habits that turn an idea into something that can run in a regulated environment. That is a teachable gap, not a talent one.

The capability ladder

It helps to think in three rungs, because not everyone needs to reach the top, and pretending they do wastes money:

• Informed user. Everyone should reach here. They understand what AI is good and bad at, they prompt well, and they know where the risks are. This is AI literacy, and it is the floor.
• Power user and shaper. Some people go further: they redesign their own workflows around AI, configure no-code tools, and scope what could be automated. They do not write production systems, but they shape them and they own the process knowledge.
• Builder. A smaller group builds and governs the automations, with the discipline to make them shippable: review steps, monitoring, audit trails.

A healthy finance function has all three, in roughly that proportion. The mistake is training everyone to be a builder (most do not need it) or training everyone only to the floor (then nothing gets built). Map your people to the rungs and target the training accordingly.

You are not trying to turn every analyst into an engineer. You are trying to give each person the rung they need, and make sure you have enough builders to actually ship.

What “good” looks like on a finance desk

Concretely, an upskilled finance team produces things, not just opinions about AI. After real capability-building, a team can take a reporting process and automate its mechanical core themselves, with the human review and audit trail in place (the build pattern is in automating regulatory and management reporting). They can look at a new use case and tell, quickly, whether it is shippable or a demo that will stall in compliance. And they build with governance as a default rather than an afterthought, because they understand why the controls exist, which is the core of AI governance for financial institutions.

That last point is what separates finance-sector upskilling from generic AI training. The goal is not just capability, it is capability that respects the regulated context. A team that builds fast but cannot govern what it builds is a liability, not an asset.

Funding the upskilling: IBF-STS

The cost question has a sector-specific answer in financial services. Training for finance professionals can often be funded through the IBF Standards Training Scheme (IBF-STS), the sector funding route, provided the course is IBF-accredited and the institution and trainees qualify. That can change the economics of upskilling a team meaningfully.

We keep this framing forward-looking and do not make blanket funding claims: eligibility depends on accreditation and your institution’s circumstances. The mechanics of who qualifies and how the claim works are in IBF-STS explained: funding training in financial services, and you can check the current options on our funding page.

A practical rollout for a finance team

A rollout that works is small, real and sequenced. Start with one team and one or two genuine workflows they want to improve, not a hypothetical case study. Set the literacy floor for everyone, then take your prospective builders deeper on those real workflows so they finish the programme with something that actually runs. Build the governance habits in from the first exercise, not as a final module. Then let that team’s shipped work and new confidence make the case for the next team.

Capability built this way sticks, because it was built on the team’s own work and pointed at outcomes they care about. That is the difference between training that gets used and training that gets remembered fondly and forgotten.

Ready to take a finance team from users to builders? Talk to us about a governance-first cohort built on your own workflows.