One brief for your page, demo, ad, and email

Coherence is what a stranger experiences moving from an ad to a page, then a short demo, then an email. If those four describe the same person, the same job, and the same next step, the product feels like one thing. A clever name does not create that. Matching hex codes do not either, when the promise changes at every step.

You can hold the standard on a single brief, open while you make the next asset:

• **Promise.** One sentence a visitor can check against the product.
• **Who it is for.** And one neighboring audience it is not for.
• **Proof you have.** A screenshot, a method, or a limit. No borrowed numbers and no quotes from people who have not said them.
• **Voice.** Three sentences you already published, so new lines have a sound to match.
• **Visuals.** Colors and type already on the site, named tightly enough that a new image does not invent a second palette.
• **Next step.** What happens after the click or the reply, in plain order.

**Worked hypothetical.** A scheduling page says "Clients book you without a four-email thread." The demo opens on a settings panel and never shows a booking. The ad says "AI for modern teams." The welcome email thanks people for joining an innovation community. Each piece can look finished. Together they describe three products. The repair is specific: open the demo on a booking completing, rewrite the ad to the page's sentence, and make the email say what arrives next and when.

Tommy Geoco, writing about Josh Puckett's launch, has argued for showing the real product and asking for feedback early. Treat that as one maker's public advice. Impression counts and fix counts in the post are the author's claims, not results anyone else has checked. The part that belongs in this brief is smaller: the demo should show the product the page is about. See the post on X from @designertom on 27 October 2026.

Read four surfaces against the brief

Put the live page, one ad, the demo's shot list, and the next email in front of you. Read the promise aloud. Mark each surface pass or fail.

The page fails when the first screen could belong to another product. Landing page best practices describes what strong launch pages make visible, from aggregate scan data. Matching that list is not a claim that revenue will rise.

The demo fails when it spends its opening on a logo or a dashboard nobody came to see. Making a launch demo with an agent is about cutting from real screens. Narration should use lines you can verify on the page. A line you would not print above the fold does not belong in the voiceover.

The ad fails when it introduces a new audience or a result you cannot show. The email fails when it starts a story the person did not agree to, or when it sounds like a different company. A short note that repeats the promise is enough. Do not quietly enroll a confirmation address into a longer sequence.

If the page is the source of truth, change the outlier to match it. If the page is the weak surface, fix the page before you repeat it in ads and mail.

A landing page analyzer explains the seven dimensions a static read can score, and what that read cannot see: live behavior, demand, or whether an ad is any good. Use those names for the page pass, then do the side-by-side yourself. The habit is the brief, not a requirement that one vendor generate every file.

Prompt

Here is my one-page brief and four assets: homepage hero, one ad, a demo shot list, and a follow-up email.

Compare each asset with the brief. Flag any sentence that changes the audience, the promise, or the proof. Flag any result, quote, or customer count that is not in the brief. Suggest a replacement that reuses words I already use.

Do not add hype. Do not publish or send anything.

Brief:
[paste]

Assets:
[paste]

You can stop when the four surfaces name the same person, the same job, and the same next step, and every proof line is something you can point to. A dry product can sound dry in all four places. A blunt one can stay blunt. What you remove is the asset that wandered into a different product.

Before you produce another round, run the page through the free scan. Keep the brief beside the report. Where the reported gap and the brief disagree, trust the page a stranger can open.