Share Case Studies Under Customer Restrictions

A customer approves a case study for one sales conversation, but a seller later puts it in a public proposal library. Another team edits the headline to make the result sound larger. Both changes can exceed the original approval even when the underlying customer story is real.

Treat each case study as two connected records: what you can support and where you may share it. Identify the approved wording, evidence, customer permission, audience and version before distributing the file. A restricted link cannot fix an exaggerated claim or missing approval.

The FTC's endorsement guidance states that advertising endorsements must be truthful and not misleading. FTC: Advertisement endorsements This guide turns that basic requirement into an operational release workflow. It does not determine the legal meaning of a customer's contract or replace your organization's approval process.

1. Define what the case study actually proves

Begin with the buyer question the case study is meant to answer. Is it evidence of implementation experience, a specific workflow improvement or a measured outcome? Avoid presenting a single customer's result as proof that every buyer will achieve the same result.

List each factual claim separately. A sentence saying that a customer reduced review time needs a defined measure, starting point, comparison period and evidence owner. A quotation needs the approved wording and speaker attribution. A statement about product usage needs confirmation that the customer used the described feature.

Keep evidence in a restricted internal record, not necessarily in the external case study. The reviewer needs to trace the claim without exposing raw personal data or confidential customer logs to every prospect. Document how the evidence supports the specific wording and what limits the comparison.

If you cannot support a numerical claim, remove or revise it through approval. Do not create a plausible-looking number to fill a template. A concrete account of the workflow and lessons can still be useful without a dramatic percentage.

Make edits visible to the approval owner. Even a small headline change can shift the meaning from “a result in this setting” to an unsupported promise. Accuracy review should cover headlines, captions, tables and the surrounding sales message.

2. Record the distribution permission

Ask what the customer approved, not merely whether someone said yes. Permission for a named buyer may differ from permission for a public webpage, downloadable brochure, conference presentation or paid advertisement. The approved company name, logo, quote and metric may each have limits.

Create a release record with the customer approval reference, approved version, allowed audiences, channels, information date and review owner. Note any expiration or withdrawal process established by the agreement. Do not invent one-size-fits-all permission terms for every customer.

A salesperson's CRM note may help locate the permission, but it should point to the actual approval record. If the record is unclear, pause release and ask the responsible owner. Do not infer permission from the fact that the customer is satisfied with the product.

Confirm the person giving approval is authorized under the customer's process. An interview participant may approve their own quote while their company requires additional approval for logos or business results. Keep those decisions distinct so one permission is not silently stretched into another.

3. Build public and restricted copies deliberately

If different audiences are allowed to see different information, create identified versions with a documented reason. For example, a public version might describe an approved workflow while a restricted version includes approved contextual details for a named buyer. The restricted version still needs substantiated claims and customer permission.

Do not achieve this by hiding slides or spreadsheet tabs and assuming the reader cannot recover them. Prepare a clean distribution copy containing only the intended material. Check comments, notes, attachments, image captions, document properties and embedded links.

An anonymized case study needs careful review. Removing the company name does not guarantee anonymity if the remaining details identify it. A distinctive industry, location, transaction and exact size can make the customer recognizable. Have the appropriate privacy and customer relationship owners assess the proposed description.

Keep version identifiers understandable. “Public-v2” and “Restricted-buyer-review-v2” can be clearer than a single file called “final.” Include a visible note about the intended audience when useful, without relying on the label as a technical barrier.

Check that the external evidence remains intelligible. Removing confidential details should not leave a numerical claim with no meaningful context. If a safe version cannot explain the method, consider sharing a qualitative lesson rather than a strong result claim.

Stock images are illustrations, not proof of the customer's identity, office or product usage. Label them accordingly. Do not place a stock portrait beside a quotation in a way that implies the pictured person is the actual speaker.

4. Deliver the approved version with enough context

Select the appropriate copy from the approved source, then choose the sharing method. Public material can use its public page. Restricted material should use a distribution approach consistent with the approved recipients and forwarding rules. Confirm the provider's actual controls before relying on them.

Tell the buyer why the case study is relevant and where it differs from their situation. A good introduction might point to a similar workflow while acknowledging a different implementation size. Avoid attaching the study with a headline that promises the same outcome for this buyer.

