Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise Software Vendors Turn Customer Success into Expansion Revenue
Transcript
- Lucas: If these conversations are useful for what you're building or running, there's something you should know: we keep this show ad-free by design. No sponsor reads, no pre-rolls, no affiliate noise. Just the conversation. If that matters to you and you want to support it, the link is buy me a coffee dot com slash fexingo. Low-key, one-time, no subscription. Okay — back to enterprise expansion. Luna: Yeah, and it's a nice way to keep the signal clean. Appreciate the folks who chip in. Lucas: Alright. So let's talk about the single most underappreciated growth lever in enterprise SaaS: expansion revenue from existing customers. Luna: And not just churn reduction, but actual growth from the install base. Lucas: Exactly. A lot of founders obsess over new logo acquisition. But the data says the fastest growing SaaS companies — the ones with net dollar retention above 120 percent — grow about two times faster than those below 100 percent, all else equal. Luna: That's from the 2025 SaaS Capital survey, right? The one that tracks private SaaS benchmarks? Lucas: Same survey. And the gap has actually widened since 2023. The top quartile of companies now sit at 130 percent net dollar retention. The bottom quartile is below 90. So the best are getting better at expanding accounts, and the rest are falling behind. Luna: So what are the levers they're pulling? Is it just selling more seats, or are there distinct plays? Lucas: There are really three. First, seat expansion — the classic 'land with 50 users, grow to 500'. Second, product upsells or cross-sells — you land with a core product, then sell the adjacent module. And third, usage-based expansion, where the customer's consumption grows naturally. Luna: Let's start with seat expansion. That seems the most straightforward, but I've seen companies botch it by not having a clear trigger for when to ask for the upsell. Lucas: Right. The best practice is to tie it to a measurable adoption milestone. For example, when a customer hits 80 percent license utilization, that's a signal to start the conversation. If you wait until they're at 100 percent, you've left revenue on the table for months. Luna: And the worst practice is to just send an email saying 'hey, you might want more seats' — no data, no context. Lucas: Exactly. The top companies use product usage data to identify expansion opportunities. They can see which departments are heavy users, which features are sticky, and where there's latent demand. Then they arm the customer success team with that insight. Luna: But that means customer success has to shift from a cost center to a revenue driver. That's a cultural change. Lucas: Huge change. Historically, customer success was about retention and satisfaction. Now, at companies like Salesforce and Zoom, CS teams have expansion quotas. They're measured on net dollar retention. And their compensation is tied to growth, not just keeping the lights on. Luna: I've heard that Zoom's enterprise business grew largely through seat expansion during the pandemic — they landed with one team, and then usage spread organically across the organization. Lucas: That's right. Zoom's product was so viral that seat expansion happened almost passively. But most enterprise software doesn't have that luxury. You need a deliberate motion. Luna: So what about product upsells? That's harder because it requires the customer to see value in a new module. Lucas: It's harder, but the payoff is bigger. The classic example is Salesforce — they landed with Sales Cloud, then upsold Service Cloud, Marketing Cloud, and so on. Each upsell increases switching costs dramatically. The customer becomes more embedded. Luna: But the timing has to be right. You can't upsell a product the customer isn't ready for. Lucas: Exactly. The trigger should be a demonstrated need. If the customer's support team is using spreadsheets to track tickets, that's a upsell opportunity. If they're happy with their current solution, forcing it will backfire. Luna: I remember a cautionary tale from a mid-market CRM vendor that pushed a premium analytics module to a customer that wasn't using their basic reports. The customer felt pressured and churned entirely. Lucas: That's the danger. Expansion has to be value-driven, not quota-driven. If the customer doesn't see the ROI, you erode trust. And trust is the hardest thing to rebuild. Luna: So the third lever — usage-based expansion. That's become more common with the shift to consumption pricing. Lucas: Right. Snowflake is the poster child. They land with a certain amount of compute credits, and as the customer's data grows, their spend grows. The customer doesn't even have to make a new purchase decision — the usage just scales. Luna: But that requires the product to be essential and usage to be elastic. Not every SaaS product can pull that off. Lucas: No, it works best when the product is infrastructure or data-related. For traditional SaaS, you're usually stuck with seat-based or tiered pricing. But even then, you can encourage usage growth by helping customers adopt more features. Luna: So the common thread is that expansion revenue is driven by customer success being proactive, not reactive. Lucas: Exactly. And the best companies structure their CS teams to own the full lifecycle — onboarding, adoption, health, and expansion. They don't hand off to sales when they see an opportunity. They handle it themselves. Luna: That requires a different skill set. CS reps need to be part consultant, part seller. Not everyone can do that. Lucas: True, and that's why compensation models are evolving. Some companies now have a 'land and expand' comp plan where CS gets a commission on expansion revenue, but a smaller percentage than sales. It keeps them focused on value, not just closing. Luna: I've also seen companies use 'expansion pods' — a CS rep, a solutions engineer, and a product specialist assigned to a set of accounts. Lucas: That's a good model. It allows for deep relationship building. And it prevents the common problem of CS being too overloaded to proactively hunt for expansion signals. Luna: Let's talk about metrics. Net dollar retention is the headline, but what underlying metrics should founders track? Lucas: Gross dollar retention is important — that's the percentage of revenue retained from existing customers excluding expansion. If that falls below 90 percent, you're leaking water faster than you can pour it in. Then you need expansion just to stay flat. Luna: And then there's logo retention versus dollar retention. A customer might stay but shrink their spend. Lucas: Right. Dollar retention is more important. You can have 95 percent logo retention but if each account is spending 20 percent less, your net dollar retention is below 100. That's a bad sign. Luna: So what's the takeaway for a founder listening who's early stage, maybe has 20 enterprise customers? Lucas: Start measuring net dollar retention from day one. Don't wait until you have a hundred customers. And build the expansion motion into your product and customer success process early. It's much harder to retrofit later. Luna: And don't let the sales team over-discount upfront just to land a logo, because that compresses the expansion potential. Lucas: Great point. The initial deal size should be reasonable, but not so small that you need massive expansion to make the unit economics work. Aim for a land deal that covers your cost of acquisition within 12 months, then let expansion drive the profitability. Luna: I think the biggest mental shift is seeing the customer relationship not as a one-time transaction but as a recurring revenue stream that should grow over time. Lucas: And that growth is predictable if you set up the right signals, incentives, and processes. It's not magic. It's just disciplined execution. Luna: Alright, next episode we should talk about the flip side — when expansion efforts fail and how to recover. Lucas: I'm already taking notes.