Landing Page Brief From Positioning (Before Pixels)
A landing page that invents its own promise will not match the ad, email, or referral that sent the visitor. Turn your positioning into a one-page brief with eight fields before anyone opens a design file.
You have a positioning line, a campaign that is about to send people somewhere, and a designer waiting for direction. If you hand over the line and say "make a landing page," the page will invent its own promise. The visitor clicked on one idea and lands on another. That gap is where most landing pages lose people, and no amount of button color fixes it.
This is the step between positioning and layout. It sits after the whole-site brief and before any wireframe. If you are still deciding who the offer is for, start with the brand positioning framework.
Positioning is the source. The brief is the translation.
Positioning answers a company-level question: who do we serve, what job do we do, and why us. A landing page answers a smaller one: this specific person, arriving from this specific place, with this specific trigger, what do they need to see to take one next step, the call to action (CTA)?
The brief is how you carry the first answer into the second without losing it. Every field in it has a parent in the positioning work. If a field has no parent, someone is making it up on the page, and that is usually where the vague copy comes from.
flowchart LR
P["Positioning"] --> V["Visitor + trigger"]
P --> M["Promise line"]
A["Arrival source"] --> M
M --> R["Proof"]
R --> C["One CTA"]
C --> X["Cut list"]Read the diagram left to right. Positioning decides who and what. The arrival source decides which words the first screen must repeat. Proof backs the promise. The CTA closes it. Anything that does not serve that chain goes on the cut list.
The eight fields
Framework. Eight fields fit on one page. Each one answers a question the designer would otherwise guess at. The last column is what goes wrong when the field is blank.
| Field | Question it answers | Comes from | If it is blank |
|---|---|---|---|
| 1. Visitor | Who is reading, in their words? | Positioning who-line | Copy talks to "businesses" in general |
| 2. Trigger | What just happened that made them look? | Positioning buying trigger | Page explains the service instead of the moment |
| 3. Arrival source | Ad, email, referral, search, or direct? | Campaign plan | First screen cannot repeat what they clicked |
| 4. Promise line | What does the first screen say they get? | Positioning promise + arrival words | Headline is a slogan |
| 5. Proof | What backs the promise, and are we allowed to show it? | Positioning proof, permissions list | Adjectives fill the gap |
| 6. One CTA | What is the single next step? | Offer and sales process | Three buttons, none of them primary |
| 7. Objections | What will make them hesitate? | Sales calls, intake notes | The page ignores the real reason people leave |
| 8. Cut list | What are we deliberately not saying? | Positioning "not for" line | Page grows a second and third offer |
Write the promise line from the arrival, not the company
This is the field that does the most work. The promise line is the first sentence a visitor reads. It should sound like a continuation of what they just clicked.
- From an ad: repeat the noun and the verb of the ad. If the ad said "fixed-scope website for a services firm," the headline should not say "digital experiences."
- From an email: repeat the subject line promise in the first sentence. The reader should not have to wonder if they are on the right page.
- From a referral: the referrer said one sentence about you. Find out what it was and write the page to confirm it. Ask your last five referred leads.
- From search: match the job in the query, in plain words. Do not stuff the phrase. A natural sentence that contains the job is enough.
The reverse check also matters. When the sales deck and the page tell different stories, the visitor notices on the first call. That check has its own method in sales deck to website message parity.
A filled brief (hypothetical)
Hypothetical. A small bookkeeping studio runs an email to past inquiries about a fixed-price year-end cleanup. This is how the brief might read. The facts are constructed to show the fields, not to claim any result.
| Field | Entry |
|---|---|
| Visitor | Owner of a service business with no in-house finance person, year-end close in six weeks |
| Trigger | Their accountant asked for reconciled books and they are not reconciled |
| Arrival source | Email to past inquiries, subject line: "Year-end cleanup, fixed price" |
| Promise line | Fixed-price year-end cleanup, so your accountant gets books they can use. |
| Proof | Description of the checklist we use, a sample reconciliation summary with client details removed (permission confirmed), and the fixed-price scope in writing |
| One CTA | Request a scope call |
| Objections | What if my books are a mess? What does "fixed" exclude? How fast can you start? |
| Cut list | Monthly bookkeeping, payroll, tax advice, team bios beyond one line |
Notice what is absent: invented testimonials, round-number savings, and "trusted by" logos nobody gave permission to show. If there is no proof yet, the proof field says what you actually do and how, and the page uses that. Empty and honest beats polished and made up.
Turn the brief into a page order
Once the eight fields are filled, the page order mostly writes itself. Follow the chain and stop when the CTA has been earned.
- First screen: promise line, one supporting sentence, the CTA. Nothing else competes.
- Trigger section: one short block that names the moment they are in. This is how they confirm "this is for me."
- Proof section: the proof from field 5, placed next to the claim it supports.
- How it works: three to five steps with what they receive. Replace adjectives with deliverables.
- Objections: answer the real ones from field 7 in plain language.
- Repeat CTA: same action, same label, same destination.
Where proof lives in the layout is its own decision. See service page proof architecture. If editors will be changing these sections later, the fields should be locked into a model that refuses drift: a content model editors cannot break.
The cut list is the part people skip
Every stakeholder has one more thing the page should mention. Write those requests down on the cut list instead of arguing about them in a review. Each one gets one of three answers.
- Supports the promise: it goes in, in the section where it helps.
- Belongs on another page: link to it once, quietly. Do not paste it here.
- Different offer: it needs its own brief. A landing page with two offers is a homepage with fewer links.
Sign-off and the change rule
One name signs the brief, with a date. After sign-off, anyone can propose a change, but the change goes through one question: does it alter the promise line, the proof, or the CTA? If yes, update the brief first, then the page. If no, it is a copy edit.
This sounds strict. It saves the week where design is nearly done and a new voice in the room asks whether the page can also say something about a different service. The brief is the receipt for that conversation.
The page then gets measured against one thing: did the visitor who arrived from the stated source take the stated action? Name the event and the owner before launch. The event dictionary is in the website measurement plan.
What this does not prove
A clean brief does not make a page convert. It removes the avoidable reasons a page fails: a promise that does not match the arrival, proof that was never checked, and a CTA that was never chosen. Whether the offer is wanted is a different question that no landing page can answer for you.
Download the landing page brief template and fill it for the next page you plan to send traffic to. If you want a second set of eyes on the promise line and the proof, that is part of how we do website work, and the positioning step sits with branding. Or send us the brief and we will tell you where the page is likely to drift.
Frequently asked questions
What is a landing page brief?
A one-page document that fixes who the page is for, where they arrived from, the single promise the first screen repeats, the proof that backs it, and the one call to action (CTA). Design and copy both work from it. If two people can read the brief and picture different pages, it is not finished.
How is this different from a website brief?
A website brief covers the whole site: pages, information architecture (IA), constraints, success in 90 days. A landing page brief covers one page with one job and one arrival source. You can fill the website brief once and write a landing page brief for every campaign or offer that needs its own door.
Do I need a positioning statement first?
You need the answers a positioning statement forces: who it is for, what job you do, and why you instead of the alternatives. If those are still arguments inside your team, fix that before the brief. The positioning framework and worksheet linked below are the quick route.
Can one landing page serve three audiences?
Framework: not well. Each audience arrives with a different trigger, so the first-screen promise has to change. If the offer is the same, share the proof and process sections and write a separate first screen for each. If the offer is different, it is a different page.
Who signs off on the brief?
The person who owns the commercial outcome, not the person who owns the design file. One name on the brief, one date, and a rule for what happens when someone asks to change the promise after sign-off.