A strong B2B case study has five parts: the client's starting situation and goal, the method and timeline, results backed by evidence, a client quote the client has approved in writing, and a plan for publishing and reuse. The most common mistake is saving approval for last. Approval is not a signature collected after the draft is done; it is an agreement set up at the start of the project and maintained while you write. A number or a quote belongs in the text only if you can trace where it came from.
Important: this article is not legal advice. Client approval, personal data and provable claims are legal questions, and the suggestions below describe a general content workflow. For questions about personal data, contracts or liability, consult your own legal adviser, and remember that rules differ by country. For detail, see the pages of KVKK, Turkey's data protection authority, and of Google Search Central.
The guide is written for agency and in-house content teams, account managers and marketers who must turn a finished project into a persuasive story. Where an example appears, it is labeled as a fictional scenario.
Situation and Goal: Building the Ground Floor
The opening of a case study lets the reader decide whether this is their situation. If that section is thin, even a strong outcome will not land, because the reader cannot see themselves in the story.
Describe the client the way a reader would recognize them
Use sector, type of organization, team shape and the role of the decision maker. You do not need a headcount or revenue band; qualitative phrases such as "a multi-site retailer" or "a small engineering team" are enough. If the client's name will stay private, say so plainly. "The client asked not to be named" reads as more honest than unexplained anonymity.
Anchor the problem in a concrete moment
Abstract lines such as "efficiency was low" tell the reader nothing. Describe the ordinary moment where work got stuck: which task, at which point, how often. Take this detail from the client rather than guessing it. A problem described in the client's own words can later serve as a quote too.
Write the goal down before the work starts
If no written goal exists at kickoff, there is nothing to compare against in the results section. Whatever the goal is, capture it in writing at the start: what are we improving, how will we look at it, and over what period? A goal reconstructed after the fact looks suspicious to outside readers.
Questions to ask in the discovery call
- What sector and type of organization is the client?
- What did they do before looking for a solution?
- What visible symptoms showed the problem?
- Was anything already tried that did not work?
- When, and by whom, was the goal written down?
- Which of this information can be published and which is confidential?
Why first-hand detail matters
Google's helpful, reliable, people-first content page (Opens in a new tab) asks whether content clearly shows first-hand expertise and depth of knowledge, and whether it offers original information. A case study is that kind of content by nature, but only when the details come from people who lived the project. Generic phrasing makes your story indistinguishable from every other vendor's.
Method and Timeline: What Happened and When
However good the results are, without a method section they are just a claim. Readers look to the method for two answers: could I repeat this, and does it hold in my conditions?
Break the work into stages
List the stages in order, for example discovery, planning, rollout, adjustment and review. For each, note who did what, what the client supplied and what obstacles appeared. Obstacles do not weaken the story; they make it credible. A project where nothing went wrong rings false to anyone who has run a real one.
Writing the timeline
Give a date range, and if the schedule stretched or shrank, say why. If the client does not want exact dates published, use ranges such as "about a quarter" or "several weeks". Where there is no precise information, do not invent one.
What to explain and what to leave out
If the method contains trade secrets a competitor could copy, decide with the client and your own team which details to share. Give readers enough to learn from, but never publish anything covered by a confidentiality clause.
Example scenario: a method section outline
Example scenario: a fictional HR software provider worked with a fictional regional manufacturer. The method section would walk through mapping the existing onboarding steps, marking which ones were manual, piloting a revised flow with one department, adjusting from feedback and then opening it to everyone. After each stage it names who on the client side signed off. This example is fictional.
| Section | Reader's question | What it needs | Avoid |
|---|---|---|---|
| Situation | Is this my situation? | Sector, role, concrete symptoms | Vague industry boilerplate |
| Goal | What were they trying to achieve? | Written goal, measure, period | A goal written after the fact |
| Method | How did they do it? | Stages, roles, obstacles | Confidential details |
| Timeline | How long did it take? | Range, deviations and reasons | Guessed exact dates |
| Results | What changed? | Sourced measurement, comparison period | Unsourced percentages |
| Quote | What does the client say? | Approved sentence with context | Edited or invented quotes |
Keep a project log
Meeting notes, email summaries and project-tracker entries are the backbone of your method and timeline. If someone later asks whether a duration is accurate, you should be able to go back to these records. When no record exists, prefer an approximate phrase over a precise one.
Results with Proof
The results section carries the most risk. An impressive percentage with no traceable source produces doubt rather than trust, and a claim you cannot prove can create legal and reputational exposure for the publisher. For a definitive legal assessment, take advice.
Match every claim with evidence
Before publishing, run each sentence in the results section through four questions: where does this come from, which period does it cover, who calculated it, and has the client confirmed it? If any answer is missing, soften the sentence or remove it.
| Type of claim | Evidence needed | Owner | If the evidence is missing |
|---|---|---|---|
| Numeric improvement | Start and end measurement, period, calculation method | Client data, project team | Drop the number, use a qualitative statement |
| Time saved | Before and after records | Client operations team | Remove the time claim |
| Satisfaction | Survey or written feedback | Client | Limit it to the approved quote |
| Product feature claim | Product documentation, version | Product owner | Rephrase generally |
| Industry comparison | An independent, citable source | Content lead | Do not make the comparison |
This table is an example internal control for content teams, not a legal standard. Keeping an evidence file helps when a correction is needed and when a client asks how a number was derived. The same claim-and-proof approach for promotional articles is described in verifiable facts in a corporate promotional article.
No number, still a result
Not every project yields a figure the client will share. A qualitative result is still valuable: how did the workflow change, which recurring meeting or manual step disappeared, which team can now do a task alone? Do not invent a figure and do not hide behind phrases like "close to total". Say plainly what changed.
Compare like with like
Match the before and after periods. Comparing a busy season with a quiet one misleads. If other factors contributed, such as another project, a pricing change or a market shift, say so. Giving all the credit to one solution is a problem of honesty toward both the reader and the client.
Original information, not borrowed statistics
Google's page asks whether content provides original information, reporting, research or analysis, and says that attribution does not replace original effort. A good case study already carries original information. Padding it with generic statistics lifted from other sites does not add value.
Example scenario: an evidence sheet
Example scenario: a fictional agency keeps an internal sheet next to a draft. Each result sentence has a line showing its source (for instance, a report the client exported, or the date of a meeting note) and who confirmed it. The sheet goes to the client before publication, and any line the client does not confirm leaves the draft. The example is fictional.
Client Quote and Written Approval
This is the legally and relationally most sensitive part of a case study. What follows rests on general practice and on KVKK's explicit consent page.
Two different permissions
The first is commercial permission to publish the client company's name, logo, data and results. The second concerns real individuals whose names, roles, quotes or photos appear. Treat them separately. The first is mostly a matter of contract and communication consent. The second can raise personal data questions that your legal adviser should settle.
What KVKK's explicit consent page says
The Turkish authority's page Açık Rıza Alırken Dikkat Edilecek Hususlar (Opens in a new tab) (points to consider when obtaining explicit consent) defines explicit consent as consent relating to a specific subject, based on information and given with free will, and says it must contain a positive declaration of will. It states that no written form is required unless other legislation says so, and that consent may be obtained electronically or through channels such as a call center. It says the burden of proof lies with the data controller. It describes broad consents not tied to a specific subject or transaction as "blanket consents" and calls them legally invalid. It also says consent can be withdrawn at any time and that withdrawal takes effect from the moment it reaches the data controller.
For a case study this translates into a practical rule: if identifying information about a person will be published, the permission should be tied to a specific use (this case study, these channels), be informed (the person saw the text) and be freely given. Which legal basis applies to your case study is a legal question for your adviser, and rules outside Turkey differ.
Why keep a record anyway
The page's lack of a written-form requirement does not mean you should skip writing it down. Because the page puts the burden of proof on the data controller, recording when approval was given, for which text, by whom and through which channel makes sense from a management view. An email confirmation, a signed form or a contract annex can serve this purpose. Which is sufficient is for your adviser to say.
What the approval message should contain
- The final text or the complete quote to be published
- The channels to be used (website, social, sales deck, print)
- Whether name, title, logo and photo will be used
- How to ask for withdrawal and what the takedown process is
- The approver's name, role and the date
Where editing a quote stops
A quote is what the person said or wrote. Trimming, grammar fixes or a change of context can shift meaning. If you edited it, send the new version back for approval. Presenting a sentence the client never said as a quotation damages both trust and the relationship. For more on presenting expert voices in articles, see writing articles with expert quotes.
The data controller's duties
KVKK's information obligation page (Opens in a new tab) says the data controller must inform the data subject about its identity, the purposes of processing, transfers, the method and legal basis of collection and the person's rights. The page menu also lists other data controller topics: data security, registration in the data controllers' registry, responding to data subject applications and compliance with Board decisions. For detail, see the authority's own pages. What a content team can do is talk to its company's data protection contact or legal adviser before publishing a case study that contains personal data.
Decision rule: no approval, no publication
- Recorded written approval exists and the text is final: you may publish.
- Approval exists but the text changed later: get the changed part approved again.
- Approval is verbal or vague: put it in writing before publishing.
- A section contains personal data and the legal basis is unclear: remove the section or ask your adviser.
- The client withdrew: start the takedown and list the copied channels.
The anonymous option
If the client cannot be named, an anonymous case study is possible. Even so, sector, location, scale and event details taken together may identify the client. Treat the "anonymous" label seriously and strip detail until it is safe, and show the draft to the client when identification is a risk.
Publishing and Reuse
An approved case study is the start of its working life, not the end. Plan its format, freshness and withdrawal before you publish.
Page structure
Open with a summary readers grasp at a glance: client type, problem, solution and outcome. Follow with the situation, method, results and quote in order. Show the publication date, the period the project covered and who prepared the page. Google's page notes that readers benefit from seeing who created content and how it was made; our guide on building an author page shows one way to present that.
Where it will be used
| Channel | How it is used | Approval check |
|---|---|---|
| Website | Full page | Approval of the final text |
| Sales deck | Short summary and one quote | Does the approval cover this channel? |
| Email and newsletter | Summary and link | Is the quote's context preserved? |
| Social media | One highlighted sentence | Channel and image approval |
| Press and partner placement | Adapted text | Client and publisher approval |
For how company news and announcements are structured, see product and service sponsored post examples.
Reuse without losing context
When you shorten an approved quote for another surface, do not change its meaning. If approval was given for certain channels, ask again before using a new one. Turning one sentence into an ad slogan can step outside the scope of the permission.
Updating and withdrawal
A case study is a dated document. Decide in advance what happens if the relationship changes, results age or the client asks to withdraw. Show the date on the page and note what actually changed in updates. Google's page lists changing dates without substantial changes among its search-engine-first warning signs.
Final pre-publication checklist
- Do the situation and goal come from the client, with a written record?
- Can the method and timeline be documented?
- Does each result sentence have written evidence and a confirming person?
- Was the quote approved in writing in its final form?
- Are the channels and the use of name, logo and photo stated?
- Has the legal basis for any personal data been settled with an adviser?
- Are confidential and competitor-sensitive details out of the text?
- Are the author, date and project period visible?
- Is there a withdrawal and update process?
Common errors
- Leaving approval to the end: if the client declines after drafting, the work is wasted.
- Unsourced percentages: they produce suspicion, not trust.
- Using an edited quote without re-approval: it shifts meaning and strains the relationship.
- Presenting one result as a general guarantee: one client's outcome is not every client's.
- Leaving identifying detail in an anonymous story: it breaks the expectation of privacy.
- Crediting only the solution: the client's own work and other factors vanish from the story.
A workflow for agencies and in-house teams
- At kickoff: put the goal and the permission scope in writing.
- During the project: keep measurement records and meeting notes.
- At draft stage: build the evidence sheet and send quotes for separate approval.
- Before publishing: show the client the final text and record the approval.
- After publishing: log the date and channels, and name one contact for withdrawal requests.
How to ask the client
For the client, a case study is extra work. Make it easier with a short explanation in the first meeting: why you are writing it, what information you will ask for, how much of their time it takes, when they will see the text before it goes live and what they can withdraw later. Transparency raises both the approval rate and the quality of the text, because the client feels informed and in control.
Voice and Tone: Writing That Earns Trust
The same facts can be told in two ways: one informs the reader, the other tries to sell. B2B readers notice the second immediately. In a case study the right tone puts the client's voice forward and does not oversell the solution.
Strip out the hype words
Words like "groundbreaking", "unrivaled" and "game-changing" turn claims that need proof into feelings. If a sentence loses nothing when you delete it, it was decoration. Put every praise line through the question "what fact supports this", and simplify when there is no answer.
Say who did what
"The process was improved" tells less than a sentence naming the actor and the decision. Make the client's team the subject where they made the decision, and describe your own part as support. Credit for the client's decisions builds trust with both the client and the reader.
State the limits
Saying that an approach does not suit every situation increases credibility. A line such as "this approach may help less for very small teams" lets the reader judge their own case. A story that only reports success reads like an advertisement to anyone who has run a real project.
Example scenario: one sentence, two versions
Example scenario: for a fictional scheduling tool, one draft says "Our platform transformed team productivity". The other says "The operations lead decided to replace the weekly status meeting with the shared board and planned to review after the first cycle whether it worked for the team". The second is longer, but it gives the reader a decision, a person and a review point. The example is fictional.
Headline and summary
The headline should name the client type and the nature of the outcome without exaggeration. If a number appears in it, the number must be confirmed in the evidence sheet. Keep the summary box to about three sentences: who, what problem, what was done, what changed. A reader who cares will keep scrolling to the detail.
Images and attachments
If screenshots, photos or logos are used, check publication permission for each. Screenshots can show other people's names, emails or confidential data, so clean them and show them to the client. If an identifiable person appears in a photo, their permission is needed as well, and your adviser should confirm the basis. Write meaningful alternative text for each informative image.
Multilingual publication
If the case study will appear in two languages, approval should cover both. A translated quote can drift in meaning, so show it to the client or the relevant person on their team. Emphasis and examples may differ for each language's reader, but the results and evidence must be the same in both.
Frequently Asked Questions
What sections should a B2B case study include?
Situation and goal, method and timeline, results with evidence, a client quote approved in writing, and a plan for publishing and reuse form the core structure. This is not legal advice; consult your own adviser on personal data and consent.
When should I get client approval?
Discuss the permission scope at kickoff, then show the final text before publication and record the approval. If the text changes afterwards, get the changed part approved again. This is a content practice, not legal advice.
Does KVKK require written consent for a quote?
KVKK's explicit consent page states that no written form is required unless other legislation says so, that consent can be obtained electronically, and that the burden of proof lies with the data controller. Keeping a record is therefore sensible management. Which legal basis applies to your case study is for your legal adviser to decide, and this answer is not legal advice.
What if the client will not share numbers?
Do not invent figures or use vague percentages. Describe qualitatively how the workflow changed, which step disappeared and what the team can now do alone. Every result sentence should have a documented source and a person who confirmed it.
Is an anonymous case study safe?
Not automatically. Even without a name, sector, location, scale and event details can combine to identify the client. Strip identifying detail and show the draft to the client. If personal data is involved, ask your adviser; this is not legal advice.
What happens if the client wants to withdraw the case study?
Define the process up front: how requests are made, how fast the page comes down and which channels hold copies. KVKK's explicit consent page says consent can be withdrawn at any time and takes effect from the moment the withdrawal reaches the data controller. For legal obligations in your situation, ask your adviser; this is not legal advice.
Conclusion
A good B2B case study takes its situation from the client, its method from the records, its results from evidence and its quote from written approval. The order that works is to collect approval and evidence at the start of the project rather than at the end of the draft. Do not publish a number without a source, do not alter a quote without re-approval, and settle the legal basis for any personal data with your adviser. Google's helpful-content page asks that readers can see who made content and how, and that it offers original information; that approach guarantees no ranking. This article is not legal advice. For client consent, personal data and proof of claims, take the view of your own legal adviser.
If you would like help drafting a case study, you can look at Akua Adforce's content writing product; scope and terms are listed on the product page.
Post a comment
Please log in to leave a comment. Login