Prompt library
Write a renewal check-in that is not an invoice warning
Renewals are decided by accumulated value evidence, not by the renewal email; leading with their numbers makes the case theirs. Naming weak adoption at day 90 converts the most dangerous renewal pattern (silent drift, then shock) into a recoverable working conversation.
Last reviewed July 17, 2026
The prompt
Write a renewal check-in email, 90 days out.
Account and their usage story: {{account}}
Renewal details: {{renewal}}
Rules:
1. Lead with THEIR value evidence: 1-2 specific usage facts or outcomes from their account ("your team ran 340 reports last quarter"), not generic product enthusiasm. If usage is weak, do not fake it; see rule 5.
2. Frame the note as a working session offer: review what worked, fix what did not, plan next year. Renewal is mentioned once, as context for timing, not as the ask.
3. Ask ONE question that surfaces risk early: what would make next year clearly worth it?
4. Offer 2 concrete agenda items for the call based on their usage pattern.
5. If the usage story is weak, the email says so plainly ("we noticed adoption dipped after March; that is on the agenda") because surprise churn conversations at day 30 are worse than candor at day 90.
6. Under 130 words, no urgency theater.
Also produce the weak-usage variant regardless, so I have both ready.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{account}} | The account and usage facts | mid-market customer, 40 seats, heavy Q1 usage, dipped since May |
| {{renewal}} | Date and terms context | renews December 1, flat pricing, no open tickets |