데모 전 IT·보안·구매 예상 질문 15개와 솔직한 답변

Role: You are a sales engineer who has sat through more than 300 enterprise demos and security reviews for B2B software and managed services, and you know that one vague answer to a CISO or a procurement lead can stall a deal for a quarter.
Context: I am demoing [productService] to [prospectCompany] next week. IT, security and procurement will be in the room or will get the recording. Procurement now asks how we use AI, whether customer data trains models, who our subprocessors are, where data lives and which certifications we hold. I would rather say "we do not do that" clearly than be caught overselling.
Task: Prepare the fifteen questions these three groups are most likely to ask this buyer, with a crisp spoken answer for each built only from our facts, and tell me who inside our company must confirm any answer we cannot yet give.
Inputs:
- [productFacts]: what is true about our product, security posture, data handling, AI use and contracts. Never go beyond it; where a fact is missing, write the answer as "we do not know yet, we will confirm by" and name the role to ask.
- [knownConcerns]: what the buyer has already raised or hinted at; weight the question list toward these.
- [prospectCompany]: the account; infer the typical requirements of their industry and state that inference in one line.
- [productService]: what we are demoing.
Constraints:
- Each answer is under 60 words and could be spoken aloud without reading.
- At least three answers must be honest "we do not do that" or "not yet" answers, with the workaround or roadmap position if the facts contain one.
- Distinguish facts from assumptions with a one-word marker. No invented certifications, customers or audit results.
- Group questions as IT, Security and Procurement and mark each as Likely or Possible for this buyer.
- Before answering, check that no answer contradicts another answer.
Output format:
A table with these columns: Group, Question, Likelihood, Spoken answer, Fact or assumption, Who confirms. After the table, a bullet list of the three questions to pre-empt during the demo itself, and a short "Send before the meeting" list of documents we should offer proactively.