Podcast · Episode 12
From CTO to CEO: Mambu's Fernando Zandona
Fernando Zandona explains how he went from being a fintech outsider to the CEO of a $5billion+ banking and financial services infrastructure provider.
Episode Description
Last valued at over $5 billion, Mambu is one of Europe's standout fintech success stories. In this episode of the LFG! podcast, CEO Fernando Zandona shares his experience of leading the company for the past three years, as well as his views on the future of banking.
Fernando's perspective is fascinating. Prior to joining Mambu in 2022, he was neither a financial services professional nor a CEO. However, after a year in the role of Chief Technology Officer, he was appointed to the top job.
This outside-in view of banking appears to be serving Fernando well. He explains here why a technology and coding background is an advantage and how it's helped him to challenge established banking norms in a productive way.
We also discuss the rise of AI and the proliferation of 'composable banking', both of which threaten the competitive moats of modern fintechs. Here, Fernando explains what's needed for a fintech to maintain a genuine advantage and walks us through the importance of distribution and trust.
It's not just business models that are changing. Fernando explains why he expects mobile banking apps to eventually decline in favour of agentic banking. He also offers his view on why talent is the 'only thing that matters' when scaling a fintech, and why banks that don't make core banking migrations now, if they haven't already, are dead in the water.
Read the full transcriptHide the full transcript
This transcript was produced with transcription software and lightly edited for readability. It may contain errors and might not be a word-for-word record of the conversation. If anything looks off, the audio and video are the definitive version.
Hello everyone, and welcome to LFG. I'm Ian Horne, and today I'm interviewing Fernando Zandona, CEO of Mambu, a core banking platform valued at over $5 billion back in 2021 when it last raised. Now, Fernando is a wonderful person to be interviewing right now, the CEO of a major European fintech who just so happens to have ample experience as a CTO, chief technology officer. So expect a fair amount of AI chatter here. With that in mind, Fernando, welcome to LFG. Great to have you here.
Thank you so much. Thanks for the opportunity to be here, really appreciate it. Looking forward to chatting with you.
No worries, pleasure's mine. It's great to have you here, Fernando. I don't always allow interviewees to talk about their career history, but in this instance I think it's going to be really relevant and really helpful to do so. So, Fernando, can you talk us through your journey before Mambu? Because you were at Microsoft for 11 years, then you went to Amazon, where you were for over a decade in total, I believe, ending up as general manager of AWS Fargate and Amazon Linux. Could you walk us through your career up until the point that Mambu came along?
Quite a journey, from building container services at AWS to leading a core banking provider in Europe. It was quite a journey. As you mentioned, I spent a lot of time at Microsoft, and another ten years at AWS. And I think my next obvious move would have been to find another big tech to go to, right? But an experience I had living in Seattle, in that environment with Microsoft, Google, AWS, Amazon, you're basically just changing the email address, but the big-tech experience is similar. The culture is very different, but similar. So I was really looking for the next big challenge I could go after, after 10 years of Amazon, or AWS. And that challenge ended up being Mambu. Well, I ended up at Mambu. And I came, as you mentioned, as a CTO. So I spent one year as CTO for Mambu, and after one year I was offered the opportunity to take over the CEO role by our board. I've been leading the company since 2023. So, quite a different experience.
Yeah, totally different environment. So what made you decide to make the leap to Mambu? Was there a moment or a realisation that made you think it was time not to join another major, multinational tech provider?
Exactly, that's exactly it. Moving to Google, for example, would have been very similar. When you're at AWS, you probably know about the culture, it's heavily on delivery, on ownership and all of that. People there feel very stressed with that, and if you don't like that culture, you're out. But it's also such a bubble, because you have all the support, you have the strong culture, the talent, the infrastructure, years of experience of running that business. So I think I was looking for something that is not that, almost like the real world outside big tech. And here I am, experiencing the bigger world, the real world, driving, from a company in the Netherlands, core banking across the globe. So, quite different.
I hate to break it to you, but I don't think fintech's the real world either. But you've found a different world.
No, but compared to a big tech, it's absolutely right. It's very different, yeah.
Sure. Out of the institution, if you will. But you clearly enjoyed that environment, because you were there for a long, long time, so it was clearly just time to try something different. The other thing that's interesting about your background, if I'm not mistaken, is that you don't have a financial services background, right?
I do not, right. So that's also quite interesting. I came from engineering, from building software, really a technical geek journey. And it's very interesting, because it opens up opportunities to talk about things differently. In a way it's a challenge, because we're talking to folks who are running banks and they expect you to understand how a bank runs, and I've been learning a lot about that from my teams. But I also brought a different aspect to it: the scalability, how to run those highly scalable services, how to build software differently, not from the mainframe point of view, but from the SaaS, cloud-based point of view. And I think that has opened up opportunities, both internally and with our prospects and customers.
Yeah, what was your first take on the financial services world? Because I can imagine, being a techie, seeing so much legacy infrastructure being used, so many inefficiencies and interoperability challenges and all the rest. What did you make of that when you first encountered it?
Surprise, on first encounter? No, we know, or I knew, that financial services is quite a range, actually. We have the fintechs who are breaking the mould, moving faster than the more legacy, established financial institutions. And then all the way to companies who are running on their mainframes and are happy with that and don't consider changing it. We have the regulators operating on top of all of that. So it's quite a challenging, peculiar segment. So, not totally surprised, but when you experience it, when your product depends on that moving faster, when you see the reality, the bubble bursts at that point. So it's also, how to say, an opportunity. That's the opportunity.
Yeah, definitely, and I think it's right to view it that way. And, as you were saying earlier, that different perspective really gave you a bit of an advantage in certain respects. At the same time, were there moments when you looked at things the financial services world does and thought, "wait, there's an easy fix here," only to realise there actually wasn't?
Yeah, yes, all the time. Every day. And sometimes that fix really is technology; technology can do so much for us today. Some of those fixes are really "we can just implement this," or "you can just do that." But then, as I mentioned, there are other layers of this stack that you don't have control over. Regulation is one of them. I just came from a meeting with a central bank where we were discussing the aspects of running core banking in the cloud, on a SaaS-based approach, which is different for them. The central banks are still trying to understand what that even means. And then you put AI on top of that. So the fixing, it's not only software or technology that helps, and it helps a lot, and we're bringing that to the market, and AI is bringing that to the market, but I think the whole industry has to evolve and catch up.
Yeah, and I think we have to discuss AI in some depth, but I'm not going to do that just yet. I'd like to go into your CEO experience a bit more, because, as you touched on earlier, you didn't launch Mambu, you kind of inherited it, right, from Eugene Danilkis. How was that experience? What was it like to be scaling a company that somebody else had built, and what did you feel you needed to protect, and what did you need to change?
Yeah, a very humbling experience. As I mentioned, I came to Mambu fully thinking I would be the CTO for the company. At no point in my career did I think, "I'm doing this because I want to be a CEO." I was happy being on the techie side. So it's very humbling to be here, very humbling to be given this opportunity, and to get the trust from the board, the investors, and the Mambuvians, as we call ourselves, to be able to lead the company. The second thing is, it's such an amazing learning opportunity to be here. I used to run a business at AWS, be responsible for a P&L, but, as I mentioned, there's so much support there that you don't fully run the business. So, lots of learning opportunities going through this process.
Yeah, and what's it like being a CTO turned CEO, in the sense that there's so much hype in fintech, especially around AI, as we've been talking about, but that's not the only thing, we always talk about blockchain, or personalisation, or a million and one other things. Does having a CTO background prove to be a bit of a competitive advantage?
I believe so, because I'm able to discuss the technical aspects of the conversation with customers and prospects. There's also an opportunity for me to understand what we're building, how we're building it, and whether there are better ways I can share my experience with our engineering teams. So it's a great advantage to be able to understand how things are built, and, in some cases, even build it myself, so I can test and operate it.
Yeah, I was going to ask, how much of that do you still do? My hunch would be that you'd miss doing some of that work.
Absolutely. Not as much at Mambu, I think we have very strong engineering teams that don't require me to be coding for them. I do a lot of AI evangelism internally, so that's still part of what I do, and I keep my hands on the code, looking at the code, experimenting, building prototypes myself and showing some of the teams, especially non-product engineering teams. But on my free time, I spend a lot of my free time still coding. We don't code anymore, but I'm still testing all the different models and writing my own little applications, so I can be prepared to talk and understand what's happening.
Yeah, how do you do that AI evangelism? How do you promote the right use of AI? Because I use AI all the time, I think most people do now. And, like you're talking about, using things like Claude Code, I'm doing all this stuff with code and I don't really have a clue what's going on. And I'm sure a lot of people in your organisation are the same. You, on the other hand, do know how some of this works. So how do you encourage the right use of AI, especially in a highly regulated environment like yours?
Yeah, I think there are a few things. One is, we have to cross that boundary of "no, this is bad." This is a tool, it's just a tool, a tool that, right now, you have to learn. You do not have an option. You have to learn how to use this tool. Your job has changed. Everyone's job has changed, and you have to learn how to use this tool. So we start from there, and then we start to evangelise and show. For Mambu, we did a 360 approach to adopting AI. We didn't just give licences to people, we started more top-down, with learning-and-development opportunities, with touch bases, with demo days where we show what we're building, with folks from non-product engineering showing the things they're building. It's so impressive. It's really impressive to see what people can do when they're given the opportunity. And also so impressive to see engineers go from being very sceptical to "we're so proud that now we can ship these things in a day," versus the time it was taking us before.
Yeah, and you're able to use AI for enterprise-quality products, right? Which is actually crazy. I mean, you're speaking to someone who's in the marketing department, so I don't use it for anything particularly dangerous. Don't get me wrong, there are very strict marketing rules in certain places, but I think you've got a slightly bigger challenge across the board. Well, let's look at one of your main value-adds. So, Mambu, every banking vendor now claims to be composable and cloud-native. As a category matures, is there much long-term future for that as a competitive moat, especially with the erosion of SaaS businesses we're kind of seeing globally?
Yeah, so Mambu coined that, right? We coined the term "composable banking," and we also delivered composable banking first, before anyone else. And it's good to know that everyone is kind of copying the message, because it shows you've been successful with it. So we've been delivering that composability since Mambu started, and I believe it's even more important today, because of AI, and because of everything we're talking about. That you have an infrastructure for your bank that allows you to connect your agents, connect the AI, or allows us to provide those AI products to our customers, because we have the ability to easily connect, with APIs, to our core. So I think that moat continues to exist, and it's our job to continue evolving that conversation. A natural path right now is towards AI, how AI can help you run a bank, and what we can do to help you provide that.
Yeah, so it's still the underlying product that's valuable, isn't it, rather than the use of AI. I think that's the relevance. And it's very different from someone else being able to just set up tomorrow and have a company that does exactly what you do. I mean, yes, someone with a similar database, maybe you could say they've got a chance to do that, but I think
Yeah, and it's more than just that, right? We have the distribution. We have the trust from regulators, the trust from banks and financial institutions. So all of that becomes, if you think about a moat, a moat for Mambu. And if you're starting now as a fintech, you have to find that moat as fast as possible, because, as we're saying, writing code in itself is not the moat anymore. It used to be, "this is a very complex piece of software, so we have a moat." Knowing how to write this, in itself, is not a moat anymore. So if you're starting right now, you have to look for what that moat is that you're bringing to the market that will allow you to scale.
Yeah, absolutely. And what you're describing here, with people being able to use your data for their own AI plug-ins and agents, this is the model context protocol layer, right? Can you explain that a bit to people who don't understand what that really means?
MCP, right? We call it MCP. So, if you're not technical, I think the best way to think about it is just a connector. It's an easy way for you to connect an AI application to a source of data or functionality. So we call that MCP, and it allows that easy connection. It's a pattern, it's a product, it's a standard that everyone can use and plug into. So we have our own Mambu MCP server, and we're working with several customers who are using it and trying it, to see how they can improve their productivity inside the bank. It becomes more and more table stakes in this market.
Yeah, but does it also lead to new products being shipped and things like that? Are any of the people plugging into the MCP launching new things they can personalise for their customers?
Absolutely. For example, internally at Mambu we have several of our productivity tools MCP-enabled, so we're connecting to all of them and we have our agents connecting and talking to all these different services. In the past you'd need to go through each UI, understand it, download the data and put it on a spreadsheet. Now we can just have our agents connecting and doing that work. For the core, it's the same thing, we're enabling that functionality for our customers, so they can build things around it so much more easily. They can point their LLM at Mambu Core and ask questions about what's happening with a specific customer, what's happening with transactions, what's happening inside the core, which, a few months ago, was something you wouldn't imagine being possible.
So you're essentially making it as easy as you can for people to personalise their service, reach specific niches, and basically do this hyper-personalisation of banking that we've been talking about for years, right?
Absolutely. And we're seeing a range of financial institutions, from those that have the ability to think this way, the skill set, the engineering capability, to say "Mambu has an MCP server, let's go and connect to it," all the way to financial institutions that just don't have that capability. So we're able to cover all of that, at the minimum, the MCP server, but we're also building the AI agents for banking. And that's the very easy, user-friendly approach, where you don't need to understand any of this, you just go there and use it. So we see that range very clearly in the industry today, where financial institutions go from being very tech-savvy to completely needing help to move forward.
Yeah. Well, this whole MCP thing, if we're talking about people being able to do more with the data you hold, where do you think this takes banking? Because it moves us from a place where people receive a very similar service from their bank, to everyone getting something more personalised. How do you think this transforms the nature of banking, and what does the bank of the future do, the bank of 20 years from now, or even 10 years from now, that the current bank wouldn't?
Yeah, if we go all the way there, into the future, I do believe that banking will continue. We need banking as an institution. But I do believe the way you interact with banking will change completely in the next few years. And I agree that we're all looking for differentiated customisations, so why not. So even the app you run on your phone today to do banking, I believe that, in the long run, will disappear as well. We're going to have my AI agents talking to my bank, figuring out what's going on with my account, and the bank's AI agent replying to my AI agent and figuring it out. So I do believe that, in the future, all of that experience will go through AI, with a flavour of AI; maybe it's not ChatGPT, but a flavour of AI, and we'll just be natural users of that. The same way that you text someone, or send a WhatsApp, that's going to be just part of our day-to-day.
Great stuff. And I want to move on to discussing an acquisition you made in 2024. At this point you've been a CEO for about 18 months, and you're thinking, "okay, let's just buy another business," as people do. This was Numeral, right, and, as far as I'm aware, the only acquisition you've made to date. Could you talk us through that one, and the strategic decision to add payments to Mambu's capabilities? Because that'd be quite good to get the inside track on how you approached it.
Yeah, let me say that it was not just "might as well buy another company." There was some strategy behind it.
I'm sure it wasn't, I'm sorry.
No, but one thing I worked really hard on, and Mambu and our Mambuvians worked really hard on, was getting to a point where we were profitable and self-sufficient. We came from the era of burning cash, as anything in tech usually does, to a place where, now, we're comfortable, and the money we raised from that last round you mentioned at the start was still available to us. So: do we keep this money in the bank, or make that money work for us? The strategy was to do the latter. And then we started looking at what's around the core, and what would add value to us. Payments was a key functionality we were considering, buy or build. And we went for the buy. We found Numeral, an excellent company, moving super fast, delivering super fast, very nimble, and that was perfect for where we are, a key capability we needed, with a strong team that was delivering.
Yeah, and you were already integrated with Numeral, if I'm not mistaken?
Yeah, yes, absolutely.
So, from that experience, what did buying, rather than building, teach you? And what did you learn about M&A that you'll take forward? If you did this again, what would you do differently, and what were the main takeaways?
Yeah, I think buying gives you real time to market, and the whole thesis has to be around that. If I invest, usually buying is more expensive than building, so you need to find a way where the equation makes sense, and usually that's time to market: how fast we can move once we acquire a company. The other one is the synergies, are we better together? Can we sell more together, because we now have this functionality in place? So that was the key point of the decision to buy rather than build: we don't have the time. What I would do differently, there's a lot of learning. Interestingly, we had a conversation today, in one of the Q&A sessions I run with the company, and I think one of the learnings is really on the tactical aspects of doing the integration. Some companies have a full team just to do M&A integrations, and we did that with the existing team we have. So: how we can more quickly figure out how to integrate, the G&A functions, commercial, the engineering organisation, and what you do not integrate, because you want to keep them moving fast. So all of that was pretty good learning that I'd carry into the next acquisition.
Yeah, I can imagine, hard-won lessons. But do you think, if you did it again, it would be much easier?
Absolutely, yeah. We learn with each one of those.
And what advice would you give to someone going through a similar process?
On acquiring another company, I think, do not dismiss the integration part. It's very time-consuming, and you need to make sure you're able to do it without distracting you from the main business you have. I think that'd be the main advice.
Yeah, great stuff. And let's get back onto core banking, the main thing you do. Many banks still say they're unhappy with their core, and in spite of this, getting them to switch isn't necessarily easy, if I understand correctly, and the ones that do often take far too long to make the switch anyway. So, in 2026, what's the real reason, in your opinion, that a dissatisfied bank doesn't move from their core banking system? And how do you help them through that decision, what are the things stopping them from moving?
Why they do not move? Yeah, doing a full core migration is a massive project, and we all understand that. Some CTOs have nightmares about that, banking CTOs have nightmares about that. So it's a difficult decision. Some customers decide to just, for example, run Mambu on the side and build new financial products on Mambu, instead of moving the full legacy provider into Mambu. That reduces the risk, and it's something we bring to our prospects as an opportunity, a modern core, on the side, to launch those financial products. What we're seeing a lot in the markets today is this "wait and see." Lots of financial institutions are in this wait-and-see mode, and they're missing the point that this is actually the time to move. Because if you don't move now, then it's too late. The winners are the ones that, in this moment, are making the moves. We saw that in the past, and it's going to repeat. We have some financial institutions, our customers, growing so fast, and they did that exactly when everyone was saying "this is a very risky time," but they took the bet, and now they're leveraging that opportunity.
Yeah, absolutely. For the ones that are still shy to move, I assume it's a case of moving bit by bit, right, doing it in instalments and slowly getting there until they're comfortable with it. But, as you say, it's still a terrifying thing. I found it interesting how you said it's a nightmare for banking CTOs, and I couldn't help but think that you don't consider yourself to be a banking CTO. Would that be right?
Yeah, I'm not a bank, right? I'm not a financial institution. We say that we run hundreds of banks across the globe, we run the infrastructure of hundreds of banks across the globe, but we ourselves are not a bank. So it's quite a different approach.
Yeah, gotcha. It was just that distinction of banking, I was interested in your background not being with a bank, and wondered if you thought of it as a different thing.
Yeah, well, what I meant is: if you're the technical leader in a financial institution and you push to do a core banking migration, that is a significant decision and a significant project for those technical leaders. Some of them have gone through the process, happy to say, not with Mambu, but with other providers, and they had difficult experiences. We've seen those transformations failing over and over. And we've had opportunities to bring them in, earn their trust, and actually make it happen together with them. So we work very differently with our customers. We have very established financial institutions working with us today to do a full core migration, and enjoying the process. It's stressful, of course, but they're still enjoying the process, because we're there with them on a day-to-day basis.
Great stuff. And one last question for you, Fernando, where does Mambu go from here? How are you looking to improve and grow the company?
Yeah, we have so many opportunities in front of us, and we're pretty excited about the future. We believe our core is the right product for this new era of AI, and we're happy to help our customers leverage all that technology. But on top of that, we're building our own AI-based products that we're making available to existing and new customers. And our mission, we say our mission is to make more possible in people's lives through easy and simple access to financial services. So that's what we're doing: making it easier and easier for financial institutions to enable more powerful services for their customers. And that's a pretty good mission to have.
Yeah, absolutely. And, I did say one question, but I'm going to ask one more, what, to your mind, is the key to scaling a business?
Talent. You have to have the right people. That is the only thing that matters, actually.
Yeah, and even in the age of AI? I keep hearing this, and I'm repeating myself from previous interviews, but is it very much about having a growth mindset towards AI, looking at how much you can build, rather than just how much you can cut?
Absolutely. When I say talent, I think it's all-inclusive, you want the talent that has the growth mindset, the talent that wants to grow a business, wants to learn how to grow a business; you want that as part of the culture you have. So all of that is included in this word, "talent." And having that is so crucial. That is the foundation. We have our strategy that we present to the company and to our board, and on every slide where we talk about our strategy, we have the Mambuvians as the foundation. That is where you build the pillars of your strategy. Without that, you don't have the strategy. So we have to have the right talent to grow the business.
Brilliant. Thank you, Fernando. I think that's a really uplifting point to finish on, I certainly think it is, anyway. So thank you for joining me. It's been really fun talking with you.
Yeah, thank you so much. Thanks for your time and for the questions, really appreciate it. It was a really good conversation.
No worries, you're more than welcome. And thank you, of course, to everyone listening in. I'm Ian Horne, and you've been listening to LFG.
