Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How SaaS Vendors Win With Embedded Finance
Transcript
- Lucas: Look, if you’re a mid-market SaaS vendor trying to close a deal with a Fortune five hundred company today, the conversation has quietly shifted from features to finances. Buyers aren’t just asking what your software does anymore; they’re asking how it moves money. We are seeing a massive wave of enterprise deals stall not because the product is bad, but because the vendor hasn’t integrated their own payment rails. Luna: Right, so procurement isn’t just checking boxes on security anymore. They’re looking at cash flow impact. If I can pay you through my existing corporate card feed instead of cutting a check or running a wire, that’s an immediate operational win for them. Lucas: Exactly. And it’s deeper than just convenience. It’s about data visibility. When a vendor embeds finance—think things like automated invoicing, real-time usage-based billing, or even embedded credit lines—they become part of the buyer’s treasury stack. That changes the stickiness factor completely. You stop being a tool they use and start being a utility they rely on. Luna: But doesn’t that introduce a whole new layer of compliance risk? Handling payments means dealing with pci dss, AML checks, and varying tax jurisdictions across different countries. Lucas: It absolutely does. Which is why most vendors don’t build this themselves. They partner. Look at how Adobe Commerce or Salesforce Billing works. They aren’t banks. They sit on top of Stripe Connect or Adyen infrastructures. The vendor provides the user interface and the logic, but the actual movement of funds happens through licensed banking partners. It’s a symbiotic relationship where the SaaS company gets better retention and the fintech partner gets volume. Luna: So the vendor becomes a de facto payment processor without taking on the full regulatory burden. That’s smart leverage. But how do you sell that to a skeptical CFO who thinks adding more third-party apps is just creating shadow IT? Lucas: You sell them on consolidation. The biggest pain point for enterprise finance teams right now is invoice reconciliation. They have hundreds of SaaS subscriptions, all billed differently. Some are annual, some monthly, some based on seats, some on API calls. Embedded finance allows the vendor to format the invoice exactly how the buyer’s ERP system wants to receive it. It automates the matching process. That saves finance teams hours every single month. Luna: I can see why that would cut through the noise. If I’m a procurement manager drowning in mismatched invoices, a vendor who offers auto-matching is basically handing me back my weekends. But is this only relevant for large enterprises, or does this trick work for smaller businesses too? Lucas: It’s actually accelerating in the mid-market now. As private equity firms consolidate portfolio companies, they’re demanding standardized billing practices across their holdings. If Vendor A sends messy PDFs and Vendor B sends structured XML files that plug straight into NetSuite, Vendor B wins the renewal. It’s becoming a competitive moat. Luna: That’s a fascinating dynamic. So it’s not just about tech specs; it’s about political capital within the buyer’s organization. The salesperson might be fighting for the feature set, but the champion is fighting for administrative ease. Lucas: Precisely. And here’s the kicker: embedded finance opens up new pricing models that were previously impossible to administer manually. Usage-based pricing used to be a nightmare for accounting departments because they couldn’t verify the usage until the end of the month. With embedded APIs, you can bill in near real-time. It aligns cost with value instantly. Luna: Real-time billing though... wouldn’t that scare off customers who prefer predictable, flat-rate annual contracts? People like knowing exactly what their expense will be at the start of the year. Lucas: It does create tension. But the trend is moving toward hybrid models. You lock in a base commitment, but overages are handled automatically through the embedded payment engine. The key is transparency. If the customer sees a dashboard that shows their current run rate and projected final bill, they’re less anxious about variable costs. Trust replaces predictability. Luna: Transparency is huge. Nothing kills a deal faster than surprise charges at renewal time. If the vendor can show me my usage trends over the last quarter, I feel much more confident signing a longer term. Lucas: That’s the psychological shift. You’re giving them control. And let’s talk about cross-sell opportunities. Once you’re embedded in the payment flow, you can offer adjacent financial products. Think about working capital advances. If a SaaS platform knows a client’s revenue trajectory via their transaction history, they can offer instant financing for expansion. That’s how you turn a software vendor into a financial advisor. Luna: Whoa, hold on. Offering lending products? That sounds like a massive regulatory jump. Are we really talking about SaaS companies acting like banks yet? Lucas: Not acting like banks, but partnering with them. It’s called merchant cash advances or revenue-based financing, facilitated by fintech partners. The SaaS company provides the data underwriting engine, and the bank provides the capital. It’s a very lucrative revenue stream for the vendor too. They take a cut of the interest spread. Luna: Okay, that changes the economics significantly. The vendor isn’t just selling software; they’re monetizing the data trust they’ve built. But how do you ensure data privacy when you’re sharing financial performance metrics with a third-party lender? Lucas: Strict consent frameworks. The customer must opt-in. And crucially, the data is often anonymized or aggregated at the source before it leaves the vendor’s environment. It’s not about exposing individual client secrets; it’s about proving creditworthiness based on aggregate behavior patterns. GDPR and CCPA compliance is non-negotiable here. Luna: So it’s a delicate balance between leveraging data for value and protecting it from liability. If a vendor gets this wrong, they lose their core reputation as a software provider. Lucas: Absolutely. Reputation is everything. But for those who get it right, the barrier to exit becomes incredibly high. It’s not just hard to leave because of migration costs; it’s hard to leave because you’d lose access to your own financial operating system. Luna: That’s a powerful lock-in effect. It’s less about contractual handcuffs and more about operational dependency. If I switch vendors, I have to rebuild my entire invoicing workflow. That’s a massive deterrent. Lucas: Right. And let’s look at the global angle. In 2026, doing business internationally means dealing with dozens of currencies and tax regimes. Embedded finance solutions can handle multi-currency settlement and local tax compliance automatically. For a global enterprise, that’s a game-changer. They don’t want to manage fifty different payment methods across Europe and Asia. Luna: They want one pane of glass. One vendor handling the complexity. It simplifies their AP and AR teams immensely. Do you think traditional ERPs like SAP or Oracle are losing ground here? Lucas: They’re adapting, but they’re slow. Their legacy architecture makes real-time, embedded integrations clunky. Specialized SaaS vendors who started cloud-native have an advantage. They built their billing engines from scratch with APIs in mind. ERPs are playing catch-up, trying to integrate these capabilities rather than natively owning them. Luna: So the niche players are eating into the incumbents’ lunch by offering better financial UX. That’s a classic disruption pattern. Software first, finance second, but the finance layer is what seals the deal. Lucas: Exactly. And it forces the big guys to innovate. We’re seeing Oracle and SAP launch their own embedded finance marketplaces to compete. But the mindset shift has already happened. Buyers expect it. Luna: If you’re a founder building a B2B product, ignoring the financial layer feels like leaving money on the table. Or worse, leaving market share to competitors who aren’t. Lucas: It’s becoming a baseline expectation. Like having a mobile app or single sign-on. You don’t get extra credit for having basic billing. You get credit for making the money movement seamless. Luna: Makes sense. So the next time I’m evaluating a new tool for my team, I’ll be asking about their billing API and tax compliance features right after I ask about security. Lucas: Do it. You’ll be surprised how many vendors still treat invoicing as an afterthought. Those are the ones struggling with churn. Luna: Well said. It’s funny how the backend operations often dictate the frontend success. Lucas: Always is. Now, before we dive back into the specifics of how to structure those API contracts, I want to mention something quick. If these conversations help you make smarter decisions about your own stack... Luna: knowing that listener support keeps this show ad-free and independent. If today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. Lucas: We appreciate it. It helps us keep digging into these structural shifts. Let’s get back to the technical side of implementation. Luna: Right, so you mentioned API contracts earlier. How do you actually negotiate the terms when the vendor is also becoming your payment processor? Lucas: Great question. You need to separate the service level agreement for the software from the merchant services agreement for the payments. Don’t lump them together. Ensure that if there’s a dispute about the software quality, it doesn’t trigger a hold on your payments. Independence is key. Luna: That’s a crucial distinction. You don’t want the vendor holding your cash hostage over a bug report. It creates a power imbalance that favors the vendor. Lucas: Exactly. And you should demand clear SLAs for payment uptime. If their payment gateway goes down, your ability to collect revenue—or in this case, your ability to pay—shouldn’t be impacted. There should be compensation clauses for downtime. Luna: Compensation clauses for payment failures. I hadn’t thought of that. Usually, we focus on uptime for the app itself, but the financial pipe is just as critical. Lucas: It’s the lifeblood. Without it, the business stops. So treat it with the same rigor as your core infrastructure. Also, watch out for hidden interchange fees. Make sure the vendor is passing through costs transparently, not marking them up. Luna: Transparency again. They love that word, but it’s the only thing that builds long-term trust in financial relationships. Lucas: Without a doubt. If you master that, you’re not just selling software. You’re enabling growth. Luna: That’s a high bar, but clearly the new standard for enterprise deals. Lucas: For now. The question is, how long until every major SaaS platform treats finance as its primary feature rather than a secondary function? Luna: Probably sooner than we think. The infrastructure is already there. It’s just a matter of who integrates it best. Lucas: Indeed. And the winners will be the ones who make it invisible.