How to use a case study after the reply

A case study is worthless in a first message and powerful in a second one. The difference is the reply in between.

Once a buyer has told you what's hurting, a case study stops being a brochure. It becomes evidence that you've solved this exact thing before.

Why timing changes everything

In a cold opener, a case study is a guess about what the buyer cares about. It's usually wrong, and it makes the message about you. I made that argument in the case against the case study in a first message.

After the reply, you're not guessing. The buyer has confirmed your hypothesis or corrected it. They've told you the problem in their own words. Now a story about a peer who had the same problem lands differently. It answers a question they're already asking themselves, which is whether you can actually do this.

Pick by problem, not by logo

The case study you send should match the problem the buyer just described. Not the biggest client you have. Not the one marketing likes best.

If a CFO wrote back that the real issue is that plant controllers don't trust the consolidated numbers, find the engagement where trust in the numbers was the hard part. It might be at a smaller company. It might be in a different industry. The match on problem matters far more than the match on logo.

If you don't have a written case study that fits, write three sentences from the engagement that does. A short, honest story beats a polished PDF about the wrong problem.

Cut it to fit

Don't attach a four-page PDF and say "see attached." Nobody reads it.

Pull out the part that matches. Two or three sentences in the body of your reply. What the client was facing, what made it hard and what changed. If the full document is useful, link it at the end for anyone who wants more.

And write it in the buyer's words. If they called it "the reconciliation mess," call it that. It shows you listened, and it makes the story easier for them to forward.

The reply to send

Say a COO replied to your opener. She said your guess about labor scheduling was off, and the real problem is that each site runs its own version of the planning process, so nobody trusts the roll-up.

That's helpful, thank you. We ran into nearly the same thing with an operations team at a regional distributor. Each of their sites had built its own planning process over the years, and the roll-up was a weekly fight. The hard part wasn't the tooling. It was agreeing on one definition of a planned hour across sites. Is that the kind of disagreement you're seeing, or is it more about the systems themselves?

It's short. It uses her framing. It names the hard part. And it ends with a question that keeps the conversation about her problem.

Make it forwardable

After the reply, your buyer will often share your note with someone else on the committee. A CFO, a technical lead, a peer who owns part of the problem.

Write the case study so it works for them too. Plain language, no jargon, no assumptions about what the reader already knows. If the story only makes sense to the person you wrote to, it'll die when it's forwarded.

You can make this easier on purpose. "If it's useful to share with your finance lead, here's a one-paragraph version" is a gift to a busy champion.

What to avoid

Don't send three case studies. One that fits is better than three that sort of fit.

Don't lead with outcomes you can't back up. If a buyer asks how you measured the result and you can't answer, you've lost more than you gained.

Don't turn it into a pitch. The case study is evidence. The next move is still a question, not a meeting request.

And don't use a case study to dodge a correction. If the buyer told you your hypothesis was wrong, acknowledge it first. Then show the story that fits the real problem.

Build your library around misery

Over time, organize your case studies by the problem they solve, not the client or the industry. A stalled migration. A new leader's first 90 days. A cost program with no data underneath it. When a reply names one of those, you'll know which story to reach for in seconds.

I covered the live version of this in proof points that land in a first conversation.

Wait for the reply. Then send one story that fits, short and in their words.