Why It’s Year 3 When You Lose Your Larger Customers (And in The AI Age, It’s Becoming Year 2)
Джейсон Лемкин обновляет свой классический тезис о том, что в B2B SaaS крупные клиенты обычно отваливаются на третий год — после долгого внедрения и инерционного продления на второй. В 2026 году цикл смерти сжался: AI-нативные конкуренты вытесняют incumbent-решения за месяцы, покупатели требуют годовых контрактов вместо трёхлетних, а стоимость переключения между AI-агентами упала до нескольких дней перенастройки промптов. Сжатие количества мест (seat compression) маскирует проблему: клиент продлевается, но платит на 20-40% меньше — у Workday, HubSpot, Zoom NRR падает, у MongoDB корпоративный сегмент сокращается под видом роста через self-serve. Customer Success превратился из союзника клиента в его врага, отчитываясь перед Sales и измеряя только NRR. Лемкин советует отслеживать вовлечённость отдельно от оттока, разделять GRR и NRR, встраивать AI-слой в продукт, делать продление формальностью за счёт глубокой интеграции в первые 90 дней и проводить тяжёлые разговоры с клиентами при падении использования немедленно.
Why It’s Year 3 When You Lose Your Larger Customers (And in The AI Age, It’s Becoming Year 2)
by | Blog Posts, Customer Success, Growth, Marketing
Recently I was catching up with a good friend who used to be CEO of an enterprise-y B2B social networking company. The usage and engagement numbers of his business were just awful.
Customers bought because they thought their organizations needed this functionality, and so they wrote the checks for Year 1, and even Year 2. But the end-user usage just never appeared.
In Classic B2B, it actually takes until Year 3 for your customers to churn out from low engagement / low usage.
The reason is as follows:
It’s probably not a coincidence ServiceNow, with 1,000+ $1M ACV customers, signs all 3-year contracts. More on that here.
We also saw this at Adobe Sign / EchoSign, at least in small parts. Most of our larger enterprise customers deployed relatively quickly, in the first 60 days. But some, most often due to internal manager changes (our purchase/champion quit, promoted, etc.), would never ever deploy at all in Year 1 despite all our attempts. Yet they would still renew for Year 2. And as long as we got them rolled and successful, we were good for the Year 3 renewal. If not, the customer would churn, but not until month 24.
So if a B2B app is fast growing, often because there’s segment pull, and there’s a lot of churn in Year 3, it can take a long time to see it. The numbers can be masked at first by all the new Year 1 and Year 2 deals. In other words, you just can’t tell unless you look at the engagement numbers, not just the churn numbers.
Churn is a lagging indicator. Especially where business process change is involved. Don’t let low churn give you comfort, unless it’s attached to high NPS and net retention.
But almost everything around it has changed in 2026, and not for the better. So let’s update.
What’s Changed in 2026: The Death Spiral Has Compressed
The Year 3 cycle was always a function of two things: enterprise procurement inertia and the cost of switching. Long sales cycles, long deployment cycles, long champion-tenure cycles. Both forces gave vendors a generous buffer to fix things before churn showed up in the numbers.
Both of those forces are eroding fast.
AI-native competitors can replace incumbents in months, not years. A B2B buyer evaluating a new AI tool in 2026 isn’t on a 12-month POC cycle anymore. It’s a 30-90 day pilot. If the agent works, it gets adopted and the legacy tool’s renewal goes from “auto-renew at last year’s price” to “we’re not renewing at all.” The 18-month cushion of Year 1 + Year 2 just doesn’t exist for a lot of categories anymore. Year 3 has become Year 2. In some categories, Year 2 has become Year 1.
The New Masking Patterns
The original post warned that Year 3 churn can be masked by all the new Year 1 and Year 2 deals coming in. That’s still true, but in 2026 there are new and more sophisticated ways the death spiral gets hidden.
What To Actually Do About It
Most of the original advice still works, just on a tighter timeline.
Track engagement, not just churn. Logins, active users, key actions taken, integrations live, time-to-first-value, time-to-second-value. Build the dashboard now, not after the Year 3 conversation. And track it per customer, weekly, with thresholds that trigger human intervention.
In 2026, also track utilization separately from active users. A customer with 100 paid seats and 60 active users has a seat compression problem coming, even if engagement among the 60 looks healthy. The other 40 seats are at risk on the next renewal. Get ahead of it with a usage-based or hybrid pricing conversation before the procurement team does the math themselves.
Multi-year contracts still help, but they’re harder to get and they’re not a defense against AI displacement on their own. In traditional B2B categories, they still protect against the procurement-cycle component of churn. But in any AI-adjacent category, the customer is going to push for one year, not three, and you’re not going to win that fight in 2026. The right move isn’t to fight the contract length. It’s to use the year you have to make yourself genuinely indispensable. Deep workflow integration. Proprietary data flywheels. Vertical depth. Things that aren’t replicated by a copy-pasted prompt. If your only retention strategy was a 36-month MSA, that strategy is over.
Make the renewal a formality, not a negotiation. This is the corollary to the contract-length point. If the customer can walk in 12 months, the only winning move is to be so embedded in their workflow within the first 90 days that the renewal isn’t a conversation. It’s just a re-up. That requires a product that delivers measurable value in days, not quarters. It requires a deployment motion that hits time-to-first-value fast. It requires a CS function that catches problems in week 4, not month 11. Earn the renewal before the question ever gets asked.
Build the AI layer in your product, even if it’s v1. Embedded agents, copilots, automations, anything that scales beyond seats. The customers most likely to churn in your Year 2 or Year 3 are the ones who deployed your product in 2023-2024 with zero AI. That product feels like ancient history to them in 2026. Modernize it, even at the cost of some short-term margin.
Get a real FDE and CS function, not a renewals function with a different name. This means CS reports to the CEO, not the CRO. It means CS comp is tied to engagement and outcomes, not just NRR. It means CS proactively flags accounts where usage is dropping, not just accounts where renewal is coming up. The original Year 3 thesis assumed a functioning CS organization. If yours has been hollowed out into a renewals desk, the death spiral hits faster and you don’t see it coming.
Have the hard conversations early. If a customer’s usage is half what it was last year, get on a plane. Today. Not at QBR. Not at renewal. Today. The $60K vendor in our story didn’t lose us in Year 3. They lost us in Year 7, silently, because no one ever asked.
5 Comments
For us, the #1 issue was a dependent integration. Most typically, their Salesforce deployment would be delayed and our contingent integration thus wouldn’t be deployed.
This so happened to us. At least it was predictable and we knew what will happen so we tried everything we could to prevent that.
Thanks. Any thoughts on how to measure user engagement in-product to provide this early warning about possible churn risk? Both in terms of what to measure, which tools to use, and which teams (customer support/success, product, etc.) should be involved.
There are tools like getamity or other customer success tools that will measure how often a certain user has logged in, their engagement and activity. At Promomash, we measure how long it takes for a user to submit a report (usually if its under 3 days, they got it, if its over 10 days, we give them a call)
Great post. (I just discovered your blog, hence I am looking at this early post!)
What do you think are the main reasons for non-use?
We are seeing some of these customers who finally pulled the plug after 2 years of not using an expensive SaaS coming to us saying they didn’t use it because it was too complex to use or was too much more than what they were looking for. Competitive replacement, IMO, can be huge in any SaaS segment with a bunch of players.