Every product has a segment of customers who never really adopted it. They signed up for one feature, they use that feature constantly, and they ignore almost everything else you built. From a product team's point of view these customers can look like a failure of adoption — all that surface area, untouched. From a testimonial point of view they are one of the most valuable people you can ask, because they can tell a prospect exactly what one job your product does better than the alternative, in the words of someone who came for that job and stayed for it. This is how to turn a narrow, single-feature user into a testimonial that is more persuasive than a full-platform power user's.
Why a narrow user gives a better quote
The instinct is to chase the customer who uses everything, on the theory that breadth equals enthusiasm. But a testimonial from a power user tends to be vague precisely because they use so much — "it does everything we need" names nothing a prospect can grab onto. The single-feature customer has the opposite problem, which is actually a gift: they can only talk about the one thing they use, so their quote is forced to be specific. "We switched for the reconciliation report and it has never once been wrong" is worth more than three paragraphs of general praise, because it maps directly onto a job a prospect is trying to get done.
Specificity is what makes a testimonial survive a skeptical read. A prospect evaluating you is rarely asking "is this a good product" in the abstract — they are asking "will it do the one thing I am hiring it for." A quote from someone who hired you for that exact thing, and is still happy, answers the only question that matters. The narrowness you were worried about is the credibility.
Find them in your usage data, not your NPS list
You cannot find single-feature customers by asking who is happy — plenty of them are quietly satisfied and would never volunteer. You find them in the product analytics. Look for accounts whose usage concentrates almost entirely in one feature or one workflow: high, steady engagement with a narrow slice and near-zero everywhere else. That pattern is the signature of a customer who solved a specific problem and stopped looking. They are stable, they are retained, and they have a clear reason they stay — which is exactly the raw material of a testimonial.
Sort these accounts by tenure and consistency. A customer who has used the same one feature every week for a year is telling you, through behavior, that this feature is load-bearing for them. That behavioral signal is more reliable than a survey score, and it gives you a warm, honest opening for the ask.
Ask about the job, not the product
When you reach out, do not ask "would you write us a testimonial." Ask about the specific job they use you for: "You have been running the weekly reconciliation through us for about a year now — what were you doing before, and what would break if you had to go back?" That question does two things. It signals that you actually understand how they use the product, which earns the reply, and it steers them straight to the concrete before-and-after that makes a testimonial land.
The answer will almost always contain a usable quote already, because you asked about the thing they care about most. Your job is to lift the specific sentence — the one that names the job, the alternative, and the outcome — and ask permission to publish a lightly cleaned-up version. Resist the urge to broaden it into general praise; the narrowness is the whole value.
Publish it where the job is being evaluated
A single-feature testimonial is a targeting instrument, not a general trust badge. Placed on your homepage it is fine; placed on the feature page or the comparison page for that exact capability, it is a closer. A prospect who lands on your reconciliation page because that is the job they are evaluating should see, right there, a real customer saying the reconciliation has never been wrong in a year. Match the quote to the surface where its job is being decided.
This is also where deliberate testimonial infrastructure earns its keep. When you collect and tag testimonials by the specific feature or job they speak to, you can route each quote to the page where that job is evaluated instead of dumping every testimonial into one undifferentiated wall. And because narrow users are easy to overlook, it helps to have a standing habit of mining your quietly satisfied customers rather than only your loudest fans — the single-feature customer and the NPS passive are often the same understudied, highly credible person.
The narrowness is the point
It is tempting to see a single-feature customer as a half-adopted account you should be upselling instead of quoting. Upsell them if the second feature genuinely fits — but do not discount the testimonial they can give you right now. A prospect trying to decide whether you can do one specific job is not reassured by breadth; they are reassured by a real person who hired you for that job, uses it constantly, and would fight to keep it. Collect that quote, tag it to the job, and put it exactly where that job is being decided.