BaaS Is Not a Product. It’s a Business Strategy.
Learn why most companies are looking at BaaS all wrong.
BaaS Is Not a Product. It’s a Business Strategy.
Banking-as-a-Service has spent the last several years being positioned as an infrastructure story.
APIs. Accounts. Payment rails. Ledgering. Compliance. Sponsor banks.
All of those things matter.
But I think we’ve been looking at BaaS through the wrong lens.
BaaS isn't simply a technology product. It’s a business strategy.
The companies that understand that distinction will be the ones that create lasting value from embedded banking, not simply adding another feature to their software.
The Infrastructure Is Becoming Easier. The Strategy Is Getting Harder.
It has never been easier for a fintech or software platform to access banking infrastructure.
Companies can connect to APIs, offer accounts, move money, embed payments, and provide financial products without becoming a bank themselves.
That's the promise of BaaS.
But access to infrastructure doesn't automatically create a great business.
The harder questions are:
Why should your customer use your financial products?
How does banking make your platform more valuable?
Where does the revenue come from?
And perhaps most importantly:
Does banking strengthen your relationship with the customer or is it simply another feature?
Those are strategy questions, not technology questions.
Start With the Customer, Not the Product
The strongest embedded banking opportunities don't begin with:
"What banking product can we launch?"
They begin with:
"What financial problem does our customer already have?"
A vertical software platform may already know when a business gets paid, when payroll is due, when invoices are outstanding, and when cash flow becomes constrained.
That creates an opportunity.
Instead of simply processing a transaction, the platform can help the customer manage the money surrounding that transaction.
Payments become the entry point. Banking becomes the relationship.
That distinction matters.
A payment can be transactional.
A banking relationship can become foundational.
Payments and Banking Should Be One Strategy
For years, payments and banking were treated as separate businesses.
Payments moved money.
Banking held money.
That separation is becoming less relevant.
Consider what happens when a platform can connect both sides of the equation.
It can accept a payment, settle funds into an account, manage balances, facilitate payouts, move money through ACH or other rails, and potentially offer additional financial products around the customer's existing activity.
The value isn't any single product.
The value is the money movement ecosystem.
That's why I believe payments and banking should be part of the same strategic conversation.
The Real Advantage Is Control
There is another reason BaaS matters:
Control.
When financial services are completely outsourced, a platform can have limited control over the customer experience, economics, data, and ultimately the relationship.
When banking and payments are embedded into the platform's core workflow, the platform can influence how money moves through its ecosystem.
That can create opportunities to improve:
Customer retention Revenue per customer Payment economics Deposit relationships Customer engagement Product expansion
The objective isn't to become a bank.
The objective is to build a better business because banking is embedded into the customer experience.
BaaS Without Discipline Can Become Expensive
This is where I think the industry needs more maturity.
Launching a banking product is relatively easy compared with managing one responsibly at scale.
Compliance matters.
Risk management matters.
Sponsor-bank relationships matter.
Operational controls matter.
And economics matter.
A program can generate impressive transaction volume and still be a poor business if the economics don't work.
I've always believed growth and discipline have to coexist.
The right BaaS strategy isn't simply:
"How fast can we launch?"
It's:
"How do we build something that can scale safely, profitably, and sustainably?"
That's a very different question.
The Next Phase of BaaS
I believe the next generation of BaaS will be less about selling banking capabilities and more about solving business problems.
The winners won't necessarily be the companies with the most APIs.
They'll be the companies that understand where money fits into their customer's workflow—and build the financial infrastructure around it.
A vertical SaaS company doesn't need to become a bank.
A marketplace doesn't need to build a payment network.
A fintech doesn't need to recreate the financial system.
They need the right infrastructure, the right partners, the right risk framework, and most importantly, the right strategy.
Because the future of banking isn't simply about putting a bank account inside an application.
It's about making financial services so deeply connected to the customer's workflow that banking becomes part of how the business operates.
That's when BaaS stops being a product.
And starts becoming a competitive advantage.