Start with the decision the visitor needs to make
A website brief becomes useful when it names the customer, the offer and the next action. “A modern website” describes appearance, but leaves the work undefined. A clinic may need appointment inquiries; a manufacturer may need product specifications and distributor leads. Those journeys lead to different page structures and different integration needs.
Write down the top three tasks a visitor should complete. Then identify what information they need to feel comfortable taking each step. This prevents the homepage from becoming a catalogue of every internal department.
- Primary audience and service region
- Primary conversion and follow-up process
- Page inventory and content owner
Separate deliverables from assumptions
A proposal should name page templates, unique pages, content quantities and the number of review rounds. “Ten pages” is not enough if one is a searchable catalogue and another is a legal document. Identify what content is supplied, what is edited and what must be created.
Integrations deserve their own inventory. Record the provider, access requirements, recurring fees and test conditions. Payment, scheduling and customer-management integrations may depend on approval or API access outside the developer’s control.
- CMS fields and editor permissions
- Forms, recipients and spam handling
- Old URLs and redirect responsibilities
- Supported browsers and accessibility goals
Define what counts as ready to launch
Acceptance should cover content accuracy, phone and email links, form behavior, mobile layouts and direct page refresh. A visible confirmation must reflect a real submission; a demo form is not a working lead pipeline. Agree on the difference before launch.
Domain ownership, hosting, licenses, analytics and backups should have named owners. Keep agency development fees separate from third-party charges. Ask for source-code handover, editor guidance and a documented process for future changes.
Use the brief to compare proposals fairly
A lower total may reflect a smaller scope rather than a better deal. Compare deliverables, exclusions and maintenance responsibilities side by side. Leave room for discovery where requirements are uncertain, and write down how changes will be estimated.
Bring a page list, examples of appropriate visual direction and a realistic content plan to the first conversation. That preparation turns a vague price discussion into a practical delivery decision.
References and further reading.
Provider capabilities and terms can change. Confirm requirements with the platform before choosing a solution.