Include the intended handling when it is part of the permission: for example, the approved evaluation group or a restriction on external publication. The wording should match the actual approval record. Do not add a blanket prohibition that your team cannot explain or enforce.

Maintain a release log for restricted copies with the version, recipient group and reason. That makes later updates manageable. It does not require collecting unnecessary personal information or treating every view as evidence that the reader accepted all conditions.

If the buyer wants to reuse a chart in an internal presentation, check whether that use is covered. Provide an approved extract or route the request for review. Screenshots and excerpts can change context, especially when a caveat or comparison period disappears.

Do not send private customer source data merely because the buyer asks for proof. Explain the approved method and offer the evidence your owners have authorized for that purpose. Protecting the source customer is part of responsible evidence sharing.

5. Worked example: one result, two permitted uses

In a fictional example, a vendor called Maple Workflow documents a customer's review process. The customer approves a description of the steps and a specific measured result for a restricted prospect discussion. It approves a simpler qualitative story for the public website. The scenario and names are illustrative, not customer evidence.

The internal claim sheet identifies the measurement method and its limitations. The public file omits the restricted result and uses the approved workflow description. The prospect file includes the result with the relevant context and audience note. Each version links internally to its approval record.

A seller wants to shorten the prospect headline from a scoped finding to “Cut review time in half.” The content owner rejects the change because it removes the setting and implies a general outcome. The seller instead explains why the customer's process is relevant and encourages the buyer to assess its own baseline.

Later, a buyer asks to include the chart in a board packet. The team checks the permitted use rather than assuming an internal board packet is covered by prospect access. If the approval does not cover it, the team requests a separate decision or supplies the approved public version.

The useful output is not more complicated marketing. It is a clear answer to which copy can be shared, why the claim is supportable and what the next audience may do with it. That clarity prevents accidental expansion of a customer's approval.

6. Handle withdrawals, corrections and release failures

A failure case is discovering that an old study uses an outdated metric or a customer attribution that is no longer approved. Remove it from the current distribution source, identify known active uses and involve the responsible owners. Do not simply rename the file and continue sending it.

If correction is needed, explain the affected claim and supply the approved replacement. If permission changes, follow the agreed handling process for public pages and restricted copies. Revoking a link cannot erase a downloaded copy, so communicate material changes directly to known recipients where appropriate.

Before releasing a case study, verify:

• Every claim has a traceable support record.
• The quotation matches approved wording.
• Logo and name use are authorized for this channel.
• The version matches the permission record.
• Results include enough context to avoid a misleading interpretation.
• The intended audience is within scope.
• Redaction does not leave identifying private details.
• Stock imagery is clearly illustrative.
• The delivery email does not exaggerate the document's claims.

Review reuse when the purpose changes. Moving a case study from a private sales room to a searchable public page is a new distribution decision. A consistent release record lets the team act quickly without treating customer evidence as material anyone can repurpose indefinitely.

Frequently asked questions

Can a case study be shared if we remove the customer name?+

Not automatically. Remaining details may identify the customer, and contractual or approval restrictions may still apply. Review the actual content and permitted use rather than treating anonymization as universal permission.

Can we shorten an approved quote?+

An edit can change meaning or remove context. Use an approved extract or obtain approval for the revised wording through your process. Do not create a stronger endorsement by trimming away qualifications.

Does a restricted link replace customer approval?+

No. Access controls manage distribution; permission and evidence determine whether the content should be distributed at all. Confirm both before sending the study.

Before you share

A reliable case study has an evidence trail and a permission trail. Keep both tied to the released version, and recheck them whenever wording, audience or channel changes.

Parent guide

• What Belongs in a Digital Sales Room?

Related articles

• Share Customer References With Permission

• Build a Buyer Business Case With Evidence

• Help Your Buyer Share Your Proposal Internally

Sources and editorial disclosure

Primary documentation reviewed October 11, 2026. Examples, templates and checklists are illustrative editorial recommendations unless explicitly identified otherwise. Product settings and entitlements may change.

• FTC: Advertisement endorsements

VDR Directory is published by the SendNow team. Product references are limited to documented capabilities; this guide does not report a signed-in product demonstration or a completed customer project. Stock photos illustrate the surrounding workflow and do not prove feature behavior. No ranking, revenue, compliance or legal outcome is guaranteed.