Every board deck has a retention slide, and it shows the same three numbers. Gross revenue retention. Net revenue retention. Net logo growth.
Those are the right numbers. They're also the slowest numbers in the building.
By the time NRR moves, whatever moved it happened two quarters ago. A customer who's going to renew flat in January decided that sometime around August, and nothing on the retention line will tell you until the invoice doesn't grow. That's not a flaw in the metric. Lagging is the job description. These are the scoreboard.
The question the board never quite asks, and should, is what you can see sooner.
The list that wasn't a list
I was working through a board update with an executive last week. We had the three numbers on one slide and a second slide of things we could watch while they moved. Onboarding cycle time. A confidence question asked after every training session. Whether every account had a named owner and written context. Whether a question asked by one customer got answered once, for everyone, instead of privately every time.
Good list. But it was a list, and a board doesn't want a list. Somebody pushed on it: what are these actually measuring?
Three things. Velocity. Confidence. Context.
Everything on the list was one of those three wearing an operational name. And once they had names, they stopped being tasks and started being signals.
Velocity
How fast does a customer get from signing to being able to do their job with the thing they bought?
Not logins. Logins can be a spike of curiosity or a spike of confusion, and the number can't tell you which. The line that matters is the one where everything is configured, the data is in, and the customer can now do the work they came for. That's onboarded. Training happens at that point because they're onboarded, not the other way around.
Once you draw that line you find the gap that's been eating it. In this case it was a stretch in the middle of onboarding that nobody had named. It took about as long as everything before it, and because it had no name, nobody was accountable for it and nobody could ask whether it was getting shorter.
You can't shorten a gap you haven't named. That's most of the work on velocity: name the stages, find the one that's silently doubling your cycle, put somebody on it.
And velocity is the one that pays twice. A customer who gets to the line faster realizes value sooner. They also see the path sooner, which is the perception clock that expansion runs on. Slow velocity doesn't just delay the first result. It delays the first time buying more becomes the obvious next step.
Confidence
After training, ask the customer how confident they feel using the product.
The first time you do this, a lot of them will say they don't know yet. They'd have to use it to tell you. That's not a failed question. That's the question telling you to ask it twice: once at training, once after they've been in the product on their own.
It's also not NPS, and don't let anybody on the board file it there. NPS asks whether they'd recommend you. That's a question about the past. Confidence asks whether they believe they can get the result, which is a question about the next ninety days. A customer who isn't confident doesn't use the product. A customer who doesn't use it doesn't realize value, and a customer who hasn't realized value has no reason to renew, let alone expand. Confidence is the earliest point on that chain where you can still do something about it.
Context
The customer should never have to repeat themselves. That's the floor, and most companies are below it.
Context is more than that. Knowledge is not making them say it again. Context is knowing what they're actually trying to accomplish, what they're worried about, what they mentioned in passing on the second call and never brought up again. It's the stuff a human on the call misses because they're paying attention to the thing being said, not the thing said sideways.
That intel is sitting in your call recordings right now. The commercial concern raised as a joke. The technical issue mentioned and moved past. The person who said what they need to prove to their own boss. None of it made the notes.
Here's why context belongs on a board slide and not in an ops meeting. You don't fully control your product roadmap. You don't fully control a delivery calendar with other people's schedules on it. You do fully control how well you understand the customer and how you show up for them. Of the three signals, context is the one with no external dependency. Nobody can be blamed for it but you, which is exactly what makes it a lever.
The part that made the whole thing click
The executive looked at the three words and said the CEO would get it immediately. Because those are the three things the CEO complains about.
Why is it taking us so long. Why are we asking the customer for that again. Why can't they get this done.
The CEO didn't know those were leading indicators. They just knew what made them angry, every week, in the form of complaints. Velocity, context, confidence, in that order. Nobody had written them down as metrics, so nobody could measure them, so nobody owned them, so they came back as complaints again the next week.
That's the pattern I'd bet is in your company too. The leading indicators for retention and expansion aren't hiding. They're the recurring frustrations of whoever's closest to the customer outcome. They've just never been named, and a thing without a name can't be measured or assigned.
What the slide looks like now
Three numbers. Three signals. Then what's been done and what's next.
The three numbers tell the board where you ended up. The three signals tell them where you're going to end up, early enough that the answer can still change. Everything under "done" and "next" is a lever on one of the three signals, or it shouldn't be on the slide.
One more thing about the "done" section, because it's where a new retention function gets its story wrong. Don't say nothing was in place before. It usually was. What was missing a quarter ago wasn't the work. It was the R. Everyone was responsible for retention, which is the same as nobody being responsible for it. Now somebody is, and they own three signals with names.
If your board deck has the scoreboard and no signals, you're reporting on a game that's already over.
Lincoln Murphy formally named and popularized Customer Success starting in 2010 and has spent 15 years connecting it to expansion revenue and commercial outcomes. Read The Premise.