Every vendor has customers who bought the whole platform and use a corner of it. They log in for one report, one workflow, one integration, and ignore the other nine-tenths of what you sell. The instinct is to leave these customers off your testimonial list — they seem like weak advocates, half-adopted and easy to lose — and to chase the power users instead. That instinct is backwards. A customer who uses one feature and depends on it completely can write a more persuasive testimonial than a power user who uses everything a little, because a narrow, deep endorsement is more believable than a broad, shallow one. The catch is that you have to collect it carefully, so the quote showcases the depth of their use without advertising the narrowness of it.
Why the light user's quote can beat the power user's
A prospect reading testimonials is suspicious of breadth. When a quote says "this platform transformed every part of our operation," the prospect discounts it — nobody's experience is that total, and superlatives read as marketing. But when a quote says "we run our entire month-end close through one report in this tool, and it has never once been wrong," the prospect believes it, because it is specific, bounded, and checkable.
That is the mechanism worth understanding. A narrow quote is credible precisely because it is narrow. The light user isn't claiming the product did everything; they are claiming it did one thing extraordinarily well, and a bounded claim carries more weight than a sweeping one. The prospect who has the exact same job-to-be-done sees themselves in that single feature and needs nothing else. So the customer who uses a fraction of your product is not a weak reference — they are the ideal reference for the specific buyer whose need matches that fraction.
Match the light user to the prospect who wants exactly that
The first move is to stop thinking of these customers as generic advocates and start mapping each one to the feature they live in. A customer who only uses your reporting engine is the perfect proof point for a prospect evaluating you for reporting. A customer who only uses your API is the perfect proof point for a developer-led buyer. The narrowness that looked like a liability becomes an asset the moment you aim the quote at the buyer with the matching need.
Practically, this means:
- Tag testimonials by the feature they endorse, not by the customer's size or logo. When a reporting prospect shows up, you want to hand them the reporting quote, not a generic one from a bigger name who barely mentions reporting.
- Collect a portfolio of narrow quotes, not a few broad ones. Ten customers each vouching deeply for one feature covers more buyer intents than three customers vaguely praising the whole thing.
- Let the light user speak only to what they know. Their credibility comes from staying inside their lane, so never stretch their quote to cover parts of the product they have never touched.
Ask about depth, not breadth
The interview mistake that ruins these testimonials is asking breadth questions — "what do you love about the platform?" — to a customer whose honest answer is "I only use one part." That question forces them to either fake familiarity with features they ignore or admit how little they use, and neither produces a usable quote. Ask depth questions instead, aimed squarely at the feature they actually rely on.
Questions that draw out the depth:
- "What would break if this one feature disappeared tomorrow?" This surfaces genuine dependence. A customer who would be in real trouble without your reporting engine will describe that stakes-level reliance vividly, and dependence is the most persuasive thing a testimonial can convey.
- "How often do you use it, and what does it replace?" Frequency plus the displaced alternative — a spreadsheet, a manual process, a competitor's tool — gives the quote a before-and-after shape without ever needing the rest of your product.
- "Who else on your team touches it, and what do they say?" This tells you whether the narrow use is deep in one person or wide across a team, and a feature that a whole team runs on is a stronger proof point than one a single user opens occasionally.
None of these ask the customer to comment on the ninety percent they ignore. Every one of them mines the ten percent they know cold, which is exactly the material a matched prospect wants.
Frame the quote around the job, not the product tour
When you write up the testimonial, resist the urge to pad it into a broad endorsement. The temptation is to add a sentence implying the customer uses more than they do, to make them look like a fuller adopter. Do not. It makes the quote less believable and risks a customer retraction when they read a claim they can't stand behind.
Instead, frame the quote around the job the customer hired the feature to do:
- Lead with the outcome, bounded honestly. "We closed our books three days faster once we moved the reconciliation into this" is stronger than "this platform runs our whole finance stack," because it is true and specific and a prospect can picture it.
- Keep the scope visible and make it a virtue. A quote that says "we use exactly one thing here, and it's the one thing we could never go back to doing manually" turns narrow use into a signal of how good that one thing is.
- Attribute it to the role that matches the buyer. A quote from the analyst who lives in your reporting tool lands harder with a reporting prospect than the same words from a VP who signed the contract but never logs in.
Done this way, the light user's testimonial never exposes how little of the product they touch — because the quote is about the depth of one thing, and depth is what the matched prospect is buying.
Turn the fraction into a roadmap, not just a quote
There is a bonus in these conversations that most vendors miss. A customer who uses one feature deeply is telling you two things at once: which feature is genuinely load-bearing, and which of your other features never earned their attention. The testimonial captures the first. Note the second internally — it is honest signal about where your product delivers and where adoption stalls — and use it to decide which narrow quotes to go collect more of.
The strongest testimonial libraries are not built from a handful of customers praising everything. They are built from many customers each vouching, credibly and specifically, for the one thing they cannot live without. The customer who uses a fraction of your product is not a gap in that library. Collected well, they are its most persuasive entry for the prospect who wants exactly that fraction and nothing more.