Stalled Deal Revival Identifier
Identify the most viable stalled proposal to revive by filtering out active negotiations and noise from your pipeline.
Customise & copy
Add the context you have. The prompt updates as you work.
Paste the list of CRM proposals with sent dates and recent activity logs.
Notes on current deal statuses (e.g., active negotiations, known pauses, support issues).
Your familiarity with recent prospect interactions and context.
Minimum duration of silence required to qualify as stalled.
Live prompt
4 fieldsAnalyze the provided CRM proposals and select exactly one genuinely stalled proposal to revive. Review the input data and apply these strict criteria: 1. The proposal must have been sent at least two weeks ago with no recent response. 2. Exclude any deal with active negotiations, known pauses, or unresolved support issues. 3. Select only a prospect whose context is clearly understood and recognizable from the notes. CRM Proposals Data: {{crm_deals_list}} Deal Status Notes: {{deal_status_notes}} Prospect Interaction Context: {{prospect_context}} Minimum Silence Threshold: 2 weeks Provide the output in the following format: - Selected Prospect: [Name and Company] - Proposal Details: [Original send date and duration of silence] - Eligibility Confirmation: [Confirmation that the deal lacks active negotiations, pauses, or support issues] - Context Summary: [Brief summary of the remembered context for the deal]
Proof before you use it
A real example
Tested on gemini-3.1-flash-lite on 2026-09-04
{
"crm_deals_list": "1. Acme Corp - Proposal sent Oct 1, last log Oct 3. 2. Globex Inc - Proposal sent Sept 15, last log Sept 16. 3. Stark Industries - Proposal sent Sept 28, last log Sept 29.",
"prospect_context": "Globex Inc: Spoke with Jane Doe, she loved the enterprise tier demo but went dark right after receiving the pricing proposal.",
"deal_status_notes": "Acme Corp: Active negotiation ongoing on pricing. Globex Inc: No active negotiations, no support tickets, completely cold. Stark Industries: Unresolved technical support ticket pending.",
"silence_threshold": "2 weeks"
}A small ritual that works
How to use it
- 01Paste your CRM deal list, status notes, and interaction context into the designated fields.
- 02Select your preferred silence threshold to define what constitutes a 'stalled' deal.
- 03Run the prompt to receive a single, qualified recommendation for your next outreach effort.
Why it works
The prompt enforces a rigorous qualification process by combining a strict time threshold (minimum silence) with explicit exclusion criteria (no active negotiations, pauses, or support issues). By requiring the model to process structured inputs across deals, notes, and context, it isolates a single, actionable target based on factual data rather than speculation.
Where it fails
INSUFFICIENT_EVIDENCE
Customisation tips
Modify the 'Silence Threshold' variable options or add specific business rules to the criteria list if your sales cycle requires a longer baseline of inactivity before a deal is considered stalled.
Watch-outs
- Ensure the CRM data and deal status notes are kept up to date; otherwise, the prompt may inadvertently select a prospect who is currently in active discussions outside the logged notes.
- Verify that the selected prospect meets all negative constraints (no pauses or support issues) before initiating outreach.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Related prompts
Want to make AI useful across your team? Explore Atul's training.