Inside Mercury's $650M Revenue Machine, with CEO Immad Akhund

In this episode, Lex chats with Immad Akhund, CEO and founder of Mercury, a leading neobank for businesses. Immad shares his entrepreneurial journey, explaining how frustrating banking experiences inspired Mercury's creation.

They discuss Banking as a Service, open banking, embedded finance, and core banking systems. Immad details Mercury's product philosophy, team structure, and migration away from Synapse before its collapse. He also outlines Mercury's impressive growth, with 300,000 customers, $650M in annual revenue, and three years of profitability.

The conversation concludes with Mercury's future plans, including lending expansion, a bank charter application, and hopes for smarter AI-driven regulatory compliance.

NOTABLE DISCUSSION POINTS:

1. Banking-as-a-Service Has Been Completely Restructured - and the Original Model Is Dead: The fintech BaaS layer that enabled the 2019–2021 neobank boom - middleware providers like Synapse, Unit, and Bond sitting between fintechs and partner banks - has effectively collapsed. The replacement model is banks themselves exposing modern APIs directly, with Column Bank and Lead Bank emerging as the new infrastructure layer. Mercury navigated this shift early, moving entirely off Synapse months before its April 2024 failure, but the broader lesson is that the hundred-program BaaS model broke under the weight of compliance and reconciliation complexity.
2. Mercury’s 40% Startup Market Share Is Just the Entry Point to a $2 Trillion Opportunity: Mercury captures over 35% of early-stage US startups, but broader SMB banking represents 30% of all banking revenue - a $2 trillion market. The company is now expanding into personal banking (launched December 2025), lending (bank charter application filed), and subscription software. Akhund frames Mercury not as a bank but as a financial operating system - the “Google suite of banking” - where deposits are the entry point to invoicing, bill pay, spend management, and eventually underwriting.
3. Stablecoins Don’t Magically Solve the Ledger Problem: Akhund pushes back on the narrative that stablecoins eliminate reconciliation risk. In practice, most stablecoin providers pool customer funds into shared wallets and run their own abstraction layers and internal ledgers - recreating the same reconciliation challenges that exist in traditional banking. The benefit only holds in the narrow case where users truly own their own keys and wallets, which is rarely how scaled fintech products operate.

TOPICS

Mercury, Synapse, Chase, Evolve Bank, Column Bank, Stripe, Plaid, Coinbase, neobank, neobanking, banking-as-a-service, BAAS, fintech, fintech regulation, reconciliation, product development, stablecoins, API, blockchain, VCs, embedded finance

 

ABOUT THE FINTECH BLUEPRINT

🔥Subscribe to the Fintech Blueprint newsletter to stay at the forefront of Fintech and DeFi: https://bit.ly/3hyhlC2

🤝 Partner with Fintech Blueprint through sponsorships: https://bit.ly/3UZllsV

👉 Twitter: https://twitter.com/LexSokolin

 

TIMESTAMPS

1’05: Signing up for six bank accounts and asking for an API nobody understood : how the idea for Mercury was born

4’57: Why depository banking was fintech's last untouched frontier : partner banks, BaaS, and the gap Mercury filled

6’54: BaaS, open banking, embedded finance, and banking cores : a plain-English breakdown of fintech's alphabet