Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Deals Require a Mutual Action Plan
Transcript
- Lucas: If these conversations are useful for what you're building or running, you might've noticed we don't run ads on this show. That's deliberate — we want the conversation to flow without interruption. If you like that approach, the simplest way to support it is buy me a coffee dot com slash fexingo. No pressure, just an option for listeners who find value here. Luna: Yeah, I appreciate that we keep it clean. It makes the whole thing feel more like a real conversation. Lucas: So let's talk about something that's quietly become table stakes in enterprise software sales: the Mutual Action Plan. MAPs are everywhere now, but I'm not convinced every team uses them well. Luna: I've seen those — basically a shared timeline with milestones, right? But isn't that just a fancy Gantt chart that the vendor pushes on the buyer? Lucas: That's exactly the risk. A bad MAP is a vendor-driven checklist. A good MAP is a co-owned project plan that both sides use to track progress, flag risks, and escalate when things get stuck. Luna: What changed? I've been in procurement at a company that never asked for one. Now I hear about them constantly. Lucas: A few things. First, enterprise sales cycles have stretched out — we talked about that in episode 3. When a deal takes nine months, you need structure. Second, procurement teams started demanding more transparency. They don't want to be surprised by a stalled review or a missing signature. Luna: So procurement actually likes MAPs? That seems counterintuitive. Usually they hate anything that feels like vendor process. Lucas: They like them when the MAP is mutual. DealDesk put out a study last year — 2024 — on about 400 enterprise deals. The data showed that deals with a formal MAP were 23% more likely to close on time. And the average cycle time was 18 days shorter. Luna: Eighteen days? That's meaningful. Especially if you're a vendor trying to hit a quarter-end. Lucas: Exactly. But the key word is 'mutual.' The best MAPs are co-authored in a working session with the buyer's procurement lead and the economic buyer. Not just the champion. If the vendor writes it alone and emails it over, it's just a to-do list. Luna: What does a well-built MAP look like? Give me the anatomy. Lucas: Sure. You start with the target close date — agreed by both sides. Then you list every major step: demo, technical validation, security review, legal, final pricing, signature. Each step has an owner on both sides and a due date. Then you add a risk register — what could go wrong and who escalates. Luna: So it's a living document, not a static spreadsheet. Lucas: Right. It gets reviewed every week in a fifteen-minute call. If a milestone slips, you talk about it immediately. The discipline is what drives the results. Luna: I can see where this could go wrong. What are the common mistakes? Lucas: Biggest one: the vendor owns the whole thing. They update it, they send reminders, they check off items. That makes it feel like a sales tool. The buyer needs to feel ownership — ideally the procurement lead is the one who says 'we need to move this legal review up two weeks.' Luna: Second mistake? Lucas: Too many milestones. I've seen MAPs with thirty items. That's overwhelming. The best ones have between eight and twelve. Everything else is noise. Luna: And third? Lucas: Not including an escalation path. Deals stall — that's normal. But if you don't know who to call on either side when a milestone blows past its date, you lose weeks. A good MAP names one escalation contact per company. Luna: So the MAP becomes a risk management tool as much as a timeline. Lucas: Exactly. And that's why procurement loves it. They're in the business of managing risk. A MAP gives them visibility without them having to chase the vendor for updates. Luna: I wonder if MAPs work differently for different deal sizes. A hundred thousand dollar deal versus a million-dollar one. Lucas: Good question. For smaller deals — under $100,000 annual contract value — a formal MAP can feel like overkill. A shared checklist in Google Docs is fine. But for anything over $250,000, I'd argue it's necessary. The stakes are too high to leave coordination to email. Luna: And what about the vendor side? Do sales reps like MAPs? Lucas: Mixed. The top performers love them because it gives them control and predictability. But some reps see it as extra paperwork. I've talked to sales leaders who say they've had to mandate MAPs for any deal over $500,000. The reps who push back usually are the ones missing their numbers. Luna: That tracks. The reps who are organized tend to outperform. Lucas: One more thing: the best MAPs are usually co-created in the same meeting where the buyer shares their internal procurement process. The vendor learns exactly what stages the buyer's organization requires — legal review, security review, board approval — and can build those into the plan. Luna: So it forces the vendor to understand the buyer's reality instead of just pushing their own timeline. Lucas: Exactly. And once you've done that, you've built a shared language. The deal stops being 'us versus them' and becomes 'us together against the timeline.' Luna: I want to push back on one thing though. Doesn't this add friction at the start? Before you even have a deal, you're asking the buyer to sit down and build a project plan with you. Lucas: It does add a step. But that step pays for itself. The DealDesk study also found that deals with MAPs had 31% fewer stalled periods of more than two weeks. So the upfront investment saves time later. Luna: What about the tooling? Is there a standard platform for MAPs? Lucas: Not really. Some vendors use their CRM — Salesforce or HubSpot — with a custom object. Others use project management tools like Asana or Monday.com. I've even seen Google Sheets work well. The tool matters less than the discipline of reviewing it weekly. Luna: So a sticky note on a whiteboard could work, as long as you actually look at it every week. Lucas: Pretty much. Though I'd recommend something digital so you can track changes over time. Luna: One more question — how do you introduce a MAP to a buyer who's never used one? You don't want to seem like you're imposing process. Lucas: Frame it as a way to protect their time. Say something like: 'To make sure we respect your internal deadlines and don't miss anything, I'd like to build a shared plan together. It usually takes about thirty minutes and saves hours of back and forth later.' Luna: That's good. You're selling the outcome, not the document. Lucas: Right. And once they see the first draft, most buyers appreciate the clarity. It's one of those things that sounds bureaucratic but actually feels helpful. Luna: I think that's a good place to leave it. Any final thought on where MAPs are headed? Lucas: I think they'll become standard in procurement RFPs within a couple of years. Buyers will start asking for a MAP as part of the vendor evaluation. The vendors that already do it well will have an edge. Luna: Makes sense. Thanks for breaking it down. Lucas: Happy to. See you next time.