Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How One Rep Won by Asking the Buyer Their Timeline
Transcript
- Lucas: One of the fastest ways to lose a deal is to push for a close before the buyer is ready. But here's the thing — sometimes the buyer isn't ready because the rep never asked them what 'ready' actually looks like. Luna: You mean asking about their timeline? Lucas: Exactly. But not just 'when do you want to buy?' — more like 'walk me through your internal process and timeline.' And then — this is the counterintuitive part — offer to slow things down. Luna: Slow down? That sounds like the opposite of every sales playbook I've ever seen. Lucas: I know. And that's exactly why this works. Today I want to walk through a case from a mid-market SaaS company — sells CRM software to companies with 200 to 1,000 employees. The rep, we'll call her Sarah, had been chasing a VP of Sales at a logistics firm for about six weeks. The VP seemed interested, but every time Sarah asked to move forward, the VP said 'not yet.' Luna: Classic stall. How did she handle it? Lucas: Instead of pushing harder, Sarah asked a different question. She said: 'I want to make sure we're aligned on timing. Could you walk me through what your internal approval process looks like and what your ideal timeline would be if everything went perfectly?' Luna: And what did the VP say? Lucas: He said the procurement committee meets quarterly — next one is in four weeks — and he needed a proposal by end of week to get on the agenda. But then he also mentioned that his team was overwhelmed with a system migration and he wasn't sure they had bandwidth to evaluate a new tool. Luna: So there were two problems: a fixed deadline and an internal resource constraint. Most reps would have rushed to get the proposal in. Lucas: Right. But Sarah did something different. She said: 'If I get you the proposal by Friday, that works. But I want to be respectful of your team's bandwidth. Would it help if we pushed the demo and evaluation period to start two weeks after the committee meeting, giving your team time to wrap the migration first?' Luna: She offered to delay the process. That's bold. Lucas: The VP was surprised. He said, 'You're the first salesperson who's ever suggested we take more time.' And he agreed. He took the proposal to the committee, got preliminary approval, and then two weeks later Sarah did the demo with a full team — not just the VP, but two of his directors who would actually use the software. Luna: So by slowing down, she actually got more access and a bigger audience. Lucas: Exactly. The deal closed three weeks later — faster than if she'd pushed for an immediate demo. And the contract was 30% larger because the directors asked for additional modules during the demo. No discount was needed. Luna: If these conversations have moved your work forward in some small way, consider supporting the show. It's listener-supported, ad-free, and you can contribute at buy me a coffee dot com slash fexingo. Lucas: Yeah, we keep it ad-free intentionally, and that's only possible because of the community. Anyway — back to the timeline tactic. What I love about this story is that Sarah didn't just ask about timeline; she used the answer to build trust and reshape the process. Luna: What specific questions would you recommend for someone listening who wants to try this? Lucas: Three. First: 'Walk me through what happens after we agree in principle — who needs to sign off, and what's the typical timeline for each step?' Second: 'Is there anything on your calendar or your team's calendar in the next 30 to 60 days that might affect your ability to evaluate a new solution?' Third: 'If we could design the ideal timeline for this evaluation, what would it look like?' Luna: I love that third one. It's open-ended and positive. Lucas: And it forces the buyer to visualize a successful outcome. Most reps skip these questions because they're afraid the answer will reveal a delay or a budget freeze. But that's exactly what you need to know. A known delay is manageable. An unknown stall will kill you. Luna: I had a similar experience when I was in consulting. A client kept pushing off a decision. Finally, I asked about their fiscal year timeline. Turned out their procurement closed at the end of the quarter — which was three weeks away. I was able to restructure the proposal to fit their deadline. Lucas: Perfect example. And that's the key — you're not just gathering information; you're showing the buyer that you care about their constraints and you're willing to adapt. That builds massive credibility. Luna: It also helps you identify whether the buyer is serious. If they can't or won't give you a concrete timeline, that's a red flag. Lucas: Exactly. If a buyer says 'I'm not sure' or 'let me get back to you' when you ask about timeline, that's a polite no disguised as indecision. A serious buyer will have some sense of the process. Luna: So what do you do if they give you a vague answer? Lucas: You push gently. Say: 'I understand it's not always clear. Based on past purchases your company has made, what was the typical timeline from initial conversation to signed contract?' Or: 'If we could make the case compelling enough, what would be the earliest possible close date?' Luna: That second question is good. It sets a collaborative frame. Lucas: And it gives you a benchmark. If they say six months, you know you're dealing with a long sales cycle. If they say two weeks, you need to move fast. Either way, you know what you're working with. Luna: Let's talk about the psychology here. Why does offering to slow down actually accelerate the deal? Lucas: Two reasons. One: it signals that you're not desperate. Buyers are conditioned to expect pressure. When you remove it, they let their guard down. Two: it gives the buyer permission to be honest about their constraints. Most buyers are afraid to say 'we're not ready' because they think the rep will push harder. When you offer to slow down, they tell you the real blockers. Luna: And then you can address them. Lucas: Right. In Sarah's case, the real blocker wasn't price or product — it was internal bandwidth. By acknowledging it and adjusting the timeline, she removed the obstacle entirely. Luna: What about the opposite scenario — what if the buyer says their timeline is ASAP? Lucas: Then you want to understand why. Is there a pressing business issue? A competitor in the mix? A budget that must be spent by end of month? That information is gold. You can tailor your proposal to align with their urgency. Luna: So the timeline question is really a diagnostic tool. Lucas: Exactly. It's not about the date — it's about understanding the buyer's world. Their constraints, their priorities, their internal politics. Once you know those, you can design a process that works for both of you. Luna: I'm thinking about the rep who's listening right now, maybe on a call tomorrow. What's the one takeaway you want them to remember? Lucas: Don't be afraid to ask about timeline — and be willing to slow down if it serves the deal. The instinct to speed up is often what kills the sale. Patience, paired with genuine curiosity, is a competitive advantage. Luna: I like that. Patience as a competitive advantage. Lucas: Next episode, we'll talk about another overlooked question — one that most reps never ask because they assume they already know the answer. Luna: Looking forward to it. Until then, keep closing.