Start with the visitor and the action
Explain who is likely to arrive and why. A prospective customer comparing services needs different information from a returning customer looking for support. Name the most valuable actions and the information required before each one.
Include what is confusing on the current site, if there is one. A concrete example of someone failing to find a service is more useful than a broad request for a cleaner design.
Make content ownership visible
List the pages you expect, the material you already have and the material still needed. Say who will supply copy, photography, product details and approvals. Missing content can change the scope of design work.
Share reference sites with an explanation of what you like: clear navigation, readable service pages or a helpful comparison. A reference is a conversation starter, not permission to reproduce another company’s work.
Define practical constraints
Explain timing, budget expectations if known, integrations and the people who must review the result. Mark uncertain items as questions instead of making them sound settled.
Ask the team to describe assumptions and exclusions in its response. That gives everyone a clearer basis for comparing approaches and planning the next discussion.
Your small, useful checklist
The best brief makes the next conversation more concrete. Bring real needs, honest constraints and enough context to discuss the work intelligently. Explore Seventh’s app portfolio for product context. For further reading, consult Google’s SEO Starter Guide.