Your buyer's AI has probably already read about you. Then somebody on their side checks what it said. In an enterprise deal the strongest check is a customer reference call, a call between your buyer and one of your customers. It is the one conversation about your product that you are not on.
This is for founders and CROs selling to enterprise buying committees from a short customer list. Plenty of founders manage every other stage of the deal carefully and treat the customer reference call as a favor they ask at the end. That is backwards. The reference call is a deal stage with an owner, a routine and a failure rate, and nobody is running it.
The shortlist gets audited
The TrustRadius 2026 B2B Buying Disconnect Report, released on July 15, 2026, surveyed 1,862 technology buyers and 444 vendors in January 2026. It found that 63% of the buyers had used AI during a software purchase, and that 94% of those buyers fact checked its answers at least some of the time. TrustRadius is now part of HG Insights and the sample covers technology buyers only, so read it as direction, not as a law of nature.
Gartner points the same way from a different angle. In a May 20, 2026 release on a survey of 645 B2B buyers, run in August and September 2025, Gartner reported that 69% of buyers prefer to validate AI generated insights with sales reps. It also said reps stay the most important source when buyers are identifying a preferred supplier, securing internal support and finalizing the purchase. Same survey, a near tie on trust: 51% said they were more likely to meet misleading information from GenAI, 49% from a sales rep.
Be careful what that proves. Gartner is talking about reps, not references. Nothing retrieved for this piece reports the share of buyers who call a vendor's customers before they sign, and anyone quoting you a tidy percentage without naming the survey is guessing. What the research does show is the direction. Buyers check, they distrust everybody a little, and the late stage is where checking happens.
Here is the inference, and it is a judgment, not a finding. If a buyer is wary of both the AI and the rep, the voice they are most likely to believe is the one with no quota. That is your customer.
The call you are not on
Look at the rest of your process. You run discovery, you build the demo, you handle pricing and you sit through procurement. Every one of those you can prepare, observe and correct. The reference call you request, then you wait.
In the CRM it shows up as a stage name and a silence. A week passes. The deal looks fine. Sometimes it stalls because the call went badly, or never happened, or happened with the wrong person, and nobody told you, because the buyer is not obliged to and your customer does not know the deal is at stake.
It is easy to blame price or timing when that deal dies. The reference problem is invisible, which is why it keeps going unfixed.
Three ways a good customer sinks a good deal
The wrong peer. Your buyer is a head of operations at a large company and your friendliest customer is a marketing lead at a small one. They have a pleasant chat that answers a question nobody asked. The buyer's real worries, integration, security review, who picks up when something breaks, go untouched. A reference should match the buyer's role and situation before it matches your relationship.
The unbriefed customer. Your customer does not know what you sold this buyer, what the committee is nervous about or what is off limits. Wanting to help, they improvise. They promise a feature that is on a roadmap, they guess at pricing, or they say something warm and vague that tells the buyer nothing. A helpful customer with no context is a risk.
The overused customer. Take an illustrative case, not a measurement. You have five customers who fit enterprise buyers. In one quarter four deals reach the reference stage and each buyer asks for two calls. That is eight calls landing on five people, and in practice on whoever replies fastest. Calls bunch up, replies slow down, and the customer who likes you starts to see you as a cost. You can burn the most valuable relationship you have for the sake of one deal.
All three have the same cause. The reference is treated as an event, when it is a small system.
Build a customer reference file
Make one page for each customer who could ever be a reference. If it takes more than an afternoon for your whole list, you have a bigger problem than references. A good page holds six things:
- Who they are. Role, segment, size, what they bought and what they actually use it for.
- Which buyer they fit. The titles and situations they can credibly speak to, and the ones they cannot.
- What is in and out of bounds. Implementation, support, results they own are in. Pricing, roadmap and other customers are out.
- Permission. A clear written yes, and how they prefer to be contacted.
- Load. Calls taken this quarter, the date of the last one and a cap. A reasonable starting rule is two a quarter. It is a rule of thumb, not a benchmark, so change it when the customer tells you to.
- Owner. One named person at your company who makes the ask, briefs the customer and closes the loop. If everyone owns it, it drifts back to the founder's inbox.
That page is the whole program for a company with a short bench. You do not need an advocacy platform, a points system or gifts.
Brief with context, not a script
Before the call, tell the customer three things: what the buyer is trying to do, who will be on the call and what the buyer is probably worried about. Say what is off limits. Leave the answers alone.
Scripts fail for a simple reason. Enterprise buyers can hear one. A committee member who has run vendor selections before will ask about implementation, about the second month, about what went wrong, and a prepared answer sounds exactly like what it is. Context makes your customer more useful. A script makes them less credible.
Make saying no easy as well. A customer who is reluctant and agrees anyway is worse than no reference. Keep a second name ready, and tell the customer that declining will not cost them anything.
Offer it early, and offer two
Many founders wait until the buyer asks, which tends to be late in the deal. Put the reference in the plan once you know who is on the committee. RivoAxis has written about multithreading enterprise deals, and a reference works the same way: it gives a different committee member a reason to trust you. It also helps your champion, who has to write something to carry upstairs. See our piece on the internal selling memo. A line like "I spoke to a peer at a company your size and here is what they said" tends to carry more weight than a feature list.
Now the fair objection. Buyers know you picked the reference. They discount a curated customer, and they lean on reviews and independent voices instead. TrustRadius reports, via Demand Gen Report coverage, that 74% of the buyers it surveyed used reviews, and that peer reviews rank among the most influential inputs when buyers commit to a vendor. The objection is right. A reference you chose is a floor, not proof.
So offer two. Give the buyer one customer you selected and let them pick a second from your public customer list. This only works if you can stand behind everyone on that list. If you cannot, the list is the finding, and you are better off knowing before a buyer does. It also fits with what RivoAxis wrote about what a buyer's AI can find before anyone calls you: the public record and the private call should tell the same story.
There is one condition where all this is wasted. If you have no customer who fits the buyer, say so early and plainly. A mismatched reference is worse than an honest gap.
Close the loop
After the call, ask your buyer what they heard. Do it within a day and keep it light. Do not interrogate the customer. Then tell the customer how the deal ended, win or lose, and thank them. Customers who never hear the outcome are less likely to say yes next time.
Log every call in the reference file: date, buyer, who made the ask. That log is also how you keep the load cap honest. And don't pay for references. Anything that looks like payment can make the call worthless to the buyer who finds out.
What to do this week
List the customers who could take a call. Fill in the page for each, name the owner and set the cap. Then go through your late stage deals and ask, deal by deal, which reference you would offer, whether they have been briefed and when you plan to raise it.
If you are not sure where your late stage deals leak, including the steps you do not run yourself, book a Revenue Diagnosis conversation with RivoAxis.
Book a Revenue Diagnosis