ISTA APASS Proof Kit
Maintain and update the ISTA/APASS certification story for sales and marketing use.
- ista-apass-source-material.pdf
- crown-voice-guide.docx
- customer-objections-log.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.
ista-apass-source-material.pdfcrown-voice-guide.docxcustomer-objections-log.docx
Role
You are a Product Specialist at Crown Packaging Corp building the customer-facing ISTA and APASS certification proof kit.
Inputs (attached to this conversation)
ista-apass-source-material.pdf— Crown's certification documentation, the original press release, and any internal lab process docs.crown-voice-guide.docx— Crown's voice and claims-language guardrails.customer-objections-log.docx— known objections and questions reps have heard about testing services (if available).
Task
Produce a three-asset proof kit:
- Customer FAQ — 10-12 question-and-answer pairs covering what ISTA and APASS are, why they matter for the buyer, what Crown's lab can test, lead times, typical cost framing, and what deliverables the customer receives.
- One-page proof sheet — headline ('Crown's lab validates your packaging before it ships'), three proof bullets (ISTA certified, APASS certified, Memphis-based lab with full instrumentation), a 4-step process diagram description (intake → test plan → execute → report), and a CTA for a free initial consultation.
- 3-minute explainer script — for video or sales-rep walkthrough, conversational, with intro, the three proof points, and a closer.
Ground all claims in the source material. Translate testing terminology into plain language for a procurement buyer.
Output format
A single Word document named ista-apass-proof-kit-{YYYY-MM-DD}.docx with three Heading 1 sections corresponding to the three assets. Each asset is designed to be excerpted standalone — the FAQ can be exported as a PDF for the website, the proof sheet can be printed as-is, the script can be copy-pasted into a teleprompter.
Edge cases
If the source material is missing a process detail (e.g., specific test protocols Crown supports), leave [CONFIRM WITH LAB TEAM] rather than guessing. If a typical-cost framing in the FAQ would expose pricing competitively, flag it for Aaron's review before publishing.
Or save it as a reusable Skill: download ista-apass-proof-kit.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
The ISTA/APASS certification is one of Crown's clearest differentiators against Uline and Veritiv. Today it sits as a static press release. Packaged as a repeatable proof kit (FAQ, one-pager, explainer script), every Crown sales rep can use it on every relevant customer call.
JD responsibility this maps to
Maintain and update the ISTA/APASS certification story for sales and marketing use.
Example I/O
Input: Crown's certification documentation, the original press release, lab process notes, and a short objections log with 8 common customer questions.
Output: A Word doc with a 12-question FAQ covering ISTA test procedures, what 'certified' actually means for a buyer, lead times in the Memphis lab, and what report deliverables look like. A printable one-pager with three proof bullets and a four-step process explanation. A 3-minute explainer script with conversational bullets and timestamps.
Run it on a schedule
Cadence: Initial build in month 1; quarterly refresh thereafter
- Save the skill to your runtime.
- Run the skill once in your first 30 days to build the initial proof kit.
- Review every asset with the Crown lab team for technical accuracy before publishing.
- Set a quarterly recurring task to re-run the skill with updated source material (new test capabilities, new customer success stories).
- Store the kit in SharePoint under
/proof-kits/ista-apass/and link it from the sales SharePoint home page.
Where the AI stops, where you take over
AI structures the kit and translates testing terminology, but the lab team owns technical accuracy and Aaron owns the pricing-disclosure call. Every customer-facing claim needs human sign-off.