GM!
A rep reopens a quiet opportunity because the quarter changed. The last buyer reply was months ago: “Not a priority right now.”
The rep sends a fresh deck, books an internal review, and moves the deal back into the active pipeline. Nothing has changed on the buyer’s side.
The operating question is: What is different in the buyer’s world now that could make a decision possible?
A calendar reminder tells the seller when to check. It does not tell the buyer why to act. Reopening a deal without that distinction adds activity to the pipeline but not necessarily a buying process.
Identify what actually stopped the deal
Start with the last buyer-confirmed reason for the pause. Was the problem real but timing dependent? Did the budget move elsewhere? Was an internal owner missing? Did the buyer choose an alternative? Or did the team simply stop answering?
Those are different states. “Closed-lost” and “stalled” are administrative labels; the re-entry condition should come from the buyer’s last known constraint.
If there is no documented buyer reason, do not invent one from the rep’s notes. Mark the cause unknown and use the next contact to learn whether the problem still exists.
A follow-up date is not a reactivation trigger. The buyer-side constraint must have changed.
Use a four-part reactivation gate
Before moving an old opportunity back into active pipeline, capture four things in a short record:
Original constraint. What prevented a decision, in the buyer’s words? Link the email or call note if available. Separate a budget freeze from a product gap or a lost competitive decision.
Change signal. What observable event might alter that constraint? A new operations owner, an announced system migration, an expiring incumbent agreement, or a buyer request to revisit the work is more useful than “it has been six months.” Mark external signals as hypotheses until the buyer confirms relevance.
Buyer test. What question will determine whether the old problem is live again? Ask about the workflow and its current owner before proposing a demo. “Has the routing exception problem changed since we last spoke?” is testable; “Ready to pick this up?” is not.
Re-entry decision. What evidence moves this back to an opportunity? Require buyer confirmation of the problem, a person accountable for it, and an agreed next step that creates buyer work. Otherwise keep it in a nurture or research queue, not the forecast.
This is a reactivation gate, not a mass-email rule. It applies when someone wants an old deal to count as active again.
Match the outreach to the constraint
Illustrative scenario: a RevOps lead paused a lead-routing purchase because a CRM migration would invalidate the proposed configuration. The rep sees a public announcement that the migration is complete.
That announcement justifies a question, not a forecast upgrade. The team might still be cleaning data or might have solved routing inside the new CRM.
A useful note names the previous constraint: “You paused the routing evaluation until after the CRM move. Is exception handling still being managed manually in the new setup, or did the migration resolve it?”
If the buyer says the problem remains and introduces the person now responsible for routing, the next meeting can test scope and urgency. If the migration solved it, close the loop. If there is no reply, leave the deal inactive.
A public event opens a conversation. Buyer confirmation opens an opportunity.
Keep the old record intact
Do not overwrite the history to make the reopened deal look new. Preserve the original loss or pause reason, last buyer evidence, and previous commercial assumptions.
Create a new activity trail or linked opportunity according to your CRM rules. Record the new trigger and the buyer’s response separately. This makes it possible to see whether the original constraint changed or whether the team is recycling pipeline to fill a coverage gap.
If the original product gap is still unresolved, a new contact or quarter does not cure it. Route that question to the product owner before asking the buyer to repeat an evaluation.
Inspect reactivated pipeline differently
In a pipeline review, ask for the buyer-confirmed change, not the date of the latest seller email.
Can the rep state what stopped the prior cycle? What changed? Which buyer acknowledged it? What work has that buyer agreed to do next? A meeting accepted out of courtesy may be a discovery chance, but it is not yet evidence of a renewed purchase project.
Track reactivated opportunities separately from newly created ones. Inspect how many reach a buyer-owned next step, rather than counting every reopened CRM record as fresh coverage. This keeps pipeline creation honest without forbidding good second chances.
Weekly action
Pull three dormant deals the team wants to revisit. For each, write the original constraint, observed change, buyer test question, and evidence required for re-entry.
Send one constraint-specific note. Do not move the deal into active pipeline until the buyer confirms the problem is still live, names its current owner, and agrees to a next step.
If the reason for the old pause is missing, make learning that reason the first action.
— Pipeline Playbook