Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How SaaS Vendors Navigate Procurement Friction
Transcript
- Lucas: The biggest myth in enterprise SaaS right now is that procurement is the villain. It’s not. Procurement is just doing its job, which is reducing risk, but they’re measuring it with outdated yardsticks. I’ve been looking at a few recent deal post-mortems from mid-market vendors, and ninety percent of the stalled contracts weren’t killed by price or feature gaps. They were killed because the buyer couldn’t see a clear path to value within their fiscal quarter. Luna: So you’re saying the delay isn’t about the software itself, but the logistics of getting people to use it? That sounds like an operations problem disguised as a sales problem. Lucas: Exactly. And here’s the thing: most sales reps are trained to talk about ROI projections, which are theoretical. But procurement needs certainty. They need to know that when the contract is signed, the implementation team is ready, the data migration is mapped, and the internal champions have time allocated to actually learn the tool. Without that operational proof, the deal goes into what we call the 'black hole' of internal alignment. Luna: It reminds me of that story about the marketing automation platform that lost a deal last month because the client’s IT team didn’t have bandwidth for API configuration until next spring. Lucas: Right. And if the contract starts in October, but the tech stack can’t be touched until April, the buyer looks foolish proposing a ten-month gap to their CFO. So they kill the deal. It’s not malicious; it’s just bad timing. This is why we’re seeing a rise in 'phased rollout' clauses, but even those require more upfront planning from the vendor than most CRMs allow for. Luna: That makes sense. If you can’t prove you’ll fit into their calendar, you don’t fit into their budget. Lucas: Precisely. And this brings us to a specific case study I want to unpack. There was a workflow automation vendor, let’s call them ProcessFlow, that recently had a forty-five thousand dollar monthly deal stall at the signature stage. Security was cleared. Legal had reviewed the DPA. Pricing was approved. But then the procurement officer asked for a detailed week-by-week implementation timeline, including who would do the data cleansing and who would run the user training sessions. Luna: Did ProcessFlow have that level of detail ready? Most startups probably don't. Lucas: They didn’t. Their customer success team was too small to provide a granular schedule, so they sent a generic one-page PDF that said things like 'kickoff meeting' and 'go-live.' The procurement officer rejected it outright. She told the account executive that without resource allocation from both sides, there was no way to guarantee adoption. The deal died three weeks later because the client couldn’t justify the expense without a guaranteed adoption metric. Luna: Wow. So the product worked, but the vendor failed to demonstrate operational competence. That’s a hard lesson for any founder who thinks feature parity wins deals. Lucas: It is. And it’s happening across the board. We’re seeing procurement teams ask for 'adoption playbooks' alongside the contract. They want to see the training materials, the help desk escalation paths, and the success metrics defined before they cut the check. It’s shifting the burden of proof from the sale to the execution phase. Luna: If that’s true, then customer success needs to be involved in the sales process much earlier, not just after the ink is dry. Lucas: 100 percent. In the old model, CS came in late to handle churn risk. Now, CS needs to be part of the close to validate the implementation plan. But most SaaS companies aren’t structured that way. Their sales teams are incentivized to overpromise on speed, and their CS teams are understaffed. You get this misalignment that kills the deal at the finish line. Luna: So the fix isn’t just better sales tactics. It’s aligning internal incentives between sales and delivery. Lucas: Right. And it requires a new kind of collateral. Instead of just slide decks about features, vendors need to produce 'deployment readiness kits.' These are simple documents that outline the client’s responsibilities, the vendor’s timeline, and the mutual dependencies. When a procurement officer sees that level of transparency, it reduces their anxiety. They feel like they’re buying a predictable outcome, not a gamble. Luna: I like that. Predictability is currency right now. Everyone is trying to manage down, so showing you can execute reliably is a huge differentiator. Lucas: It absolutely is. Let’s pause for a second here. If these conversations are useful for what you're building or running, and you want to support the choice to keep this network free of advertising, the link is buy me a coffee dot com slash fexingo. Your support helps us keep digging into these operational details without selling out. Luna: Yeah, it really matters. Ad-free content means we can take the time to explain the nuance instead of rushing to the next sponsored segment. Lucas: Back to ProcessFlow. After the deal died, the account executive went back to the drawing board. He realized that the issue wasn’t the software; it was the lack of operational clarity. He brought in the head of customer success to co-host the final negotiation call. Together, they presented a phased rollout plan. Phase one was a pilot with two departments. Phase two was full deployment after thirty days of usage data confirmed adoption. Luna: That’s smart. It lowers the risk for the buyer while giving the vendor a chance to prove the model. Lucas: Exactly. And it turned a dead deal into a live one. The client signed a smaller initial contract for the pilot, but with a clear path to expand. It’s a win-win because the procurement team gets to validate the solution with minimal exposure, and the vendor gets a foot in the door. It’s slower, yes, but it’s more sustainable. Luna: But doesn’t that hurt your top-line revenue numbers in the short term? Smaller initial contracts mean less immediate cash flow. Lucas: It does, but it protects your net revenue retention. Churn is the silent killer of SaaS valuations. If you sign a big deal but fail to implement it properly, you’ll lose the customer in year two anyway. By slowing down the close to ensure proper onboarding, you’re actually protecting the lifetime value of the account. It’s a trade-off: lower initial ARR for higher LTV. Luna: That’s a tough pill to swallow for founders focused on quarterly growth targets, but mathematically sound. Lucas: It is. And another trend we’re seeing is the rise of 'implementation fees' that are separate from the license cost. Some vendors are charging a upfront fee to cover the cost of dedicated project management during the first ninety days. This signals commitment. It shows the buyer that you’re investing resources to make them successful, which builds trust and reduces procurement friction. Luna: I’ve seen that. It’s like a deposit for success. If you’re willing to pay for the setup, it proves you believe in the product. Lucas: Right. And it filters out buyers who aren’t serious. If a client balks at paying for implementation, they probably aren’t going to use the software anyway. So it’s a good screening mechanism. It saves sales teams from chasing low-intent leads. Luna: So, pricing strategy is becoming part of the operational pitch. It’s not just about the monthly subscription anymore. Lucas: Correct. We’re moving toward outcome-based pricing models in some sectors. Instead of charging per seat, vendors are starting to charge based on transactions processed or workflows completed. This aligns the vendor’s incentive with the buyer’s success. If the buyer doesn’t use the tool, the vendor doesn’t get paid. It forces the vendor to ensure adoption because their revenue depends on it. Luna: That sounds risky for the vendor, though. What if the client’s business slows down? Lucas: It is risky, which is why it’s mostly used in high-volume, predictable environments. But for those cases, it’s incredibly powerful. It removes the fear of 'shelfware'—software that sits unused. Procurement loves it because it ties cost directly to value. Sales teams hate it initially because it’s harder to forecast, but once you get the hang of it, it builds deeper relationships. Luna: Forecasting is always the nightmare for finance teams. How do you predict revenue when it’s tied to client activity? Lucas: You use historical data from similar clients to build a baseline. It’s not perfect, but it’s better than guessing. And many vendors are finding that the stickiness of these contracts is higher because the client feels invested in making the model work. It’s a partnership, not just a transaction. Luna: Partnership is the keyword. Enterprise buying has become so collaborative internally that the vendor has to act like a partner, not just a supplier. Lucas: Spot on. And that requires a shift in mindset. Salespeople need to think like consultants. They need to understand the client’s operational pain points deeply enough to propose a realistic roadmap. It’s a higher bar, but it’s the only way to survive in a market where buyers are skeptical and procurement is ruthless. Luna: So, the soft skills of empathy and operational planning are becoming as important as technical proficiency. Lucas: Absolutely. And for anyone listening who runs a SaaS company, I’d suggest auditing your last ten lost deals. Ask your prospects why they walked away. If the answer is 'timing' or 'readiness,' you might have an implementation gap, not a product problem. Luna: That’s actionable advice. A lot of people just blame the market, but sometimes it’s just their own housekeeping. Lucas: Exactly. The market is tough, but clarity is always valued. If you can remove the ambiguity around how you will deliver value, you unlock the deal. It’s about reducing the cognitive load on the buyer. They don’t need another shiny tool; they need a solution that works without breaking their team. Luna: So, the goal isn’t just to sell software. It’s to sell peace of mind. Lucas: Peace of mind and predictable growth. Those are the two things every CFO cares about. If you can position your implementation process as a driver of both, you’ll cut through the noise. It’s a subtle shift, but in 2026, it might be the difference between closing and churning. Luna: I wonder if this trend will push more vendors toward managed services models, where they take on more of the operational heavy lifting. Lucas: I think it already has. The lines between software and service are blurring. The best vendors are those who treat the technology as the engine, but the service as the vehicle. Without the vehicle, the engine goes nowhere. It’s a holistic view that requires investment, but the returns in loyalty and retention are worth it. Luna: A holistic view. That’s a good way to frame it. It changes the entire conversation from features to outcomes. Lucas: It does. And as we move into Q4, I expect we’ll see more vendors adopting these phased, operationally rigorous approaches. The ones who don’t adapt will find themselves stuck in the black hole, waiting for a signature that never comes. Luna: So, the question isn’t just what you sell, but how you deliver it. That’s a powerful distinction. Lucas: It is. And for the listeners out there building the next generation of enterprise tools, maybe it’s time to stop selling the dream and start selling the plan.