Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise RFPs Now Probe Vendor Bankruptcy Risk
Transcript
- Lucas: So you close a seven-figure enterprise deal, and the signature comes back with a new section in the RFP — section nineteen, right between 'incident response' and 'data residency.' And it's titled 'Financial Viability Assessment.' Luna: That's becoming the new normal. I've seen it in three separate deals this quarter alone. Lucas: Right, and it's not just the big banks requesting it anymore. I was talking to a founder of a mid-market SaaS company — about twelve million in annual recurring revenue — and their buyer, a logistics firm, wanted audited financials, a full debt schedule, and a covenant analysis. For a twelve million dollar ARR vendor. Luna: That's intense. And it stalled the deal? Lucas: Six weeks. The risk team needed to reconcile their numbers against the financial statements, and the founder had to keep the deal warm while his CFO pushed back on how much to share. Eventually they redacted quite a bit, but the damage was done — the deal slipped a quarter. Luna: So what exactly are these buyers looking for? Is it just a solvency check? Lucas: It's more than a solvency check. They're digging into what I'd call 'survivability.' They want to know: if your largest customer leaves, if your key investor pulls out, if the market tanks — can you still keep the lights on? And for software companies, that analysis is tricky because your asset base looks different from a manufacturer's. Luna: Right, because we don't have factories or inventory to liquidate. Lucas: Exactly. And that's where the old 'we're growing, we're fine' pitch stops working. Buyers have been burned too many times by vendors that looked great on a hockey-stick curve and then hit a wall. I read a stat from a procurement association — something like sixty percent of their members now require some form of financial viability check for any software deal above five hundred thousand dollars. Luna: That's a big shift from just a few years ago when it was only for mission-critical systems. Lucas: And it's not just the big guys. Even mid-market buyers are asking. They've learned from the collapses of vendors that were household names in the SaaS world — the ones that folded overnight and left customers scrambling. Luna: So what's the specific data point that sets off alarm bells? Is it negative working capital? Lucas: Negative working capital is one. But for SaaS, the bigger red flag is revenue concentration — if one customer is more than thirty percent of your ARR, that's a huge risk. And then there's the debt structure. I had a CFO tell me he wouldn't sign a deal until he saw a schedule of the vendor's convertible notes and the conversion triggers. Luna: That's deep. But honestly, if I'm a private company, why would I ever hand over my full financials to a prospect? That feels like giving away the playbook. Lucas: So there's a tension there. The buyer's risk team wants as much as possible, and the vendor wants to protect sensitive information. The key is to find a middle ground — share enough to demonstrate financial health without exposing trade secrets or strategic plans. Luna: Like what? What's the minimum viable set of numbers that satisfies a risk officer? Lucas: I'd say audited financials are the gold standard. But if you don't have those, a reviewed or compiled statement can work for smaller deals. And you can redact things like customer names, specific revenue breakdowns by product line, and any details about your cost structure that would reveal your margins. Luna: But wait — if you redact the revenue concentration, how do they know you're not one customer away from collapse? Lucas: That's the crux. You can't redact everything. You need to give them a clear picture of your revenue health — maybe an aggregate percentage of your top five customers, without naming them. And you should always include a three-year survivability projection. That's the new ask that's really gaining traction. Luna: A survivability projection? Like a cash-flow forecast under different scenarios? Lucas: Yeah, exactly. They want to see that you've stress-tested your business. So you model a base case, a downside case where churn doubles, and maybe a severe case where you lose a major anchor customer. Show that you can still operate for at least three years without new funding. That's the kind of thing that builds confidence. Luna: And what if you can't show that? What if your projections are ugly? Lucas: Then you have a hard conversation. Some founders might be tempted to cook the numbers, but that's a world of pain if discovered. Better to be upfront — maybe the deal doesn't close, but you preserve your reputation and avoid a potential lawsuit. Luna: That's a tough position. But I bet most healthy SaaS companies can put together a reasonable projection. Lucas: Most can, but they need to be prepared. I've seen too many founders freeze when the RFP lands in their inbox. They don't have the financials ready, or they don't know what the buyer's risk framework expects. And that's where a good CFO or a fractional finance person is worth their weight in gold. Luna: So is this a case where the buyer is essentially asking you to prove you're not going to go bankrupt on their watch? Lucas: Exactly. And honestly, if this conversation was useful to you — if you're a founder or a sales leader dealing with these new RFPs — and you feel like buying us a coffee to keep the show ad-free, that would be great. The link is buy me a coffee dot com slash fexingo. It's a small ask, but it genuinely helps us keep doing this. Luna: Yeah, no pressure at all. We're just happy you're listening. Lucas: So let's go back to that redaction line. Where's the boundary between 'we're transparent' and 'we're giving away too much'? Luna: I'd say customer names are the first thing to go. No reason they need to know who your other clients are. Lucas: Agreed. And the same goes for specific pricing details with those customers — that's commercially sensitive. But you still need to show gross revenue, net revenue retention, and maybe your burn multiple if you're unprofitable. Luna: So the trend is clear: financial viability is becoming a standard section in enterprise RFPs. What's the smartest way for a SaaS vendor to prepare? Lucas: First, get your financial house in order — even if you're private, consider getting audited statements. Second, have a data room ready with a financial packet that you can customize per deal. Third, rehearse the conversation with your CFO so you're not caught off guard. Luna: And what about the actual response? Do you send a PDF, or is there a standard template? Lucas: There's no universal template yet, but most buyers will provide their own questionnaire. If they don't, you can propose a format: a one-page executive summary of financial health, followed by the detailed financials and projections. The key is to make it easy for the risk team to check their boxes. Luna: I also heard that some vendors are adding a financial viability guarantee to their contracts — like a clause that says if they go bankrupt, they'll help transition the customer or provide escrow services. Lucas: That's a smart proactive move. It shows confidence and gives the buyer a safety net. We covered escrow agreements in episode 147, but tying that to a financial viability clause is a natural evolution. It's like saying, 'We're so sure we'll be here, we'll put our money where our mouth is.' Luna: But for a small vendor, that might be a huge ask. How do you manage that risk? Lucas: You can cap the guarantee — say, the cost of migration assistance up to a certain amount. Or you can tie it to a third-party escrow service. The point is to offer something that mitigates the buyer's fear without putting your own balance sheet at risk. Luna: So what's the one thing a listener should take away from this episode? Lucas: That financial viability is no longer a back-office concern — it's a sales tool. If you can prove you're stable, you can stand out from vendors who treat this as an afterthought. And if you can't prove it, you need to fix that before you chase enterprise deals. Luna: And maybe have that conversation with your CFO before it lands in your inbox. Lucas: Exactly. A little preparation goes a long way. Thanks for listening, everyone. We'll catch you next time.