Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How One Rep Won by Asking the Buyer to Set the Implementation Date
Transcript
- Lucas: There’s a moment in almost every enterprise software deal where the reps get nervous. The paperwork is out for signature, legal is reviewing the MSA, and the buyer starts going quiet. That lull is dangerous. Luna: Right, because the buyer starts thinking about other priorities, or worse, they start second-guessing. What’s the move to keep that from happening? Lucas: One of the smartest things I’ve seen a rep do: she asked the buyer to schedule the implementation meeting before the contract was signed. Not as a contingency — as a condition of even moving forward with the proposal. Luna: Wait, she asked for a date and time for the kickoff while the deal was still technically open? Lucas: Exactly. The buyer was a mid-sized manufacturing company. The rep — let’s call her Megan — had been in a three-month evaluation cycle. The internal champion was on board, but the procurement team kept dragging their feet. So Megan said, ‘Let’s set a date for the project kickoff. I’ll put it in the vendor calendar. If we can’t agree on a date, I’m honestly not sure this is a priority for you.’ Luna: That’s a gutsy move. Did the buyer flinch? Lucas: No. The champion looked at his calendar and picked a Tuesday three weeks out. Suddenly the deal wasn’t theoretical — it had a timeline. Megan sent a meeting invite right there. The contract was signed the next day. Luna: So the implementation date became a forcing function. It made the buyer visualize the post-sale reality and signaled to internal stakeholders that they were committed. Lucas: That’s exactly it. The act of scheduling the kickoff is a psychological commitment device. It’s harder for the buyer to back out once they’ve told their boss, ‘I’ve blocked off August 18th for the vendor training.’ Luna: And it gives the rep a natural reason to follow up. ‘Hey, just confirming the kickoff prep call next week. By the way, has legal signed off?’ Lucas: Right. The implementation date becomes the stake in the ground. It changes the conversation from ‘should we buy?’ to ‘how do we get ready?’ Luna: I want to push back a little. Doesn’t this only work if the buyer has decision-making authority? What if the champion is a mid-level manager who can’t set dates without their boss? Lucas: Great point. Megan’s champion was a VP of operations, not the CEO. But she asked him to get buy-in from his boss for that specific date. She said, ‘Who else needs to be at the kickoff? Can you check with them and send me the date?’ That way, the champion had to socialize the timeline internally, which actually built more consensus. Luna: So it forces the buyer to do the internal selling for you. I like that. Have you seen this backfire? Lucas: I have. There was a rep who pushed for the implementation date too early — before the buyer had internal alignment. The champion said, ‘I’ll check with my team,’ and then the whole thing stalled because the team hadn’t been looped in. The rep didn’t have the relationship with the other stakeholders. So the timing matters. Luna: So you need to have at least verbal confirmation from the champion that the project is a go before you ask for the date? Lucas: Exactly. Megan had already done a discovery call with the implementation team. She knew their constraints. The date she picked was feasible. The request wasn’t a shot in the dark — it was a logical next step. Luna: Let’s talk about the psychology. Why does this work even when the buyer is hesitant? Lucas: One reason: it reduces cognitive load. The buyer has been evaluating vendors for months. They’re exhausted. Giving them a concrete next step — ‘pick a date’ — is easier than asking them to make a final decision. It’s a smaller ask that leads to a bigger commitment. Luna: That’s the classic ‘foot-in-the-door’ technique. Start with a small commitment, then escalate. Lucas: And there’s a second factor: loss aversion. Once the buyer puts that date on their calendar, they start to mentally allocate resources. If the deal falls through, they have to go back and tell their team, ‘Never mind.’ That’s painful. Luna: I’ve also seen reps use the implementation date to handle the ‘I need to think about it’ objection. They say, ‘While you’re thinking, let’s pencil in a tentative start date. If you decide to move forward, you’ll already have a slot.’ Lucas: That’s a beautiful move. It turns the objection into a planning exercise. And if the buyer says no to that, you’ve got a much clearer signal of their true intent. Luna: So the takeaway: don’t wait for the signature to start talking about implementation. Bring the future into the present. Lucas: That’s the core of it. And honestly, these kinds of insights are why we do this show — the small shifts in conversation that make a real difference in outcomes. Luna: Yeah, it’s amazing how a single question can change the trajectory of a deal. Speaking of small things making a difference — a couple of dollars a month is genuinely what keeps these episodes going. If these conversations have moved your work forward in some small way, consider tossing something into the hat at buy me a coffee dot com slash fexingo. Lucas: We keep the show ad-free because it’s the right way to have these conversations. That listener support is what makes it possible. Even a few coffees a month adds up. Luna: Alright, so we’ve talked about getting the date on the calendar. But let’s flip it — what about the rep who didn’t do this and lost the deal? Lucas: I’ve got a good one. A rep selling cloud infrastructure to a financial services firm. The evaluation went well, the demo was flawless, and the buyer said, ‘We’re going with you.’ The rep relaxed. She sent the contract and waited. Luna: Classic mistake. Lucas: Two weeks go by. She follows up. The champion says, ‘We’re still reviewing.’ Another week. Then the champion puts her on a call with legal, and legal has a dozen questions about data residency. Suddenly the deal is in limbo. Luna: Because there was no deadline. The buyer had no reason to prioritize the contract review. The implementation date would have forced that conversation earlier. Lucas: Exactly. The rep ended up losing the deal to a competitor who came in late with a lower price. But if she had set a kickoff date during the close, the buyer would have been locked in before the competitor even entered the picture. Luna: So the lesson is: don’t let the buyer drift. Pin them down with a date. Lucas: And the beauty is it’s a low-risk ask. Worst case, the buyer says ‘I’m not ready,’ and you learn that the deal isn’t as solid as you thought. Best case, you’ve just turned a maybe into a done deal. Luna: I think a lot of reps avoid this because they’re afraid of being pushy. But it’s not pushy if you frame it as helping the buyer plan. Lucas: Right. It’s a consultative move. You’re saying, ‘Look, I want to make sure when you’re ready, you get the resources you need. Let’s block that time now so we’re not scrambling later.’ Who would object to that? Luna: Nobody reasonable. And the ones who object are giving you valuable intel about their real level of interest. Lucas: That might be the single best filter for deal quality. If they won’t pick a date, they’re not committed. Luna: Alright, so we’ve got a concrete tactic to try this week. I’m curious — what’s the next episode about? Lucas: We’re going to look at a rep who won by asking the buyer to identify the risk of doing nothing and quantify it in dollars. That’s a heavy one. Luna: Can’t wait. Until then, go schedule those kickoffs.