Author:Kangdi 19-11-2026
Pain Patch Buyer Interview Guide 2026: 12 Questions That Reveal What a Buyer Will Actually Buy
Planning to talk to your customers to find out what they need, and not sure what to ask? This page is the interview design for a pain patch business: the 12 questions in the order that produces usable answers, the 3 that reliably open a conversation, the 4 that produce data rather than opinions, and the trap questions that make a buyer give you a polite answer instead of a true one. It is built for the manufacturer or brand owner who has market feedback from three conversations and thinks that is enough.
By the end of this page you will know the 12 questions in their working order, the 4 questions that produce data rather than opinion, the 5 traps that produce polite answers, and how to turn 8 interviews into a specification rather than a set of notes.
There is one thing about buyer interviews that most people get wrong, and it explains why most of them produce nothing usable: buyers are extremely good at describing their problems and extremely bad at describing what they would buy to solve them. Ask a distributor what they want and you will hear a wish list assembled from every supplier brochure they have ever read. Ask them what they actually did last time they faced this problem and you will hear something you can build a product around. The whole design of this guide is built around that distinction.
Bottom line. The 12 questions below are ordered so that the easy ones come first, because the first three are what get a buyer talking, and the specific ones come last, because a buyer will only answer them accurately once the conversation has established that you are listening rather than selling. The four questions marked as data questions are the ones that produce something you can put in a specification. The five traps in Section 5 are the questions that produce a polite answer, and the most important thing about them is that you usually cannot tell from the answer that it was useless.
Table of Contents
- What a buyer can and cannot tell you
- The 12 questions in their working order
- The 4 questions that produce data rather than opinion
- The 5 traps that produce polite answers
- How to run the interview: 6 mechanics
- Turning 8 interviews into a specification
- Who to interview, and who not to
- Recording and coding: making the notes usable
- A 20-minute interview script, ready to use
- FAQ: buyer interview questions manufacturers ask most
- About Kangdi Medical and how we interview buyers
1. What a Buyer Can and Cannot Tell You
The table below separates the two categories, and it is worth reading before any interview because it determines what you should write down when the answers arrive.
| Dimension | Buyers are reliable on | Buyers are unreliable on |
|---|---|---|
| Past behaviour | "What happened the last time this occurred" — actual, dated, specific | Nothing; buyers misremember their own history less than you would expect |
| Constraints | "Our listing rule requires 21 months" — policy, not opinion | "We would pay more if the quality were better" — a wish, not a budget |
| Numbers | Order volumes, lead times they tolerate, margin they need — roughly | The volume they would buy if the price were right — a fantasy number |
| Future behaviour | Almost nothing | Everything. "We would try that" carries no information |
| Opinions about your product | Little | Everything. Buyers flatter and criticise for the same reason |
The last row is the one that wastes the most interview time. A buyer asked what they think of your current product will tell you what they want to hear, because the interview is also a negotiation. The interview only produces usable data when the questions are about their past and their constraints, and never about your product.
2. The 12 Questions in Their Working Order
| # | Question | What it opens up | Type |
|---|---|---|---|
| 1 | "Walk me through the last order you placed for a pain patch." | The whole conversation, in the buyer's own sequence | Behaviour |
| 2 | "Who was involved in that decision, and what did each of them care about?" | The real decision structure, which is often not the one you assume | Behaviour |
| 3 | "What was the hardest part of that order for you?" | The pain, in their words, which becomes your opening | Behaviour |
| 4 | "What had to be true for that order to work?" | The specification constraints as they see them | Constraint |
| 5 | "What is your shelf life requirement, and where does that number come from?" | A hard number and its origin | Data |
| 6 | "What documentation do you need before you can list this?" | The exact document set, per market | Data |
| 7 | "What lead time would you be able to work with, and what happens if it slips?" | The tolerance and the consequence of missing it | Data |
| 8 | "What do you pay your current supplier, per unit, and what does that include?" | The price anchor and the inclusions | Data |
| 9 | "What happens when your current supplier lets you down?" | The switching trigger, which is the mechanism | Behaviour |
| 10 | "What would you need to see to feel comfortable placing a 50,000-unit order?" | The qualification checklist, in their order | Constraint |
| 11 | "If we could solve one thing about that last order, what should it be?" | The single priority, and the wording for the case study | Behaviour |
| 12 | "Is there anyone else we should talk to about this?" | The second referral, and often the harder interview | Behaviour |
Question 12 is the one that is almost always skipped and it is the one that determines whether a single interview produces anything. The buyer who tells you their problem is usually not the buyer who decides, and the person they name is frequently a different kind of person with a different set of constraints. Eight interviews that each generate one additional interview is how a manufacturer ends up with twenty conversations and a complete picture of a market, and eight interviews that do not is how a manufacturer ends up with eight conversations that all sound the same.
3. The 4 Questions That Produce Data Rather Than Opinion
The four data questions are numbered 5, 6, 7, and 8 in the list above. They are the ones that produce something you can put into a specification, a price model, or a production plan, and they share a property: each asks for a number or a named artefact that already exists somewhere in the buyer's organisation.
| # | Question | The artefact that already exists | What you can do with the answer |
|---|---|---|---|
| 5 | Shelf life requirement and its origin | A listing rule or a quality policy document | Set the delivery shelf-life commitment, and build the production and transit plan around it |
| 6 | Documentation needed before listing | The buyer's own compliance checklist | Turn your document set into a checklist that matches theirs, which removes a whole round of questions |
| 7 | Workable lead time and the consequence of a slip | The buyer's stock planning assumptions | Set the lead-time commitment and the safety stock you should recommend, and know how much slack the account can absorb |
| 8 | Current price per unit and inclusions | The current purchase order or the supplier's price list | Know the true price anchor, including whether it is FOB or delivered, and whether it includes freight and clearance |
Question 8 is the one that most often produces a surprise, because the buyer's stated price and their actual landed cost differ. A buyer comparing your FOB quote against a competitor's CIF quote will conclude that you are expensive, and you will be quoting a like-for-like number only if you ask what the price includes. Question 8 is what prevents a price conversation you cannot win.
4. The 5 Traps That Produce Polite Answers
| # | Trap question | What the answer sounds like | Why it fails | The replacement |
|---|---|---|---|---|
| 1 | "How would you improve our product?" | A polite list of three features | Buyers answer this to be agreeable, and the answer reflects what they have seen rather than what they need | "What did you have to work around last time?" |
| 2 | "Would you buy a product that did X?" | "Yes, definitely" | A hypothetical purchase carries no commitment and no information | "What did you buy last time instead, and what did that cost you?" |
| 3 | "How much would you pay?" | A number, higher than realistic | Buyers quote their aspirational ceiling rather than their budget | "What do you pay now, and what does that leave you at the retail end?" |
| 4 | "What do you think of our current service?" | Graceful, non-specific | It is a negotiation and the buyer is managing the relationship in the answer | "What was the last thing that went wrong with a supplier, and how did you handle it?" |
| 5 | "Is there anything else you would like to tell us?" | "No, that's everything" | The most common answer in the world, and it closes the interview before the real material surfaces | "If you could fix one thing about working with suppliers like us, what would it be?" |
Trap 5 deserves a note because the polite close is where the best material usually is. When a buyer says "no, that's everything", it is almost always because the interview has not yet touched the part they did not expect to talk about. Asking the specific alternative question in the last row reopens the conversation, and the answer is frequently the most useful thing you will get.
The general pattern across all five traps is that they are all questions about the future or about you. The replacements are all questions about the past or about their own organisation, and that is the entire design principle.
5. How to Run the Interview: 6 Mechanics
| # | Mechanic | What it does |
|---|---|---|
| 1 | Interview about the last project, never about a future one | Past behaviour produces facts; future behaviour produces intentions |
| 2 | Ask the first three questions before saying anything about your product | The first three questions establish that this is research, and everything after it is answered more honestly |
| 3 | Ask for a number every time you get a description | "How many units?" "How many months?" "What percentage of your volume?" — a description without a number is unusable |
| 4 | Use the buyer's own words in your notes | Quoted phrasing is what makes a case study later, and it surfaces what your own vocabulary is missing |
| 5 | Do not defend or explain at any point | The moment you defend, the buyer stops giving you data and starts managing you |
| 6 | End with question 12 and with an explicit follow-up date | The referral produces the next interview, and the date produces the next conversation |
Mechanic 3 is the one that requires the most discipline. A buyer will describe a situation for two minutes without a single number, and the instinct is to supply one. Do not. Ask "how many" until you get it, because the number is the only part of the answer you can use in a specification, a price model, or a claim you make in a case study.
6. Turning 8 Interviews Into a Specification
Eight interviews produce a large volume of notes and no conclusion unless they are processed. The table below is the processing method.
| Step | Action | Output |
|---|---|---|
| 1 | Code every answer against a fixed list of categories: shelf life, documentation, lead time, price, packaging, format, channel, and other | A count per category, and a sense of what is common |
| 2 | Count how many of the 8 mentioned each category unprompted | The frequency ranking, which is not the same as what they said mattered most |
| 3 | Pull out every hard number, with its source | A numbers table with the requirement and how many buyers stated it |
| 4 | Identify the requirements stated by 6 or more of the 8 buyers | The specification floor: below this, most buyers will not buy |
| 5 | Identify the requirements stated by 1 or 2 buyers but with strong language | The differentiation candidates: these are where a brand can win |
| 6 | Identify what nobody mentioned | The questions you did not think to ask, and the open question for the next round |
Step 2 is where the value is, and it produces the finding that surprises people most often: the requirement buyers mention most is not the requirement they rank highest. Shelf life is mentioned by everyone because it is on every buyer's checklist. But when you count how many buyers describe it as the thing that made them choose their current supplier, the answer is frequently something else — lead time consistency, or documentation support, or a specific pack configuration. Step 5 in the table exists to capture that, because a requirement stated by one buyer with strong language is often the market's real gap.
Step 6 is the one most teams skip and it is the one that turns eight interviews into a programme. If nobody mentioned it, either it does not matter, or you did not ask. You cannot tell which without another round, and the second round should be shaped by what was missing.
7. Who to Interview, and Who Not To
| Who | Interview them | Why |
|---|---|---|
| Your current active buyer | Yes, first | They can describe the last order in detail, and they will tell you what went wrong |
| A buyer who rejected you | Yes, and it is more useful than a satisfied customer | They have no reason to be polite, and they will name the exact disqualifier |
| A buyer who is evaluating you now | Yes | Their constraints are live and they are the ones you are about to fail |
| A distributor in a market you want to enter | Yes | Their constraints are the ones you have not designed for |
| Your own sales team | Not as the primary source | They hear what buyers say in a sales context, which is not the same as what they say in research |
| A buyer who orders 200 units a year | Occasionally | Useful for the marketplace segment, misleading for anything else |
The second row is the one that produces the most uncomfortable and the most valuable conversations, and it is the one every manufacturer avoids. A buyer who rejected you has already made the decision, so they have no incentive to manage the outcome, and they will tell you what the disqualifier was in one sentence. That sentence is frequently the same across several rejected deals, and it is almost never the price.
8. Recording and Coding: Making the Notes Usable
| Element | What to record | Why |
|---|---|---|
| Verbatim quotes | The buyer's exact words for anything that sounds like a requirement | This is the raw material for the case study and for the specification wording |
| Numbers | Every quantity, period, percentage, and monetary figure, with its context | A number without context is useless; a number with context is a requirement |
| Source | Who said it, their company, their segment, and their market | Because a requirement from a pharmacy chain and one from a marketplace seller are not the same requirement |
| Emphasis | Words the buyer repeated or slowed down on | Repetition is a frequency signal, and it appears in the notes before it appears in the counts |
| Silence | What you asked that they did not answer | The unanswered questions are the next round's agenda |
| Not their words | Your interpretation, clearly marked | Mixing interpretation with quotes destroys the ability to use the notes later |
The last row is a discipline that matters more than it appears. An interview note that blends what the buyer said with what you concluded is unusable six months later, because nobody can tell which parts are evidence. Two clearly separated sections — quoted and interpreted — take ten seconds to maintain during the call and save a day of re-interviewing later.
9. A 20-Minute Interview Script, Ready to Use
The script below is the structure in Section 2 compressed into a working 20 minutes. It is written as a guide for the interviewer rather than a document to read aloud, because reading a script aloud produces exactly the polite answers the guide is designed to avoid.
| Minutes | Segment | What to do | Do not |
|---|---|---|---|
| 0-2 | Open | State the purpose in one line, state the time, ask permission to take notes. Do not mention the product | Do not pitch, do not bring samples, do not say "we are the leading" |
| 2-7 | The last order | Questions 1 to 3, in sequence, without interruption. Take verbatim notes on anything that sounds like a requirement | Do not interrupt to clarify, and do not offer an explanation when they describe a problem |
| 7-12 | The constraints | Questions 4 to 8. Every time they describe, ask "how many" or "what number" | Do not accept "a lot" or "it depends" without a follow-up |
| 12-15 | The switching trigger | Question 9, then a pause. This is where the most useful answer arrives, and silence is what produces it | Do not rescue the silence, and do not reassure them about your current performance |
| 15-18 | The qualification checklist | Question 10, then question 11. Write their exact words for question 11 | Do not ask whether they would buy from you, and do not respond to praise with thanks |
| 18-20 | Close | Question 12, confirm the follow-up date, and say what you will do with the answers and by when | Do not leave with a promise to send information unless you intend to send exactly that |
The two instructions in the fourth column are the ones that require discipline rather than knowledge. The most common failure in a buyer interview is the interviewer explaining their own product in the middle of an answer, which ends the flow and signals that the interview is a sales call. The second is filling silence: a pause after question 9 frequently produces the most valuable sentence in the conversation, and the instinct to rescue it is what destroys it.
One preparation note. Before the call, write down your three hypotheses about what this buyer needs. After the call, check whether the evidence supports them. The purpose is not to confirm them — a buyer interview that only confirms what you believed was going to happen is a wasted call — but to notice where you were wrong, and that is where the specification lives.
10. FAQ: Buyer Interview Questions Manufacturers Ask Most
9.1 How many interviews do I need?
Eight to ten per segment to reach the point where no new requirement appears, and you will usually see the saturation point at six. One interview per major account type tells you almost nothing, because every account is a story about itself rather than about the market. The rule of thumb is that a requirement has to be stated by at least six of eight buyers before it goes into the specification floor.
9.2 Should I interview in the buyer's language?
Yes, if you can. Buyers in most markets will give longer, more specific answers in their own language, and the translation is where the nuance is lost. If you cannot, use a bilingual interviewer and keep the notes in the buyer's language rather than translating them yourself afterwards.
9.3 Should I record the call?
With permission, and it is worth asking because the specific words are the asset and they are frequently not what you wrote down at the time. Where recording is not appropriate, the second-best method is to send the buyer a short written summary within 24 hours and ask them to correct it, which turns the notes into a shared document and doubles their accuracy.
9.4 What if the buyer asks what we are going to do with the answers?
Tell them the truth, which is that you are going to change the product or the documentation to match what they need. That answer produces better information than a confidentiality promise, because it makes the interview feel useful to them rather than one-sided. It also happens to be true, and if it is not true, the interview was a waste of their time and you should not be running it.
9.5 Should I interview my competitors' customers?
Yes, and this is where the differentiated requirements in Section 6 step 5 come from. A buyer who chose someone else has told you why, and the reason is frequently something structural about the market rather than about the product.
9.6 How do I stop the interview becoming a sales call?
Mechanic 2 and mechanic 5 in Section 5, plus one practical rule: do not bring a sample, a quote, or a specification sheet to the interview. Their presence changes what the buyer says. If you need to show something, show it after question 10.
9.7 What if I cannot get access to the buyers I want?
Work upward: the buyers you can reach usually know who the buyers you cannot reach are. The referral question at the end of each interview is the mechanism, and the people they name are frequently willing to talk to a manufacturer who was recommended rather than to one who cold-called.
9.8 How do I turn interviews into something I can publish?
The case study. The nine-question buyer interview in the testimonial guide is a subset of this one, and a buyer who has given you four specific answers about a real project has already given you most of a case study. Separate the notes into your production facts, the buyer's stated situation, and the outcome, and you have a publishable document without asking for a single additional permission.
9.9 Should I run the same interview for every segment?
No. The first six questions are universal and should be identical, so you can compare across segments. The remaining questions need segment-specific versions, because the constraint that dominates a pharmacy chain buyer and the one that dominates a marketplace seller are completely different. A single interview script across all segments produces a report that is legible and useless.
9.10 Can Kangdi run buyer interviews for us?
Yes. We run buyer interviews across our existing account base, using the twelve-question structure, and we send you the raw notes with the coded counts and the numbers table. Send us a note with "Buyer Interviews" and the segments you want covered, and we will run the first six interviews within 10 business days and send you the coded summary with the specification floor identified.
11. About Kangdi Medical and How We Interview Buyers
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 run buyer interviews across our own account base using the twelve-question structure, and we send the coded results rather than the notes alone.
Three steps to run buyer interviews with us. (1) Email us with "Buyer Interviews" as the subject line, including the segments and markets you want covered. (2) We will run the first six interviews, using the twelve questions, with the first six kept identical across segments for comparability. (3) We will send you the coded summary, the numbers table with every hard requirement and its source count, and the specification floor: the requirements stated by six or more of the buyers we spoke to.
- Step 1: Email export@kangdimedical.com with "Buyer Interviews" as the subject line, including segments and markets.
- Step 2: Receive the coded summary, the numbers table, and the specification floor within 10 business days.
- Step 3: Receive the list of requirements that only one or two buyers mentioned, with strong language, as the differentiation candidates.
Tell us the segments and markets you want covered, and we will run the interviews within 10 business days.
+86 19937104978


