Explain the business as you would to a customer
Describe what you sell, who it fits, where you operate and what usually happens after an enquiry. List the main services or products and the questions people keep asking. You do not need perfect marketing language; specific information gives the designer something concrete to structure.
Choose the first customer action
Should the visitor ask for a quote, request a booking, place an order or speak to someone? Explain how the business handles that action today. The website should support a process that exists or a clearly agreed new process, rather than create expectations the team cannot fulfil.
Gather real material and approvals
Collect your logo files, usable photographs, service or product information and approved work examples. Identify prices, qualifications or claims that need owner review. Use testimonials only with permission and a genuine source. Mark missing assets clearly so the launch scope can account for them.
Know who owns the accounts
List the domain, hosting, current website and relevant Google accounts. Use provider invitations or the agreed access process where possible. Account ownership should stay understandable throughout the project; do not casually share passwords in a general brief.
Agree scope and review responsibilities
Confirm pages, functionality, revision rounds and separate costs before committing. Identify who reviews copy, prices and images and how feedback will be consolidated. A clear decision process helps the build move without promising an arbitrary delivery date.
Your practical checklist
- Business, audience and service area.
- Core offer and next customer action.
- Logo, photographs and approved proof.
- Accurate service or product information.
- Domain and relevant account ownership.
- Scope, reviewer and revision expectations.