PDP Carousels
PDP Carousel Playbook
This is the plain HTML version of the playbook for non-JS agents, crawlers, and text-focused readers.
Canonical visual page: /playbook
Markdown version: /playbook.md
Plain text version: /playbook.txt
Archive index: /archive.md
LLM discovery file: /llms.txt
What this playbook is for
This playbook turns the archive from a set of examples into a reusable operating system. The goal is not to copy another brand slide for slide. The goal is to understand the underlying conversion logic well enough to build a carousel that feels native to the brand while still doing the hard commercial work.
A strong PDP carousel should behave like a sequenced persuasion layer. By the time a shopper finishes the image strip, they should understand what the product is, why it matters, why they should believe it, and why buying now feels safe and worthwhile.
The job of the carousel
| Job | Question | What the carousel should do |
|---|---|---|
| Recognition | What is this? | Make the product, format, and context obvious immediately. |
| Desire | Why would I want it? | Translate the product into outcomes, relief, or aspiration. |
| Belief | Why should I trust this? | Layer proof in the form the category respects most. |
| Differentiation | Why this one? | Show what is distinct in the formula, construction, bundle, or experience. |
| Risk reduction | Is this safe to try? | Add trust marks, guarantees, clarity, and confirmatory assets. |
| Validation | Does the claim hold up? | Use facts panels, detail shots, comparisons, or evidence to confirm the story. |
Recommended sequence
A strong default structure is usually six to eight slides. The opener establishes the product and promise. The middle reduces doubt. The close validates the decision.
| Slide | Strategic job | Typical contents |
|---|---|---|
| 1 | Recognition plus promise | Product hero, offer, category cues, most legible promise. |
| 2 | Benefit simplification | Core outcomes, icons, pain-point translation, use-case clarity. |
| 3 | Proof | Review count, customer volume, study result, badge, testimonial, survey data. |
| 4 | Mechanism or expectation | Ingredient spotlight, timeline, how it works, feature demonstration. |
| 5 | Differentiation or value | Comparison chart, bundle logic, gifts, ingredient grid, premium detail. |
| 6 | Validation | Facts panel, operational standards, trust proof, detail confirmation. |
Copy hierarchy
The loudest element should be the most commercially useful takeaway. Desired outcomes and quantified proof should usually be larger than supporting explanation. Compliance language and caveats should stay visible but visually subordinate.
| Element | Weight | Rule |
|---|---|---|
| Desired outcome | Largest or near-largest | Make the key customer takeaway the most memorable element. |
| Quantified proof | Largest on proof slides | Let big numbers do the recall work fast. |
| Product object | Prominent | Keep the sale grounded in the actual thing being bought. |
| Supporting explanation | Medium | Clarify the headline without competing with it. |
| Compliance verb | Small | Preserve legal accuracy without letting it own recall. |
| Methodology or disclaimer | Smallest | Contain it visually so the shopper skims the slide correctly. |
Proof systems
Proof should match the shopper's doubt. Raw proof is weaker than translated proof.
| Doubt | Best proof system | Why it works |
|---|---|---|
| Does anyone buy this? | Customer count, review volume, social proof headline | Adoption reduces risk fast. |
| Does it actually work? | Study result, survey percentages, before-and-after claim, timeline | Converts abstract outcomes into evidence. |
| Is it safe or clean? | Purity badge, third-party testing, compliant facts panel, operational standards | Reassures cautious shoppers. |
| Is it better than alternatives? | Comparison chart, ingredient differentiation, mechanism explainer | Makes the premium or switch feel justified. |
| Is it worth the price? | Bundle visualization, free gifts, savings, what-is-included frame | Expands perceived value. |
How to use this
For operators and founders
Use the playbook to decide what each frame should accomplish before briefing design. Start with sequence, choose the proof system that resolves your category's biggest doubt, then use the archive to study how similar brands phrase and stage those ideas.
For agents
Read this page as a decision framework, not a swipe file. Classify the product, pick the right sequence, map one job per slide, and only then use the archive to calibrate tone, proof style, and visual density.
Agent rules
- Preserve brand voice and category fit instead of cloning a reference brand literally.
- Choose the proof system that resolves the biggest shopper doubt first.
- Assign one dominant job to each slide before recommending design or copy.
- Make the loudest visual element the most commercially useful takeaway.
- Use archive examples as evidence, not as templates to trace.
Archive examples
Gruns
Magna
First Day
Mars Men
Brooklinen
Graymatter
VitaWild
Lemme
Heights
Timeline
ARMRA
Absorb More
AG1