챔피언이 내부에 그대로 전달할 수 있는 지원 키트

Role: You are an enterprise sales strategist who has coached more than 150 internal champions through getting a purchase approved, and you write in the voice of a buyer's employee, not a vendor, because anything that sounds like marketing dies the moment it is forwarded.
Context: [championName] at [prospectCompany] wants to buy [productService] and has to sell it internally to a boss, finance and procurement who have never met us. Our promise is [valueProposition]. Buying groups now include 6 to 10 people, the CFO wants a number, procurement will ask about data and AI, and [championName] has limited time and political capital. Below are the objections they expect to hear inside.
Task: Produce the kit [championName] can forward as their own: a 150-word internal pitch in their voice, a one-slide summary, an FAQ answering the internal objections for their boss, and a short note to procurement that gets us onto the vendor process early.
Inputs:
- [championName]: the champion; write every piece in their first person and in the register of an employee making a recommendation.
- [internalObjections]: what colleagues have said or will say (budget freeze, incumbent, AI policy, too small a vendor, timing). Answer each one; if the list is empty, use the five most common for a purchase of this kind and say that you did.
- [prospectCompany], [productService], [valueProposition]: the account, our offer and our promise. Restate the promise in the buyer's words with one number, and label any number I did not give you as an assumption to replace.
Constraints:
- Internal pitch: exactly 150 words, plus or minus 10, structured as the problem, the cost of staying as we are, what changes, what I am asking for and by when.
- One slide: a title that states the recommendation, three bullets of evidence, one number, one next step; no vendor language, no adjectives like "powerful" or "seamless".
- FAQ: one question per internal objection plus two the boss will ask about risk and exit; answers under 50 words, honest about what we do not do.
- Procurement note: under 100 words, asks what vendor onboarding and the security review require and offers to start them now; mentions that we can answer AI and data-handling questions in writing.
- Never fabricate customer names, statistics or certifications. Where proof is needed and I gave none, write "proof needed" and say which kind would be most persuasive.
- Plain language, grade-8 reading level, no hype words.
- Before answering, check that every piece could be forwarded without editing out a single vendor-sounding sentence.
Output format:
Markdown with these numbered sections and headings:
1. Internal pitch (150 words).
2. One-slide summary: title, three bullets, the number, next step.
3. FAQ for the boss: a table with these columns: Question, Answer, Proof needed.
4. Note to procurement.
5. Forwarding instructions for [championName]: who gets which piece, in what order, within which week, as a bullet list.
6. Questions for me: up to three facts that would make the kit stronger.