AI Landing Page Brief Workflow

5 steps to a reviewable draft

1. 01

   Define the page decision

   Name the action the page should support and the reader who needs to take it. A page cannot serve several unrelated audiences without tradeoffs.

   Result: A clear page goal, reader and decision point.

2. 02

   Collect the proof and objections

   List approved offer facts, customer evidence, product constraints, common objections and the owner of each source.

   Result: A fact sheet that separates usable proof from requested proof.

3. 03

   Generate the page brief

   Ask for a section-level brief that names what each part of the page needs to establish and which evidence can support it.

   Result: A page brief that gives design and writing work a shared factual boundary.

   Your prompt

   Copy prompt

   Create a landing-page brief using only the approved inputs below.
   
   Page goal and reader: {{goal}}
   Offer and action: {{offer}}
   Audience evidence and objections: {{audience}}
   Approved proof and source owners: {{proof}}
   Brand, legal and design constraints: {{constraints}}
   
   Return sections for message, reader problem, offer, proof, objections, call to action, page structure, missing inputs and review owners. Mark unsupported proof as [NEEDS INPUT]. Do not invent product capabilities, customer results, prices, guarantees, legal terms or conversion outcomes.

   Example input

   Create a workshop registration page for existing users who struggle with weekly client reporting. Proof includes the agenda and an approved product screenshot.

   Example output

   Proof section: agenda and product screenshot. Customer outcome claim: [NEEDS INPUT]. Review owner: product lead.

4. 04

   Check the evidence route

   Inspect every planned claim, quote and visual. Confirm the page can show it, or remove it until a source owner approves it.

   Result: A brief that does not ask writers to fill evidence gaps with copy.

5. 05

   Hand off the brief

   Share the final brief with writing, design and approval owners, then set a review point before the page is published.

   Result: A coordinated page plan with fewer ambiguous decisions during production.