What it is, who it's for, one call to action. This is September's one-liner, unchanged if it was any good. A stranger decides here, in about four seconds, whether to keep reading.

Logos, numbers, one real sentence from a real user — right under the hero, before you've earned any patience. Proof placed halfway down the page is proof nobody sees.

Three steps. If it genuinely needs five, the product is explaining itself badly and the fix is upstream of the page. Show the thing doing the thing; a screenshot outperforms a paragraph.

Price, lock-in, security, "we already use X" — say the worried thing out loud and answer it. Otherwise they leave to go worry about it somewhere you can't reply.

The same call to action from the hero, repeated. Not a second one. Five competing CTAs is the same as none, and it's the most common self-inflicted wound on a builder site.

Palette, type scale, spacing scale, the wordmark — one file the whole surface reads from. Not a Figma page someone copies hex codes out of by hand, but a module an agent can import. Decide it in an hour on day one and never decide it again.

Buttons, cards, tables, section headers, the footer. Build them once and consistency stops being discipline and becomes a dependency — you get it for free even at 1am on a Saturday of the hackathon.

Decks, one-pagers, case studies, OG images — rendered from structured content by the same components as the site. These slides are an array in a repo, drawn by the design system you're looking at. No export step, and a typo is a one-line commit.

The brand isn't only visual. The segment, the value props and the USPs from Sep 16 get baked into the strings every surface renders — hero, bio, pinned post, email footer. One brief, many outputs, no drift.

The pitch deck, the sales one-pager, the GitHub README, the banner, the receipt. A stranger meets you in a random order and shouldn't be able to tell which one you built first.