I spent the first few years of my career doing what most product managers at SaaS companies do: watching monthly recurring revenue climb slowly while sales and product argued over discount tiers. Pricing meetings kept circling back to one core question: how do we grow revenue per customer without raising prices again? Eventually, I moved into a role built around answering that exact question. Today, I lead embedded finance for a mid-market software company, and I have learned firsthand that while the subscription model has a ceiling, integrated financial tools offer a realistic way to grow past it.
This isn’t a theoretical argument. I’ve watched this shift play out inside my own company’s numbers, and it’s showing up across the industry too. Adyen and Boston Consulting Group studied the addressable embedded finance opportunity for SaaS platforms in North America and Europe. They put the number at around 185 billion dollars. Platforms have actually captured less than 20 percent of that so far. That’s not a rounding error. Most of the market is still sitting on the table, waiting for someone to pick it up.
The subscription ceiling
Subscription pricing is a wonderful business model because it’s predictable. Investors love it. Finance teams can forecast against it. Customers generally understand what they’re paying for.
But predictability has a limit. Once a customer accepts a given price point, your options for growing that account narrow fast. You can raise the price and risk churn. A tier upsell is another option, though customers may not need what’s in it. Adding seats works too, but only if your product genuinely requires more seats to deliver value.
I’ve sat through enough renewal conversations to know how uncomfortable price increases feel, especially with loyal customers who feel punished for staying. Embedded finance sidesteps that whole conversation. Instead of asking a customer to pay more for the same software, you give them a new way to get value from the software they already use. You collect a share of the value you helped create.
Picture a vertical SaaS platform for contractors that adds payment processing. It isn’t charging customers more for the project management tool. It’s making it easier for a contractor to get paid by their client, and it earns a small percentage of a transaction that was going to happen anyway.
That distinction matters more than it might sound. Customers resist fee increases on things they already own. They accept a new charge far more easily when it solves a problem they were already handling elsewhere, often through a clunkier tool and a less trustworthy vendor.
What embedded finance actually means
I want to be precise here, because people throw this term around loosely. Embedded finance integrates financial products, think payments, lending, banking, and insurance, directly into a non financial company’s core product. The financial product shows up at the exact moment the customer needs it. It is not a partnership where you slap a bank’s logo on a landing page and call it a day. Done well, the financial product feels like a native feature of your software, not a bolted on add on.
McKinsey has tracked this shift for years. Their researchers estimate that as much as half of traditional banking revenue pools could eventually move into products suitable for embedding. Why those products specifically? They carry lower risk, they automate well, and they already have proven demand. That’s a meaningful chunk of an enormous industry shifting toward companies like mine instead of toward traditional banks.
Three verticals matter most for software platforms: payments, lending, and insurance. Each one has its own maturity curve, its own implementation lift, and its own revenue profile. It’s worth walking through them one at a time instead of treating embedded finance as a single feature to ship.
Payments: the entry point almost everyone starts with
Payments is where most platforms begin, and for good reason. It’s the most mature category. The infrastructure is the most standardized. Your customers already process payments somewhere. The only real question is whether they do it through your platform, or through a separate tool that adds friction and shares nothing with you.
When my team built our platform’s first embedded payments launch, the business case wasn’t complicated. Customers left our software every time they processed a transaction, and we lost visibility the moment they did. A payment processor collected money that could have been ours. Once we built payment acceptance directly into the product, invoicing, checkout, and payouts all happened without the customer ever leaving our screen. Adoption beat our internal targets within two quarters. We weren’t asking customers to change their behavior. We were removing a step they never wanted to take in the first place.
The monetization mechanics here are fairly well established. Some platforms charge a small markup on interchange. Others take a flat percentage per transaction. Some bundle payment processing into a premium tier and monetize through subscription upgrades instead. Whichever model you choose, your customers’ business activity drives the revenue directly. That means it grows automatically as your customers grow, and you never have to sell anything new to earn it.
Payments adoption across the industry has already crossed 60 percent among SaaS platforms that offer it. That means payments alone no longer differentiates you. It’s closer to table stakes now. The real differentiation happens in what you build on top of it.
Lending: where the real economics live
Lending is the category my team asks me about most, and it’s also where I see the most hesitation. Product teams often assume lending is too complicated or too risky to touch. I understand the instinct, but it’s outdated. You don’t need a banking license to offer working capital to your customers. You need a lending partner who handles underwriting and capital, plus a product team that knows exactly where a cash flow gap shows up in the customer journey.
Here’s a stat that changed how seriously I take this category. Platforms that offer lending, banking, payroll, insurance, and accounting products see revenue per customer increase by 2x to 5x compared to platforms that only sell core software. Not 2 to 5 percent. Two to five times. That gap is too large to ignore. It’s part of why I now spend most of my week on lending products, even though payments is where my career in this space actually started.
Why the data advantage matters
Data explains why lending works so well inside software. A SaaS platform that processes a merchant’s invoices, tracks their inventory, or runs their payroll reads that business’s cash flow far better than a traditional bank ever could. A bank works from a credit score and a few months of bank statements. Your platform watches revenue and expenses happen in real time. That data advantage lets embedded lending underwrite faster and more accurately than a customer’s existing bank. Customers notice the difference quickly, and adoption follows.
Here’s the catch, and I say this from experience: lending is not a feature you bolt on in a single sprint. It demands real thought about underwriting partners, credit risk exposure, and how you surface a loan offer without it feeling like a predatory upsell. I’ve watched platforms push credit products too aggressively at customers who didn’t need them, and it damaged trust in the entire software product, not just the lending feature. Get the timing and targeting right, though, and lending becomes one of the stickiest features you can offer. A customer with an active loan on your platform rarely churns to a competitor.
Insurance: the newest frontier
Insurance trails the other two verticals in adoption, sitting under 40 percent among platforms with some form of embedded finance already live. But it’s also growing the fastest of the three. The global embedded insurance market reached roughly 145 billion dollars in 2025. Analysts expect it to grow at a compound annual rate above 30 percent through the early 2030s, a trajectory that pushes it well past a trillion dollars within a decade.
Insurance fits naturally into specific moments in a customer’s workflow, and that’s what makes it interesting from a product standpoint. A logistics SaaS platform that helps a company book freight sits in a perfect position to offer cargo insurance right at the moment of booking. A platform serving event organizers can offer cancellation coverage during checkout. The insurance product stops being a separate purchase decision. It becomes a checkbox at the exact moment the customer is already thinking about risk.
I’ll admit insurance is the vertical I understand least, compared to payments and lending. The regulatory and underwriting complexity sits with a different set of partners than the ones I work with day to day. But even from a distance, the pattern holds. Retention improves whenever more of a customer’s financial workflow lives inside your platform, and insurance gives customers one more reason to stay.
Why this works better inside software than outside it
Embedded finance succeeded inside software platforms specifically, rather than through banks building better standalone apps, for one simple reason: distribution. A bank spends enormous amounts of money acquiring a single customer for a checking account or a loan product. A SaaS platform already has that customer. It already has their trust. It already understands their business in granular detail, because the software runs their operations every single day.
This is also why the fastest moving platforms are locking in an advantage that gets harder to challenge over time. Once a customer’s payments, lending relationship, and possibly insurance policies all run through your product, the cost of switching to a competitor’s software jumps dramatically. You stop being just a tool they use. You become the financial infrastructure their business runs on.
Recent survey data backs this up. Roughly 68 percent of software platforms already have some form of embedded finance live. Another 18 percent are actively building it. Only a small remainder are still evaluating whether to bother. The window to become a first mover in a given vertical keeps closing.
Five questions before you build anything
Before any team I work with commits engineering time to a new embedded finance product, I ask them to answer five questions honestly.
First, does this financial product solve a problem our customer already has, or are we inventing a need to justify a new revenue line? Second, do we hold the transaction or behavioral data to underwrite or price this product better than an outside provider could? Third, can we partner with a licensed provider for the pieces that require a license, rather than trying to become a bank or an insurer ourselves? Fourth, will this feel like a natural extension of the workflow our customer already lives in, or will it feel like an upsell that interrupts their work? Fifth, what happens to customer trust in our core product when this financial feature fails, whether that’s a declined loan, a failed payment, or a denied insurance claim?
Teams skip that last question more often than they should. Your core software product and your embedded finance product share one brand, even when a partner handles the underwriting behind the scenes. A bad experience with the financial feature bleeds straight into how customers feel about the software itself.
Build versus partner
Nobody should build payment rails, lending infrastructure, or insurance underwriting from scratch in 2026. The infrastructure layer for embedded finance has matured enough that partnering is almost always the right call. Building in house usually signals that a team hasn’t looked hard enough at what already exists. Your job as a product team isn’t to become a bank. Your job is to build an excellent product layer on top of partners who already handle the regulated, capital intensive work well.
In house effort matters most in the experience layer. That means how you surface the financial product, when you offer it, how you price it, and how you explain it. Your customer may never have used anything like it before. A generic banking as a service provider can’t do that part for you, because they don’t understand your customer’s workflow the way your product team does.
A short story from inside our own roadmap
Let me share one example, because it’s more useful than another abstract statistic. About eighteen months ago, our lending pilot launched with a single use case: short term working capital for customers waiting on unpaid invoices. We picked that use case for two reasons. It was narrow enough to underwrite safely, and common enough that nearly every customer segment we served ran into it at some point.
How the pilot actually ran
The first version stayed deliberately unglamorous. A customer saw an offer inside their invoicing dashboard, priced using their own payment history running through our platform. They could accept funding in a few clicks, without leaving the product or filling out a separate application.
The results surprised even the people on my team who pushed hardest for the project. Within the first year, customers who used the lending feature churned meaningfully less than customers who didn’t. Average revenue per account among that group grew well beyond what our pricing team had modeled for a typical upsell. We didn’t get there by discounting the core software or adding a new subscription tier. We got there by solving a real cash flow problem the exact moment it appeared, and taking a small share of the value we created.
What surprised me personally was how little marketing the feature needed. Customers found it because it showed up inside a workflow they were already in, not because we ran a campaign asking them to consider a new financial product. I keep coming back to that pattern whenever I talk with other product leaders in this space. Embedded finance rarely needs a sales pitch the way a new software feature does. It needs to show up in the right place, at the right moment, for the right customer. Adoption tends to follow on its own.
The friction we didn’t expect
None of this happened without friction. Our underwriting partner initially set approval thresholds too conservatively, so the system declined a meaningful share of applicants. A decline inside your own product stings more than a decline from an outside lender, because customers blame you, not the partner working behind the scenes. We spent a full quarter working with our partner to recalibrate those thresholds using the platform data we could share. Approval rates improved substantially, and default rates barely moved. That tuning process, more than the initial launch, made the product actually work.
Where this is heading
I don’t think embedded finance stays a differentiator much longer. Within a few years, a vertical SaaS platform without embedded payments, lending, or insurance will look outdated. Nothing will have failed. It will simply look the way a platform without mobile support looks today. Think about construction software, healthcare practice management, logistics, and professional services. The platforms that win the next decade in those categories will figure out how to become the financial operating system for their customers’ businesses. They won’t settle for being just the software vendor.
If you’re a product leader wondering whether this is worth the organizational effort, look back at that 2x to 5x revenue per customer figure. Very few product investments in software today offer that kind of return, and fewer still come with retention benefits attached. Treat embedded finance as a side project, and the platforms that treat it as core to the roadmap will outpace you.
Frequently Asked Questions
What is embedded finance in simple terms?
Embedded finance means offering financial products, such as payment processing, lending, or insurance, directly inside a non financial company’s product, instead of sending customers to a separate bank or financial provider. Stripe offers a clear introduction to the concept: https://stripe.com/guides/introduction-to-embedded-finance
How is embedded finance different from just partnering with a bank?
A basic bank partnership usually refers customers out to a third party product. Embedded finance builds the financial product directly into your software’s workflow, so the customer never has to leave your platform or apply somewhere else. McKinsey covers this distinction and how banks and platforms are converging: https://www.mckinsey.com/industries/financial-services/our-insights/embedded-finance-how-banks-and-customer-platforms-are-converging
Do I need a banking or lending license to offer embedded finance?
In most cases, no. Software platforms typically partner with a licensed bank, lender, or insurance carrier that handles the regulated activity, while the platform focuses on product experience and distribution. Apideck’s state of the market report explains how platforms structure these partnerships: https://www.apideck.com/embedded-finance-report
Which embedded finance product should a SaaS platform launch first?
Most platforms start with payments, because the infrastructure is the most mature and customers already expect to pay through software. Lending and insurance tend to follow once a platform gathers enough transaction data to underwrite well. a16z lays out this sequencing in detail: https://a16z.com/fintech-scales-vertical-saas/
How much revenue can embedded finance realistically add to a SaaS business?
Reported figures vary by product and industry. Several studies point to a 2x to 5x increase in revenue per customer for platforms that successfully embed lending, payroll, insurance, and accounting products, compared to software only competitors. The Apideck report linked above documents this range in detail.
Is embedded insurance worth pursuing for a smaller SaaS platform?
It depends on whether insurance fits a natural moment in your customer’s workflow. If your platform already touches a decision point involving risk, shipping, events, or equipment, embedded insurance can work well even for smaller platforms, since underwriting partners absorb the complexity. Grand View Research’s market analysis shows how quickly this category keeps growing: https://www.grandviewresearch.com/industry-analysis/embedded-insurance-market-report
References
Adyen and Boston Consulting Group, cited via Stripe, embedded payments market opportunity for SaaS platforms: https://stripe.com/resources/more/embedded-payments-for-growth
Stripe, Embedded finance for software platforms: https://stripe.com/guides/introduction-to-embedded-finance
McKinsey and Company, Embedded finance: Who will lead the next payments revolution: https://www.mckinsey.com/industries/financial-services/our-insights/embedded-finance-who-will-lead-the-next-payments-revolution
McKinsey and Company, Embedded finance: How banks and customer platforms are converging: https://www.mckinsey.com/industries/financial-services/our-insights/embedded-finance-how-banks-and-customer-platforms-are-converging
Apideck, The State of B2B Embedded Finance Report: https://www.apideck.com/blog/state-of-b2b-embedded-finance-report
Apideck, The State of B2B Embedded Finance 2026 Report: https://www.apideck.com/embedded-finance-report
Andreessen Horowitz, Fintech Scales Vertical SaaS: https://a16z.com/fintech-scales-vertical-saas/
Grand View Research, Embedded Insurance Market Report: https://www.grandviewresearch.com/industry-analysis/embedded-insurance-market-report
Forbes, Embedded Fintech Meets AI, Vertical SaaS Platforms To Vertical Agents: https://www.forbes.com/sites/davidmoon/2025/05/28/embedded-fintech-meets-ai-vertical-saas-platforms-to-vertical-agents/