Beyond NPS: A More Rigorous Way to Measure Customer Advocacy

For years, customer experience has been summarized in a single number: Net Promoter Score. Ask a VP of Customer Success how their customers feel and they'll give you a number between -100 and 100. Fair enough. NPS provides a directional view of sentiment, it allows benchmarking across industries, and it fits neatly into board slides.

But here's what NPS can't tell you: whether any of that goodwill is actually getting used. A company can have an NPS of 70 and still struggle to produce credible case studies, verified quotes, or reference customers when a deal depends on it. We see this constantly. The promoter score looks great. The pipeline of usable customer proof? Thin.

That's the core NPS limitation, and the reason more teams are exploring net promoter score alternatives — and, more fundamentally, why NPS and voice of customer aren't the same kind of thing. NPS measures whether customers would recommend you. It says nothing about whether anyone captured what they said, structured it into something usable, or kept the pipeline fresh. Measuring customer trust requires more than a survey question.

So the real question becomes: is customer advocacy compounding, or quietly eroding? Answering that requires customer advocacy metrics that go beyond a single score.

Advocacy Is a System, Not a Survey Result

Think about how advocacy actually works inside an organization. Someone has a great call with a customer. The customer says something genuinely compelling about the impact of your product. What happens next?

In most companies: nothing systematic. Maybe someone mentions it in Slack. Maybe it gets half-remembered in a quarterly review. Maybe, if the stars align, someone from marketing follows up three weeks later and the customer can't quite remember what they said. That last one happens more than anyone wants to admit.

The problem isn't a lack of happy customers. It's that the machinery for converting those experiences into durable, reusable proof breaks down at predictable points:

Signal capture gaps — Great experiences happen all the time. Most go unrecorded. There's no structured story capture process, no systematic extraction of claims, no way to catch the moment before it fades into marketing decay.

Activation friction — Feedback gets captured but sits in a backlog. Nobody reviews it. Nobody verifies the proof. Three months later it's stale and the customer has changed roles.

Momentum decay — A team runs a customer story blitz in Q1, collects a dozen great interviews, then does nothing for six months. The proof pipeline looks full in March and empty by August.

Traditional voice of customer software surfaces the feeling. They don't track what happens to it afterward.

Three Signals That Actually Matter

Customer advocacy breaks down into three distinct signals. Each captures something that standard customer experience metrics like NPS miss on their own.

1. Enthusiasm

This is closest to what NPS already measures, but with more texture. Enthusiasm asks: are customers expressing advocacy in ways that translate into credible proof?

That means looking at:

• Promoter density from NPS — what share of your base is actively positive?
• Language specificity — are customers citing concrete outcomes ("reduced churn by 18% in Q3") or offering generic praise ("great product, love the team")?
• Claim density — how many customer proof claims are emerging per interview or survey response?

The difference between those two types of customers matters enormously. "I love your product" is nice. "We cut our sales cycle by three weeks after deploying your proof library across the BDR team" is a revenue asset. One makes you feel good; the other closes deals.

2. Activation

This is where most organizations quietly fall apart. Activation measures whether the team is actually doing something with whatever enthusiasm exists.

Concretely:

• Are captured claims being reviewed on a regular cadence?
• Are they getting verified or rejected, not just accumulating?
• Is proof spread across multiple customers and segments, or concentrated in the same three logos everyone already knows?
• Is the marketing governance backlog growing or shrinking?

We should be honest about why this happens: it's usually not laziness. It's that nobody owns the process. Customer success captures the signal. Marketing needs the output. But the handoff between them (reviewing claims, verifying accuracy, making proof reusable) falls into a gap where neither team has clear accountability.

3. Momentum

Advocacy momentum answers the forward-looking question: is proof generation accelerating, holding steady, or winding down?

This shows up across several dimensions: the rate of new Story Studio interviews, the velocity of new structured claims, NPS participation volume, and how consistently these activities happen week over week.

Here's where measurement gets tricky. Momentum should be calculated using slope over time, not simple period-over-period comparisons. A team that collects 30 stories in January and zero in February has terrible momentum even though their January number looks impressive. Spikes mislead. We've seen teams celebrate a "record quarter" for customer stories that was really just one burst followed by silence.

The question that matters: if we keep operating at this pace, will we have more usable proof in six months, or less?

The Customer Love Index

Most customer advocacy metrics stop at sentiment. The Customer Love Index (CLI) pulls all three signals into a single composite score:

The weighting is deliberate. Enthusiasm gets the largest share because it reflects an external reality you can't manufacture. Customers either advocate for you or they don't. Activation and Momentum split the remainder because they represent the internal levers a team can directly improve. You can't force customers to love you, but you can build a better system for capturing and acting on that love when it shows up.

