They Asked for a Case Study You Do Not Have

A prospect asks for a case study. You have none cleared for publication. The conversation stalls.

This is the wall every early-stage founder hits: you need case studies to win customers, but you need customers to create case studies. Admitting you have no story does not end the conversation if you understand what the buyer actually needs.

The case study request is rarely about the case study. It's about risk. The buyer wants evidence that someone like them made this decision and lived to tell the story. When you lack a signed-off client reference, your job is to replace proof-of-success with proof-of-understanding.

This playbook presents four substitutes for a traditional case study, why buyers ask for proof in the first place, and how to get a story cleared for the next prospect who asks.

Why do buyers ask for case studies?

A LinkedIn post by Nicholas Hill, a B2B sales consultant, identifies two reasons prospects request case studies. First, it's part of their buying process. They don't know how to evaluate vendors any other way, and the case study is a checkbox they believe they need to tick. Second, the request masks a hidden objection. The buyer is hoping to use the absence of a case study to raise concerns or find reasons not to proceed.

In both scenarios, the prospect is trying to mitigate risk. HubSpot's analysis of sales objections notes that buyers often hold back when they doubt a solution can deliver the value promised, lack trust in the vendor, or work in organizations with complex approval processes. The case study serves as social proof that someone else took the risk first.

The mistake is treating all case study requests as identical. A prospect following a checklist can be satisfied with alternative proof. A prospect hunting for an exit will use the missing case study as ammunition. Your response depends on diagnosing which type of request you're facing.

What do you send when you have no case study?

The method documented works because it shifts the conversation from 'have others succeeded?' to 'does this process make sense for us?' According to a Magrios guide on proof points, a detailed methodology sits at the top of the proof hierarchy as a verifiable artifact. The buyer doesn't have to trust your claims; they only have to inspect your reasoning.

A reference call carries more weight than a logo because a named customer puts their reputation behind your work. Force Management's research on proof points in sales found that testimonials demonstrating tangible, measurable results convert skeptical buyers more effectively than generic enthusiasm. The risk is overuse: if you route every prospect to the same three clients, those clients stop agreeing to calls.

A scoped pilot turns the proof conversation into a live experiment. NoirDove's guide for early-stage startups recommends pilot projects and design partner programs as the source of the first 3 to 5 real case studies. The pilot proves fit before the buyer commits fully, and it gives you the raw material for the next case study request.

A public artifact demonstrates your work without requiring a customer to vouch for you. A published security certification, a detailed changelog, or a sandbox the buyer can try all function as proof. The artifact shows that your team ships, maintains, and thinks through edge cases.

Does admitting you have no case study kill the deal?

Admitting you have no case study does not kill a deal that has real fit. It only exposes deals that were fragile to begin with.

A buyer who walks away because you lack a case study was likely hunting for an exit. According to Ebsta and Pavilion's 2024 B2B Sales Benchmarks, 61% of lost deals are attributed to buyer indecision. The missing case study gives the indecisive buyer permission to stall or disengage without confrontation.

The conversation that works acknowledges the gap, confirms fit, and defers the proof until after commitment. Hill's LinkedIn post recommends this script: 'OK great, so am I right in thinking this is a good fit and you're happy with everything we've discussed so far? If so, we can get started, I can still put you in touch with a client to speak to but I'll do this after our agreement is in place. It's actually easier to arrange once you are fully on board, plus it saves me asking a client to spend time on this if you're not ready. If for any reason you're not happy with what you see, I will make a provision in the agreement for us to part ways without you paying a penny, so there's no risk whatsoever. How does that sound?'

This approach accomplishes two things. If the prospect has a hidden objection, this flushes it out. They will either back off or raise the real concern you haven't addressed. If the prospect is simply following their standard buying process, you allow them to tick the box without derailing the timeline.

When should a prospect ask for a case study?

A case study request belongs in the advanced stages of a sales process, after discovery and initial fit are confirmed. If a prospect asks for a case study in the first conversation, it signals one of two problems.

First, your site or marketing materials lack enough proof for the buyer to self-qualify. Magrios notes that buyers increasingly meet your claims secondhand, summarized by AI assistants that reproduce specific, attributable statements more faithfully than unattributed superlatives. If your site relies on generic assertions instead of named outcomes or verifiable artifacts, the buyer arrives at the first call with no foundation of trust.

Second, the prospect may not be the right fit at this stage. A buyer who leads with 'send me a case study' before understanding the problem you solve is shopping, not buying. Force Management's framework for handling sales objections recommends treating early case study requests as a signal to dig deeper: 'Just so I understand, what specifically are you hoping to learn from a case study? Is it how we've solved [specific problem], or are you still figuring out whether [specific problem] is worth addressing?'

How do you get a case study cleared for the next prospect?

The time to ask for a case study is not when a prospect requests one. The time to ask is as soon as a customer reaches meaningful usage.

Most founders wait too long. NoirDove's startup guide warns that if you wait too long after a customer achieves a result, the case study goes stale rapidly. The customer's memory fades, the team that championed you moves on, or the workflow changes and the story no longer applies.

Capture the raw material early, even if you don't publish it immediately. As soon as a customer completes onboarding or hits a milestone, log the before state, the pain they articulated, and the change they experienced. Save screenshots. Record quotes. Document the metrics they care about, even if the numbers are small.

Frame the request as mutual value, not a favor. 'We want to show how your workflow improved so we can help similar teams. Would you be open to a short write-up?' Most buyers agree if the request is positioned as collaborative and the story is anonymized or lightly branded.

Start with a short-form story, not a polished PDF. A 300-word testimonial with a named customer and one concrete outcome is more useful than a four-page case study that takes six months to get legal approval. You can expand the story later once you have permission and a relationship that supports deeper collaboration.

Which substitutes work best for comment-led outreach?

For a service like Well Met, where the play is comment-led outreach that builds familiarity before the connection request, the proof question is slightly different. The buyer isn't evaluating a product feature set. They're evaluating whether daily commenting will actually result in booked calls.

The method itself becomes the proof. A detailed explanation of the four-move play (show up, get familiar, connect warm, say hello) answers the buyer's question: does this make sense? The directional claim allowed by the grounding document (a warmed connection request converts several times better than a cold one, in our experience) sets the expectation without guaranteeing a number.

A public artifact works well here: a screen recording of the activity dashboard, a sample comment thread, or a walkthrough of the unified inbox. These artifacts prove that the work happens and that the workflows exist, which addresses the buyer's risk that they're buying vaporware.

A reference call is particularly effective because the buyer's real question is 'will this actually work for someone like me?' A conversation with a current client who runs the play on their own profile or operates rented agents answers that question better than any written case study.

The scoped pilot is harder to structure for a service, but a 30-day test engagement with a clear activity target (100 comments per day, 100 connection requests per week) and a defined success metric (connection acceptance rate above X%, reply rate above Y%) serves the same function. The pilot proves the process without requiring the buyer to commit to six months upfront.