# Objection-driven deck QA

This note was distilled from a pitch-deck build session.

## When to use
Use this workflow for sales decks, fundraising decks, and any presentation where the audience is likely to challenge the logic, not just the visuals.

## Proven loop
1. Draft the deck content around one clear buyer persona.
2. Spawn a skeptical reviewer persona and ask for objections, embarrassing questions, and what would make them buy.
3. Reframe the deck around control, proof, and downside protection instead of pure hype.
4. Generate the PDF.
5. Render slides to images and inspect a contact sheet.
6. Re-check the dense slides individually at full size.
7. Fix clipping, cramped columns, small typography, and unbalanced spacing.
8. Re-render and re-check.

## What the skeptical reviewer should test
- Is the promise credible in 30 seconds?
- Is the value framed as ROI, control, or risk reduction?
- Are there compliance or consent questions left unanswered?
- Could the buyer accuse the deck of buzzword packaging?
- Is there a clear stop button, audit trail, and validation flow?

## Visual QA checklist
- No text clipped on the right edge.
- No columns touching the slide margin.
- Avoid tiny text in dense three-column layouts.
- Keep the last card/badge from floating too far off the main grid.
- Make sure light slides still have enough contrast in subtitles.

## Good signs
- The deck survives a skeptical pass without relying on exaggerated claims.
- The final slide includes a concrete next step or pilot framing.
- The layout feels premium because spacing is deliberate, not because of more decoration.