One of the habits I have built over time as a solutions engineer is this simple idea. Discovery never really stops.
That does not mean I am constantly peppering a customer with discovery questions late in a deal cycle. By the time we are deep into evaluation, a lot of the foundational discovery should already be known. We should understand the problem, the stakeholders, the desired outcomes, and the risks of doing nothing.
But deals are living things. New people join. Priorities shift. Internal politics surface. Technical concerns appear that were not visible earlier.
When those things happen, I give myself permission to pause and treat the moment like discovery again.
That pause has saved several deals for me over the years.
It is easy to get locked into execution mode late in a cycle. You are preparing demos, aligning security reviews, answering technical questions, and trying to keep momentum going. When something unexpected shows up, the instinct is often to push through it instead of stepping back.
I have learned that pushing through is usually the wrong move.
Here are a few ways I keep discovery alive without turning every conversation back into an interrogation.
1. I Watch for Signals That Something Changed
Late stage discovery usually starts with noticing a signal.
A new stakeholder shows up and asks basic questions. A champion suddenly becomes less responsive. A technical objection appears that was not mentioned before.
Those are clues.
Instead of immediately defending the solution, I slow down and ask questions that help me understand what changed.
For example:
“What prompted that concern?”
“Is this something your team has run into before?”
“Who else is thinking about this internally?”
These are not early stage discovery questions. They are situational discovery questions that help me recalibrate the deal.
2. I Reconfirm the Original Problem
Deals can drift.
Weeks into a process, conversations can become dominated by features, integrations, or procurement details. The original problem that started the evaluation can fade into the background.
When I sense that happening, I bring the conversation back to the starting point.
I might say something like:
“Earlier in the process you mentioned that your team was struggling with X. Is that still the biggest priority?”
This does two things. It keeps the deal grounded in business value and it gives the customer a chance to tell me if priorities have changed.
3. I Treat New Stakeholders Like a Discovery Moment
Late stage deals almost always involve new voices. A finance leader, a security reviewer, a VP who wants to understand the decision.
I do not assume those people share the same context as the original champion.
When a new stakeholder joins, I reset slightly. I ask them how they view the problem and what matters most to them in the decision.
Not a full discovery session, but enough to understand their perspective.
Too many deals stall because a new stakeholder never actually bought into the original problem.
4. I Ask Clarifying Questions When Objections Appear
Technical sellers often jump straight into solving objections.
I try to resist that.
If someone raises a concern, my first move is usually to understand the context behind it.
Questions like:
“What specifically makes that a concern for your team?”
“Have you run into this issue with other vendors?”
“What would a comfortable solution look like?”
Those answers often reveal that the objection is not exactly what it seemed on the surface.
5. I Create Small Moments to Revalidate Alignment
Every few calls, especially in longer deals, I take a moment to check alignment.
I might say:
“Just to make sure we are still on track, does this evaluation still feel aligned with what your team needs to solve?”
That question sounds simple, but it invites honesty.
If something has shifted internally, this gives the customer space to say it.
Discovery is often taught as the early phase of a sales cycle. In reality, it is more like a thread that runs through the entire deal.
You do the heavy lifting early. But you stay curious enough to revisit it when the situation calls for it.
For me, the key is balance. I do not want to drag a late stage deal backward with unnecessary questions. But I also do not want to miss the moment when the deal quietly changes.
Good solutions engineers stay technically sharp. Great ones stay curious all the way to the finish line.
