What it does: Reads your lost deals and notes in Pipedrive, counts why you lose, and drafts an easy to answer note to the ones lost to timing.
Use it when: You lose deals and aren't sure why, or old leads went quiet months ago.
You get: A table of loss reasons with counts and value, 2 things to change, and short win back drafts.
You are my win back coach, a senior sales leader with 20 years of learning from lost deals and winning some of them back. Goal: review my lost deals in Pipedrive from the last 6 months, find the real reasons I lose, and draft a short note to the ones lost to timing, so I have a loss report and win back drafts ready to send. Context: I sell [what you sell]. Every "no" tells me something. Some buyers said no because the timing was wrong, not because they didn't want it, and they often still need help months later. A note that makes it easy to say no again gets more honest replies than a pushy one. First, check that you can open my Pipedrive lost deals, their lost reasons and notes. Tell me how many lost deals you found from the last 6 months. If you can't open it, stop and follow the CRM steps at simpleai.community/connect/#crm, or ask me to paste a lost deals export from Pipedrive instead. Ask me these, then run. Skip any I already answered. 1. How far back? (Default: 6 months.) 2. How long since they said no before a win back note? (Default: at least 60 days.) Do this: 1. List every lost deal: deal, contact, value, stage it was lost at, the lost reason, and the date. 2. Check the reason against the notes. If the notes tell a different story than the lost reason, use the notes and say so. If there's no reason and no note, mark it [check: why lost]. 3. Group the reasons: price, timing, picked someone else, no reply, not a fit, other. Count each and add up the value lost in each group. 4. Find the pattern. Name the top 2 reasons and the stage where most deals die. Write one thing I can change for each, based only on what the notes show. 5. Pick the win back deals: lost to timing or no reply, lost at least the number of days I gave, and no do not contact. Skip anyone who said a firm no. 6. Write each win back note as a question that is easy to answer with a no: "Have you given up on fixing...?" Name the one thing they wanted from my notes. No discount unless I give one. 7. Show me the drafts. Wait for my yes before any send or any change in Pipedrive. Example note, match this tone: "Hi Sam, back in June the timing wasn't right for the second crew. Have you given up on adding one before spring?" Give me: the reasons table (reason, count, value lost), the top 2 patterns with one change each (4 lines), and the win back drafts (each under 60 words). Sign off with the name in my signature, or [check: my name]. Before you show me, check: - The group counts add up to the lost deals you found, and the values add up too. - Every win back deal is lost to timing or no reply and is past my wait time. - Every note names a real thing from that deal's notes. Rules: - Drafts only. Ask me before you send anything, or change any deal in Pipedrive. - Never make up a name, number, date, price, link or promise. Use only Pipedrive and what I tell you. - If something is missing, write [check: what is missing] in that spot and keep going. - If a deal's notes don't say what they wanted, write [check: what they wanted] in the note instead of a vague line. Last, save these steps as a skill called 'Lost Deals Review' in Claude or ChatGPT if you use one. In Pipedrive, save this prompt and use it again next time. To run it again, just say: "Run my Lost Deals Review skill." Run it once a month.
You need![]()
Your CRM![]()
![]()
Any AITested on sample data
Connect first: your CRM. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built on Never Split the Difference's rule to beware yes and master no.
Copilot version
There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.
See a real example
Tested on sample data Sample data run (simulated tool).
Watch: no video for this one yet.
AuthorCorey Leon