Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise RFPs Now Ask About Vendor Support SLAs
Transcript
- Lucas: So we got a note from a procurement director at a mid-size logistics company, and she said something that stopped me: 'Your support SLA is a deal-breaker if it says best effort.' Not uptime, not security — support response times. Luna: Interesting. So she's reading the fine print before she even talks to sales? Lucas: Exactly. And she's not alone. I've seen more RFPs in the last year with a section that's just dedicated to support service levels. They want specific numbers, not vague promises. And if you can't match their expectations, they walk. Luna: What kind of numbers are we talking? Like, response within four hours? Lucas: That's part of it. But it's more nuanced. They're asking for response-time tiers based on severity. A P1 — that's a critical outage — they want a response in under fifteen minutes, and a resolution target in under four hours. For a P2, maybe an hour for a response, a business day for a fix. Luna: And if you don't hit those numbers? Lucas: That's where it gets interesting. They want penalty clauses. Automatic service credits, or even a right to terminate if you miss the targets too often. This used to be reserved for infrastructure vendors, but now it's in software RFPs. Luna: So a missed SLA could literally cost you revenue, not just goodwill. Lucas: Right. And that changes how you price your support tier. You can't just give away enterprise support if you might have to pay credits every time something breaks. Luna: Have you seen this in actual deals? I mean, a vendor actually walking away because they couldn't commit? Lucas: Yes. Last quarter, I heard about a seven-figure deal that died during negotiation because the vendor's SLA said 'commercially reasonable efforts' for P1 response. The buyer wanted thirty minutes, the vendor could only commit to two hours. They compromised on the price, but not on the SLA. The vendor wouldn't budge, and the buyer walked. Luna: That's a big miss for something that's just operational, maybe? Lucas: But the buyer saw it differently. Their internal cost of downtime is huge. They calculated that every hour of a critical system being down costs them about $250,000 in lost productivity and shipment delays. So a four-hour response time could mean a million dollars in losses. They needed a guarantee. Luna: So support is suddenly a financial risk metric, not a service checklist. Lucas: Exactly. And that's why we're seeing procurement teams bring in their own experts to assess vendor support capabilities. They're not just asking 'what's your average response time?' They're asking 'how many support engineers do you have per customer?' 'What's your after-hours coverage?' 'Do you have a follow-the-sun model?' Luna: So it's not just about saying the number — it's about being able to back it up with staffing and processes. Lucas: Right. And that's where a lot of SaaS companies trip up. They promise 24/7 support, but they have one on-call engineer with a pager. If that engineer is asleep, your response time is going to be closer to three hours than fifteen minutes. Luna: So what's the right way to structure a support SLA that doesn't scare off buyers but also doesn't put you at risk? Lucas: First, be realistic about what you can deliver. Start with your historical data — what's your actual average response time? If you're hitting forty-five minutes consistently, don't promise fifteen. You'll just be setting yourself up for penalties. Luna: But what if the buyer demands fifteen anyway? Lucas: Then you have a conversation about what it would take to get there — maybe they need to buy a higher support tier. But that's actually a good outcome because you're turning a risk into a revenue opportunity. Luna: So the SLA becomes a pricing lever, not just a legal obligation. Lucas: Exactly. And you can also structure it with credits that are a percentage of the monthly fee, so the exposure is limited. For example, if you miss a P1 response target, they get a five percent credit for that month. That's a lot easier to swallow than a full refund. Luna: And what about the uptime guarantee? Is that separate? Lucas: Yeah, uptime is usually its own SLA. And we're seeing buyers ask for 99.9 percent uptime as a baseline now. For a SaaS product, that's about forty-three minutes of downtime a month. That's achievable if you have a solid infrastructure and a good deployment process. Luna: But what about the trade-off? If you're a smaller vendor, can you realistically offer that? Lucas: It depends on your product and your engineering culture. If you're on a single instance in one region, 99.9 percent is hard. But if you're multi-tenant and you've designed for failure, it's doable. Just be honest about your architecture. Luna: I've also seen some RFPs ask for a defined escalation matrix. Like, what happens if you don't meet the response time? Who gets notified? Lucas: Yes, that's becoming standard. They want to know that if a critical ticket comes in at 2 a.m., there's a clear path to a senior engineer, not just a helpdesk person reading from a script. Luna: So it's really about proving you have the operational maturity to support their business. Lucas: And that's why we're seeing vendors start to publish their support SLAs on their website, almost like a badge of honor. It's a trust signal. If you're confident enough to put your numbers out there, it says a lot about your reliability. Luna: But isn't there a risk that publishing your SLA makes you a target? Like, if a competitor sees you promise fifteen-minute response, they might try to outdo you. Lucas: Possibly, but that's a good problem to have. It pushes the whole industry to be better. And buyers love it because they can compare apples to apples. Luna: So what's the takeaway for a B2B SaaS founder listening to this? Lucas: Don't treat support SLAs as a legal afterthought. Bring your sales, engineering, and support teams together early to define what you can actually commit to. Use your historical data to back it up. And remember that a well-structured SLA can be a competitive advantage, not a burden. Luna: And if you're on the buyer side, push for specific numbers and penalties. A vendor who hesitates is a red flag. Lucas: Exactly. And that's also the kind of thing that keeps this show ad-free. If today's insight saved you a headache or helped you win a deal, you could keep us going with a coffee. Just go to buy me a coffee dot com slash fexingo. It's a small gesture, but it matters. Luna: Yeah, and every little bit helps us keep bringing you these deep dives. Lucas: So back to that SLA structure. One more thing I want to mention is the concept of 'credits versus termination.' Some buyers want the right to terminate if you miss SLA targets multiple times in a quarter. That's a big ask, but if you're confident in your service, you can push back and offer higher credits instead. Luna: So it's a negotiation. Lucas: Always is. And the best way to negotiate is with data. Bring your actual response times and uptime percentages to the table. That gives you credibility and helps you push for terms that are fair to both sides. Luna: And what about the sales cycle? Does having a strong SLA actually speed things up? Lucas: It can. I've seen deals where the SLA was the last sticking point, and having a clear, generous SLA took that off the table. It removes friction. And buyers are more likely to trust you if you're transparent. Luna: So it's not just about avoiding penalties; it's about building trust. Lucas: Exactly. And in a world where buyers are more risk-averse than ever, that trust is currency. So if you're a SaaS founder, take a hard look at your support SLAs. Are they strategic, or are they just boilerplate? Because your buyers are noticing. Luna: I think that's a great place to leave it. Thanks for the insight, Lucas. Lucas: Thanks, Luna. And thanks to everyone listening. We'll be back on Friday with another deep dive.