Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise RFPs Now Ask Vendors About Their Pricing Models
Transcript
- Lucas: So there's a question that's started showing up in enterprise RFPs that I don't think we've ever talked about on the show, and it's not about security or AI governance or any of the other things we've covered. It's literally, and I'm quoting a procurement doc from a large European bank here, 'describe your pricing model in detail, including how it adapts to changes in customer usage.' Luna: That's a big shift. A couple of years ago, pricing was just a line item at the back of the RFP, if it was there at all. Now they're asking vendors to explain their pricing model like it's part of the architecture. Lucas: Exactly. And I think it's because buyers have gotten burned. There's this thing called subscription fatigue — IT leaders are looking at their SaaS stack and realizing they're paying for licenses that barely get used, and they're pushing back. They want to know, before they sign, exactly what happens when usage goes up or down. Luna: And this is where the ad-free thing comes in for us. We keep these conversations going because we think they're genuinely useful for people who build and run software. If you find value in that, supporting us at buy me a coffee dot com slash fexingo is what keeps it that way. Lucas: Yeah, no ads, no sponsors, just the research. And we're back to pricing models because that's the thing that's actually changing how deals get won and lost. Luna: So walk me through a concrete example. What does a bad pricing model answer look like in an RFP? Lucas: So there's a mid-market CRM vendor — I won't name them — who recently lost a seven-figure deal because their pricing was a flat per-seat fee. The buyer, a logistics company, had a seasonal workforce. Their headcount spiked by forty percent during peak season, and they'd have been paying for seats that sat idle for half the year. The vendor couldn't flex, and the buyer walked. Luna: Ouch. And I've seen the flip side too — a procurement team at a manufacturing firm told me they now ask every vendor to model their total cost of ownership over three years, including implementation and training costs, not just the license fee. They got a quote that was fifty percent higher than the sticker price once they added it all up. Lucas: That's the core of it. Procurement folks are becoming amateur financial analysts. They're not just comparing prices; they're stress-testing the pricing model itself. Will this pricing scale with our usage? What happens if we double our users? What if we cut them in half? A rigid pricing model is starting to feel like a red flag. Luna: And it's not just the bank or the manufacturer. I've seen RFPs from mid-sized tech companies that ask for a detailed breakdown of how the vendor calculates their pricing — what metrics, what triggers a price change. It's almost like they're auditing the vendor's revenue model. Lucas: Right. And here's the thing — this is a relatively new development. Historically, pricing was a commercial term you'd negotiate after the vendor was shortlisted. Now it's a technical evaluation criterion alongside security and architecture. That changes the sales cycle in a fundamental way. Luna: Because the sales rep can't just say 'we'll work out the details later' anymore. They have to come to the table with a clear, defensible pricing model that holds up under scrutiny. Lucas: Exactly. And I think that's why we're seeing more vendors preemptively publish their pricing pages. Not just the vague 'contact us' but actual numbers. It's a way to get past the first filter. If your pricing is transparent, the buyer assumes you're confident in your value. Luna: But does that actually work? I mean, enterprise deals are almost never signed at list price. Doesn't publishing pricing just invite more negotiation? Lucas: It's a trade-off, for sure. But the data we've seen suggests that vendors who publish pricing see shorter sales cycles — buyers come in more qualified, and they've already budgeted for the product. Negotiation still happens, but it's less about the basics and more about terms like payment schedules or multi-year commitments. Luna: That makes sense. And I've noticed that some vendors are now offering usage-based pricing as a differentiator — like, 'you only pay for what you use.' But that can be scary for the vendor because it introduces revenue uncertainty. Lucas: It does, and that's the other side of the coin. The buyer wants flexibility, but the vendor needs predictable revenue to run a business. So we're seeing hybrid models — a baseline subscription that covers a certain amount of usage, with overage charges beyond that. It's a compromise. Luna: And that's actually what the bank's RFP was asking for — 'how does your pricing adapt to changes in customer usage?' A hybrid model answers that better than a flat fee or pure usage-based pricing. Lucas: Yeah. And I think the smart vendors are the ones that model this for the buyer in the RFP response. They'll say, 'here's what your total cost would be if you use this much, and here's what it would be if you use fifty percent more.' That kind of proactive analysis is what wins points. Luna: It's almost like they're doing the procurement team's job for them. And that's probably a good strategy, because procurement is often stretched thin and appreciates vendors who make their life easier. Lucas: For sure. But there's also a risk. If a vendor builds their pricing model in a way that's too complicated — too many tiers, too many variables — the buyer might just see it as a way to hide costs. Clarity is key. Luna: And I think that's the real lesson here. The pricing model isn't just a commercial detail anymore; it's a signal of how the vendor thinks about partnership. If you're transparent and flexible, you're signaling that you're in it for the long haul. Lucas: Right. And that's why I think we're going to see more RFPs like the bank's, and more vendors getting asked these tough questions early. It's a shift that rewards vendors who've actually thought through their pricing strategy, and it punishes the ones who just tack on a per-seat fee and hope for the best. Luna: So for the sales rep listening, what's the one thing they should do differently tomorrow? Lucas: I'd say, before you send your next RFP response, sit down with your finance team and model out three scenarios — low usage, expected usage, high usage. If you can show the buyer exactly what their cost looks like in each scenario, you're way ahead of the competition. Luna: And if you're on the buyer side, I'd say, push for that kind of analysis. Don't settle for a flat price. Ask the vendor to show you how the pricing flexes with your business. If they can't, that's a red flag. Lucas: Yeah, and I think that's the forward-looking piece. Pricing models are becoming a core part of enterprise software evaluation, and it's only going to get more sophisticated. The vendors who embrace this will win; the ones who don't will find themselves losing deals they thought they had in the bag. Luna: Well, that's a great note to end on. Thanks for listening, and we'll catch you next time on B2B SaaS Talks.