What to prepare before hiring a web designer.

Describe the problem in plain language

Explain what is changing in the business and what the current website fails to do. Name the audience and the most important action you want a visitor to take.

A useful starting sentence is: “We need a website for [audience] that helps them [action], because the current experience [problem].”

Collect the material you already have

1. Current website and analytics access
2. Service or product information
3. Existing copy, presentations, and sales material
4. Logos, brand files, photography, and video
5. Customer questions and objections
6. Examples of websites you find useful, with reasons

Separate requirements from preferences

A payment provider, content editor, CRM connection, launch date, or accessibility standard may be a requirement. A preferred animation or layout is a preference. Labeling them helps the designer protect what matters while exploring the solution.

List the systems and accounts the website must connect to, even if you do not know the technical details.

Name the decision-maker and review process

Decide who gives feedback, who approves scope, and who signs off on content and launch. Consolidated feedback keeps the project moving and prevents contradictory revisions.

Share any immovable events, dependencies, legal review, or internal approvals that affect timing.

Bring questions, not a finished solution

Ask what the designer needs to learn, what is included, what you must supply, how revisions work, how the website will be maintained, and what you will own after launch.