The brief starts with a decision
A landing-page brief should explain which customer decision the page supports. “Get more leads” is too broad to guide the copy, form, or follow-up. A better brief might say: help owners of established service businesses request an assessment of their current booking journey. That statement identifies a reader, a problem, and a useful action. Before discussing layouts, write down who should respond, who should not, and what a successful inquiry needs to contain. If the team cannot agree on those three points, design will expose the disagreement rather than resolve it.
Make the promise match the destination
Write the main campaign message beside the proposed headline. Do they describe the same offer? If an advertisement promises a website assessment, the page should not suddenly sell a full marketing retainer. Explain what the assessment covers, what information is required, and whether it leads to a sales conversation. Avoid an attractive but vague “free strategy” promise if the actual experience is an introductory call. Accurate expectations help visitors make an informed choice and give the person handling the inquiry a better starting point.
A worked example: a consultation offer
Consider an illustrative website consultancy campaign. Its audience is business owners whose websites receive inquiries but whose teams lose track of follow-up. The offer is a review of the form-to-appointment journey. The page explains what will be reviewed, asks for a business URL and a short description of the problem, and offers a consultation request. The next step is confirmation from the team, rather than an automatic promise that every applicant qualifies. This is a planning example, not a client case study or evidence of conversion improvement.
Gather proof before designing a proof section
Collect only evidence you can publish: approved project screenshots, a real process walkthrough, permissioned customer comments, or a useful demonstration. Record who owns each asset and whether names and results can be shown. When client proof is unavailable, explain the method and label concept work clearly. An honest explanation of the review process is more useful than a borrowed logo strip. Give the designer the actual assets and captions early; otherwise the most persuasive part of the page may become an empty space waiting for approval.
Decide what the form must qualify
For each field, name the decision it enables. An email address enables a reply; a service selector routes the inquiry; a project description prepares the conversation. If a field has no useful purpose at this stage, remove it or make it optional. Budget can be helpful when it changes the next step, but explain the options and include currency. On mobile, use visible labels and a clear submission state. A shorter form is not automatically better if the team must immediately ask the same essential questions again.
Put the handoff in the scope
The brief should name the destination of a submission, the person responsible, and the message the visitor receives. Decide what happens when delivery fails, the request is duplicated, or nobody is available. Document the required CRM fields and how campaign information will travel from the first visit to the inquiry. A “thank you” screen does not prove a contact reached the right place. Test with a synthetic inquiry and check the receiving system before sending campaign traffic. Keep personal test details out of shared screenshots.
Your copyable briefing checklist
Prepare seven short answers: the target customer; the exact offer; the one primary action; the evidence available; the qualification fields; the lead owner and destination; and the definition of a successful inquiry. Add the source campaign, device priorities, and any access or content dependencies. Agree on what is included in launch testing and who signs off on copy. A complete brief does not eliminate revisions, but it makes them decisions about the visitor experience rather than repeated attempts to discover what the project was meant to do.