Reference Customers: What to Send When a Buyer Asks "Who Else Like Us?"

The short answer: when a buyer asks who else like them you have worked with, what closes the gap is usually something you can send within the hour, not a call you have to schedule. A case study from a similar company, one relevant quote, or a short email naming a specific result does the job a live reference call would have done, at a fraction of the lead time and without spending one of the same three willing customers you always end up asking.

Why this question always seems to land badly

"Who else like us have you worked with" is one of the most common questions in a B2B sales cycle, and it is also one of the worst-timed. It usually arrives late, after the buyer has already decided the product works in general and is now checking whether it works for a company like theirs specifically. That is a good sign for the deal and a bad time to discover you cannot answer it quickly.

The actual problem is rarely that no reference exists. It is that proof gets organized by when it was published, not by who it is for. Ask most marketing teams "who do we have that looks like this specific prospect" and the honest answer is a scramble through old files, not a lookup. The same audit that decides whether a battlecard is usable, segment by segment: named proof, quantified, a reference willing to take a call, usually turns up one strong row and several empty ones. The empty rows are exactly where this question catches a team flat-footed.

What actually answers it, ranked by speed

Most of what arrives mid-deal is answerable with the first two rows. The mistake worth avoiding is treating every version of this question as a request for the third row by default, because the third row is the one option here you cannot manufacture on demand.

When to reach for which

• ●The buyer asked casually, mid-call, without pushing? Send a written case study from the closest matching segment within the hour. Most of these asks are checking a box.
• ●The buyer named a specific concern ("but does it work for a company our size")? Pair a case study with a short email restating that exact concern and naming the outcome. Generic proof does not answer a specific objection.
• ●The deal is large enough that a customer's time is worth spending? Offer the call, but confirm first that the buyer has already read a written story. A call that only fields follow-up questions is a better use of a reference's time than one that has to repeat the whole account from scratch.
• ●Nobody on your list matches this buyer's segment? Say so, and offer the closest adjacent story with an honest note about the difference. A buyer who catches a stretched reference trusts you less afterward than one who hears the honest version.

The reference-call problem specifically

A live reference call is the one option above you cannot produce on demand, and most enablement libraries quietly treat it as an unlimited resource anyway. It is not. TrustRadius's 2024 survey of 2,164 B2B buyers found 56% spoke to an actual product user before purchasing, but only 27% used a vendor-provided reference. Most buyers who want to talk to someone go and find their own person, rather than waiting for a vendor to arrange one.

Read that gap the right way round. It means the buyers a written case study can reach, the ones checking a box or forming an impression, are a larger group than the ones who will ever ask for a live call. Spending a written asset on the larger group and reserving a live customer's time for the smaller one is not a compromise. It is matching the tool to the job.

The same three or four willing customers end up fielding every reference call for a given segment, and each one has a limit before "always happy to help" turns into visible fatigue. Treat that willingness as a resource you spend on purpose. Running an actual rotation so no single account carries the whole segment is a distinct, harder problem worth its own treatment later; the point here is narrower: most of the calls that would spend it are avoidable with something you could have sent instead.

Build the bench before the question lands again

The teams that never scramble for this have done one specific thing before the question ever comes up: they know which segments have a named, quantified, callable reference and which do not, the same way a usable sales enablement library tracks proof by situation rather than by product feature.

Building that bench does not require a special reference-gathering project. Every customer conversation that is already happening is a candidate: a renewal call, a QBR, a support ticket that closes well. A five-minute voice interview run off the back of any of those produces a written case study, a pull quote, and a sales email in one pass, StoryVoice's own version of this generates all three from the same conversation, which is exactly the artifact this question is asking for, sitting ready before anyone asks. Turning that single interview into the deck slide and one-pager a rep can actually use is the same underlying move, and so is everything else worth cutting from one finished story rather than treating each format as a separate project.

There is also a version of this question that never has to be answered live at all. A prospect doing their own research who finds a closely matching story on your site during evaluation has effectively answered it themselves, and the request never reaches a rep in the first place. That does not replace the moment this post is actually about, a live deal where the question has already landed mid-call, but a library published where search and an AI answer engine can both find it shrinks how often that moment happens.

If you already run a formal reference or evidence program, the individual named stories your sales team wants to attach to a specific deal are usually the part left to a marketer to produce by hand even inside that program, and platforms built for aggregate, blinded statistics are not a substitute for one. If you are shopping for something to organize that library, we compared the category honestly, sorted by the actual job each tool does rather than treating every result as interchangeable.

Try it on a conversation you already have: paste an old call transcript or your notes into the free AI case study generator. No email required. If the material genuinely does not support an honest reference, it says so rather than manufacturing one, which is exactly the behavior you want from anything you might hand a skeptical buyer.

What if nobody matches this buyer's segment

Sometimes the honest answer is that you do not have one yet. Say that plainly rather than stretching an unrelated story to fit. "We don't have a customer in your exact vertical yet, here's the closest one, and here's specifically why it's still relevant" reads as more credible than a forced match, because it signals you are not willing to oversell proof you do not have. Buyers who are far enough along to ask this question are also far enough along to notice when a reference doesn't quite fit, and the recovery from a noticed mismatch costs more trust than the honest gap ever would have.

That gap is also the clearest signal you will get about where to spend the next interview. If this segment keeps coming up empty, it is the next customer conversation worth turning into a case study, not the twentieth story from a segment you already cover well.

The honest verdict

Most of what gets asked as "can we get a reference" is actually a request for evidence a specific person solved this problem, and a well-matched written case study answers that as completely as a call does, in a fraction of the time and without spending a favor. Save the live call for the deals big enough to justify it and the buyers who have said, specifically, that a written story is not enough. Build the bench out of conversations you are already having, and the next time this question lands mid-deal, it stops being a scramble.

Turn your next customer conversation into a reference-ready story. First case study free, no credit card required.