Prepare a Reference Call to Help the Buyer Decide

A prospect asks for a customer reference after security and business review. Treat the request as a decision question, not a routine checkpoint. A helpful peer conversation starts with a buyer uncertainty. One buyer wants to hear how a similar team introduced a new workflow. Another wants a peer view of review process. A broad request for “someone like us” gives little direction to the reference customer and often leaves the prospect with polite but unusable answers.

Ask an opening question before searching for a customer. “What would you want to learn from a peer which you cannot learn from our team?” Then listen for a decision behind the request. The prospect might need confidence about who should join implementation planning. A security participant might want to understand how another team organized their own internal review. A sponsor might need a peer account of early user response. You do not need to answer every question yourself. Your job is to identify which question belongs in a reference conversation.

Clarify the buyer’s decision and timing. Ask who will use the call, what choice follows, and when such a choice needs to happen. A reference before a steering discussion needs different preparation from one before a technical review. If a buyer says, “We want broad reassurance,” ask what concern sits underneath reassurance. Their answer might reveal a rollout concern, an internal ownership question, or uncertainty about which users should begin. A precise question respects everyone’s time.

Choose a reference customer by relevant context, not by a perfect story. Look for a customer willing to share their own experience with a similar team shape, workflow, or stage of adoption. Do not promise identical results. Do not present the customer as proof of a future outcome. A peer gives perspective from one organization’s choices and limits. Tell the prospect this before arranging the conversation. Honest framing reduces pressure on the reference customer and produces a more credible exchange.

Match on the question first. Industry labels or company size might help a search, yet neither replaces a shared decision. A buyer preparing supervisors needs a peer who remembers preparation choices. A buyer sorting internal reviewers needs a peer who is able to describe how their own group organized discussion. A reference customer does not need a perfect match. The conversation needs a relevant experience and a willing participant.

Consider this fictional practice situation. Noah, an account executive, hears a request from Dana, an evaluation sponsor. Dana says, “We want to talk with someone who has been through this.” Noah asks which choice the conversation should inform. Dana explains her operations director worries about preparing supervisors for a first rollout. Dana needs examples of preparation work, not a product tour or a claim about results. Noah now has a real matching criterion for a reference search.

Noah asks a customer success colleague for a customer with experience introducing a similar workflow to supervisors. The colleague identifies Leah, who has agreed to occasional peer conversations. Noah first asks Leah whether a 30 minute call next week fits her schedule. He sends Dana’s two questions in advance: how Leah prepared supervisors before the first group began, and which preparation issue Leah wishes her team had discussed earlier. Noah does not write answers for Leah. Leah chooses what personal experience she wants to share.

Before Noah sends an invitation, he checks Leah’s availability and interest in the subject. A reference request should feel optional. Leah might prefer a different week, fewer participants, or a topic closer to her experience. Noah relays those limits without apology. Dana then decides whether the conversation still fits her need. This small step prevents a calendar hold from becoming pressure on a customer who volunteered time.

Prepare the prospect as carefully as the reference customer. Send a short note describing purpose, participants, and two questions. Ask Dana to invite only people who will use the conversation. Extra attendees often create unrelated questions and reduce time for the original concern. Tell Dana Leah will speak from her own experience, with no obligation to discuss private details, pricing, or future plans. This boundary gives both sides permission to decline a question without awkwardness.

Ask Dana what she already knows before the call. If Leah repeats information Dana has heard from Noah, time slips away from the open issue. Dana might know expected rollout size and still need help thinking through supervisor preparation. Noah records this distinction in his invitation. “Dana seeks a peer’s experience preparing supervisors for an initial group. She does not need a review of product details.” A clear purpose helps Leah choose useful examples.

Set a simple agenda. Begin with introductions and a one sentence purpose from Dana. Give Leah room to describe her context in her own words. Move to Dana’s first question, then second question. Reserve a few minutes near the end for a final question related to the same decision. A short agenda prevents Noah from becoming the main speaker. Noah should intervene only for time, clarity, or a boundary. The peer relationship belongs at the center of the call.

Noah opens with a brief boundary: “Thank you, Leah, for sharing your own experience. Dana is looking for perspective on supervisor preparation. Please skip any subject you do not wish to discuss.” Then he steps back. If Dana asks about pricing or private operational details, Noah redirects without embarrassment. “Let us keep our time on Dana’s preparation question.” He offers a later commercial conversation with Dana if pricing still needs discussion.

Avoid coaching a reference toward favorable language. A buyer hears rehearsed praise quickly. More importantly, pressuring a customer puts their relationship at risk. Leah might mention a difficult early step, a choice her group later changed, or a limit in her experience. Those comments have value because they are honest. Dana needs a peer’s decision process, not a sales script. If a concern appears during the call, write down the concern and arrange a later discussion with a relevant internal participant.

During the fictional call, Leah says her supervisors asked local questions only after an early preparation meeting. Dana asks what Leah’s group did next. Leah describes how her group collected questions and chose who would answer them. Noah does not translate Leah’s answer into a promise. He waits until after the call to ask Dana what part of Leah’s experience affects Dana’s own preparation decision.

Dana says Leah’s early meeting with supervisors helped identify local questions before rollout. Dana plans a similar meeting for her group. Noah records this as Dana’s internal action, not as a customer promise or standard outcome. He thanks Leah with a brief note naming the time she shared and avoids sending a long survey. His note does not ask Leah to approve a recap of her personal experience. Dana owns her own next step.

Sometimes a reference request arrives before the buyer knows what they need. Do not rush to fill a calendar slot. Offer a short preparation discussion first. Ask the buyer to name one decision, one question, and one participant who will use the answer. If such details do not emerge, wait until later in evaluation. A poorly timed reference consumes goodwill and gives the buyer another conversation to interpret without a decision path.

Keep the customer relationship in view after every request. Leah has shared personal time, and another request should not follow by default. Noah records her stated topics and preferred cadence for future internal use. When a different prospect needs a reference, Noah checks whether Leah’s experience fits before asking again. If no fit exists, he returns to buyer discovery instead of forcing a weak match. Dana also receives a clear follow up route. Questions about her own preparation plan belong with Noah and buyer participants, while personal details from Leah’s organization stay with Leah.

In a fictional practice situation, Dana schedules a supervisor preparation meeting for Tuesday, October 14. Noah drafts her invitation to Leah for a 30 minute call on Thursday, October 9. The invitation names Dana and her operations director, asks Leah about supervisor preparation and early discussion topics, and asks Leah to remove any question she would rather not address. After the call, Noah enters “Dana schedules supervisor preparation meeting for October 14” as the next action in his opportunity record.