You do not need a finished design before speaking with a website designer. You do need enough context to explain what the site must do. A short, honest brief helps both sides decide what belongs in scope and what should wait. Use the checklist below to make that first conversation more productive.
Describe the business goal
Start with the outcome you want the website to support: qualified enquiries, product purchases, course enrolments, clearer information or something else. Explain who makes the decision and what they need to know. “We need a modern website” describes a look; “customers need to compare two services and request a consultation” describes a job the site can be designed to do.
List the most important questions potential customers ask you in calls, messages and emails. These questions often become useful page sections and FAQs. If you already have a site, share what works and what frustrates users. Separate observed problems from guesses.
Gather the pages and content you already have
Write a rough list of pages: Home, Services, About, Projects or Testimonials, Journal and Contact are common starting points, but your actual site may need fewer or more. Share existing copy, brand assets, product information, policy text, photographs and case studies. Say which items are final, which need editing and which do not exist yet.
Do not hide content gaps. If a service page depends on a case study that has not been approved for publication, the designer can plan another form of evidence. If you have photos or screenshots, confirm permission to use them and supply original files where possible.
Explain the features and workflows
Describe what happens after someone clicks the primary button. Does a form email the team? Should the visitor choose an appointment time? Should a product be added to a cart and paid for online? Does a learner need a dashboard, lessons, quizzes or certificates? The complete journey matters more than a long list of plugin names.
For ecommerce, gather product types, variations, delivery rules, payment methods and refund or support processes. For online learning, outline course structure, enrolment, access rules, progress tracking and who manages lessons. Tell the designer about existing tools that need to connect, such as a CRM, payment provider or email platform. Ask for a test of these flows before launch.
Set a realistic budget and decision process
Give a budget range if you have one. A range helps the designer prioritize the parts that matter most and identify optional features. Ask what is included in the proposal: discovery, design, development, copy or content entry, testing, training, hosting setup and post-launch support may be separate work. Clarify who approves design and who supplies feedback; long approval chains often affect timelines.
If you have a launch date, explain why it matters and which content or integrations must be ready beforehand. A timeline is more useful when it includes both the designer’s work and your own decisions and materials.
Ask about ownership and upkeep
Confirm who owns the domain, hosting account, WordPress administrator access and licenses. Ask how the site will be backed up, updated and handed over. Request a demonstration of how to edit common content. A site is easier to maintain when ordinary updates do not require a developer for every sentence or new article.
Look at the designer’s relevant work and ask what they personally delivered. A store, portfolio and learning platform have different challenges; the best example is one that relates to your workflow, with a clear explanation of the choices made. Avoid treating a claimed performance number or attractive mockup as proof without context.
A brief you can copy
- What my organization offers and who the site serves.
- The main action I want visitors to take.
- Pages and existing content, including missing materials.
- Required user journeys and integrations.
- Brand files, images and permissions.
- Budget range, target date and who approves work.
- Current website and specific problems, if any.
- Who will manage the site after launch.
Bring this brief to a discovery call. It does not have to be perfect; it gives the designer a basis for better questions and a proposal that reflects your actual needs. To see how I structure WordPress projects, read my website design service or book a call.
