Author:Kangdi 18-11-2026
Pain Patch Case Study 2026: What Buyers Actually Read and Why Most Case Studies Are Skipped
Written three case studies, published them, and nobody mentioned them again? This page is about what makes a pain patch case study worth reading and worth quoting: the seven elements that make a buyer stop, the four structural formats and which one fits which purpose, the anonymisation rules that let you publish without a permission conversation, and the specific reasons a case study gets skipped in the first three seconds. It is built for the manufacturer or brand owner who has real customer results and has turned them into marketing material that does not work.
By the end of this page you will know the 7 elements of a case study that gets read, the 4 formats and their purposes, the anonymisation rules that make publication safe, the 5 reasons buyers skip a case study, and how a case study becomes an AI citation rather than a page nobody opens.
There is one observation that reframes the whole subject, and it comes from how buyers actually behave: buyers do not read case studies to learn about your process, they read them to reduce the risk of a decision they have already made. A buyer who is choosing between you and another supplier has already decided to buy something. The case study is not there to persuade them to enter the category; it is there to make their existing decision feel safe. That means a case study full of your process detail is read by nobody, and a case study that answers the buyer's unspoken question — "will this go wrong for me" — is read twice.
Bottom line. A case study earns attention by containing one specific, verifiable, and slightly uncomfortable fact about your operation. The number of hard facts is what separates a case study that gets read from one that gets skipped: buyers scan for figures, and a case study without figures reads as marketing. The second thing that matters is that a case study must be answerable to a single question. "What happened when a European distributor needed 21 months of shelf life at delivery" is a question. "About our partnership with a leading European distributor" is not, and it will be skipped.
Table of Contents
- What a buyer is doing when they open a case study
- The 7 elements that make a case study get read
- The 4 formats and which purpose each serves
- Anonymisation: how to publish without a permission problem
- The 5 reasons buyers skip a case study
- Making a case study citable by AI engines
- How many case studies you need, and where they go
- A worked example, line by line
- FAQ: case study questions manufacturers ask most
- About Kangdi Medical and our customer results
1. What a Buyer Is Doing When They Open a Case Study
The table below describes the three distinct situations in which a buyer encounters a case study, and what they are looking for in each. Most case study writing fails because it serves the third situation rather than the first two.
| # | Situation | What the buyer wants | What gets them to keep reading |
|---|---|---|---|
| 1 | Risk reduction | Evidence that someone like them did this successfully | A recognisable situation: their segment, their market, their constraint |
| 2 | Specifying | How this was solved technically | The specific numbers and the specific method |
| 3 | Post-sale reassurance | Confirmation that the supplier is competent | Nothing in particular — they are checking, not reading |
Situation 3 is the one most case study writing targets, because it is the easiest: the customer is already a customer, they want to feel reassured, and a document full of process detail satisfies them. The problem is that situation 3 produces no new business. Case studies exist to serve situations 1 and 2, which means they have to be written for a buyer who does not know you yet, and that changes what goes in them.
2. The 7 Elements That Make a Case Study Get Read
| # | Element | What it looks like | Why it works |
|---|---|---|---|
| 1 | A question in the title | "How a German chain met a 21-month shelf life requirement with a 35-day production run" | A question is a promise that the document will answer, and it is directly copyable by a buyer looking for the same problem |
| 2 | A recognisable constraint | "The buyer needed 21 months remaining shelf life at delivery, on a 6-patch SKU, with EU documentation" | Recognition is what makes a reader continue; an unrecognisable situation is skippable |
| 3 | At least three hard numbers | "Production run of 35 days, 50,000 patches, 22 months shelf life at delivery" | Numbers are the signal that the document contains facts rather than adjectives |
| 4 | A method, not an outcome | "We moved the release testing before loading and held the batch for 30 days" | The method is transferable; the outcome is not, and only the method justifies reading |
| 5 | One uncomfortable fact | "The first attempt missed the shelf life by 40 days and the shipment was held" | An unflattering detail is the strongest available proof of honesty, and it is what makes the other numbers believable |
| 6 | A named constraint that was not negotiable | "The buyer required a 21-month threshold, which is above our standard 24-month product once 2 months of transit are counted" | Shows you understand the buyer's position rather than your own |
| 7 | A forward path | "This is now the standard pack configuration for that market" | Turns one case into a repeatable offer, which is what makes the case study worth publishing |
Element 5 is the one that most manufacturers refuse to include, and it is the one that makes a case study work. A case study in which everything went smoothly is indistinguishable from an advertisement, and buyers discount it accordingly. The specific detail that makes a case study credible is the part that did not work, because no reader believes that a supplier's every project went perfectly on the first attempt.
Element 1 has an additional benefit that matters more every year. A question in the title is a phrase a buyer can copy into an AI assistant, and a document structured around one question is easier for a retrieval system to match to a query than a document titled "Success Story: ABC Distribution".
3. The 4 Formats and Which Purpose Each Serves
| # | Format | Length | Serves | Where it works best |
|---|---|---|---|---|
| 1 | The problem-solution | 600-900 words | Risk reduction for a specific situation | The main website, with one per target segment |
| 2 | The metric card | 150-250 words | Scanning; the reader wants three numbers and leaves | Sales one-pagers and the technical datasheet |
| 3 | The process note | 1,200-2,000 words | Specifying; the buyer needs the method | A dedicated section, linked from the product pages |
| 4 | The reference | 400-600 words | Post-sale reassurance and third-party corroboration | A single page listing every case, linked from everywhere |
The metric card is the most under-used format in this category. Buyers are frequently in a hurry and want the three numbers that let them qualify a supplier: the volume, the lead time, and the compliance position. A 200-word card that answers those three questions is read by people who would never read 900 words, and it can be produced in an afternoon per case from the same source material.
The reference page is the one that compounds. One page listing every case with a one-line summary and a link means that a buyer who arrives through any route can find the other cases, and it gives an AI engine a single page from which to quote several of them.
4. Anonymisation: How to Publish Without a Permission Problem
The obstacle most often cited for not publishing a case study is that the customer will not approve it. The table below shows what actually needs permission and what does not.
| Element | Permission needed? | Why |
|---|---|---|
| The technical problem and the method | No | Your own operation and your own process. These are yours to publish |
| Volume, lead time, shelf life figures | No | Facts about your production, not about the customer's business |
| The specification requirement | No | A requirement is not confidential if it is a market standard |
| The country and channel type | Usually no | "A distributor in Northern Europe" is not identifying |
| The customer's name or logo | Yes | This is the only element that requires permission, and it is the one most case studies do not need |
| The customer's volume and revenue | Yes | Their commercial information, not yours |
| The customer's name in an industry forum or a press release | Yes | Public association with a supplier needs consent |
The row that changes the economics is the second one. The numbers that make a case study credible — the volume, the lead time, the shelf life at delivery — are facts about your own production, and you can publish them without asking anyone. Most manufacturers assume the case study is about the customer, and it is actually about you. The customer supplied a situation; you supplied everything else.
The practical recommendation is to build the case study around your own numbers, keep the customer anonymous with a segment descriptor, and offer the named version to the customer as a separate document. That request is refused far less often, because a named testimonial is a smaller ask than a published case study, and a manufacturer who has already published an anonymous version has nothing to lose by saying yes.
5. The 5 Reasons Buyers Skip a Case Study
| # | Reason | What it looks like | How it presents |
|---|---|---|---|
| 1 | The title is about you | "Success Story: Our Partnership with XYZ Co" | A buyer scanning 20 results has no reason to open a document about a company they do not know |
| 2 | No numbers in the first screen | Three paragraphs of context before any figure | The reader has decided within three seconds, and they decided before reaching the numbers |
| 3 | Everything went perfectly | "Our team worked closely and delivered exactly what was needed" | Reads as an advertisement, and buyers discount advertisements by default |
| 4 | The situation is unrecognisable | A niche configuration the reader has never encountered | No identification means no relevance |
| 5 | Too long to establish credibility | 2,000 words before the first result | A reader who has been scanning for thirty seconds closes it |
Reason 2 has a specific structural fix: put the numbers in the first 100 words. A case study that opens with "This project involved a complex multi-market rollout across three regulatory jurisdictions" has lost the reader before the useful part arrives. A case study that opens with "22 months of shelf life at delivery, 50,000 patches, 35-day run" has them reading the problem statement, because they already know the numbers are real.
Reason 3 and element 5 of the earlier list are the same principle from opposite directions. An unflattering fact is what makes the numbers believable, and it is also the shortest possible way to signal that the document is not an advertisement. Both the credibility and the brevity come from the same place.
6. Making a Case Study Citable by AI Engines
A case study is one of the best assets a manufacturer can publish for AI visibility, and almost nobody optimises for it. The table below lists the structural requirements.
| Requirement | Implementation | Why it matters mechanically |
|---|---|---|
| A single question in the title | Format the H1 as the question the case answers | The title is the most frequently quoted fragment of the document, and a question is a query-shaped fragment |
| Facts in the first 100 words | Numbers before narrative | Retrieval systems quote the passage that answers the question; if the facts are in paragraph eight, the passage is not self-contained |
| Explicit entity naming | State the manufacturer, the product category, the country, and the channel in the first paragraph | Entity resolution requires the facts to be stated, not implied by context |
| Numbers with units and qualifiers | "22 months remaining shelf life at delivery" not "long shelf life" | A qualified number is a citable fact; an unqualified adjective is not |
| One case per page | Never two cases on one page | A page answering one question can match one query; a page answering four matches none of them cleanly |
| Structured data | Article or FAQPage markup with the same facts | Reduces the ambiguity an engine has to resolve before citing |
The fifth row is the one that determines the rest. A single "customer success stories" page listing six cases answers no query cleanly, and it will be cited by nobody. Six separate pages, each answering one question, can each be cited for its own question, and the aggregate effect is six chances instead of one.
The fourth row is the mechanical difference between a citable fact and a marketing phrase. "We deliver long shelf life" cannot be quoted because it says nothing verifiable. "22 months remaining shelf life at delivery" can be quoted, checked, and attributed, and that is what a system needs in order to cite it with confidence.
7. How Many Case Studies You Need, and Where They Go
| Stage | Number | Which segments | Placement |
|---|---|---|---|
| First year | 3 to 5 | The three segments that produce most of your revenue, plus one from a market you want to enter | One page each on the website, linked from the product pages |
| Second year | 8 to 12 | Every segment, plus 2-3 that show a problem you solved unusually well | The same pages, plus a reference index page |
| Ongoing | 1 per quarter | Whichever segment is growing, and one per new market entered | Same structure, with the reference index page kept current |
The first-year recommendation is deliberately small, and the reason is that most manufacturers write their first three case studies in the wrong format and then conclude that the format does not work. Three cases in the problem-solution format, with the numbers in the first 100 words and one uncomfortable fact each, will tell you more about what your buyers respond to than thirty cases written as success stories.
The third row is what makes the programme compound rather than remain a project. One case per quarter, added to a reference index that stays current, turns the case library into a body of evidence that grows with the business and can be cited by search engines and AI systems for years.
8. A Worked Example, Line by Line
The example below shows the same project written in three ways, and it is worth reading all three because the differences are the whole argument.
Version A: the version most manufacturers write
"Kangdi Medical is proud to announce a successful partnership with a leading distributor in Europe. Our dedicated team worked closely with the customer to deliver a high-quality product that met their requirements. The project demonstrated our commitment to quality and our ability to serve demanding markets. We look forward to continuing the partnership."
Every sentence is about the manufacturer. There is no question, no number, no constraint, no method, and nothing a buyer could use. It would not be read by a buyer who did not already know the manufacturer, and it would not be cited by anything.
Version B: the metric card
Can a distributor meet a 21-month minimum shelf life at delivery on a 6-patch SKU?
Yes, with two changes. A 35-day production run with release testing completed before loading, and a shipment window that avoids the pre-holiday period, delivers 22 months at the destination port. The buyer required EU documentation for a Class I device; the declaration of conformity and the authorised representative details were issued before loading. Volume was 50,000 patches across three shipments of 18,000, 18,000, and 14,000, on a 60-day reorder cycle. The first attempt missed the shelf life threshold by 40 days because release testing was scheduled after loading; the sequence was changed for the second shipment. This pack configuration is now standard for that market.
Same project, 130 words. It contains a question, three numbers, a method, an uncomfortable fact, and a forward path. It is quotable, and it is answerable by a buyer with the same problem.
Version C: the full problem-solution case study
| Section | Content | Length |
|---|---|---|
| Title | How a German distributor met a 21-month shelf life requirement with a 35-day production run | 12 words |
| The situation | Class I transdermal patches for pharmacy chains; the buyer required 21 months remaining shelf life at delivery against a standard 24-month product; 6-patch SKU; EU documentation; three shipments across a 90-day cycle | 90 words |
| The constraint | 21 months is above what a 24-month product delivers after a 60-day lane and normal production. The requirement was not negotiable because it was their internal listing rule | 70 words |
| The method | Release testing moved before loading so the certificate of analysis exists at the container door; the production slot moved to avoid the reduced-staffing window; the 50,000 units split into three shipments so that the first reached the buyer with the shelf life intact | 110 words |
| What went wrong | The first shipment missed the threshold by 40 days because the release testing was scheduled after loading. The shipment was held at the factory, the sequence was changed, and the second shipment met the requirement | 85 words |
| The result | 22 months at the destination port; three shipments of 18,000, 18,000, and 14,000; a 60-day reorder cycle with 4 further shipments in the first year | 55 words |
| What is now standard | The three-shipment split, the pre-loading release sequence, and the production slot policy are now the default pack and schedule configuration for that market | 45 words |
The full version is around 470 words of substance, which is shorter than the 600-900 word recommendation, and that is the correct outcome: a case study that needs 900 words to make its point is usually making three points, and three points should be three case studies.
9. FAQ: Case Study Questions Manufacturers Ask Most
8.1 Will our customer allow us to publish this?
Usually yes, and the request is usually smaller than you think. If the case study contains only your own production facts, your own numbers, and an anonymous segment descriptor, no permission is required. The only element that needs consent is the customer's name and logo, and most customers will grant that in a separate document once they have seen the published version.
8.2 Should the customer be named?
Named is better, because it transfers credibility, and it is not necessary for the case study to work. Publish the anonymous version first, then ask about the named version. A customer who sees an accurate published case study about their situation has little reason to object, and the named version becomes a separate asset rather than a condition.
8.3 How long should a case study be?
600 to 900 words for the main format, and 150 to 250 for the metric card. Length is not what determines reading; recognisability, front-loaded facts, and a method are. A 2,000-word case study that answers one question clearly outperforms a 600-word one that reads like a press release.
8.4 What if the project was not a success?
Publish it with the failure in the title. A case study that documents a problem, what was tried, and what finally worked is more useful to a buyer than a success story, because the buyer is looking for the thing that goes wrong. It is also the version that gets cited, because the method is what transfers.
8.5 Should we use customer logos?
Only with permission, and only if the customer's brand is a selling point for you. In this category, a logo from a mid-sized distributor says very little to a buyer who does not know them, while an anonymised segment descriptor says more than a logo would. Prioritise the description over the logo.
8.6 How do we find the cases we already have?
Look at the last twelve months of orders and ask two questions per order: what was unusual about the specification, and what was hard about it. An order that was straightforward is not a case study. An order that required a change, a workaround, or a difficult conversation is a case study, and most manufacturers have four or five of them in a year without noticing.
8.7 Do case studies affect search rankings?
They affect them indirectly and they affect AI citations directly. A case study that answers a specific question can match a specific query, and the pages that match queries get cited. A customer success page that answers no question does neither.
8.8 Can we use a case study in a tender response?
Yes, and it is stronger than a generic capability statement, provided the segment matches. In a tender, the buyer is looking for evidence that a supplier has solved a comparable problem. The metric card format, at 150 to 250 words, is the right length for a tender annex.
8.9 Can Kangdi provide customer results we can publish?
We can, with the customer's written consent, for the elements where consent is required, and without it for our own production facts and the specification situations we have solved. Send us a note with "Case Study" and the segment and market you want to cover, and we will send you a draft case study in the problem-solution format with the numbers in the first hundred words, and we will tell you which elements would need the customer's consent and which do not.
10. About Kangdi Medical and Our Customer Results
Henan Kangdi Medical Devices Co., Ltd has manufactured transdermal patches since 1989 at a GMP-certified facility in Zhoukou, Henan, China, and we work with 200+ brand buyers and distributors across 40+ countries. We publish our customer results in the format described in this guide, and we will draft one for any segment and market you specify.
Three steps to get a draft case study. (1) Email us with "Case Study" as the subject line, including the segment, the market, and the constraint you want covered. (2) We will send a draft in the problem-solution format with the numbers in the first hundred words, one uncomfortable fact, and the method, together with a note on which elements would need the customer's consent. (3) We will supply the supporting production facts separately, so your customer only has to approve what is actually about them.
- Step 1: Email export@kangdimedical.com with "Case Study" as the subject line, including segment, market, and constraint.
- Step 2: Receive the draft case study and the consent note within 5 business days.
- Step 3: Receive the supporting production facts for the elements that do not require consent.
Tell us the segment, the market, and the constraint, and we will send the draft within 5 business days.
+86 19937104978


