Proof relevance and matching

Proof earns attention when the prospect recognizes their own situation. Match the example to the company's size and stated problem, then choose a customer story that gives the buyer something they can apply.¹ Use discovery findings to choose and reference relevant proof afterward, once the prospect has given you the concern it needs to answer.² Social proof works when the buyer identifies with the referenced companies and their problem.³

Find the concern before you choose the proof

Prepare by identifying what the prospect cares about and which customer experiences they are likely to ask about.^{4, 5} Before the meeting, research customers that resemble the prospect's business.⁶ During the call, ask what prompted the conversation and listen for the problem in the prospect's own words. Ask what a successful outcome would change for them and who else needs to believe the decision makes sense.

Move on when you can describe the concern without relying on your own category labels. If you cannot, more proof will create noise instead of relevance.

Filter the match

Use a simple filter once you understand the concern. The best example gives the buyer a reason to think, "That situation looks like ours."

Choose social proof using geography and industry when those details shape how the prospect sees the problem.⁷ Check the specific use case too. A sample proves relevance by showing that the work has been done for that use case.⁸ Judge the evidence for its quality and its fit for the decision the buyer is making.⁹

Ask which detail the buyer will recognize immediately. If the prospect cares about how the work operates in a particular setting, use proof from that setting. If the prospect is deciding whether the solution fits a particular problem, use a story that starts with that problem.

Frame similarities and differences

Explain why the example belongs in this conversation. Give the buyer enough similarity to see the connection and enough difference to judge whether the lesson transfers.

A case study can show another customer who had the same problem.¹⁰ Use information about similar customers to frame the conversation with the new prospect.¹¹ Explain the ways the reference customer differs from the prospect so they can assess the comparison themselves.¹²

You can say, "We have similar problems and here's how they solved it. Would you like to know more?"¹³ Stop after the question. Let the prospect tell you whether the comparison fits, where it breaks, and which part deserves attention.

When the match is imperfect, say so plainly. A difference in operating context, scale, or situation does not automatically disqualify the proof. Hiding the difference makes the buyer do the correction themselves.

Choose the format after the match

Choose a format that lets this buyer inspect the relevant part. A short story may work during discovery, while a fuller case study or a customer conversation may suit a later decision.

After the prospect describes their struggles, share a relevant case study or solution.¹⁴ Bring customer stories, case studies, or videos that fit the stakeholder group involved.¹⁵ When arranging the meeting, you can offer to share a relevant case study beforehand.¹⁶

If the prospect asks for a reference, point to an existing case study and ask, "Is this the type of client reference you're looking for?"¹⁷ That question tells you whether the proof format and the customer match meet the requirement. If a champion is helping you prepare for an executive conversation, ask whether a case study or customer call would resonate with that executive.¹⁸

Use the response to choose the next proof asset. A request for operating detail calls for a different example than a request for financial impact or peer reassurance.

What not to do

Generic proof creates work for the buyer. These mistakes make the prospect sort through your evidence before they can decide whether any of it applies.

• Do not present every technical case study, training, and capability you have collected.¹⁹
• Do not lead with the largest enterprise customers when the example does not create credibility for this buyer.²⁰
• Do not use a vague statement such as "We enjoy high levels of customer satisfaction" without saying how high.²¹
• Do not say "We have low employee turnover" without giving the buyer a comparison.²²
• Do not claim relevant experience without stating what the experience is relevant to.²³