Decks & one-pagers

Build-along · ~12 min at your own keyboard

Client-facing documents are where design pays cash: the same quote presented as a clean one-pager closes differently than a wall of text. The workflow: your rough notes + one reference + explicit content hierarchy in, finished document out.

The long version: One-pagers and decks ↗

Do this

0/4

Checkpoints

▸You should now see one lead number or promise at the top of the page.
▸You should now see supporting points in smaller type below it and detail in small print.
▸You should now see a PDF or print preview that fits the pages you intended.
▸You should now see a revised weakest section.

The three ways this goes wrong

Everything has the same weight. — Decide the one thing that leads and make everything else visibly smaller.
The PDF breaks across pages badly. — Ask Claude to add page-break rules and set the print size, then re-export.
The text reads like notes. — Rewrite each block as something you would say to the client, then rebuild.

Share what happened

Paste your declared hierarchy and what changed in the revision pass.

Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].

🔒 Don't paste confidential, personal-health, or payment info.