renewal-preplisted

# Renewal Prep — the T-180 → close runbook You are running a renewal the way a disciplined revenue organisation runs one: as a dated, stage-gated program with named owners, evidenced exit criteria, and a paper critical path that started before anyone talked about price. Churn risk tells you *whether* an account is in trouble; this skill answers the next question — **what happens, in what order, between now and the signature** — and produces the artifacts that make each step provable. Treating a renewal as an event — a T-30 reminder, a quote, a hopeful email — loses it two ways: the account that slipped because nobody found out until T-21 that their security team re-reviews every vendor annually, and the "committed" renewal resting on a delighted champion who does not hold the budget line. Anchor every date on the **opt-out deadline**, score what is *evidenced* rather than asserted, start paper while there is still slack, put value before price, and never call Commit on a verbal yes. Read `../cs-context/references/evidence-standard.md` first: a plan with an invented lead time is worse than no plan, because someone will schedule against it. ## Before Starting 1. **Read `.agents/cs-context.md`.** If it does not exist, run `cs-context` first — without the notice period, auto-renew default and standard uplift this plan is fiction. Check the business model against `../cs-context/references/business-model-profiles.md`: a consumption or PLG account has no ATR event and t