Start with a decision, not a page count
A useful website brief explains what visitors should accomplish. A service business might want qualified enquiries; a club might want membership applications. Write one primary outcome and identify who needs it. “A modern website” leaves important decisions unanswered. “Help facility managers request a maintenance quotation” gives the design a clear job.
Map one complete visitor journey
Describe the steps from arrival to completion. For a quotation journey, list the service page, eligibility information, enquiry form and confirmation. Explain what happens internally after submission: who receives the request, where it is recorded and when the customer hears back. This reveals work that a list of screens can miss.
Separate essential content from optional features
Prepare your service descriptions, logo, contact information and approved project examples. Assign an owner to each missing item. Then label features as launch essentials or later improvements. A booking calendar may be essential for a court rental service, while an animated project map can wait until the core journey works.
Make acceptance concrete
Instead of “the form should work,” require a test enquiry to reach the designated inbox, show a useful confirmation and reject missing required fields. Include mobile use, keyboard navigation, editing access and a handover checklist. Ask the developer to state assumptions and exclusions so two quotations cover comparable work.
Your next step
Write a one-page brief with five headings: audience, main outcome, visitor journey, content owner and launch checks. Attach examples of design you like, explaining what you like about them. This gives your developer enough direction to discuss scope without locking the project into a premature technical solution.
Official references
Published by DevMania with AI assistance. Examples illustrate planning approaches and do not claim client results. Check current provider documentation before implementing product-specific features.