What to prepare before hiring a web designer.
Start with your business goals, audience, current website and the actions visitors need to take. Gather existing content and brand materials, then list the functionality you need. You do not need a finished design or perfect copy to begin a useful conversation.
Explain what the website needs to do.
Describe the business in plain language and name the people you want to reach. Choose the main action the site should support, such as requesting a quote, making a booking or understanding a service before contacting you.
Examples are helpful when you explain what you respond to. “I can find the room information quickly” is more useful than “make it look like this site.”
- What is changing in the business?
- Which visitors matter most?
- What should those visitors understand or do?
- What is the current site making difficult?
Gather what already exists.
Collect your logo files, brand guidance, photographs, service descriptions and any content that should remain. Identify what is accurate, what needs rewriting and what is still missing.
If you want to include testimonials, team biographies or project results, gather the original information and confirm permission to publish it. Good content is easier to plan when its source is clear.
- Existing website address and a list of important pages.
- Brand files and photographs you have permission to use.
- Current service or product details.
- Real examples, credentials and customer evidence where available.
Separate essential functionality from possibilities.
Write down the things the website must actually do. A contact form, a booking integration, a shop and a member area have different implications for scope and maintenance.
Say which tools you already use. If you need to update the site yourself, describe the changes you expect to make and how often. That helps the platform discussion begin with your needs.
Ask what the proposal includes.
A shared understanding of the work is more useful than comparing headline prices alone. Ask how the pages, content, design, development and review stages are defined.
If a service is not included, clarify who will handle it and when it is needed. Content preparation and approvals can affect the schedule as much as design work.
- Who supplies or writes the copy?
- Who supplies photography and checks image permissions?
- How are feedback and revisions organized?
- Which integrations, search setup and launch tasks are included?
- What happens if the scope changes?
Make access and handoff part of the conversation.
Identify who controls the domain, hosting and existing website accounts. You can describe those systems at the first meeting; share account access later through an appropriate invitation or secure method rather than placing passwords in a project brief.
Ask what you will receive at handoff, which accounts and licenses remain your responsibility, how editing works and whether ongoing maintenance is available. If you have a deadline or a working budget, share it early so the proposed scope can account for it.