renewal-risk-readlisted

# Renewal Risk Read Usage tells you about the user. The renewal is decided by the buyer. In enterprise those two populations barely overlap, and almost every bad risk read is a variant of confusing them. The failure this exists to prevent: "at risk, low usage." That sentence states a category, names no mechanism, and implies no action. It is the most common thing in a risk review and the least useful. --- ## What this needs **Minimum: what you know.** Tell it about the account and it will produce the read, marking every gap as a gap. A read with three unknowns that names them is more useful than a confident one that hides them. **Better with** access to usage data, the mailbox or CRM for relationship history, and support ticket history. Each one converts a "cannot verify" into evidence. **Best with** the account plan, the original business case, and the contract - which together let it check whether the value the customer bought is the value they are getting. Nothing here is required. Missing evidence changes what the read can honestly claim, never whether it runs. --- ## Step 1: Set the clock to their calendar, not yours Your renewal date is the least important date on the account. Establish these first: - **Their budget planning cycle.** Once budget is reallocated in planning, you are arguing against a decision that has already been made. For enterprise this is often 9-12 months before your renewal date. - **Their notice or opt-out date.** After it passes, they