RetentionCX
Blog

Who Defines Proof

Every customer eventually decides whether your product worked.

The only question is whether you're part of that conversation.

It's a common gap I see in Customer Success. A team does the hard part. They define first value. They agree on strategic outcomes with the customer. They might even build a baseline. And they still can't get the customer to measurable proof.

Picture the customer who loves the product. Uses it constantly. Strong champion. Healthy score on nearly every dimension except the one that matters most: goals. Ask them what the product is worth, and they can't tell you. Not in a way they could take to their boss.

That's the scene that worries me. A budget review. Someone asks about the spend. "We love it. The team is great." Then: "What's the ROI?" Silence.

Early in my career, I worked with a team that sold a service with a simple promise: we'll prove your sales go up. And they did. The graphs showed a clear upward turn right when we got involved. Then, in the recap meeting, customers would look at it and say, "We don't think it was you. We just had a good quarter."

Some of them cancelled.

That's what happens when you leave proof to the customer. They'll decide it without you, and they rarely give you the credit.

So why do CS teams avoid this conversation? Because measurement is hard, and nobody wants to be wrong. Many customer teams have no native metrics for the work your product touches. They don't track their time, and they aren't measured on revenue. Proof means asking the customer to do some work.

Here's where I see teams get stuck: they treat proof as one thing. It's two.

1️⃣ The strategic outcome. What the executive actually bought. This must be sharp, specific, and measurable, even if it takes 12 months or more to show up.

2️⃣ The predictors. The signals you believe tell you that outcome is coming. Faster answers to routine questions. Fewer status calls to outside partners. Fewer surprises.

The outcome has to be precise. Predictors can be rough. Self-reported estimates and before-and-after snapshots are fine. You're looking for direction, not decimal points.

But rough numbers still need tight logic. Your customer has to agree that the predictor points to the outcome. Otherwise it's your proof, not theirs.

And you won't get the predictors right the first time. Try something. If it doesn't move, try something else. Customers often say, "We didn't see that, but we did see this." That's usually the better measure anyway.

The easiest way to start? Ask before you propose. "In 12 months, how will you know this worked? What do you expect to see in the first month or two?" Keep your own list as a backup.

Being wrong about a predictor is recoverable. Staying silent isn't.

When renewal comes, you want the decision-maker thinking, "We've talked about this every month for a year." Not trying to connect the dots on their own.

So who's defining proof for your customers right now: you, or them?

More articles