Rethinking LTV: True Lifetime Value Is Not Revenue, but the Behavioral Accumulation a User Invests in the Product

One of the best-loved slides in any investor deck is the LTV/CAC ratio. Three, four, sometimes five. Everyone in the room relaxes. I spent years building that slide, and I will admit I enjoyed the relief it brought.

Then I started seeing cohorts with flawless LTV on paper fall apart within a few months. The formula wasn't miscalculating anything. It was just calculating the wrong thing.

The formula's quiet assumption

The classic LTV calculation is simple: average revenue, gross margin and average customer lifetime. We usually derive the lifetime from churn. If monthly churn is three percent, the average user stays thirty-three months, we multiply, and out comes a number.

Hidden inside that calculation is a quiet assumption: the past is a good predictor of the future. However users behaved yesterday, they will behave tomorrow.

But a user paying you is not the result of getting value. It is the result of believing they get value. There is a time lag between the two. People keep paying for a while after they stop getting value. The card is charged automatically, they forget to cancel, they tell themselves “busy month, I'll look at it later.” The revenue curve trails the value curve by a few months.

So revenue-based LTV is a rear-view mirror. It shows very clearly where you came from. It doesn't show where you are going.

What does the user leave behind?

Earlier in this series I argued that value should compound over time. The longer a user stays, the more valuable the product should become for them. There is a flip side to that: the longer a user stays, the more they leave inside the product.

Three years of work history in a project management tool. Customer notes accumulated in a CRM. A team's shared library in a design tool. Bank accounts, integrations and automation rules connected to accounting software. The recommendations of a music app that knows you better than you know yourself.

I call this behavioral accumulation. The sum of the time, data, habits and organizational effort a user has invested in your product. Paying is a transaction; accumulation is a relationship.

True lifetime value is not the money a user pays you. It is what they have invested in your product and can't easily take back. The money is a consequence of that investment.

The reason I like this definition is that accumulation is a leading indicator. When a user's accumulation starts to shrink, revenue hasn't dropped yet. But it will.

Four layers of accumulation

Every product is different, but the forms of accumulation I see most often fall under four headings.

The first is data accumulation. Everything the user puts into the product, creates inside it, and would find tedious to move elsewhere. Documents, records, history, content.

The second is workflow accumulation. Where has the product settled into the user's day? Is it the first tab they open in the morning, or a tool they remember once a month? A product wired into a process, with automations set up and integrations to other tools, has a very different life expectancy from one sitting on the sidelines.

The third is team accumulation. You see this clearly in B2B. If one person uses the product, the product leaves when that person leaves the company. If people from five departments work in the same place, the product is no longer someone's preference; it is the organization's infrastructure.

The fourth is personalization accumulation. How well the product knows the user. Settings, preferences, learned recommendations, calibrated defaults. Switching to a new product means getting to know each other from scratch. And people don't enjoy starting from scratch.

A value health score

Put these four layers next to your revenue metrics and you get a far more honest picture. With the teams I work with we call it a “value health score.” The name doesn't matter; the logic does.

The score usually includes the recent repeat frequency of the product's critical behavior, the amount of data or content added in the last thirty days, the number of active integrations, how active users in an account are spread across roles and teams, and how much the personalization settings are actually used. Every product should pick its own components; what matters is testing whether the components you chose actually separate the users who stay from the users who leave.

Build that score properly and two things happen.

First, you see churn before it happens, not after. If an account's accumulation has fallen three months in a row, its renewal conversation will be hard. Knowing that two months before the renewal date is very different from finding out on the day.

Second, your growth conversation changes. Instead of “more users” you start talking about “deeper users.” Acquiring new users is expensive. Deepening the accumulation of existing users is often much cheaper, and the return lasts longer.

Don't turn accumulation into a prison

I need to add an important warning here, because this idea is easy to abuse in the wrong hands.

Accumulation can be used to keep users locked in. You make exporting data hard, turn the cancellation flow into a maze, keep the format closed. Churn drops in the short term. The charts look good.

But that isn't value; it's a hostage situation. The user stays because they can't leave. And a user who can't leave will never recommend you, and will leave at the first chance they get. Then they will talk about you wherever they go next.

My distinction is this: healthy accumulation makes the user say “staying here is better for me.” Unhealthy accumulation makes them say “getting out of here is too much hassle.” Both look identical on a churn chart. One is an asset, the other is a debt. We will talk about how that debt builds up in the final piece of this series.

Don't delete the LTV slide, add one next to it

None of this means revenue-based LTV is useless. Unit economics are real, cash is real, and investors are right to want that slide.

My suggestion: put another slide next to it. One that shows what your users leave inside your product. The accumulation curves of your cohorts. Which cohorts deepen over time, and which stay on the surface.

The revenue curve tells you what you earned yesterday. The accumulation curve tells you what you will earn tomorrow.

And when the two start to diverge, don't look at any other metric until you find out why.