In twenty years of working inside and alongside financial institutions, I've seen more good ideas stall inside large banks than I can count. The reason is rarely the idea. It's the process. Banks are approval machines. Getting something through requires satisfying multiple stakeholders, each with different questions, different risk tolerances, and different definitions of success.
Cross-border payments modernisation is particularly challenging because it sits across so many teams. Sales and relationship managers feel the customer pain directly. Product stakeholders own the roadmap and resist anything that disrupts it. Risk, legal and finance are gatekeepers who need assurance before they'll sign off. And the C-suite needs a narrative they can carry to the board.
Here's how to build a case that moves through each layer.
Start with the commercial team
Sales, relationship and FX teams are usually your most natural advocates. They're losing customers to challengers. They're hearing feedback from clients about the experience gap. They have skin in the game.
What they need from you is ammunition: specific, credible data on revenue at risk, customer attrition data if you have it, and a clear narrative about what fixing this makes possible for their book of business. Give them something they can repeat in a corridor conversation. Make the cost of doing nothing concrete and personal.
Working with product stakeholders
Product stakeholders are often the hardest to move. Their concern is legitimate: any significant infrastructure change creates dependencies, consumes capacity, and risks disrupting existing roadmap commitments.
The key is to frame the conversation around what they gain, not what they give up. A well-designed integration doesn't consume product roadmap — it clears it. If the cross-border payments infrastructure is currently a source of technical debt and ongoing maintenance burden, removing that burden creates capacity. The question to ask is: what would your team build if they weren't maintaining this?
Offer co-design early. Product stakeholders who feel like they're being handed a decision resent it. Product stakeholders who feel like they've shaped the solution advocate for it.
Risk, legal and finance: the assurance layer
These teams are not obstacles. They're doing their job. What they need is documentation that lets them do it efficiently.
For a payments infrastructure change, that means: a full RACI establishing who owns what responsibilities, SLAs with clear escalation paths, security certifications (SOC 2 Type 2 is the benchmark), data flow diagrams, BCP documentation, and privacy compliance statements. The more complete this pack, the faster these teams can move. Gaps in documentation don't make risk disappear — they make it harder to assess, which slows everything down.
On the finance side, the case needs to quantify both the cost of the change and the cost of not changing. The second number is often more powerful than the first. Revenue at risk from customer attrition, operational cost of manual processing, regulatory exposure from compliance gaps — these are the numbers that move a CFO.
The C-suite and board narrative
Executives have a 30-second attention span for new initiatives. The narrative needs to be simple, strategic, and connected to something they already care about.
"We are losing SME customers to challengers at a rate of X per quarter, at an average lifetime value of Y. Fixing our international payments experience addresses the primary reason for that attrition. Here's what it costs, here's what it returns, and here's the risk of doing nothing."
That's the shape of a board-ready narrative. Everything else supports it.
The process is the product
The lesson I keep coming back to is that the quality of the internal approval process is often as important as the quality of the solution itself. A great solution that fails to move through the organisation doesn't get implemented. A well-navigated approval process builds institutional commitment that sustains the project through implementation.
Invest in the process. Map the stakeholders early. Understand what each person needs before you're in the room with them. And don't mistake a first meeting for progress — progress is when the right stakeholder says yes.
In Part 2 of this series, we look at the external pressure that is now making these conversations easier — and why the window for banks to act is narrower than it appears.