The clock nobody is watching
Go and look at the ERP. It knows the install date. It knows the term. It knows which partner sold it, and it has known all three for three years. What it has never done is tell anyone the window is open — because a transactional system is built to record what already happened, not to say what is about to.
At month 34 of a 36-month term the renewal is live. The quote that lands first usually wins, because by then the customer is comparing a number against a number and has no particular reason to prefer yours.
Then there is the quieter half. Every box that shipped with no service attached at all is not a renewal you lost. It is one that was never created.
Why it survives every reporting cycle
Renewals are not a report anybody runs. They are a date buried inside a line item, in a system with no concept of what that date implies. By the time an expiry surfaces on a dashboard the competing quote went out weeks ago, from someone who was watching the same clock and got there first.
The maddening part is that this is the least ambiguous of the five. There is no inference in it, no modelling, nothing to argue with. It is arithmetic on dates you already own.
What Renewal Radar does
It reads the transaction history you already have and produces the renewals coming due — ranked by value and by how much time is left, each one carrying the sale it came from and the partner who owns the relationship.
Attach gaps fall out of the same pass: the sales that shipped without service, grouped so the pattern is visible instead of the individual misses. It is rarely random. It is usually one partner, or one product line, or one rep.
The uncomfortable part
We are not going to tell you what share of this is recoverable. That depends on your terms, your competitors, and how late you already are — and a number published here without measuring your business first would be a claim we could not defend in front of your own team. The Scan measures it on your data. Then we both know.