Begin with a concrete outcome
Replace “a modern website” with a visitor journey and a business requirement. For example: “A visitor can understand our two services, submit a qualified enquiry and receive confirmation; staff can find that enquiry in the CRM.” This is an illustrative brief, not a promise of increased leads.
Specify the audience and the evidence you already have about its needs. If demand or conversion data is unavailable, label the assumption. A design preference can be useful context, but it should not substitute for the website's purpose.
Copy and complete this brief
| Field | Your answer |
|---|---|
| Outcome | What must the visitor and the business be able to do? |
| Audience | Who is this for, in which languages and markets? |
| Pages | List pages, shared templates and structured content types. |
| Content | Who supplies, approves and enters text, images and data? |
| Workflows | Describe forms, bookings, payments, accounts and integrations. |
| Existing site | What stays, what moves and which URLs may change? |
| Constraints | State budget ceiling, deadline and genuine dependencies. |
| Operation | Who edits, maintains and pays for the services? |
| Acceptance | List observable checks for launch and handover. |
| Exclusions | Name work deferred or handled by another party. |
Attach an inventory rather than making the table excessively long. Include sample content and non-sensitive example records. Never put passwords, private customer exports or API keys in a public brief.
Turn feature labels into acceptance checks
“Contact form” becomes: required fields are validated, a successful request reaches the agreed destination, the visitor receives confirmation and a failed delivery is visible to staff. “Editable website” becomes: the named editor can change a real service page using the supplied instructions.
For each check, name the owner and evidence. A screenshot may confirm appearance; it cannot prove that a submitted enquiry arrived in the CRM. A technical SEO checklist can establish implemented controls; it cannot guarantee ranking or traffic.
Ask suppliers to respond consistently
Request the included deliverables, assumptions, exclusions, revision process, recurring commitments and change-pricing method. Ask suppliers to identify unclear requirements rather than silently choosing the cheapest interpretation.
Separate essential launch scope from optional improvements. If a budget ceiling cannot support every requirement, invite a smaller workable first release. This is more useful than obtaining a fixed total for an ambiguous promise.
Use the SiteCost methodology to understand the planning model, then share a calculator scenario with this completed brief. The scenario provides context for discussion. The supplier's written scope and commercial terms determine the actual offer.