Guide
How to prevent deals from stalling
A review workflow for agency deals waiting on scope, budget, technical checks, or approval.
What should you do when a deal stalls?
Check the last buyer-confirmed step, name the blocker, and agree who will do what next and by when. Review stage age and contact history separately. Update the forecast when the buyer's plan changes.
Read the dates separately
A long stage can have a clear buyer timeline. A recent record edit can leave the buying decision untouched. Use both time and context in the review.
Time in stage
Count from entry into the current stage. Compare similar deal types and scopes in your own history. Use the result to choose which deals need a conversation.
Last buyer interaction
Check the last reply, meeting, or agreed decision. Note missing capture or access to a conversation before treating an empty timeline as silence.
Next action and expected close
Check whether the action has an owner and a date confirmed with the buyer. Repeatedly moving a close date needs a new reason in the record.
Match the next step to the blocker
Ask what the buyer needs to decide. Keep the reply in the deal record so another team member can follow it.
Scope is unclear
List the open scope questions. Agree which buyer and delivery lead will resolve each one before revising the proposal.
Budget has no owner
Ask who can approve the spend and when that review happens. Record an unconfirmed budget as unconfirmed.
Technical review is waiting
Identify the reviewer, the material they need, and the date they expect to respond. Check whether your team owes them an answer.
Legal or procurement is active
Record the open request, its owner, and the next checkpoint. Base the follow-up on the review plan agreed with that team.
Follow up on one unfinished decision
This fictional message uses an agreed scope step. Replace the details with facts from the conversation.
Hi Alex, We agreed to confirm the integration scope before revising the proposal. Is the API review still planned for Thursday? If the timing has changed, please send the next review date so I can update our plan. I can also send the field map if that would help.
Ask for a specific answer
Use the open question from the last conversation. Avoid adding a new pitch to every follow-up.
Set a follow-up boundary
Agree a cadence when possible. If messages go unanswered, make a clear final check on whether the work is still planned and record when to stop.
Handle the reply
Update the blocker, date, and owner. Cancel follow-ups that the reply makes irrelevant.
Give each reviewed deal a clear outcome
Use a weekly review as a starting routine. Adjust it to the length and volume of your sales cycle.
Continue
Keep the opportunity active when there is a current need, a buyer contact, and a dated next decision. Record what must happen before the stage can change.
Pause
Record the reason and the event that would restart the discussion. Apply your team's forecast rules so a paused project does not keep an unsupported near-term close date.
Close
Close the opportunity with the confirmed reason when the buyer cancels, selects another supplier, or no longer has a funded project. Treat an unknown outcome as unknown.
Correct the process
Look for repeated waits at the same stage. Missing scope information calls for a different fix from a buyer's scheduled budget review.
Check the rules behind a CRM warning
When comparing CRM tools, ask the vendor to demonstrate the trigger with a sample deal. Pipedrive, for example, documents that notes, email actions, and field edits can reset its rotting timer, while a future activity date does not prevent a deal from becoming rotten.
Which clock is used?
Ask whether the warning uses stage entry, record edits, or buyer activity. Confirm how imports and missing history affect it.
Who can act?
Check that the deal owner can see the evidence, change the next action, and record a planned pause. Test the view with the permissions the team will use.
What happens next?
Ask whether the flag only marks the deal or also starts a task, draft, or message. Check the controls that stop any pending action after a buyer replies.
Questions before you start
Sources
Sources checked on 20 September 2026. Examples are fictional. Review steps are suggestions for your team.