Start with the goal, not a feature list
Explain why the website or application is being considered now, what does not work today, what result should be visible after launch and which visitor actions matter most.
Describe users and decision situations
A new customer compares services, an existing customer looks for documents, a partner needs technical information, an internal team manages content or an owner wants to see enquiry sources.
Clarify content, integrations and operating constraints
Say whether content will be rewritten, who supplies expert material, whether CRM or other tools are involved, who manages the site and which URLs must survive a redesign.
Separate the first version from future development
Not every idea belongs in launch scope. A calmer project starts with a usable first version and a backlog of improvements that can wait.
What to send before the first consultation
Send the goal, current website, key services, target users, examples you like or dislike, required integrations, known constraints and any fixed deadlines.
A good brief is not a rigid document
It should help the supplier ask better questions and propose options. The final solution may change after discovery, but the starting conversation will be much better.
How iDoWeb helps
iDoWeb helps shape briefs, clarify scope and design the first version so quotes are more accurate and projects start with fewer hidden assumptions.
Related service: Websites and web applications