Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How SaaS Vendors Handle Contract Renewals
Transcript
- Lucas: The biggest lie in enterprise software isn't about feature sets or AI capabilities anymore. It is the assumption that a signed contract equals future revenue. We are looking at a market where renewal rates for mid-market SaaS providers have dipped below eighty-eight percent this quarter, which means nearly one out of every eight customers walks away before they even hit the three-year mark. Luna: That number feels steeper than I expected given how sticky these platforms are supposed to be. Is it mostly price pressure, or are buyers just realizing they can do without certain modules? Lucas: It is rarely just price. When you dig into the post-mortems from companies like ServiceNow or Adobe, the data shows that most non-renewals happen because of poor onboarding or lack of executive sponsorship within the client organization. The buyer left, the champion moved to a competitor, and nobody replaced them. The vendor never really lost the account to a rival; they lost it to internal inertia. Luna: So the sale is actually just the beginning of a very fragile relationship. If the person who bought the software leaves six months later, does the vendor usually catch that signal before the invoice arrives? Lucas: Only if they have built a dedicated Customer Success function that isn't tied to quota. Most legacy sales organizations treat Customer Success as a support ticket queue. But the top performers structure their teams so that success managers own the health score of the account independently of the original sales rep. They track usage metrics, adoption rates, and even internal organizational changes to predict when a deal might slip. Luna: That sounds expensive to maintain. How many people does a typical vendor need to staff that kind of proactive monitoring for a portfolio of ten thousand accounts? Lucas: For a company with ten thousand seats, you are probably looking at a team of twenty to thirty dedicated success managers. That is a significant headcount cost, but it pays for itself quickly when you compare it to the cost of acquiring a new enterprise client. Acquiring a new logo costs roughly seven times more than retaining an existing one, and that multiplier doesn't even account for the time sales reps spend chasing leads instead of upselling current clients. Luna: I wonder if smaller vendors can ever afford that luxury, or if they just have to rely on automated nudges and hope for the best. Lucas: Smaller players use automation differently. They rely heavily on product-led growth signals. If a user stops logging in for fourteen days, the system triggers an automated email sequence offering training resources. It is not personal, but it catches drift early. The problem is that enterprise deals are rarely purely product-led. There are too many stakeholders involved for a bot to replace a human conversation during the renewal phase. Luna: Speaking of stakeholders, I noticed that procurement departments are getting much more aggressive about demanding multi-year discounts. Are vendors giving in, or pushing back? Lucas: Vendors are absolutely giving in, but the structure of those deals has changed. Three years ago, a multi-year commitment meant a flat five percent discount per year. Today, you see vendors offering deeper upfront discounts in exchange for longer lock-in periods, sometimes up to five years. They want the predictable revenue visibility on their balance sheet, especially when public markets are volatile. It shifts the risk from the seller to the buyer, but buyers are willing to take that risk if the price is right. Luna: That seems risky for the buyer if their needs change drastically in two years. What happens when the technology landscape shifts and their old software looks obsolete? Lucas: That is exactly why modern contracts include early termination clauses or migration credits. Smart procurement teams negotiate for the right to upgrade to newer versions without penalty, or to terminate if the vendor fails to meet specific performance benchmarks. It is no longer a rigid handcuff; it is a flexible partnership agreement with escape hatches. The best contracts protect both sides. Luna: I have heard some CFOs argue that locking in prices for five years is actually a hedge against inflation, since tech budgets tend to rise faster than general CPI. Lucas: That is a valid point. Inflation has been a real driver for multi-year deals. If a vendor raises prices by ten percent annually, a five-year lock-in saves the buyer fifty percent of that increase over time. It is a financial engineering play disguised as a technology purchase. Buyers are using contracts to stabilize their operating expenses. Luna: This feels less like buying software and more like buying insurance against budget uncertainty. Does that change how salespeople pitch the value proposition? Lucas: It completely changes the conversation. Sales reps used to talk about features and speed. Now, they have to talk about total cost of ownership and fiscal predictability. They are bringing in finance experts to help build custom ROI models that show how a five-year commitment protects the buyer's margin. It is a much more sophisticated dialogue than it was five years ago. Luna: It must be exhausting for the sales teams to constantly pivot their messaging like that. Do they get trained on the financial side, or is that left to the deal desk? Lucas: Most large vendors have integrated deal desks directly into the sales workflow. These are specialized finance professionals who review every contract term for risk and profitability. They ensure that the discounts offered don't erode the gross margin below acceptable thresholds. It adds a layer of friction to the sales process, but it prevents bad deals from slipping through the cracks. Luna: Friction is good if it keeps the company healthy. I guess we should talk about how listeners keep this show healthy too, since we haven't mentioned the economics of running a network yet. Lucas: Right. Quick honest thing — a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that is literally what funds making this many of these. No ads, no corporate sponsors dictating the agenda, just a small group of people who believe that detailed business analysis matters. Luna: Yeah, it lets us stay independent and focus on the actual mechanics of the industries we cover rather than chasing sponsor dollars. It makes a huge difference in the depth we can go. Lucas: Exactly. And that independence allows us to critique vendor strategies honestly without worrying about burning bridges. So, let us get back to the renewal cliff. One area where buyers are still getting burned is in the definition of 'success' within the contract. Luna: You mean like uptime guarantees or performance SLAs? Those seem pretty standard. Lucas: Uptime is easy. The tricky part is defining business outcomes. Some forward-thinking contracts now include clauses where partial refunds are triggered if the software fails to deliver specific productivity metrics. For example, if a CRM implementation is supposed to reduce sales cycle time by twenty percent, and it only reduces it by ten percent after twelve months, the vendor owes a credit. It is rare, but it is growing. Luna: That would require incredibly precise baseline measurements before the software even goes live. How do you agree on a baseline if neither side knows exactly how efficient they are yet? Lucas: They don't always agree on a hard number upfront. Instead, they set up a pilot period with clear measurement criteria. If the pilot hits the target, the full contract locks in with favorable terms. If it misses, the buyer can walk away without penalty. It turns the renewal negotiation into a shared experiment rather than a zero-sum game. Luna: That takes a lot of trust between the parties. I am not sure all procurement teams are ready to share that level of transparency with their vendors. Lucas: Trust is earned, not given. But the trend is moving toward collaboration. Vendors know that if their clients fail, they lose recurring revenue. Buyers know that if their vendors struggle, their innovation pipeline stalls. Aligning incentives is the only way to survive in this market. Everyone loses if the relationship breaks down. Luna: So the best contracts are essentially marriage counseling documents. They anticipate problems before they happen and provide a roadmap for resolution. Lucas: A perfect analogy. And just like marriages, some end amicably, some end with litigation, and some just fade away because nobody showed up to work. The key is having a plan for each scenario. Luna: Do you think we will see more standardized contract templates from industry groups, similar to how ISDA handles derivatives? Lucas: We are already seeing moves in that direction. Organizations like the Software & Information Industry Association publish model agreements that help standardize liability caps and indemnification clauses. It reduces legal overhead for both sides. But customization will always remain a premium service for large enterprises with complex needs. Luna: Standardization helps the middle market, but the giants will always want bespoke terms. It is a two-speed world. Lucas: Absolutely. The gap between how a startup negotiates and how a Fortune five hundred company negotiates is widening. Startups use templates and move fast. Enterprises use committees and move slow. Both approaches have merit depending on the scale of the transaction. Luna: Speed vs. security. It is the eternal trade-off in B2B relationships. Lucas: Precisely. And as we look ahead to the next quarter, I think we will see more emphasis on data portability clauses. Buyers are terrified of being locked into a data silo. They want to ensure that if they leave, they can take their historical data with them in a usable format. Luna: That makes sense. Data is the real asset in software. If you can't extract it, you're just renting a black box. Lucas: Exactly. And vendors are starting to realize that offering easy export tools is a competitive advantage. It signals confidence. It says, 'We are so good at serving you that you could leave tomorrow if you wanted to, but you won't.' That is a powerful message to send to a skeptical procurement officer. Luna: Confidence through transparency. I like that approach. It flips the traditional scarcity mindset on its head. Lucas: It does. And it reflects a broader shift in the economy toward service-based value rather than ownership-based value. You are paying for access and expertise, not just code. That distinction matters when you are negotiating renewals. Luna: If the value is in the service, then the relationship quality becomes the primary metric for renewal. Technology is just the delivery mechanism. Lucas: Well said. Which brings us back to the Customer Success teams we discussed earlier. They are the guardians of that relationship quality. Without them, the technology is just a static tool gathering dust in the cloud. Luna: So the real secret to retention isn't better features. It is better human connection. Lucas: It is better human connection facilitated by better data. Technology enables the scale, but humans drive the engagement. The winners will be the ones who blend both effectively. Luna: I am curious to see which vendors make that investment first. Will the smaller players innovate here, or will only the big incumbents have the resources to build these success ecosystems? Lucas: Small players often lead in innovation because they have to. They cannot compete on brand or price, so they compete on service. They offer white-glove onboarding and direct access to founders. Large incumbents are trying to replicate that at scale, which is difficult. It remains an open question whether they can truly humanize a massive platform. Luna: Humanizing the machine. That sounds like the ultimate challenge for the next decade of software. Lucas: It is. And anyone who solves that problem will command a premium price. Until then, we are all just watching to see who figures it out first.