Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / The Rep Who Won by Asking for the Buyer's Implementation Timeline
Transcript
- Lucas: So Luna, I want to talk about a deal that nearly died on the vine. A rep I know, let's call him Dan, was selling a project management tool to a mid-sized logistics company. The demo went great, the champion loved it, but the deal sat in limbo for two months. Every check-in got the same answer: 'we're still evaluating.' Luna: Ah, the classic stall. What broke it? Lucas: A single question. He asked the buyer, point blank, 'If we signed today, when would you want to roll this out to your first team?' And the buyer's answer changed everything. Luna: Okay, I'm intrigued. What did the buyer say? Lucas: He said, 'Well, we'd need to pilot in the operations group first, and that can't start until Q1 because we're in peak season right now.' Which, by the way, was August. So Dan realized the buyer had a perfectly good reason to wait, but he'd never mentioned it. Luna: So the timeline question surfaced a hidden constraint. That's clever. But why didn't the buyer just volunteer that? Lucas: Because it's not his job to make the sale easy. He's busy, he's got a million things to do, and 'we're still evaluating' is a polite way to end a call. But when Dan asked about implementation timing, he forced the buyer to think about the 'how' and 'when' of the project, not just the 'if.' Luna: And that led to the actual objection. So what did Dan do next? Lucas: He didn't push back. He leaned in. He said, 'Okay, so if we target a Q1 pilot, what's the latest we'd need to get the contract signed to make that happen?' And the buyer paused and said, 'Probably mid-December, before the holidays.' Luna: So suddenly there's a deadline. A real one. Lucas: Exactly. And Dan didn't invent it. The buyer created it himself. From that point on, the conversation shifted from 'if' to 'when.' They mapped out the steps backwards: legal review, procurement, security check, all the way to a signing date in early December. Luna: That's the power of asking about the timeline. It moves the buyer from evaluation mode to planning mode. And it's so simple, you'd think more reps would do it. Lucas: You'd think. But most reps focus on price and features, and they never ask the one question that forces the buyer to visualize the implementation. I've seen this work across industries. It's not just software. Luna: Give me another example. Any industry. Lucas: I talked to a rep who sells industrial safety equipment. His buyer was a plant manager who kept saying 'we're interested' but wouldn't commit. The rep asked, 'If we installed the new sensors next month, what would that do to your compliance audit schedule?' And the plant manager said, 'Actually, our audit is in March, so we'd need it done by February.' Luna: So the question uncovered a regulatory deadline. That's a compelling reason to buy. Lucas: Right. And the rep didn't have to manufacture urgency. He just asked about the timeline, and the buyer provided the urgency himself. That's the key: you're not pressuring the buyer, you're helping them think through the logistics. Luna: But there's a fine line. If you ask about the timeline too early, before you've built value, it can feel like you're rushing them. I've seen that backfire. Lucas: That's a great point. The question only works if you've already established that the solution is a fit. If you ask on the first call, it sounds like you're trying to close before they're convinced. But once you've had the demo, once the champion is engaged, that's the time to start asking about implementation. Luna: So what's the right way to phrase it? I'm sure our listeners want the exact words. Lucas: There are a few variations. You can say, 'If we were to move forward, when would you want to see this live?' Or, 'What would a realistic rollout timeline look like from your end?' The key is to make it a hypothetical, so it doesn't feel like a demand. Luna: And then you follow up with the 'what would happen if we missed that date' question, right? Lucas: Exactly. You want to understand the consequences of delay. That reveals the true cost of inaction. In Dan's case, missing the December deadline would have pushed the pilot to Q2, because Q1 was already booked for other projects. That one fact made the deal urgent for the buyer, not for Dan. Luna: It's like you're uncovering the buyer's own internal deadline, which is way more persuasive than any discount you could offer. Lucas: And that's the real lesson. This isn't a trick or a manipulation. It's a way to have a more honest conversation about what it takes to get a project off the ground. When you ask about the timeline, you're treating the buyer as a partner in planning, not just a target. Luna: I love that. And you know, this reminds me of something I've been thinking about lately. We get so many emails from listeners who say these conversations have helped them in their own sales roles. It's really rewarding to know. Lucas: It is. And it's exactly why we keep doing this. If you're one of those listeners, and these episodes have moved your work forward in some small way, a couple of dollars a month is genuinely what keeps these going. You can find us at buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small gesture that makes a big difference for us. We don't run ads, and that's because of people like you. Lucas: Alright, back to the timeline question. There's a nuance I want to dig into: what if the buyer gives you a vague answer, like 'sometime next year'? How do you pin that down? Luna: That's the challenge. I'd probably say something like, 'Help me understand what 'sometime' means. Is there a month that works best for your team?' Lucas: Right. You're not accepting the vague answer. You're gently pushing for specificity. The buyer might not know the exact quarter, but they can usually say, 'We'd want to avoid our busy season in May,' or 'We need to align with our budget cycle in September.' Luna: And sometimes the buyer really doesn't know. But the question itself plants a seed. It gets them thinking about the implementation steps, and that's valuable even if they can't commit to a date on the spot. Lucas: Absolutely. I've seen reps use this to build a shared roadmap. They'll say, 'Let's sketch out the milestones together.' That turns the conversation into a collaborative planning session, which is far more constructive than a typical sales pitch. Luna: So what's the takeaway for our listeners? What should they do differently tomorrow? Lucas: Next time you're in a sales conversation, and you've already gotten past the initial interest, ask the timeline question. Don't wait for the buyer to bring it up. And don't be afraid of the answer, even if it's 'we're not ready yet.' Because that tells you exactly what you need to work on. Luna: And if they say 'not ready,' at least you're not wasting your time chasing a ghost. You can pivot to addressing the real obstacle. Lucas: Exactly. In Dan's case, the timeline question didn't just save the deal, it made the buyer more confident in the purchase. Because now they had a plan. And a plan is a commitment. Luna: That's a great closing thought. I think we've given our listeners a lot to chew on. Lucas: We have. And I hope they'll try it out. The worst that can happen is you learn something. The best case, you close a deal that was stuck. Luna: And that's the kind of win we like to celebrate. Thanks for joining us on this episode of Closing the Deal. Lucas: Yeah, thanks for listening. We'll be back next week with another tactic you can use in your next conversation.