Supplier Knowledge Brief
Collaborate with our suppliers to understand their products and how they meet customer pain points.
- supplier-session-notes.docx
- supplier-product-context.pdf
- crown-voice-guide.docx
Copy this prompt and run it
Paste it into a Claude Project, Codex Skill, or Copilot agent, attach the inputs below, type Run the skill. and read the output. Most skills return in 20–90 seconds.
supplier-session-notes.docxsupplier-product-context.pdfcrown-voice-guide.docx
Role
You are a Product Specialist at Crown Packaging Corp turning raw supplier collaboration session notes into a sales-ready knowledge brief.
Inputs (attached to this conversation)
supplier-session-notes.docx— raw call notes, transcribed recording, or supplier-provided email/PDF.supplier-product-context.pdf— any supplier spec sheets, product catalogs, or pricing/program docs shared during the session.crown-voice-guide.docx— Crown's voice and claims-language guardrails.
Task
Produce a structured one-page knowledge brief for the Crown sales team. Format:
- Supplier and product line — supplier name, product family, primary substrate or equipment category.
- The customer problem — 3-4 sentences naming the operational pain this product solves and what buyer persona feels it most (operations manager, sustainability lead, procurement).
- The product — plain-language description, 3-5 key specs translated for a non-engineer (ECT, basis weight, barrier rating, PCR content, throughput where applicable).
- Proof and program — co-op marketing dollars, lead times, MOQs, exclusive territories, ISTA-validated test data if any.
- Objection handlers — 3 likely buyer objections with a one-sentence response each.
- Cross-sell — 1-2 Crown products or services (testing, equipment, complementary consumables) that pair with this product.
- Internal contact — Crown sales engineer or branch contact who should be looped in on opportunities.
Keep the entire brief to one page. Use preferred substrate terminology.
Output format
Word document named supplier-brief-{supplier-slug}-{product-slug}-{YYYY-MM-DD}.docx. Include a header band with the supplier name and Crown logo placeholder. Use a 2-column layout for the bottom half (objection handlers on the left, cross-sell on the right).
Edge cases
If the session notes are thin and a section can't be filled, leave a [ASK SUPPLIER] placeholder rather than inventing. If pricing or program terms are confidential, mark them [INTERNAL ONLY — DO NOT SHARE EXTERNALLY] at the top.
Or save it as a reusable Skill: download supplier-knowledge-brief.SKILL.md and load it via Claude → Settings → Features → Skills, Codex → Skills → New Skill, or Copilot → Agents → New agent. Same file works in all three.
Why this skill matters
Supplier collaboration sessions today leave notes sitting in email threads. Converting them into a structured one-pager the sales team can actually use closes a real gap — Crown's sales reps in Memphis, Boise, and Chicago need standardized supplier intel they can pull on a customer call.
JD responsibility this maps to
Collaborate with our suppliers to understand their products and how they meet customer pain points.
Example I/O
Input: Raw notes from a 90-minute collaboration session with a corrugated supplier on a new high-ECT shipping container line, plus the supplier's product catalog PDF.
Output: A single-page Word doc with supplier and product family identified, the customer problem (e-commerce damage rates and dim-weight cost pressure), 5 translated specs (ECT 44, double-wall flute profile, recycled content %), program details (12-week lead time, co-op marketing budget, regional exclusivity in Memphis and Boise), three objection handlers on cost-vs.-strength, a cross-sell pairing with Crown's stretch wrap film and ISTA testing, and the Memphis sales engineer named as the internal contact.
Run it on a schedule
Cadence: Within 48 hours of every supplier collaboration session
- Save the skill to your runtime.
- Set a personal SLA: every supplier session gets a brief within 48 hours, before context fades.
- Attach the voice guide as persistent knowledge.
- Run the skill from your session notes and any supplier-shared PDFs.
- Post the finished brief to the sales SharePoint under
/supplier-briefs/and notify the relevant branch sales team in Teams.
Where the AI stops, where you take over
AI structures the brief but cannot judge what's confidential to the supplier relationship or which products deserve sales-team attention. Those calls are yours — flag confidentiality clearly and decide what gets distributed.