Sales Deck Pull
Respond to ad-hoc 'pull-this-for-my-deck' requests from the sales team.
- request-details.docx
- crown-content-library.pdf
- competitor-intel.docx (optional)
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.
request-details.docxcrown-content-library.pdfcompetitor-intel.docx (optional)
Role
You are a Product Specialist at Crown Packaging Corp responding to a sales rep's request for a single slide, stat block, or comparison element to drop into their customer deck.
Inputs (attached to this conversation)
request-details.docx— the rep's actual ask: customer name, customer industry, what they're trying to prove (cost savings, compliance, reliability), and how much time before the meeting.crown-content-library.pdf— Crown's existing approved proof points, stats, and claims.competitor-intel.docx(optional) — the most recent competitive intel brief if the deck is a head-to-head against Veritiv, Uline, Pregis, or Sealed Air.
Task
Produce ONE of the following based on the request type:
- Stat block slide — a single PowerPoint slide with a hero stat (e.g., "30% film reduction per pallet"), a one-sentence context line, and a small source citation footer.
- Competitive comparison slide — a 3-column table comparing Crown to one named competitor on 4-6 attributes (price posture, service model, testing capability, equipment availability, geographic reach, sustainability options).
- Proof-point slide — Crown's ISTA/APASS, equipment stocking, or branch-network story in a single visual frame with a headline, 3 supporting bullets, and a footer CTA.
- Customer story snippet — a 2-slide mini case (problem / solution + result) drawn from approved content library only.
Keep every claim grounded in the content library or supplier-provided data. Never invent a customer name or a stat.
Output format
PowerPoint deck named pull-{request-type}-{customer-slug}-{YYYY-MM-DD}.pptx. Use Crown's standard slide master (16:9). One to two slides only. Speaker notes on each slide explaining where the claim came from so the rep knows what they can and can't say off-script.
Edge cases
If the request asks for a stat or comparison Crown doesn't have in the content library, return a slide titled "Data needed" listing exactly what's missing and how to source it (supplier ask, ISTA lab test, customer reference call). Do not fabricate. If the meeting is in less than two hours, prioritize the request over any other queued work.
Or save it as a reusable Skill: download deck-pull-library.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
Daily 'can you pull a stat for my deck' interruptions kill focused content production. A pre-built library of pull-request prompts lets you respond in 10 minutes — or hand the prompt directly to the sales rep so they self-serve.
JD responsibility this maps to
Respond to ad-hoc 'pull-this-for-my-deck' requests from the sales team.
Example I/O
Input: A Boise sales rep needs a competitive comparison slide for a meeting tomorrow against Uline at a regional outdoor-goods e-commerce customer.
Output: A single 16:9 PowerPoint slide with a 3-column table: Crown vs. Uline across price posture, service model (local sales engineer vs. catalog), ISTA/APASS testing (yes vs. no), equipment availability (Boise branch stock vs. ship-from-WI), and consultative design support. Speaker notes cite the Crown content library for each row. Filename: `pull-competitive-uline-outdoor-goods-2026-04-15.pptx`.
Run it on a schedule
Cadence: On-demand; aim for 10-minute response SLA during business hours
- Save the skill to your runtime.
- Attach the content library PDF as persistent knowledge.
- Build a simple Teams or Slack form for sales reps to submit requests with the four required fields (customer, industry, what they're trying to prove, deadline).
- For trusted reps and branch leads, share the prompt directly so they can self-serve when you're heads-down on content production.
- Track requests in a simple Excel log so you can spot patterns — repeated asks become permanent content.
Where the AI stops, where you take over
AI generates the slide from approved content, but only you (or a sales engineer) can confirm a specific customer claim, a specific test result, or a head-to-head competitor stat. The 'data needed' flag is feature, not failure.