Landing Page Brief: AI Workflow and Template

5 steps to a reviewable draft

1. 01

   Define the page decision

   Name one primary action and the reader expected to take it. Record the destination URL or form and its owner, so the call to action can be checked rather than invented.

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

2. 02

   Collect the proof and objections

   List approved offer facts, the source of each claim, audience questions and any required terms. Mark customer results, testimonials and prices as unavailable unless you have permission and a current source.

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

3. 03

   Generate the page brief

   Copy the template below. Replace each placeholder with your actual offer and evidence; leave unknown fields marked [NEEDS INPUT]. The example shows a fictional workshop brief, not a tested landing page.

   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 a fillable brief with these fields:
   - Reader and the problem in their own words
   - One primary page action and the real destination
   - Offer: what is included, eligibility, date or price if supplied
   - Message and page sections: proposed purpose of each section, not finished copy
   - Proof ledger: proposed claim | exact source | approved for use? | owner
   - Top objections: confirmed answer or [NEEDS INPUT]
   - Required visuals and reuse permission
   - Review owners, open questions and handoff checklist
   
   Mark unsupported proof as [NEEDS INPUT]. Do not invent product capabilities, customer results, prices, guarantees, legal terms or conversion outcomes.

   Example input

   Fictional example. Reader: existing users preparing weekly client reports. Action: register through the existing workshop form (URL to confirm). Offer: a live workshop on checking missing dates and owners in a report; approved agenda is available. Proof: approved screenshot of the report view. Customer outcome claim and registration deadline are not approved. Owners: product lead for screenshot and feature facts; marketing lead for form and final page.

   Example output

   Illustrative landing page brief: Reader/problem: existing users need a way to check dates and owners before sending a weekly client report. Action/destination: register for the workshop; form URL [NEEDS INPUT, marketing lead]. Offer: live reporting workshop; date, duration and eligibility [NEEDS INPUT]. Sections: (1) identify the report-review task; (2) show the approved agenda; (3) explain the report-view screenshot; (4) address practical questions; (5) registration action. Proof ledger: agenda | approved agenda file | usable after marketing review | marketing lead. Report-view image | approved screenshot | usable after product review | product lead. Customer outcome | no approved source | DO NOT USE | product lead. Objection: “When is it?” [NEEDS INPUT]. Visual: screenshot reuse confirmed by product lead before publishing. Handoff: marketing lead verifies form and workshop details; product lead verifies image and feature wording; writer drafts only after missing facts are resolved.

4. 04

   Check the evidence route

   Compare the proof ledger with the proposed page sections. Remove any section whose main claim still reads [NEEDS INPUT]; do not hide the gap behind generic copy. Check the real form, destination and required disclosures.

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

5. 05

   Hand off the brief

   Give writing and design the same reviewed brief. Assign who confirms each remaining fact and set a review point before copy, visuals or form go live.

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