By Love & Pixels editorial · Published and reviewed 2026-10-14
An editorial guide, based on documented practices. This is not first-hand research or a claim of measured client results.
Start with the business decision
A website brief is most useful when it describes a decision your audience needs to make. A visitor may need to understand whether your service fits, compare packages or ask for a proposal. Write down that decision before listing visual references. Then identify the primary audience, the offer and the action you want a qualified visitor to take. A small business website does not need to support every possible audience on its first screen. Prioritizing one audience helps the page structure and copy stay coherent.
Describe what is changing in the business. Perhaps the current site no longer reflects your services, inquiries lack useful context or a new offer needs a dedicated destination. These are concrete problems a studio can scope. “Make it more modern” is a useful aesthetic preference, but it is not an acceptance criterion. Pair it with a functional requirement, such as a clear service comparison and an inquiry flow that saves submissions reliably.
Define the content before the page count
A five-page website can be straightforward or demanding depending on what belongs on those pages. List the information visitors need: service descriptions, inclusions, exclusions, starting prices, process, contact details and any evidence you are permitted to publish. Mark which copy already exists and who will approve new copy. If you have no approved case studies, say so. Clearly labeled concepts are more credible than invented client results.
Prepare an asset inventory covering logos, fonts, photography, illustrations and video. Record the license or ownership for each item. A file arriving in a shared folder does not establish permission to publish it. If new assets are needed, identify whether they will be original, commissioned or licensed, and who will pay any additional costs. For an AI-assisted project, clarify which assets may use generative tools and what human review is required before publication.
Ask what AI actually changes
AI can assist with exploration, coding and drafting. It does not remove the need for an accountable person to check the result. Ask the studio to describe where AI enters the workflow, what data is shared with external providers and how generated material is reviewed. Do not send confidential customer records merely because a tool can accept them. Data access should be proportional to the job and agreed explicitly.
Evaluate deliverables rather than the number of tools used. A working website should have readable content, responsive layouts, accessible navigation and verified interactions. If the proposal includes automation, ask what happens when the model is wrong, an integration is unavailable or a request times out. A bounded workflow with a documented exception path is easier to operate than a broad promise of autonomous work.
Agree measurable acceptance criteria
Translate the brief into checks that can be performed. Navigation should reach the agreed routes. A valid inquiry should be durably stored or delivered; an invalid request should show a useful error. The primary content should remain available if a visual effect fails. Keyboard users should be able to reach the menu, links and forms with visible focus. Define supported browser and device coverage instead of assuming every device is equivalent.
Performance should also have a measurement context. Lab tests help identify regressions, but they are not proof of real-user Core Web Vitals. Agree which pages and test settings will be reported. An interactive scene may load after the main text and use a lower rendering quality on slower hardware. This is an implementation choice worth discussing before the design is approved.
Clarify ownership and recurring costs
List the accounts involved: domain registrar, hosting, email delivery, analytics and storage. Decide which accounts should be owned by your business and what access the studio needs. A handover should explain how to update the site, where submissions are stored and who maintains dependencies. Source ownership, third-party licensing and payment milestones belong in the written agreement.
Separate the project fee from recurring charges. Hosting, paid fonts, database usage and AI calls can create ongoing costs. Ask for the likely cost categories and usage assumptions rather than a false promise that everything is free forever. Finally, agree how feedback is consolidated and how additional scope is handled. A good brief protects the quality of the work by making responsibilities visible.
A useful first brief
You can begin with one page of plain text: your business, target audience, main offer, desired visitor action, existing site, approved assets, budget range and timing constraints. Add the questions you cannot answer yet. Discovery should help resolve them. The goal is not to prescribe every implementation detail; it is to create enough shared understanding to compare proposals and make informed decisions.