Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise Software Deals Now Require an Implementation Success Plan
Transcript
- Lucas: So you've got the contract signed, the security questionnaire approved, the pricing negotiated. But now there's a new gate before the deal is truly done: the Implementation Success Plan, or ISP. Luna: I've been hearing this term more and more from procurement contacts. It's not just a project timeline — it's becoming a contractual deliverable. Lucas: Exactly. And it's a direct response to a very expensive problem. According to a Gartner study from last year, nearly 30 percent of six-figure SaaS deals fail to achieve full deployment within the first twelve months. That's millions in shelf-ware. Luna: Ouch. So buyers are saying, 'We're not just buying your software — we're buying your ability to get us live and using it.' Lucas: Right. And they're codifying that expectation. We're seeing RFPs now that include a mandatory ISP appendix. If the vendor can't provide a detailed, pre-signed implementation roadmap with milestones and penalties, they're disqualified. Luna: This is a big shift from even two years ago. Then, implementation was a post-sale handoff to services. Now it's part of the deal negotiation. Lucas: Before we dive deeper — and I want to get into a specific deal I heard about — I want to say something about this show. We deliberately don't run ads on these episodes. No sponsors, no mid-roll interruptions. And that's a choice we've made because we think this kind of conversation — operators and builders talking shop — shouldn't be cluttered. Luna: It's one of the reasons I love doing this show. We get to go deep without a break. Lucas: If you find these discussions useful for what you're building or running, and you want to support that ad-free mission, there's a simple way: buy me a coffee dot com slash fexingo. That's it. No pressure, no perks, just knowing you're keeping the conversation independent. Luna: And speaking of independent, let's get back to that deal. Lucas, you mentioned a CRM vendor. Lucas: Yeah. There's a mid-market CRM company — I'll leave them unnamed — that was competing for a $2.4 million annual contract with a financial services firm. The product was a great fit, the pricing was competitive, the security review passed. But when the buyer asked for the Implementation Success Plan, the vendor's response was basically a one-page timeline: 'Month one: data migration. Month two: training. Go live.' Luna: That's not a plan. That's a wish. Lucas: The buyer's procurement team rejected it. They wanted specific milestones with dates, resource commitments from both sides, risk mitigation steps, and penalties if milestones slipped. The vendor couldn't commit. They lost the deal to a competitor who had a detailed ISP ready to sign. Luna: So what did that winning ISP look like? What level of detail are we talking? Lucas: I spoke to a procurement leader at a manufacturing company who now requires ISPs. She said the best ones include: a named project manager from the vendor, weekly status calls for the first 90 days, a joint governance committee that meets monthly, success criteria for each phase, and financial penalties tied to missed milestones — usually a percentage of the annual contract value. Luna: Penalties. So if the vendor doesn't deliver the data migration on time, they owe the buyer money. Lucas: Exactly. And it's not just about punishment. It's about alignment. The vendor has to staff the project properly from day one. They can't just hand it off to a junior implementation consultant. Luna: This feels like a natural evolution of the procurement function. They've already professionalized security reviews, pricing negotiations, and contract terms. Implementation was the last unmanaged risk. Lucas: Completely agree. And the data backs it up. The same Gartner study found that deals with a formal ISP had a 40 percent higher likelihood of full deployment within the first year. That's a massive improvement. Luna: So for vendors, this is a competitive differentiator. If you can show up with a polished ISP, you're ahead of the pack. Lucas: But it's also a cultural shift. Sales reps hate being asked to commit to implementation details before the deal closes. They want to close and move on. But the best reps are learning to sell the implementation as part of the product. Luna: How do they do that? I imagine it requires a lot of coordination with customer success and professional services. Lucas: It does. Forward-thinking vendors are creating 'deal desk' teams that include a sales engineer, a customer success manager, and a professional services lead. They collaborate on the ISP during the sales process. That way, when the buyer asks for it, it's ready to go. Luna: So the ISP becomes a shared artifact between sales and delivery. That's a big organizational change. Lucas: It is. And it's spreading beyond just software. I'm seeing similar requirements in hardware as a service deals and even some consulting engagements. Any recurring revenue model where deployment is critical. Luna: And what about the buyer side? Are they standardizing their ISP requests? Lucas: Some are. Large enterprises with mature procurement teams have templates. They ask for the same structure from every vendor. But smaller buyers are still figuring it out. They might just ask, 'What's your implementation plan?' and judge based on the answer. Luna: That's a risk for them too. If they don't know what to ask for, they might accept a weak plan. Lucas: Exactly. So the best procurement teams are educating themselves. There are now industry benchmarks for implementation timelines based on deal size and complexity. For a million-dollar deal, a realistic timeline might be six to nine months. Luna: And what about the penalties? Are they becoming standard? Lucas: They're common but not universal. Many vendors push back, arguing that implementation depends on the buyer's readiness too — data quality, stakeholder availability, internal resources. So we're seeing shared-risk models: if the vendor misses a milestone due to their fault, they pay a penalty. If the buyer causes the delay, the timeline extends. Luna: Seems fair. It aligns incentives on both sides. Lucas: It does. And it forces honest conversations early. Instead of promising a three-month go-live that everyone knows is unrealistic, the vendor and buyer agree on a realistic plan from the start. Luna: This also changes the role of the sales rep. They have to understand implementation constraints before they promise anything. Lucas: Right. The old-school rep who says 'we can have you live in 60 days' without checking with services is becoming a liability. The new-school rep says, 'Let me bring in our implementation team to scope this properly.' That builds trust. Luna: And trust is what gets deals done, especially in enterprise. Lucas: So the message for vendors is clear: invest in your implementation planning capability. It's not a cost center — it's a sales enablement tool. And for buyers: if you're not asking for an ISP, you're leaving money on the table. Luna: I've seen some procurement teams now include ISP quality as a weighted criterion in their vendor scorecard, alongside functionality and price. Lucas: That's the next frontier. Just like security questionnaires became standardized, I think we'll see ISP scorecards become common. Vendors will compete on implementation confidence as much as product features. Luna: And the winners will be the ones who treat implementation not as a handoff, but as a core part of the product experience. Lucas: Exactly. Because at the end of the day, the software only delivers value if it's actually used. The ISP is the bridge between the contract and the outcome. Luna: And that bridge is getting a lot more scrutiny. Great topic. Lucas: Thanks, Luna. We'll keep watching how this evolves. For now, if you're in procurement or sales, start thinking about your Implementation Success Plan — it might be the difference between winning and losing the next deal.