Proof points that land in a first conversation

The best proof point in a first conversation is the one that answers the problem the buyer just told you about. Not the biggest logo. Not the most impressive outcome. The closest match.

Everything else is noise they'll politely sit through.

Proof comes after the problem

Sellers reach for proof too early. The buyer says hello, and before the coffee's cool the seller has walked through three client stories and a slide of logos.

That order is backwards. Proof only means something once the buyer has said what's hurting. Before that, a client story is a guess about what they care about, and it usually guesses wrong.

So the first conversation runs in this order. You test your hypothesis. They confirm it or correct it. They tell you more in their own words. Then, and only then, you offer one piece of proof that fits what they said.

I made the case for holding proof out of the first message in the case against the case study in a first message. The same logic holds in the first meeting. Proof is a response, not an opening.

What a proof point that lands sounds like

It's short. Two or three sentences, out loud, with no slide.

It matches their situation on the things that matter to them. Same kind of problem, a similar kind of company, a seat that looks like theirs. It doesn't need to be the same industry. A CFO at a manufacturer will care about a CFO at a distributor if the problem was the same.

It names the hard part, not only the happy ending. "We cut their close from twelve days to five" is a claim. "Their close took twelve days, mostly from reconciling two ERPs by hand, and the hard part was getting the plant controllers to trust one source" is a story the buyer can see themselves in.

And it ends with a question that hands the floor back. "Does that sound like what you're dealing with, or is yours different?"

Here's what that sounds like after a COO has said her biggest headache is that site managers each run their own scheduling spreadsheet.

We worked with an operations leader at a mid-size distributor who had the same thing. Eleven sites, eleven spreadsheets, and no one could see labor cost by shift until the month closed. The hard part wasn't the software. It was getting site managers to give up the spreadsheet they trusted. Is that the part that worries you, or is it something else?

That last line matters. It keeps the conversation about her.

What doesn't land

A logo slide doesn't land. Senior buyers have seen your logos on your website, and they know logos say nothing about whether you did good work.

A big number without the setup doesn't land. "We saved them millions" invites the buyer to wonder how, from what base and whether it's true.

Three stories in a row don't land. One story the buyer connects with beats three they half follow. If they want more, they'll ask.

And a story where you're the hero doesn't land. The buyer wants to hear about a peer who had their problem. Your firm's role is the supporting part. Talk about what the client faced, what changed and what was hard. Let the buyer infer that you were good at it.

Build a short bench

Before first meetings, keep a short bench of proof points in your head, not a deck. Four or five stories, each tied to a problem, not to a client.

Index them by the misery they solve. A stalled migration. A new leader who inherited a mess. A cost program with no data underneath it. A team that can't ship fast enough. When the buyer names one of those, you know which story to tell.

Practice each one out loud until it takes under a minute. If it runs longer, you're telling it for yourself.

When you don't have a match

Sometimes the buyer describes a problem you've never solved in that exact form. Say so. "I don't have a story that's exactly this, but the closest is..." is more credible than forcing a fit.

Then ask more questions. A first conversation where you learned the real problem and told one honest story beats a meeting where you performed every case study you own.

One problem, one proof point, one question back. That's what lands.