A few design decisions worth mentioning. The score uses conservative statistical smoothing so it stays stable even with low data volume. You don't need thousands of responses. Every sub-dimension is visible, so when the number moves you can trace why. And there are guardrails against gaming, because we've seen what happens when teams discover they can spike a metric by bulk-verifying a backlog of stale claims in one afternoon. (It doesn't count.)

Proof Depth: A Fourth Signal

In addition to the three core dimensions, CLI factors in proof depth — a measure of how diverse and quotable your customer evidence actually is.

Proof depth looks at two things. First, type diversity: are your claims spread across the four proof-native types (Metric, Outcome, Process, Before State), or concentrated in just one? A company with "we saved 40%" (Metric), "legal stopped blocking launches" (Outcome), "automated the approval workflow" (Process), and "used to spend three weeks per approval" (Before State) has a complete proof narrative. A company with only generic outcomes does not.

Second, quotable density: what percentage of your claims have language vivid enough to use on a quote card, in an ad headline, or in a case study? High quotable density means your interviews are producing marketing-ready assets, not just data points.

Proof depth is a small additive bonus (up to 5 points), but it rewards the kind of evidence that actually closes deals — diverse, specific, and authentically expressed.

Why the Trend Line Matters More

Here's where it gets interesting. A high CLI is fine. But the trend is almost always more revealing than the absolute number, and it's where the concept of "vanity love" becomes visible.

Vanity love is what happens when a company has strong NPS, a handful of genuinely great customer testimonials that get recycled across every deck, and leadership that references customer love in every all-hands. On the surface, everything looks healthy. But the customer evidence inventory is shallow. The same three case studies cover one vertical. Quotes are months or years old. When a sales rep needs a reference for a specific use case, there's nothing ready.

CLI makes this visible through trend:

A high but declining CLI means you're consuming proof faster than you're replenishing it. Great inventory today, but the pipeline is drying up. Interview cadence has dropped, or the review backlog is growing faster than anyone can process it.

A moderate but rising CLI is actually the stronger position. The advocacy flywheel is building. Each month produces more usable evidence than the last. The absolute number might not look impressive yet, but the trajectory says the system works.

A stable CLI with sustained activity is the mature state. No heroic efforts needed. Just consistent execution, week after week. Most teams underestimate how rare and valuable this is.

If you have to pick one thing to watch, watch the trend. Levels tell you where you are. Trends tell you where you're headed.

Finding the Constraint

Rather than chasing a higher composite number, the more productive move is figuring out which signal is the bottleneck. The fix depends entirely on where the system breaks.

Low Enthusiasm? The raw material isn't there. Usually this means the team isn't conducting enough structured customer interviews, or the interviews aren't surfacing outcome-specific language. Sometimes it means detractor feedback isn't getting closed-loop attention, which quietly suppresses promoter share over time. This is the hardest constraint to fix because it depends on customer behavior you can't directly control.

Low Activation? Raw material exists but isn't being processed. Almost always a cadence and ownership problem. Nobody has explicitly claimed responsibility for reviewing captured claims, verifying them, and making them usable. Establishing a weekly proof review rhythm, even just 30 minutes, fixes this faster than any tool. Assign an owner. Set a recurring meeting. The marketing operations discipline matters more than the tooling.

Low Momentum? The system works when someone pushes it, but it doesn't run on its own. Invitation volume is inconsistent. Interviews happen in clusters around launches or QBRs instead of steadily throughout the year. The fix is treating advocacy generation as an always-on operating motion, like demand gen or content marketing, rather than a periodic project.

Why This Matters Now

AI-generated content is making generic marketing claims worthless. When anyone can produce a polished blog post or landing page in seconds, the bar for credibility shifts hard. Buyers want to see where claims came from. Specific customers, specific outcomes, specific contexts. Measuring customer trust in this environment means showing your work.

The companies that build a system for producing and sustaining advocacy, measured with real customer advocacy metrics and not just sentiment surveys, will have a structural advantage. Everyone else will keep running quarterly testimonial campaigns and wondering why the proof is never ready when deals need it.

Frequently asked questions

How is CLI different from NPS? Think of it this way: a company with NPS 65 and CLI 38 has customers who love them but an organization that isn't capturing or using that love effectively. NPS tells you the raw sentiment exists. CLI tells you whether it's being turned into verified customer evidence at a sustainable pace. You need both numbers to understand the full picture.

Do I need a lot of data for CLI to be useful? No. The scoring uses statistical smoothing designed for real-world B2B volumes, not consumer-scale data. Even a handful of interviews and a modest NPS sample produce a meaningful directional signal. Activation and Momentum are especially useful early because they measure your team's operational behavior, not customer survey responses.

Where does CLI live? Is it a separate tool? CLI is built into Shine Studio as part of the proof operations dashboard. It pulls from NPS data, interview activity, and claim verification status that already exist within the platform. No additional data collection or integrations required.

What is proof depth? Proof depth measures whether your customer evidence covers the full proof spectrum. A healthy proof pool has metrics (numbers), outcomes (results), process descriptions (how), and before-state pain points (why). CLI rewards breadth because prospects need to see the complete story — not just one type of evidence repeated across every customer.