Verified against ChatGPT · 2026-08-10
Draft renewal outreach for an account showing signs of churn risk before the contract date
Writes a renewal check-in for an account with early churn signals, surfacing the risk honestly to open a real conversation rather than a cheerful renewal reminder that ignores what's actually going on.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Draft renewal outreach for Fennimore Retail Group, whose contract renews in six weeks, but who's showing signs of churn risk — this needs to open a real conversation about what's going on, not a cheerful 'time to renew!' reminder that ignores the risk signals. RISK SIGNALS OBSERVED Logins dropped roughly 40% over the last two months, and their main champion left the company three weeks ago with no clear successor identified. RELATIONSHIP AND CONTACT HISTORY Previously strong relationship with the champion who left; no established contact with anyone else on their team yet. WHAT WE'D WANT TO OFFER OR ADDRESS IF THE RISK IS REAL Could offer a re-onboarding session for whoever takes over, or a temporary success-manager check-in cadence. SECTION 1 — ACKNOWLEDGE, DON'T IGNORE Open by referencing something specific and true about their recent experience — a dip in usage, a support ticket that didn't resolve well, a champion who left — rather than opening with contract logistics as if nothing has changed. If you don't have a specific enough signal to reference honestly, say that explicitly instead of inventing a plausible-sounding one to open with. SECTION 2 — ASK, DON'T ASSUME Ask a direct, specific question about what's changed, rather than assuming you already know the cause of the risk signal and pitching a fix to a problem that might not be the real one — the point of this outreach is to find out what's actually happening, not to preemptively solve a guessed-at problem. SECTION 3 — MAKE THE RENEWAL CONVERSATION SECONDARY Mention the renewal date only after the relationship question, framed as something to figure out together once you understand what's going on, not as the primary reason for reaching out — leading with the contract date when the relationship is at risk reads as self-interested timing. OUTPUT FORMAT One outreach message (Email, with a phone call as a planned follow-up if no response in three days.), plus a separate one-line internal note flagging the specific risk signal that most needs a real answer before this renewal can be considered safe.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
The instruction to acknowledge a real risk signal rather than open with contract logistics addresses a common failure of AI-generated renewal templates: asked to write 'renewal outreach' without more context, a model defaults to the generic register of a renewal reminder, because that's the more common pattern in its training data, even when the actual account context describes clear churn risk — the explicit acknowledgment requirement forces the output to match the real situation rather than the generic template shape the request superficially resembles. The instruction to ask rather than assume the cause matters because a model given a risk signal (dropped usage, a departed champion) will often jump straight to proposing a plausible-sounding fix, which risks solving the wrong problem entirely — usage dropping after a champion leaves could mean the replacement hasn't been onboarded, or it could mean the whole account is deprioritizing the tool internally, and these call for completely different responses, so the outreach needs to surface which one it actually is before offering a remedy. Making the renewal date secondary to the relationship question is a deliberate sequencing choice that changes how the message reads: leading with 'your contract renews in six weeks' to an account with visible risk signals reads as the vendor's self-interest driving the timing of the outreach, while leading with a genuine question about what changed and mentioning the date afterward reads as actually caring about the relationship independent of the contract clock — the same information in a different order produces a materially different impression on the reader. Requiring an internal note naming the specific risk signal needing an answer, separate from the customer-facing message, keeps the account owner honest about whether this renewal is actually safe rather than treating the act of sending outreach as having resolved the risk.
What you get back
Hi Marcus, I noticed things have looked a bit different on your end the past couple months — usage has dropped off some since Dana moved on, and I wanted to check in directly rather than assume what's going on. Is the team still finding the platform useful day-to-day, or has something shifted on your side? Once I understand where things stand, we can figure out the renewal together — no rush on that part yet. Internal note: the open risk signal that needs an answer before this renewal is safe is whether a successor to the departed champion has actually been assigned.
Verified against
ChatGPT GPT-5.1 · 2026-08-10
Changelog
- 2026-08-10 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
