
Some deals are easy to read. The prospect has a clear problem, the right people are involved, the next step is agreed, and both sides know what needs to happen before a decision.
The harder deals are the ones that look active while the buying process is still unclear. Meetings are happening. The product is being evaluated. Pricing may already be on the table. Yet the rep still does not know whether the prospect has enough reason, evidence, or internal commitment to move forward.
That is where deals start to drift.
This playbook helps reps spot those gaps earlier and provides practical tips for next steps. It covers what to establish in discovery, what a demo or trial needs to prove, how to turn interest into commitment, how to diagnose stalled deals and commercial objections, and what still needs to happen before closing.
Discovery starts to break down when reps use the call to learn basic facts instead of using what they already know to uncover the problem beneath them.
Strong reps come in with context, confirm only what matters, and spend their time understanding the pain, its consequences, and the outcome the prospect needs to achieve.
Avoma's analysis of 12,847 sales calls found that top performers asked 40% fewer situational questions and 3x more impact questions than average performers. They also stayed with a pain point longer instead of switching topics or moving to the product too quickly.
"A great discovery isn't about asking more questions. It's about asking better questions in the right sequence."
Aditya Kothadiya, CEO and Co-founder, Avoma

3 situational questions, maximum
Use research to avoid spending the call collecting information you could have learned beforehand. Confirm the context you need, then move deeper.
2 layered pain questions
Stay with one pain point long enough to understand its consequences. Anchor the follow-up in something the prospect has already said.
"You mentioned [THING THEY SAID]. What specifically [CONSEQUENCE/CHALLENGE] does that create for [THEIR ROLE/TEAM]?"
1 impact question
Once the problem and its consequences are clear, connect them to the outcome the prospect wants to achieve.
"If this were solved in the next 90 days, what would success look like for your team? Which metric would move first?"
When a second major problem comes up, restart the 3-2-1 sequence around that topic.
Once discovery has clarified the pain, impact, and use case, the demo should focus on what the prospect needs to validate before moving to a decision.
Do the basic homework before the demo so you do not spend the meeting asking questions you could have answered yourself. Review the prospect’s company, role, current setup, and likely priorities before the call. Then use the demo to test what matters instead of starting from zero.

The demo should help define what comes next rather than trying to show the full product.
Understand what triggered the evaluation, what the prospect wants to improve, and what a successful outcome would look like. Then focus the demo on the two or three capabilities most closely tied to that problem.
By the end of the demo, the rep should have clarity on the:
Similar to a demo, a trial should make the buying decision easier. Too often, it reaches the final days with plenty of product activity and little clarity about whether the prospect has seen enough value to move forward.
The problem usually starts much earlier:
Once those points are clear, the trial should be structured around what the prospect still needs to validate before making a decision. At Avoma, our reps use a 5-phase trial system to manage that process.
The five phases keep the evaluation focused, surface problems while there is still time to address them, and prevent the trial from ending in an open-ended request for more time.

1. Pre-trial discovery
Scope the trial before kickoff.
Define the one or two use cases that matter most. Identify who will use the product, judge the outcome, and can influence or block the decision.
Also ask whether the prospect has evaluated similar products before and what stopped them from moving forward. That can reveal what this trial needs to prove differently.
"The questions that actually determine whether a trial succeeds—who's involved, what success looks like, who has veto power—need to be answered before the countdown starts."
Aditya Kothadiya, CEO and Co-founder, Avoma
2. Kickoff call
Bring the right users in from day one and put the key milestones on the calendar:
The final evaluation should already be scheduled when the trial begins.
3. Manage the trial with evidence
Check whether users are active, important workflows are being tested, integrations are working, and the trial is producing evidence the prospect can evaluate.
Bring that evidence into the check-in.
"I reviewed your account before this call. I can see [X] users completed [workflow], and [Y] results are already showing up. I want to walk through what we are seeing and make sure it is useful."
This surfaces setup or adoption problems while there is still time to address them.
4. Diagnose the reason behind an extension
A request for more time should trigger a diagnosis:
Ask:
"What are we trying to accomplish in the extra time that we did not get done in the first two weeks?"
If a decision-maker is away, keep setup and usage moving so they return to evidence from their own environment.
5. End with a decision
Review what the trial showed, surface remaining concerns, and make sure the relevant stakeholders saw the evidence.
Then ask:
"Based on what we have seen over the last two weeks, does this solve the problem you came in with?"
The trial should end with a decision or a clearly defined gap.
A call can end on a positive note and still leave the deal exposed.
"Let us discuss internally." "We will review the options." "We will get back to you." None of those responses is inherently negative. The problem starts when the conversation ends without a reason to reconnect, a date on the calendar, or meaningful action from the prospect.
Prospect commitment is the clearest evidence of progress. Look at what they have agreed to do next, when they will do it, and whether that action moves the decision forward.
Go into an important call knowing:

