Sales Enablement Aside—Reference Call Prep: How to Coach B2B Customers to Sell for You on Live Calls
By Rick Elmore ·
Most reference calls are set up like blind dates. You pick a happy customer, forward an intro email, and hope the chemistry works. Then you cross your fingers while two people who've never met try to have a useful conversation about your product with no shared context and no plan. Sometimes it lands. Usually it drifts.
A reference call is not a favor you're collecting on. It's a sales asset you're deploying at the highest-stakes moment of the deal. And like any asset, it performs based on how well you prepare it.
What is reference call preparation, and why does it decide the outcome?
Reference call preparation is the deliberate work you do before a prospect talks to an existing customer: matching the right customer to the right prospect, briefing that customer on what to emphasize, and pointing the conversation at the specific doubts blocking the deal. Done well, your customer walks in already knowing which objections to defuse and which outcomes to highlight.
Here's why it matters so much. By the time a prospect asks for a reference, they've largely decided they want to buy. What they're doing now is looking for a reason not to. They want a peer to confirm the risk is real but manageable. An unprepped reference call leaves that confirmation to chance. A prepped one turns your customer into a peer advocate who addresses the exact fear keeping the buyer up at night.
The difference between the two isn't luck. It's twenty minutes of prep and a repeatable system.
How to match the right customer to the right prospect
The single biggest lever in reference call preparation is the match. A generic "happy customer" is worth far less than a customer who mirrors the prospect's situation. Buyers discount praise from companies that don't look like them. "Sure, it worked for a 500-person enterprise, but we're 40 people in a regulated industry" is a thought your reference can't overcome if the fit is wrong.
When you're choosing who to put on the call, weight the match across a few dimensions in order of importance:
- Same primary objection overcome. If your prospect's blocker is "we tried something like this and it failed," your best reference is a customer who had a failed prior attempt and succeeded with you. This trumps every other factor.
- Similar company profile. Size, industry, and business model. The prospect needs to see themselves in the reference.
- Comparable use case. They should be using the product the way the prospect intends to, not for some adjacent workflow.
- Peer-level role. A VP wants to hear from a VP. Match seniority and function so the conversation happens between equals.
- Recency and enthusiasm. A customer who onboarded recently remembers the fears the prospect has right now. A customer who's genuinely enthusiastic will sell without being asked.
You can't nail all five on every call, but if you get the top two right, the reference does most of the work on its own. This is also why your reference program needs enough depth that you're choosing from a pool, not begging your one available advocate. Building that pool is a separate discipline, but the prep only works if the bench exists.
How to brief your customer so they know exactly what to sell
The brief is where most teams fail. They either send nothing ("thanks so much, the prospect will reach out!") or they over-script the customer into sounding like a paid actor. Neither works.
The goal of the brief is simple: give your customer enough context to speak naturally and specifically to the things that matter for this deal. You're not writing their lines. You're handing them the map.
A good brief has four parts, and it should fit on one screen:
| Brief section | What it contains | Why the customer needs it |
|---|---|---|
| Who they're talking to | Name, role, company, company size, and one line on why they're evaluating you | Lets the customer calibrate tone and pick relevant examples from their own experience |
| The two or three objections in play | The specific doubts the prospect has raised, in plain language | So the customer can address them proactively instead of waiting to be asked |
| What to emphasize | The outcomes and moments in the customer's own journey that map to those objections | Points them at the parts of their story that will resonate, not a rehearsed pitch |
| What to avoid | Any known sensitivities: features not yet live, a rough patch during onboarding, pricing specifics | Keeps an honest customer from accidentally torpedoing the deal with a detail out of context |
Notice what's not on that list: a script. You want the customer to sound like a customer. The brief steers them toward the right territory and lets them speak in their own words. When a reference says "honestly, I was worried about the same thing you are, and here's what actually happened," it lands ten times harder than any line you could write for them.
Deliver the brief at least a day ahead, and keep it short. A busy executive will skim a one-pager. They will ignore a three-page document. If you can get five minutes on the phone with your customer before the call, use it to walk through the two objections and nothing else.
How to steer the call toward the objections that actually matter
The objections you put in the brief have to be the real ones, not the polite ones. Prospects rarely lead with their true blocker. They'll ask about integrations when the real fear is that your company is too small to survive their procurement cycle. Your job before the reference call is to know the difference.
Pull the real objections from three places. First, your own notes from every conversation in the deal, especially the moments where the prospect went quiet or changed the subject. Second, the deal's stage and pattern. A deal that's been stuck for three weeks after a strong demo usually has an unspoken risk objection, not a feature objection. Third, ask the prospect directly what they want to get out of the reference call. Their answer tells you where their doubt lives.
Once you know the real objection, aim the reference at it precisely. If the fear is implementation risk, brief a customer to walk through their own onboarding timeline and what went smoother than expected. If the fear is that the product won't get adopted internally, brief a customer to describe how their team actually uses it day to day. Match the ammunition to the target.
One tactic that consistently works: give your customer permission to be honest about the hard parts. A reference who says "the first two weeks were a grind, but by month two the team was fully on it" is more believable than one who claims everything was perfect. Buyers trust texture. A little honest friction, framed as resolved, disarms skepticism far better than a flawless story.
How to templatize and semi-automate reference call prep
Everything above works for one call. The problem is doing it consistently across every deal without it eating your reps' time or getting skipped when things get busy. That's where templating and light automation come in.
Start by turning the brief into a template with fillable fields: prospect name, company profile, top objections, matched customer, emphasis points. The rep fills in the deal-specific parts in a few minutes instead of writing from scratch. Consistency goes up and prep time goes down.
Then build a tagged reference library in your CRM. Every reference customer gets tagged by industry, company size, use case, and the specific objection they overcame. When a rep needs a match, they filter the library instead of asking around in Slack. This is the difference between a reference program that scales and one that depends on tribal memory.
From there, a few pieces can run semi-automatically:
- Match suggestions. When a deal reaches the reference stage, the system surfaces the top two or three matched customers based on the prospect's tags. The rep confirms rather than searches.
- Draft briefs. Pull the deal's logged objections and the matched customer's profile into a pre-populated brief the rep edits before sending.
- Scheduling and reminders. Automate the calendar coordination between customer and prospect, plus a reminder to the customer with the brief attached the day before.
- Post-call capture. A short automated follow-up to the rep asking what the prospect said and whether the deal moved, so you learn which references and framings actually close.
The point of automation here isn't to remove the human judgment. Matching and steering still need a person who knows the deal. The point is to remove the friction that causes prep to get skipped, and to make the good version the default version. When the system does the searching, drafting, and scheduling, the rep's remaining job is the twenty minutes of thinking that actually moves the deal.
What good reference call prep looks like in practice
Put the pieces together and a well-prepped reference call runs like this. The deal hits the reference stage. The system surfaces two matched customers who overcame the prospect's exact objection. The rep picks one, edits the auto-drafted brief to sharpen the two real objections, and sends it a day ahead with a two-minute heads-up call. The customer walks into the call knowing who they're talking to and what fear to address. They tell their own story, honestly, aimed at the right target. The prospect hears a peer confirm the risk is survivable, and the deal moves.
None of that is complicated. It's just deliberate. The gap between reference calls that close deals and ones that stall is almost never the quality of the customer. It's whether anyone did the prep.
Where this fits
Reference call preparation sits inside the larger sales automation layer of a revenue engine, alongside your CRM hygiene, deal-stage automation, and follow-up sequences. It's one of the highest-leverage places to apply light automation, because a single reference call often decides a deal that's already worth thousands or more. Get the match right, brief the customer well, aim at the real objection, and build the templates so it happens every time. That's how you turn your best customers into a repeatable closing asset instead of an occasional lucky break. If you want to see how this connects to the rest of your pipeline tooling, our packages lay out where reference automation lives in a full system.
If your reference calls are still run on gut feel and forwarded intros, we can help you build the matching, briefing, and automation that makes every one of them land. Book a Revenue Systems Audit.