Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Reps Are Selling to the CFO's FP&A Team
Transcript
- Lucas: If you've been following enterprise software sales over the last few years, you know the rep's job has gotten harder. It used to be you sold to the IT director, maybe the line of business VP, and if the demo went well, the deal got done. Now there's a whole committee. Luna: Procurement, legal, security, finance. We've done episodes on each. But there's one group within finance that I think is the quietest bottleneck of all. Lucas: The FP&A team. Financial Planning and Analysis. And what's interesting is that FP&A analysts aren't typically in the room for the demo. They don't talk to the vendor. But their spreadsheet—that rolling forecast model they update every month—that spreadsheet is the real decision-maker. Luna: So the rep never even meets the person who's actually killing the deal? Lucas: Exactly. And it's becoming a bigger problem. I talked to a VP of sales at a mid-market SaaS company last week. He told me about a deal with a financial services firm—call it a regional bank—that had been in pipeline for six months. The CFO was on board, the CISO had signed off on security, legal had approved the contract. Then it got killed at the eleventh hour. Luna: By FP&A? Lucas: By a senior FP&A analyst who ran a cost-benefit model and decided the software's projected productivity gains didn't meet the company's internal hurdle rate. The rep never even knew the analyst's name. Luna: Hurdle rate being the minimum return the company expects on any investment? Lucas: Right. And FP&A teams are getting more sophisticated. They're applying the same discipline they use for capital expenditures to software subscriptions. A $500,000 annual SaaS contract? That's a capital allocation decision now. They want to see a discounted cash flow analysis, not a slide deck with smiley faces. Luna: So the rep has to sell to a spreadsheet they can't see. How do you even start? Lucas: You have to understand what's in that spreadsheet. And the single most important number is the company's weighted average cost of capital, or WACC. That's the discount rate they use to calculate the net present value of future savings. If your ROI calculator assumes a 10 percent discount rate and their WACC is 14 percent, your payback period just got longer by months. Luna: And the rep probably doesn't know their prospect's WACC. Lucas: Almost never. Public companies disclose it in their annual filings, but most reps don't look. And for private companies, you have to estimate based on industry benchmarks. The best reps now ask procurement, during the business value assessment stage, 'What discount rate do you use for capex analysis?' And if they get a blank stare, they know FP&A isn't involved yet—and they have a window. Luna: That's a great tactical point. I heard a story from a friend in procurement at a large retailer. She said their FP&A team built a shadow P&L for every software contract over $250,000. They modeled not just the subscription cost but also the internal implementation hours, the training downtime, the opportunity cost of the team not doing their day job. Lucas: And the vendor's ROI calculator never factors in those internal costs. So the true total cost of ownership can be two to three times the contract value. FP&A knows that. The rep, if they're not careful, is selling against a phantom number. Luna: So what's a rep supposed to do? Give up? Lucas: No, they need to preempt it. The best play is to provide a data room that FP&A can pull into their model. Not a PDF, but a spreadsheet with unit economics—cost per user, cost per transaction, implementation hours broken out by phase, assumptions about ramp-up time. The more granular, the more credible. Luna: And that also means the rep has to understand their own unit economics. Not just list price, but what it actually costs to deliver the software and support it. Lucas: Exactly. I saw a case where Salesforce lost a deal—a $2 million annual contract with a mid-cap insurance company—because the buyer's FP&A team ran their own model and found that the productivity gains Salesforce claimed didn't materialize until year three, but the company's internal payback threshold was 18 months. Salesforce's standard ROI calculator didn't account for that. The rep never knew. Luna: And there's no way to recover from that if you don't know the threshold going in. Lucas: Right. Which is why the smartest enterprise reps now request a meeting with the FP&A team during the evaluation. They don't ask for a meeting with the CFO—that's too high-level. They ask for a working session with the senior analyst who owns the software budget. And they come prepared with a model, not a slide deck. Luna: Do they actually get that meeting? Lucas: More often than you'd think, especially if the rep has already established credibility with the line of business buyer. The line of business VP can say, 'Look, the vendor's willing to share their assumptions—let's have a 30-minute call.' And once FP&A sees that the rep understands their language, the trust goes up. Luna: And the rep can also learn what the analyst is actually worried about. Maybe it's not the payback period—maybe it's the risk of switching costs or the impact on the team's headcount. Lucas: Exactly. I heard of a deal where the FP&A analyst was concerned that the new software would automate a manual process currently done by three junior analysts. The rep was able to reframe the value: not as 'you can fire those three people' but as 'those three people can now do higher-value analysis.' That made the model look better because it didn't show headcount reduction risk. Luna: It's basically selling to the person who builds the model that the CFO uses to say yes or no. Lucas: Exactly. And here's the thing—FP&A teams are under pressure too. They're being asked to do more with less. A lot of them have adopted rolling forecasts, which means they update their budget models every month instead of once a quarter. That creates more opportunities for a deal to get re-evaluated. Luna: So it's not just about getting the initial approval—you have to stay in the model. Lucas: Right. A deal that gets signed in Q1 might get flagged in Q2 if the company's revenue comes in light. FP&A will look at all discretionary spend, and a new software contract is an easy target. So the rep needs to build a relationship with the post-sales team at the buyer to ensure the value is being tracked and reported back. That way, when FP&A reviews the model, they see actual realized savings, not just projected ones. Luna: That's a whole new level of post-sale engagement. Most SaaS companies hand off to customer success and never think about FP&A again. Lucas: And that's why churn happens. The initial champion leaves, the new CFO's FP&A team runs the numbers again, and the contract gets non-renewed. The vendor never even knew the model was being updated. Luna: So the lesson is: sell to the spreadsheet. Or better, sell to the person who owns the spreadsheet. Lucas: That's the headline. And if this kind of practical, tactical insight is valuable to you—if you're building or running a business where these dynamics play out—the way we keep this show ad-free and focused on stuff like this is through listener support. If you found this useful, you can buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. It genuinely helps us keep the conversations going without interrupting them. Luna: Yeah, it's a small thing that makes a big difference for us. And we really appreciate it. Lucas: So back to FP&A—one more tactical takeaway. The most effective reps I've seen don't wait for procurement to ask for a business value assessment. They proactively build a three-year model in the buyer's format and share it with the FP&A team. That way, they control the assumptions. Luna: And if the assumptions are honest, that builds trust. If they're too aggressive, it backfires. Lucas: Exactly. Honest assumptions—maybe even conservative ones—that you can defend. That's how you become a partner, not just a vendor. And that's how you survive the spreadsheet. Luna: I think that's a good place to wrap. Next episode, we'll talk about something I've been hearing more about: how procurement teams are starting to use AI to audit vendor contracts. Should be interesting. Lucas: Yeah, that's a real frontier. Until then, thanks for listening.