Count back from the renewal date and the calendar closes faster than the playbook implies. A contract requiring 90 days of notice to signal non-renewal [7] puts the last day you can credibly say no on the same day Zylo has you sending formal counter-offers [8][13]. Run it in that order and the counter-offer is a request, because the vendor can see the window has shut. Begin the preparation work at 180 days and you buy 90 days of slack ahead of that deadline [14], which is the real case for the long runway.
That much is contract arithmetic rather than opinion. The runway itself is Zylo's judgment: it calls the start date the single biggest determinant of the outcome [10], and the post carries no sample size, survey population or method for the 79% figure [17]. Read it as a vendor's playbook that happens to contain useful dates, and use the dates.
Teams tell themselves the renewal is a price conversation with a rep. What buyers do is wait for the quote, because the quote is what triggers the internal review, and by then the notice window is whatever it is [7]. The second habit worth breaking is treating an uplift cap as cover. A cap governs the base rate on the order form, while the charges buyers report from consumption lines and from features described as included sit outside it [3][4]. Zylo's instruction at 120 days, to document every commitment the vendor makes because verbal promises that never reach the order form rarely survive, is the cheapest line in the whole document [15].
The money is worth putting in one place. Zylo puts the historic routine bump at 5% to 7% and the common one now at 15% or higher, climbing further on sticky, business-critical apps [6]. On $1m of annual software spend, that is $70,000 against $150,000, a difference of $80,000 in a single year [12].
For Monday, the sort is two columns rather than five checkpoints. Column one is the renewal date minus the notice period, the only date in this story that binds the vendor as well as you. Column two is whether you could actually leave. Where spend is high and leaving is hard, stop bidding on the rate and negotiate the clauses: a rate lock, an uplift cap, true-down and roll-over rights, an AI opt-out [9], because the discount is exactly what a vendor holds on the apps you cannot drop [6]. Where spend is high and switching is plausible, the 180-day work earns its cost: utilization data, named alternatives, benchmarks, and one internal position that IT, finance and procurement have agreed before the vendor calls [16]. Where spend is small, a calendar alert on the notice date and a shrug at the increase is the honest answer, and it frees the time for the first two boxes.
Everything Zylo recommends at 180, 120 and 90 days is downstream of that one date not having passed [8].
