A brief is useful when two people can read it and agree what a successful website must let a visitor do. “Modern and professional” is a preference, not an acceptance test. Start with the business outcome: a customer finds the right service, understands its limits and can make an appropriate enquiry without sending confidential information.
Start with real journeys
List the main audiences and their questions. A new customer may need examples, location and a straightforward enquiry route. An existing customer may need support instructions. Neither necessarily needs a member login. Put those tasks in order and describe the content or function each requires. Distinguish something essential for launch from a later convenience.
Bring an inventory of existing pages, media and useful search addresses. For a rebuild, say what must survive, including old URLs, contact forms, downloads and domain/email records. A supplier should not discard valuable information just because a new template is easier. If a page will move, agree where its old address should lead and how that will be checked.
Make the scope measurable
Describe page types and content responsibilities, not only an attractive homepage. Who supplies photographs, approves claims and writes service copy? Who has the right to use each image? What happens if the content is late? Specify a manageable review process with one authorised person consolidating feedback. New requirements and defects against the agreed brief need different treatment.
Useful acceptance examples include completing a keyboard enquiry journey, reading service boundaries at a phone-sized viewport, receiving a safe submission reference, and finding company information. Name the test conditions and who makes the customer decision. An automated accessibility scan or a desktop screenshot alone cannot prove the whole experience works.
Ask about ownership and continuing cost
Identify domain, hosting and primary account owners before purchase. Ask what editable files, source, licences and operating notes you receive. List renewal, maintenance and optional marketing costs separately. A cheap initial price can be misleading if moving away requires rebuilding or if a necessary subscription was never mentioned.
Include the target date, genuine deadline and dependencies. Ask for assumptions and exclusions alongside the price, and agree who authorises deployment after review. A staging link is not automatically permission to change DNS or activate tracking. If the brief contains important unknowns, a bounded discovery with a useful written output is often safer than pretending a precise build price already exists.
A practical next step is a one-page task list plus the old-site inventory. That gives a supplier enough context to explain whether the right route is a focused improvement, a configured product or a new build, while leaving detailed visual decisions until the basic job is understood.
Sources and review
Prepared by Yellow Brick Tech. General guidance; the source and test conditions for your own situation still matter.
Next review: 4 May 2027