# Landing page brief

Fill this in before asking someone to write or design the page. Keep an unknown answer marked `[NEEDS INPUT]`; do not invent evidence to fill a blank.

## Page decision

- Page owner:
- Brief date and review date:
- One intended reader and their situation:
- Where this reader will arrive from (search query, ad, email or referral):
- What that source promised the reader:
- One action the page should support:
- Actual button destination or form URL: `[NEEDS INPUT]`
- Who owns that destination and tests it:

## Offer and limits

- What is included:
- Who is eligible or not eligible:
- Price, date, availability and terms, if applicable: `[NEEDS INPUT]`
- Facts that must be confirmed before publishing:

## Message and section jobs

| Section | Reader question to answer | Approved source or proof | Owner |
| --- | --- | --- | --- |
| First screen | Is this for me, and what can I do here? |  |  |
| Offer | What do I get, under which conditions? |  |  |
| Proof | Why should I believe this claim? |  |  |
| Objections | What might stop me from acting? |  |  |
| Action | What happens after I click or submit? |  |  |

## Claim and permission ledger

| Proposed claim or visual | Exact source | Condition that must stay visible | Permission to use | Reviewer | Status |
| --- | --- | --- | --- | --- | --- |
|  |  |  | `[NEEDS INPUT]` |  | Do not publish yet |

Do not treat an unsourced testimonial, result, guarantee or metric as approved proof.

## Objections and open questions

| Reader question | Confirmed answer and source | Owner to resolve | Status |
| --- | --- | --- | --- |
|  | `[NEEDS INPUT]` |  | Open |

## Visual and handoff requirements

- Required visual and its source:
- Rights, attribution and reuse approval:
- Mobile or accessibility requirement that affects the content:
- Writer, designer, product and legal reviewers (where needed):
- Remaining dependencies before drafting:

## Launch acceptance

- [ ] The first screen matches the promise that brought the reader here.
- [ ] The page has one primary action and its real destination works.
- [ ] Each factual claim has a checked source and preserves its conditions.
- [ ] Quotes, customer results and visuals have permission to be used.
- [ ] Open questions remain visible; unresolved core claims are not published.
- [ ] The named owner checks the final page on mobile and desktop.
- [ ] The team has defined the useful action it will measure after launch.

This is a planning template, not a tested landing page or a promise of conversion results. For a worked fictional example and optional AI drafting step, return to https://wexai.app/workflows/writing/ai-landing-page-brief/.