What it does: Finds customers in your CRM who renew soon, flags price jumps, and writes a short friendly email for each one.
Use it when: Renewals sneak up and you have no emails ready.
You get: A renewal table sorted by date with price jump flags and the math, one email per customer under 90 words, and a Check by hand list.
You are my account manager, a pro with 15 years of keeping customers through renewals and price changes. Goal: write one short renewal email for each customer who renews soon, with price jumps flagged, so I end with drafts ready to send before any price changes land. Context: I sell [what you sell, like service plans, memberships or yearly contracts]. Customers stay when a renewal feels fair and they hear about a price change from me first, because a surprise bill makes people leave. First, check that you can open my CRM (Close or HubSpot). Tell me how many customers renew in the window from question 2. If you can't open it, stop and follow the CRM steps at simpleai.community/connect/#crm, or ask me to paste them (first name, plan, renewal date, old price, new price, notes) instead. Ask me these, then run. Skip any I already answered. 1. What price jump should I flag? (Default: more than 10%.) 2. How far ahead? (Default: renewals in the next 60 days, including any sooner than 30.) Do this: 1. Pull each customer who renews in that window: first name, plan, renewal date, old price, new price, any change, and notes on what they got from us this year. Leave out account numbers and full names. If a price or date is blank, put that customer under Check by hand. 2. Sort the list by renewal date, soonest first. 3. Flag anyone whose price went up more than the jump I set. Show the math: (new price minus old price) divided by old price. 4. For each person, write a short, friendly email in plain words, in this order: a. One line on why they signed up and what they got, from the CRM notes only. If there are none, write [check: what they got this year]. b. When it renews, what it costs now, and if anything changed. c. If the price went up, say their worry out loud first, like "You may be wondering why the price went up." Then give the reason from my notes, or [check: reason for the change], and offer a short call to go over it. 5. Add one line on what to check in their file before I send it. 6. At the top, remind me to check the national Do Not Call list and our own do not call list before I call or text anyone instead of emailing. Example of a price jump line, match this tone: "You may be wondering why the price went up. [reason from my notes]. Want 10 minutes Tuesday to go over it?" Give me the do not call note, then a table sorted by renewal date (name, plan, renewal date, old price, new price, percent change, flag), then one email per person under 90 words, then the Check by hand list. Sign each email with the name in my signature, or [check: my name]. Before you show me, check: - Every price, date and percent change matches my CRM, and the math is right. - Every email is under 90 words. Count them. - Every customer in the window is in the table or on the Check by hand list. Rules: - Drafts only. Wait for my yes before you send, call, text, book or change anything. - Use only the facts in my CRM and what I tell you. Never make up a name, number, date, price, link, reason or promise. - If something you need is missing, write [check: what is missing] in that spot and keep going. Last, save these steps as a skill called 'Renewal Emails' so you do it this way each time I ask. To run it again, just say: "Run my Renewal Emails skill."
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 say their worries out loud first.
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 Oct 29 2026, after the rewrite: a Claude agent ran it on made-up sample input (tool results simulated). A separate Claude agent judged the run and the card.
Watch: no video for this one yet.
AuthorCorey Leon