Every product has a set of customers who are quietly using it for something it was never designed to do. The invoicing tool being run as a lightweight CRM because the contact fields happened to be enough. The survey app doubling as an internal knowledge base. The scheduling product repurposed to coordinate a volunteer rota. Product teams tend to treat these customers as edge cases — off the roadmap, hard to support, faintly embarrassing. That instinct is backwards. A customer who bent your product to solve a problem you never anticipated is handing you one of the most persuasive testimonials you can publish, because their story proves something a designed-for testimonial never can: that the product is useful enough, and flexible enough, that people reach for it unprompted. Here is how to find these customers and turn their improvisation into social proof.
Why the unexpected use case persuades
A testimonial that says "we used it exactly as intended and it worked" confirms the brochure. A testimonial that says "we started using it for something you never advertised, and it became essential" does something stronger — it signals that the product has depth and adaptability the marketing hasn't even claimed yet. Prospects read that as a product with headroom. If real customers are already stretching it past its stated purpose, the buyer reasons, then it will comfortably cover the ordinary purpose they came for, with room to grow into.
There is also a credibility effect. A story about an unusual use is inherently specific and hard to fake. Nobody invents "we run our contractor onboarding through your form builder" as a marketing line — it is too particular, too obviously grounded in a real workflow. That specificity is exactly what makes it believable. The odder and more concrete the story, the more it reads as something a real person actually did rather than a quote the vendor wrote for them.
How to find these customers
Unexpected use cases rarely announce themselves. The customer doing something clever with your product usually assumes they are the only one, and they will not think to tell you. You have to go looking. Three places reliably surface them.
The first is usage data that doesn't fit the profile. A customer on your invoicing plan who never sends invoices but creates hundreds of contact records is telling you, in behavior, that they are using the product for something other than invoicing. Anomalies in feature adoption — heavy use of a feature that is peripheral to your stated purpose — are the trail.
The second is support and success conversations. When a customer asks "is there a way to make it do X?" where X is outside the core use case, they have revealed an improvised workflow. Those tickets are usually closed and forgotten; they should instead be flagged as testimonial leads.
The third is simply asking. A short question in an onboarding survey or a check-in — "what are you actually using this for?" — routinely turns up answers the team never expected. Customers who use a product creatively are often delighted to be asked about it, because nobody ever has.
Ask about the workaround, not the product
When you approach one of these customers, resist the urge to steer them back to the official story. The temptation is to say "we're so glad the CRM features are working for you" — but they don't think of it as a CRM, and correcting their framing flattens exactly the detail that makes the story valuable. Instead, ask them to describe their own workflow in their own words. "You've set this up in a way we don't see often — can you walk me through what you're using it for and why it works?" invites the specific, textured answer that becomes the testimonial.
The best quote here is one that keeps the customer's framing intact. "We couldn't justify a separate CRM, so we just used the contact fields in ProofShow, and honestly it's all we needed" is worth more than any polished sentence about features, because it carries the ring of a real decision a real team made under real constraints. For related situations where the customer's relationship to the product is unusual, see how to get a testimonial from a customer who only uses part of your product and how to get a testimonial from a customer who credits their own team, not your product.
Place the story where the imagination it sparks does the most work
An unexpected-use testimonial is wasted on a generic wall of quotes. Its value is that it expands the buyer's sense of what the product can do, so it belongs where prospects are forming that judgment — on a use-cases page, beside a feature that is more capable than it looks, or in the sales conversation when a prospect asks "can it also handle...?" A quote from a customer who already made it handle exactly that answers the question with proof instead of a promise.
Be careful, though, not to over-claim on the back of one story. An unusual use case is evidence that the product is flexible, not evidence that the unusual use is officially supported. Frame these testimonials as "here's what a customer did" rather than "here's a feature we sell," and let the buyer draw the flattering conclusion themselves.
Make capturing improvisation a habit, not a lucky find
The reason these testimonials are rare is not that the use cases are rare — it is that nothing in the normal workflow catches them. Usage anomalies scroll past unremarked, "can it do X?" tickets get closed, and the customer who found a clever workaround never gets asked to describe it. The fix is to make the capture deliberate: a standing prompt in your success check-ins asking what customers actually use the product for, and a lightweight way to flag the interesting answers to whoever owns testimonials. A tool like ProofShow makes that flag-to-quote path automatic, so the customer who quietly turned your product into something you never designed becomes a published story instead of a curiosity nobody wrote down.