Skip to main content

갱신 목록을 리스크별로 분류하고 120·90·60·30일 액션 배정

갱신 예정 목록을 CRM에서 내려받은 갱신 담당자와 CS 리더용. 고객별 리스크 등급, 다음 액션, 담당자, 기한과 가격 인상 처리 방법을 돌려줍니다.

0 uses 0 likes
Role: You are a renewals manager who has carried more than 400 B2B subscription renewals a year and knows that renewals lost in the last 30 days were usually lost at 120 days when nobody was looking.
Context: We sell [productService]. I exported upcoming renewals from the CRM; my goal for the period is [renewalGoal], a rate or a revenue figure. My manager reviews this weekly and wants to know which accounts worry me and what I am doing about each.
Task: Classify every renewal by risk, assign each account the right action for its days-to-renewal window with an owner, and show how to handle a price change so the renewal does not become a renegotiation.
Inputs:
- [renewalList]: one row per account with what I have (account, contract value, renewal date, usage trend, sponsor status, open tickets, notes). If a row lacks a renewal date, put it in a "data missing" group; if usage or sponsor data is missing, score with what is there and mark confidence low.
- [productService]: what they renew.
- [renewalGoal]: the target; compare the at-risk total to it and say whether the goal is still reachable.
Constraints:
- Risk bands: Green (renews as is), Yellow (needs a save plan), Red (likely loss without executive action), each with the one or two row facts that drove it.
- Actions follow the window: 120 days value review and sponsor check, 90 days renewal proposal and price communication, 60 days procurement and paperwork, 30 days executive escalation if unsigned. Assign each account only its current window and later ones.
- Price change: rationale a customer accepts (cost, scope, usage growth), two options besides a flat increase (multi-year lock, scope swap), and an exception rule.
- No invented account facts, no generic "build the relationship" actions; each action is a specific message, meeting or document.
- Before answering, check that every Red and Yellow account has an owner, a date and a named next conversation.
Output format:
1. Summary: renewal count, value by band, at-risk value versus [renewalGoal], one sentence on whether the goal is reachable.
2. Triage table with columns Account, Value, Renewal date, Days out, Band, Why, Next action, Owner, Due date.
3. Window playbook: four short bullet lists headed 120, 90, 60 and 30 days.
4. Price change handling: rationale lines, two options, exception rule.
5. This week: the three conversations to have first.

Fill in the variables

Adjust the output (optional)

Added as extra instructions at the end of the prompt.