The landing page brief: the spec that saves you three rounds of revisions

The contractor ships a first version that matches what they understood, then finds out the form is supposed to feed a CRM nobody mentioned, that the hero photo doesn't exist yet, and that the offer on the page isn't the one being sold. Every round eats into the budget that was meant for optimizing the page once it was live. A brief isn't paperwork: it's the document that decides whether quotes are comparable and how many revision rounds you'll go through.

Why a vague brief costs both sides money

Facing a vague request, a serious contractor has two options: decline, or price the uncertainty. They add a buffer covering everything that wasn't said — an unknown tool to integrate, content to produce, unlimited revisions. The client ends up paying for a risk they could have removed by writing ten more lines. If the estimate is tight instead, the adjustment variable becomes time spent, and the relationship sours by the third round. It's one reason landing page prices vary so much for what looks like the same scope.

The vagueness has a second effect: it makes proposals impossible to compare. Three contractors given the same fuzzy request price three different projects. The mechanism is documented on the supply side: a study by Ajay Agrawal, Nicola Lacetera and Elizabeth Lyons published in 2016 in the Journal of International Economics shows that, on an online marketplace for remote work, standardized and verified information about contractors' track records reduces buyers' uncertainty — and that this reduction particularly benefits applicants from developing countries, who started out with an informational disadvantage (Agrawal, Lacetera & Lyons, 2016). The same mechanism runs in reverse on the demand side: by standardizing the information they hand over, the client reduces the uncertainty the contractor has to charge for.

The brief template: ten sections, in order

This outline fits on one page and gets reused on every project. Send the exact same document to every contractor you approach — that's the condition for getting comparable answers.

1. One measurable goal. A single action matters on this page, and you know how you'll measure it. If two goals coexist, say which one wins.
2. Audience and awareness level. Who the page speaks to and what those people already know: they know you, they're discovering the category, they're comparing options.
3. The exact offer and promise. What's sold, at what price, under what conditions, what's promised and what isn't. Attach the value proposition if one already exists.
4. Expected action and where the lead goes. Where the data lands, in which tool, who handles it, with what follow-up.
5. Content provided or to be produced. Copy, photos, logo, testimonials: for each item, an owner and a date.
6. Technical constraints. Hosting, domain name, email tool, CRM, analytics, tag manager, consent solution.
7. Legal constraints. Regulated industry, mandatory notices, privacy policy, how form data is processed, accessibility.
8. Visual frame. Existing brand guidelines or not, two or three pages you find well done, and what you don't want.
9. Deadlines and milestones. Target launch date plus the intermediate steps: design approved, content delivered, sign-off.
10. Sign-off, ownership and handover. Who approves, against what criteria, with how many revision rounds included; who owns the delivered code.

Goal, audience, offer: the foundation

These three sections drive most of the rest, and they're the ones people dash off in a single line. "Generate leads" isn't a goal, it's a category. "Get qualified quote requests, counted in the CRM" is one: it settles everything downstream — price shown or not, long form or short, one call to action or two levels of commitment. Awareness level sets the length: cold paid traffic doesn't need the same demonstration as a list that already knows you. And the offer has to be written precisely, because it's what the contractor will rewrite. Our guide to the anatomy of a landing page that converts gives you the shared vocabulary for those conversations.

What happens after the click

This is the most commonly missing section, and the top cause of a delivery that's "technically correct but unusable." A form only has value if it feeds something: a shared inbox, an email tool, a CRM, a booking calendar. Specify the tool, who owns the account, who gets the notification, what the visitor sees after submitting, and which conversions need to reach your analytics — consent included. A contractor who discovers mid-project that they have to wire up a CRM and add a consent banner isn't making a tweak: they're doing a chunk of work that wasn't quoted.

Content, tech and legal: what blows up timelines

• Unassigned content. "We'll send you the copy" with no name and no date is the number one source of delay. Decide: either the contractor writes — a line item of its own, covered in our article on landing page copywriting pricing — or you supply it, on a firm date.
• Images. Usable existing photos, stock to purchase, or a shoot to organize don't carry the same cost or the same lead time. Spell out usage rights.
• Testimonials. Name, photo, written permission: collect them before kickoff, not during sign-off.
• Access. Registrar, hosting, email tool, ad account: list who holds what. Projects sit blocked for a week over DNS credentials nobody can find.
• The legal layer. Legal notices, privacy policy, form data processing information, consent checkboxes: say who produces them.

Sign-off, code ownership and handover

Three lines here save weeks of argument. Sign-off first: list what will be checked — mobile rendering, form submission all the way to the destination tool, conversion tracking, load time, legal links — and how many revision rounds are included. Ownership next: the delivered code belongs to you, it lives in a repository you control, and the project doesn't depend on an account opened in the contractor's name. Handover last: who edits the page in six months, with what technical level — that's what determines the real cost of maintaining a landing page.

The questions a good contractor will ask if you haven't answered them

• "Two months from now, what would make you say this page worked?" That's the goal, rephrased. If you hesitate, the page isn't ready to be briefed.
• "Where will the traffic come from?" Paid ads, search, email: the source changes the headline, the length and the amount of proof required.
• "What happens when someone submits the form?" If nobody can answer, the project has a functional gap that design won't fill.
• "Who approves, and do they share the goal?" An approver discovered late in the project is a full revision cycle added.
• "What envelope does this page have to fit, all in?" A range lets scope be adjusted instead of quality; our article on the full cost of a landing page covers the line items people forget.

Briefing a redesign: what changes

A redesign brief doesn't just describe the page you want: it also describes the one being replaced. Three pieces of information are almost always missing. First the history: where current traffic comes from, at what volume, which campaigns point at that URL right now. Then what was working: a section, a headline, a proof format you have reason to believe is effective — throwing those out for the sake of novelty is the most common way to make a page worse by rebuilding it. Finally what must not break: URL, redirects, tracking IDs, integrations, forms already connected. Add the real reason for the redesign: the question of when to redesign a landing page is settled before the brief is written.

A brief is judged on one thing: how many questions it makes unnecessary. Write it once, reuse it, and send the same document to every contractor, whichever route you take between a template and a custom build. The 10 LanderKit templates (€89 each, €229 for the full pack) ship as standalone Next.js projects, code included: the brief then stops being about building the page and becomes about the content and the offer — the only sections nobody but you can fill in.