B2B Proof and Case Study Guide

B2B Case Study Template: What Evidence to Gather Before Writing

A credible case study explains what the client needed, what work was completed, and what evidence supports the outcome. This template helps teams collect the facts and approvals before writing, so the finished story is clear without overstating results.

Explore Case Study Writing Services Contact Us

Quick answer: Before drafting, confirm the client’s permission, the project scope, a documented starting point, the work actually delivered, the dates covered, and evidence for every outcome claim. Label estimates and limitations clearly. If a metric cannot be verified or approved, leave it out or describe the work without implying a measured result.

1. Confirm permissions and the audience

Agree who the case study is for and what decision it should help that reader make. Ask the client for written approval to name the organization, describe the project, use logos or screenshots, and publish any performance data. Some clients may approve an anonymized example but not public identification. Clarify who will review the draft and how revisions will be handled. Approval should cover the final version, not only an early outline. Keep a record of what can be published and any restrictions on dates, names, screenshots, or commercial details.

2. Record the business context and starting point

Describe the client’s relevant context without disclosing confidential information: sector, audience, business goal, and the problem that prompted the work. Record what was happening before the project. For a measurable outcome, note the baseline, period, data source, and how the metric was defined. Do not compare numbers from different periods or systems as if they were directly equivalent. If a baseline is unavailable, say that the story documents the project and deliverables rather than a measured performance change. An honest limitation is more useful than a made-up before-and-after claim.

3. Document the work and your role

List what the team actually did, in sequence. Specify which tasks were performed by your organization, the client, or another provider. Note relevant decisions, constraints, and why the chosen approach fit the situation. Use project records, approved deliverables, or interviews to verify the details. Separate the activity from the outcome. For example, “we rebuilt the form and mapped its fields to the CRM” describes work. It does not by itself prove that lead quality, revenue, or conversion rate improved.

4. Gather evidence for each claim

Create a claim-to-evidence table before writing the story:

Claim: the exact result or fact you want to state.
Evidence: the report, record, interview, or approved artifact supporting it.
Period: when the measurement was collected.
Owner: who can verify and approve the claim.
Limit: any caveat, attribution gap, or context readers need.

Use screenshots only when you have permission and can protect confidential details. Do not turn a correlation into a causal claim unless the evidence supports that interpretation.

5. Use a simple case study structure

At a glance: client type, challenge, work, and approved outcome.
Challenge: what was not working and how it affected the business.
Starting point: baseline, constraints, and available evidence.
Approach: decisions made and work completed.
Outcome: verified results and the period measured.
What the team learned: limitations, next steps, or ongoing work.

Keep the story specific to the project. A case study should not read like a generic service page with a client name attached.

6. Final accuracy and publication check

Before publication, verify organization and person names, dates, service descriptions, screenshots, numbers, and links. Ask the client to confirm the version and the specific claims they are approving. Make sure any visual uses are authorized and that the story does not expose private or sensitive business information. If a project has no public results yet, you can still describe the scope, decisions, deliverables, and lessons—provided the client approves the account. Do not invent a testimonial or imply that one project guarantees similar results for another company. For writing support, see B2B Case Study Writing Services and the website growth work portfolio.

Frequently asked questions

Can I publish a case study without client approval?

Get permission for the client identity, project details, quotes, images, and results you intend to publish. If you cannot obtain approval, do not disclose confidential or identifying information.

What if I do not have before-and-after metrics?

Do not invent or imply measured improvement. You can describe the challenge, work, deliverables, and approved lessons, while being clear that performance results were not measured or are unavailable.

Should every case study include a percentage improvement?

No. Include a metric only when it is meaningful, documented, correctly attributed, and approved for publication.

Explore the next step

Prepare the evidence before drafting the story. See how B2B case study writing support can help organize interviews, claims, and approvals.

Explore Case Study Writing Services