The Right Case Study First
Five references that do not fit convince nobody. One that hits the exact situation your contact is in does. So the sequence opens with the question about their starting situation, and the one case study that belongs to it comes right after. Here is how to sort your customer results by starting situation instead of industry, and what to ask next so you can tell whether the proof landed.
Why your reference list convinces nobody
This is not the first time your contact has had the topic on the table. They have been through two providers already, one promised too much and with the other the project quietly died. They are not wondering whether your work is good. They are wondering whether it worked for someone who was in the same spot they are in right now. And the answer they get from you is usually a list: eight logos, three quotes, a PDF with everything you have ever done.
That list asks your contact to do the work that is actually yours. They are supposed to figure out for themselves which of the eight cases has anything to do with them. Most of the time they do not, they skim and put it aside. Yet this is exactly the material that decides whether you make the shortlist at all, and that list is short: in a survey of 1,862 technology buyers, 83 percent end up with three or fewer vendors on it, and 74 percent use reviews and customer accounts to put it together.
The second bill arrives later. Someone who stays unsure does not decide against you, they do not decide at all. Across an analysis of 2.5 million recorded sales conversations, 40 to 60 percent of qualified opportunities are lost not to a competitor but to a decision nobody makes. 56 percent of those lost deals come down to indecision, to the fear of choosing wrong. A reference list that shows everything and proves nothing feeds exactly that fear, because it leaves open the only question that matters: does this work for me.
The fix is not a better PDF, it is a different order. First your contact answers a single question about their starting situation, three options to tap. Then they get one case study, the one that belongs to their answer. Then you ask whether they recognise themselves in it. That is the whole sequence, and it has to stand without you: 67 percent of B2B buyers prefer a rep-free buying process, according to Gartner. Your proof gets read while you are not in the room.
For that to hold, you sort your customer results by starting situation rather than by industry. Industry is your filing system, you know what separates a manufacturer from an agency. Your contact does not recognise themselves in it, because “manufacturing” says nothing about their problem. The starting situation does: they tried it in-house and it stalled. They had a provider and it went wrong. They are starting from zero and do not know where. Someone recognises themselves in one of those three sentences within two seconds. And that is the precondition for the case study being read afterwards as an answer rather than as advertising. That is why the question comes before the proof: proof without a question in front of it is a claim, proof after an answer is a reply.
How the proof sequence is built
An opening promise that earns the question after it
Entry comes from an ad, a link under your offer or a referral from an existing client. It opens with an approved template that says what is about to happen: a result from a project that matches their own situation, instead of a list. It asks for nothing yet, because the free window opens only with your contact’s reply. And it supplies the reason anyone answers the next question at all, because they know what they get for it.
The starting-situation question, three options
One decision node with three buttons, and the options describe situations, not industries: tried in-house and stalled, already went wrong with a provider, not started at all. Three options fit on a phone screen and are taken in at a glance. What matters more is what the answer does to your contact. They have described themselves before you claim anything, so everything that follows reads as a response to that description.
One case study, not three
Each branch leads to exactly one customer result. The reflex to send two at once costs the first one its effect, because your contact is back to picking which one is meant for them. That was the problem in the first place. Proof is a budget you spend, not a stack you dump. Whether the case study sits at that spot as text, hangs there as a PDF or runs as a short video is up to what you already have. The blueprint reserves the spot and tells you which starting situation the material there has to cover.
Every case study is told in the same pattern
Five pieces, always in the same order: the starting situation, what was tried before, what was concretely changed, what was measurably different afterwards, over what period. The fixed order is not tidiness for its own sake. It means your contact already knows where to look by the second case study, and it forces you to fill in the part that is missing most often: what you actually did differently. The starting situation comes first because your contact should recognise their own position before they weigh the number at the end.
The follow-up question that shows whether the proof landed
After the case study comes one question with three options: that is roughly our situation, ours is stuck somewhere else, sounds good but one point is different here. The third answer is the most valuable, because it names the doubt instead of carrying it away. Proof nobody argues with is rarely convincing, usually it has simply gone unanswered. The answer is stored as a variable and sets a tag, so it stays visible later which case study ran and which objection came with it.
A second case study only for the person who needs it
A condition node reads the follow-up answer. Anyone who recognised themselves moves straight on, because piling on would only dilute what already worked. Anyone who names a different sticking point gets the second result, the one that covers exactly that point, and so answers their own question rather than yours. That keeps the whole sequence at two questions and at most two case studies, and your contact is through in a few minutes.
The booking as a continuation of the case study
Only now does the booking link appear as the single action button, and the invitation picks up the case study: you will go through what of it transfers to their situation and what does not. That makes the call not a fresh start but the next step on a path already under way. The handover to your CRM goes with the link, so the stated starting situation, the case study that ran and the open objection travel with it. Your booking link has a fixed place in the plan, and your booking tool reporting back is drawn in as a signal. Anyone who does not book runs into a branch of their own with a tag instead of into nothing.
Example scenario: a process automation provider serving mid-sized companies
A provider runs automation projects for mid-sized companies. The decision stretches over several weeks and several people. Almost every prospect has touched the topic before, often with another provider, and brings a matching amount of scepticism.
Every inquiry gets the same reference PDF: eight projects sorted by industry, with a paragraph of company history in front. The prospect skims it, finds nothing that matches their situation and replies “I will take a look, I will be in touch”. Mostly nobody is in touch. Those who are come into a first call that starts from zero, and the objection that has been slowing things down for weeks surfaces in the second half at the earliest, often not at all.
The sequence opens with the starting-situation question and three options. Anyone who says it already went wrong with a provider gets exactly the project that began with the same history, told in the fixed pattern. Then the follow-up question about whether it fits. Anyone who names a different sticking point gets the second result that covers that point. The booking link only appears after that. The CRM record shows which starting situation was stated, which case study ran and which objection is still open. So the call does not begin at “so, tell me what this is about”, it begins with what from the project shown transfers to their situation.
What you get
The blueprint of the proof sequence
The full sequence laid out visually: entry, the starting-situation question, the three branches with one case study each, the follow-up question, the condition node for the second case study, goal and handover. Each node states what it is for and which piece of information it needs or hands over. What you write stays yours, the frame for it is set.
Your customer results sorted by starting situation
Which three situations actually describe your market, which of your projects belongs to which, and where a case goes when it fits two of them. Plus how the three answer options need to be cut so they exclude each other and cover the field between them. This is the thinking a reference list sorted by industry skips.
The pattern every case study is told in
The five pieces in fixed order and what each of them has to accomplish so your contact gets from recognition to the number. The blueprint lists three released customer results as required assets, one per starting situation, and tells you for each which situation it has to cover and which result it has to carry. So before the first click you know which of your projects belongs where and which client you still need sign-off from.
A buyer persona with over 50 data points
What drives your audience, what they resist, where they get stuck and who signs off in the end. That tells you which three starting situations genuinely separate people, because an option everyone taps sorts nothing. The same material tells you which doubt has to sit in the follow-up question as the third option, so it comes out into the open instead of staying in your contact’s head.
Variables, tags and the handover point
Which answer is stored as a variable, which tag it sets and which fields should arrive in your CRM, so the call opens with what already happened. Plus the spot for your booking link, your booking tool reporting back as a planned signal, and the separate branch for everyone who has not booked yet after the case study.
More funnel blueprints
Clear Out Objections
Asks at the decision point what is still holding someone back and puts a separate piece of proof behind every answer.
View blueprintDiscovery Call Pre-Qualification
Four questions in chat decide who gets a slot, who comes back later and who gets a friendly no.
View blueprintShow the right case study first
The proof sequence arrives finished: structure, branching logic, your customer results sorted by starting situation, buyer persona and asset list. You write the messages yourself, and the core takes under six hours to rebuild in your messenger tool. One-time payment, no subscription.
Build my funnel blueprintOne-time payment, no subscription. You get the complete strategy and overview first.