Back to Blog
testimonials
credibility
conversion

How to Attribute Results Honestly When a Customer's Win Was Partly Luck

ProofShow Team··5 min read

A customer tells you their revenue is up 40% and they're thrilled with your product. You want to quote them — "Since switching to us, revenue grew 40%." It's true, technically. They did say it, and the number is real. But you both know the fuller story: they also hired two salespeople, launched in a new market, and caught a favorable quarter. Your product helped. It did not, by itself, produce 40%.

This is the attribution problem, and it sits at the center of every results-based testimonial. Claim too little and the testimonial is toothless. Claim too much and you've written a quote that will not survive a skeptical prospect's first question — "Was that really the software, or was that everything else they did that year?" The goal is not to shrink the claim. It's to claim exactly the credit you earned, and to make the boundary of that credit visible.

Why over-attribution quietly kills trust

A prospect reading "revenue grew 40% after switching" does one of two things. The naive reader believes your product single-handedly moved the number — and is disappointed later when their own results are smaller. The sophisticated reader, the one who actually buys, immediately discounts the claim, because they know revenue never moves for one reason. Either way you lose: the first customer churns confused, and the second customer trusts you less for having implied a causation you can't defend.

Correlation stated as causation is the most common credibility leak in testimonials. "After using us" is not the same as "because of us," and experienced buyers hear the difference even when you don't spell it out. The fix is to be the one who spells it out — because a vendor who names the limits of their own contribution is a vendor worth believing on everything else.

Isolate the mechanism, not the outcome

The honest version of a results testimonial doesn't claim the outcome. It claims the mechanism — the specific thing your product did — and lets the outcome sit nearby as context.

Compare:

  • Over-attributed: "We grew revenue 40% with ProofShow."
  • Honestly attributed: "ProofShow cut the time to publish a customer testimonial from three weeks to a day, so our sales team finally had fresh proof to send. Revenue was up 40% that year — new hires and a strong market drove most of it, but we stopped losing deals to 'can you show us a reference.'"

The second version is longer and more persuasive, not less. It names a concrete, believable mechanism (faster proof in the sales cycle), it concedes the other drivers, and it makes a modest, defensible causal claim (fewer lost deals). A prospect can picture that happening to them. That's what converts — a mechanism they can reproduce, not a headline number they can't.

A three-question test before you publish a number

Run any results claim through these before it goes live:

  1. Could the customer have hit this number without us? If yes, the number belongs as context, not as the claim. Attribute the mechanism instead.
  2. What else moved the metric? If you can name two other drivers, the honest testimonial should acknowledge at least the biggest one. Concession is credibility.
  3. Would the customer defend this exact phrasing on a reference call? If the quote implies more than they'd say out loud to a prospect, you've over-reached. Pull it back to what they'd actually stand behind.

Any claim that fails these isn't false — it's unsupported, which reads as false the moment someone probes it.

Let the customer draw the line

The cleanest way to attribute honestly is to ask the customer to do it for you. Instead of "How much did revenue grow?" ask "What did our product specifically change about how you work?" and "What else was going on that year?" The first question gets you the mechanism; the second gets you the honest boundary. Customers are usually relieved to give both — most of them are uncomfortable letting a vendor imply their whole success came from one tool, because they know their own team did the work.

When you send the draft back for approval (a step you should never skip on a results claim), the concession you included is what makes them comfortable signing off. "Revenue was up 40%, though most of that was our own expansion" is a sentence a customer will happily approve. "Revenue grew 40% with ProofShow" is the one they quietly ask you to soften — and now you've lost the number entirely.

Modest and specific beats bold and bare

The instinct is to reach for the biggest number and the shortest sentence. Resist it. A precise, bounded claim — "cut our proof turnaround from three weeks to a day" — outperforms a vague blockbuster — "transformed our business" — because prospects buy mechanisms they can reproduce, not miracles they have to take on faith.

For the related problem of a testimonial that's true but too fuzzy to persuade, see how to turn a glowing but vague testimonial into specific proof. And when a claim genuinely needs a caveat to stay honest, adding a results disclaimer is the right tool rather than deleting the whole testimonial.

Claim the credit you earned. Name the credit you didn't. The boundary is not a weakness in the testimonial — it's the thing that makes the rest of it believable.

Ready to get started?

Start collecting and showcasing testimonials in under 5 minutes.

Start Free