You do not need to arrive at a website conversation with a technical specification, a completed sitemap and a firm opinion about hosting architecture.
You do need to explain what the website should help people do. A short, honest brief gives a designer a better starting point than a long list of features collected from other websites.
These are the details worth gathering before you ask for a quote. Rough notes are absolutely fine.
Explain the business and the people it serves
Describe what you offer, who usually buys or uses it, and where you work. Include any audiences with different needs, such as customers and potential volunteers.
Then name the most important action for a visitor. Is it sending an enquiry, buying a product, reading a menu or finding out how to attend an event?
If there are several actions, put them in order. A designer can help you build a page around a clear priority.
Describe the problem you want to solve
If you already have a website, explain what is not working. Perhaps visitors cannot find a service, the content is difficult to update or the site no longer reflects the business.
Separate what you know from what you suspect. “We get calls asking where to park” is useful evidence. “We need a moving banner” is a proposed solution that may or may not address the problem.
For a new website, explain what people currently rely on instead and where that causes difficulty.
List the information and functions you need
Start with the content: services, products, background, project examples, contact details and common questions. Then add any functions such as payments, booking or an event listing.
Describe how a function should work in practice. If you need enquiries to reach different people, say who receives what and what should happen afterwards.
Mention connections to existing tools. A form feeding a CRM needs a different conversation from a form that simply emails an inbox.
Be clear about what already exists
List the materials you can provide: logo files, photographs, copy, product information and testimonials you have permission to use.
Say where you need help. Writing, photography and organising a product catalogue all take work, so they should be discussed as part of the scope.
Include who controls your domain and current hosting if you know. Share account access through an agreed secure process later, rather than putting passwords into the brief.
Share preferences with a reason
A few example websites can help, provided you explain what you like about them. It might be the clear navigation, useful product information or calm use of colour.
Mention anything that would feel wrong for your business too. “Friendly and straightforward, without constant pop-ups” tells a designer more than “make it modern”.
The aim is to communicate your priorities, not request a copy of someone else’s website.
Discuss timing, budget and the handover
Explain any genuine deadline and what it depends on. If content is still being gathered, say so. An available budget range helps shape a realistic proposal.
Ask what the quote includes, which ongoing costs sit outside it and who will maintain the site. Discuss training if you want to make updates yourself.
You can bring these notes to Estuary Connect’s website design service without polishing them into a formal document. Tell us about the website you need, and we can work through the gaps together.