A buyer can like the product, and your rep can still have no deal.
They can agree with the pain. They can say the demo made sense. They can tell you the timing looks promising. You can still put it in the forecast. You just can’t do that with any certainty.
A late-stage deal starts to become real when there’s a shared timeline: the decision, the people involved, the work between now and signature, and what has to happen after signature for the project to succeed.
Until then, the rep is mostly forecasting enthusiasm.
The rep hears, “We’re still keen.”
The forecast says Commit.
The calendar says something else.
That’s the gap. Not because the buyer is misleading you. Because enthusiasm reads like progress, and positive language gets logged as forward motion when nothing on the buyer’s side has actually moved.
Keen isn’t the same as moving
This is where a lot of late-stage deals drift.
The champion wants to move forward, but legal hasn’t seen the agreement. Security hasn’t been briefed. Finance hasn’t reviewed the numbers. The implementation owner doesn’t know the deal exists. The person who cares most about the outcome is waiting for someone else in the organisation to do the first stretch of work.
Your champion can advocate. They can’t run multiple parallel workstreams on their own.
When deals stall late in the process, it’s rarely because the buyer changed their mind. It’s because the buying-side work was never mapped, never assigned, and never started.
Follow-up changes when there’s a timeline
Without a shared plan, follow-up stays generic:
New Message
Hi Alex,
Just wanted to check in. Are we still on track for this month?
Best,
Jordan
The champion says yes. The close date stays. Nothing moves.
With a shared plan, follow-up sounds like project management:
New Message
Hi Alex,
If we still want the team live in the first week of July, we probably need security reviewed by next Friday, commercial terms agreed the week after, and, as discussed, a planning call with Marcus before the end of the month.
Does this work for you? Any concerns?
Best,
Jordan
That second version is still direct. You’re naming dates and dependencies. It can feel like pressure. But the intent is different: you’re not chasing your quarter. You’re trying to coordinate and run the deal properly on a plan you built together.
That makes it harder to dodge, and it usually lands better, because the buyer can see you’re acting in good faith on their project, not just yours.
The difference isn’t whether the email asks for something. It’s whether both sides are working from the same facts: named steps, named owners, and dates that came from the buyer’s go-live goal, not your quarter-end.
What to map together
Don’t send a seller-built checklist and call it collaboration. Build the plan with the champion, in a live conversation, working backward from the date they actually need this working.
A useful timeline doesn’t need to be complicated. It needs to answer six questions:
- What outcome are we trying to hit?
- What date does that outcome depend on?
- Who needs to approve the decision?
- Who needs to implement or own the change?
- What work has to happen before signature?
- What work has to happen after signature?
The post-signature part matters. Many reps stop at procurement and miss the buyer’s real anxiety: what happens once they say yes.
If the buyer believes the project will be messy after signature, that risk shows up before signature. It may look like legal delay, pricing concern, or “we just need to regroup internally.” Sometimes the real objection is that the buyer doesn’t know how the change will land.
Name the people, not the departments. “Legal” isn’t an owner. “Priya in procurement, who might need two weeks once she has the draft” is useful. The moment the champion adds names and dates to a shared doc, the deal gets more real. When they stop updating it, that’s a signal worth paying attention to.
Work backward from the buyer's go-live or value date. If the plan only exists to hit your quarter-end, they'll notice. If it exists to get them live before a board review, a seasonal peak, or a compliance deadline, the timeline has a reason to hold.
A simple meeting move
Late in the deal, try this:
If we worked backwards from the date you’d want this live, what would need to be true by then?
Then build the timeline with the buyer. Don’t present it like a closing trick. Build it like a shared operating document.
Walk backward through approvals, reviews, and implementation steps. Write down what they say. Share the doc before you leave the call. Ask them to add anything you missed.
The rep should leave with dates, owners, and risks. The buyer should leave with a clearer path through their own organisation.
- What date is the buyer working backwards from, and who set it?
- Name every approval path still open.
- Who owns implementation after signature?
- Write down the next three buyer-side actions with owners and dates.
- Mark the one step most likely to slip.
- Has the champion confirmed or updated the plan since the last agreed milestone?
What managers should inspect
Managers should be wary of deals with strong language and weak logistics.
Good buyer language matters. But if the rep can’t explain what happens next, who does it, and when, the deal isn’t as mature as the stage suggests.
The manager question isn’t only, “Does the buyer want it?”
The better question is:
Does the buyer have everything they need to actually get this to signature?
That is what a timeline reveals.
It turns optimism into something inspectable. It gives the rep a reason to ask harder questions. It helps the buyer see the path. And it makes the forecast less dependent on whether the champion sounds excited this week.
Keen starts the conversation. A shared timeline is what makes the deal real.