Getting a Client to Say Yes to a Case Study: The Ask Nobody Practices

‍TL;DR: Most case study requests fail not because the client is unhappy with the product, but because the ask itself is vague, poorly timed, or asks for more effort than the client is willing to give without a clearer sense of what's actually involved. A well-constructed ask specifies exactly what participation requires in terms of time, offers a genuine, specific benefit to the client beyond a vague "great exposure," is timed to a moment of demonstrated satisfaction rather than a random point in the relationship, and gives the client meaningful control over what gets published. Most companies skip straight to "would you be open to a case study" without any of this groundwork, which is why the yes rate on that ask tends to be low even among genuinely satisfied clients.

‍

A genuinely happy client turning down a case study request isn't usually a sign they're not satisfied; it's usually a sign the ask itself was vague, poorly timed, or didn't clearly explain what participation would actually require. The specific construction of the ask matters as much as the underlying satisfaction it's trying to capture, and most companies never treat the ask itself as something worth deliberately designing.

Why a vague ask produces a low yes rate even from satisfied clients

"Would you be open to being featured in a case study" asks a client to say yes to an undefined commitment, no clear time estimate, no clear sense of what information will be requested, no clear sense of how much control they'll have over the final content. A reasonable, busy person facing an undefined commitment defaults to caution, even when they're genuinely satisfied with the product, simply because agreeing to something vague feels riskier than agreeing to something specific and bounded.

The four elements a well-constructed ask needs

Why a specific time commitment removes the biggest hidden barrier to a yes

Most clients declining a case study request aren't declining because they dislike the idea; they're declining because the undefined time commitment feels like an open-ended obligation they can't easily fit into an already busy schedule. Specifying "one 30-minute call, we'll draft everything from that conversation and send it to you for approval" removes this ambiguity entirely, turning an open-ended, vaguely uncomfortable commitment into a bounded, easily scheduled one.

Why "great exposure" isn't a genuine benefit and clients recognize this

Case study requests routinely offer vague exposure as the client's benefit for participating, and most B2B decision-makers, particularly at a company already succeeding well enough to be a strong case study candidate, don't need or particularly value this kind of generic visibility. A genuinely compelling benefit is more specific and more directly useful to the client: a backlink supporting their own company's SEO, co-promotion across both companies' channels, or an invitation to a relevant industry event or roundtable. Identifying what this specific client would actually find valuable, rather than defaulting to generic "exposure" language, considerably improves the odds of a yes.

Why timing the ask to a specific moment of demonstrated satisfaction beats asking at a random point

Asking for a case study during a routine quarterly check-in, disconnected from any specific recent positive moment, misses the psychological advantage of asking right after a client has just experienced or explicitly acknowledged a strong result. purple path's analysis of why case studies often get the story wrong is relevant here from a different angle: a case study asked for and drafted close to the actual result, while specific details are still fresh in the client's memory, produces both a higher likelihood of a yes and considerably more specific, usable detail for the mechanism-level story that article covers, compared to asking many months later when the specifics have faded from memory.

Why giving the client real approval control increases willingness to participate, not just final content quality

A client understandably hesitant to have their company's name and specific business details published without any control over the final content is more likely to say yes when explicitly told, upfront, that they'll review and approve the final draft before anything goes live, and can request specific edits or even decline to publish after seeing the draft if they're not comfortable with it. This isn't just a courtesy; it directly increases the initial yes rate, since removing the risk of an uncontrolled, potentially inaccurate or overly revealing public description of their business makes the ask considerably less risky to agree to in the first place.

Why the specific person making the ask matters as much as its content

A case study request coming from whoever the client has the closest, most trusted relationship with, typically their account manager or the specific specialist who did the work, tends to succeed more often than the same request coming from a marketing team member the client has never directly interacted with. This isn't about marketing lacking credibility; it's that the ask lands better when it comes from someone the client already has an established, trusted relationship with, rather than a new, less familiar point of contact making a request that feels more transactional.

A practical script structure that incorporates all four elements

A well-constructed ask might read: "We'd love to feature the results we achieved together in a short case study. It would just be one 30-minute call where I ask you a few questions, we'll handle all the writing, and you'll have full approval over anything before it's published. As a thank you, we'd include a link back to your site and feature it across our own channels, which some of our other case study clients have found brings some nice visibility their way too." This single ask incorporates a specific time commitment, a concrete benefit, and explicit approval control, all in a natural, conversational tone rather than a formal, intimidating request.

Why tracking yes and no rates over time reveals whether the ask itself needs further refinement

Treating each case study request as a small, trackable experiment, noting whether it was accepted or declined and any feedback given, over time reveals whether a specific element of the ask, perhaps the offered benefit, or the timing relative to a recent positive result, needs further refinement. A consistently low yes rate despite genuinely satisfied clients is a signal the ask itself, not the underlying client relationships, needs to be reconsidered and rebuilt using the four elements in this article.

Why a company should have a small set of pre-approved benefit options ready before making the ask

Rather than improvising a benefit offer on the spot during each individual ask, having two or three pre-approved, genuinely valuable benefit options ready in advance, a standard backlink offer, a co-promotion package, an event invitation when relevant, makes the ask itself faster and more confident to deliver, and ensures whoever is making the request across different clients isn't offering inconsistent or unauthorized benefits that create administrative complications later.

Why declining clients should still be asked for a lighter-weight alternative before giving up entirely

A client who declines a full case study isn't necessarily unwilling to help at all; offering a lighter-weight alternative, a short written testimonial quote, or permission to reference their company name and a general outcome without the full case study format, sometimes succeeds even when the fuller request didn't, since it addresses the same underlying hesitation, usually around time commitment or control, at a meaningfully lower bar of required effort and risk.

Frequently Asked Questions

Is it appropriate to offer a direct financial incentive for participating in a case study?

This varies by industry norm and company policy; a non-monetary benefit like a backlink, co-promotion, or event invitation is more commonly used in B2B SaaS specifically and tends to feel more natural and mutually beneficial than a direct payment, which can sometimes raise questions about the case study's authenticity.

How soon after a positive result should the case study ask actually happen?

Within a few weeks of a clearly demonstrated positive outcome is generally ideal, close enough that specific details remain fresh in the client's memory, while allowing enough time for the result to be genuinely confirmed and stable rather than asking prematurely before the outcome has fully materialized.

What should happen if a client agrees initially but then declines after seeing the draft?

Respecting that decision without pressure is important both ethically and practically, since a client who felt pressured into publishing something they weren't fully comfortable with is unlikely to agree to future requests or continue speaking positively about the relationship informally.

Should the case study ask be made in writing or in a live conversation?

A live conversation, even brief, tends to work better for the initial ask, since it allows for a natural, personal explanation of the four elements and immediate handling of any questions or hesitation, with written follow-up used afterward to confirm details and next steps.

Is it reasonable to ask multiple clients for case studies around the same time, or should requests be spaced out?

There's no strict need to space them out for the client's sake, though spacing requests out somewhat makes it easier for the team managing the case study process to give each one the individual attention and quality the mechanism-level detail covered elsewhere in this content actually requires.

‍

Rebuilding your next case study ask around these four specific elements is a fast way to improve a yes rate that's likely lower than your actual client satisfaction would suggest. Talk to purple path about designing a case study request process that actually works.