During a competitive evaluation:
"You're going to see several products, and parts of them may start blending together. Why don't we reconnect after you've seen what's out there? Bring what stood out, and we can compare it against what you need."
When the next conversation already has a clear purpose, reduce the effort required to schedule it:
"I went ahead and blocked some time. Let me know if the timing works. I have a couple of things I want to walk through, and it will be easier to do that live."
A meaningful next step could be bringing in another stakeholder, sharing information, starting a review, or scheduling the next decision point.
The prospect asks for a lower price. Before you offer a discount, find out what they are asking you to solve.
A pricing objection can come from several places: a fixed budget, uncertainty about value or adoption, cash-flow constraints, procurement pressure, or a competing offer. The right response depends on the reason.
When another vendor enters the conversation, understand what the prospect sees as different.
Ask about the workflows, capabilities, or outcomes they are comparing so you can understand their decision criteria.
"That is fair. What are you seeing from those alternatives that you are not seeing here? Or is this primarily a pricing comparison at this point?"
Keep the conversation focused on what matters to the prospect rather than turning it into a list of competitor claims.
Cash-flow pressure may come down to when the prospect pays. An annual commitment with quarterly billing can address that concern while preserving the contract value.
If price needs to move, connect the discount to a longer contract term, higher seat commitment, or broader scope. This gives the prospect a clear trade-off rather than reducing the price with nothing changing in return.
When procurement presents a lower number, first establish what that number represents:
"Help me understand that number. Is it a firm ceiling from finance, or a target based on what you expected to pay?"
Once you have presented the strongest viable offer, avoid reopening the negotiation without new information from the prospect.
The outcome of this stage should be clear: you know what is driving the objection and which commercial response gives the prospect a credible path forward.
After the verbal yes, the buying process shifts to getting the purchase approved and signed. Legal, security, procurement, or internal approval can still delay the deal.
The rep needs to know what remains open, who owns it, and whether those steps can be completed by the target date.
Identify the remaining steps on the prospect's side and whether they can realistically be completed before the expected close date.
Ask which approvals or reviews are outstanding, who owns them, and what your team needs to provide to keep them moving.
If security review takes three weeks and has not started, a close date two weeks away is no longer realistic.
Your champion may support the purchase and still need help getting legal, finance, security, procurement, or leadership aligned.
Find out where the internal process is stuck and what would help move it forward. That might mean providing security documentation, helping build the business case, bringing in an executive, or resolving a final commercial question.
If a contract start date affects an internal pricing exception or another commercial term, explain that clearly. Avoid creating urgency around an arbitrary signature date that can simply be extended later.
Before the contract is finalized, check whether another team is likely to need the product and show the prospect both pricing scenarios.
If broader adoption is already part of their plan, comparing the cost of including that team now versus adding it later can help them make a better scope decision before signature.
The outcome of this stage should be clear: you know what could delay the signature, who owns the remaining steps, and whether the deal can close on the expected timeline.
A deal can stall at any point between discovery and signature. When prospect engagement drops, next steps slip, or the close date moves again, the rep needs to find out what changed before deciding how to re-engage.
You usually know when a deal has started to stall. Replies take longer, meetings get pushed, prospect engagement falls, or the expected close date moves again.
What is harder to understand is why the buying process slowed down.
The cause could be a shift in priority, weaker stakeholder support, an evaluation that lost structure, or a deal that never had enough prospect commitment to begin with. Identify what changed before deciding how to re-engage.

If the reason for the stall is clear, respond to it. If it is not, audit the deal for signs that the prospect is still moving forward.
A stalled deal can still look active in the CRM because the rep keeps following up. Before you keep treating it as a live opportunity, look for clear 3 signs that the prospect is still committed to moving forward.

If the prospect has taken little action, there is no dated next step, and the deal still depends on one contact, the opportunity may be weaker than the CRM suggests. Requalify it before carrying it forward.
When a meeting is declined, find out whether timing is the issue or something in the evaluation needs attention.
When a champion leaves:
"I was working with [champion] on evaluating [product] for [use case]. It looks like they may no longer be with the company. Who would be the right person to continue the conversation with? I'm happy to provide a quick summary of where things stood."
For larger deals that continue to drift, set a clear boundary and leave the door open for the prospect to restart when the initiative becomes a priority again.
This playbook gives reps practical tips, tricks, and frameworks to work through deals with more structure and efficiency.
But how do you make reps more effective in the conversations that move those deals forward?
That is where Avoma's conversation intelligence comes in. It shows managers how reps handle sales conversations, where their execution breaks down, and where coaching can improve performance.
A sales manager overseeing 8 to 12 reps rarely has time to listen to calls, so feedback runs on self-reported updates instead of what actually happened on the call. Without that data, coaching defaults to generic advice, telling every rep to ask better discovery questions when the real gap is how they handle a pricing objection or whether they confirmed a next step.
Avoma's AI sales coaching scores every call against a scorecard, MEDDIC, BANT, SPICED, SPIN, or your team's own criteria, and flags the skill gap by stage: discovery, objection handling, demo delivery, closing, the same moments this playbook walks through. A manager gets a weekly digest of where each rep's gap actually sits, timestamped to the call, instead of piecing it together from a stalled pipeline review.
When a pricing objection comes up mid-call, live answer cards built on the team's own playbook surface a tested response in the moment. New reps ramp faster off playlists of top-performer calls organized by deal stage, hearing what each stage in this playbook actually sounds like instead of just reading about it.
Teams using this see a 40% increase in win rate and 30% higher quota attainment.
Use this companion library when you need practical language for the moments covered in the playbook, from discovery and trial management to stalled deals, pricing, negotiation, and closing.


