Define what the website needs to change in the business.
Before comparing designers, write down the business result you need: more qualified inquiries, better support for a sales team, easier event discovery, stronger recruiting, online sales, or a more credible first impression. This gives every potential partner the same problem to respond to.
Be cautious when a proposal jumps directly to page count and visual style without asking about customers, lead quality, operations, content, or measurement. The scope should follow the job the website needs to do.
Ask who will make the strategic and content decisions.
A strong layout cannot rescue unclear positioning or thin service content. Learn who will organize the pages, shape the message, write or edit the copy, gather proof, and decide what belongs on each screen.
Clarify what your team must provide and when. If photography, project details, approvals, or technical access arrive late, the schedule changes. A good partner makes those dependencies visible instead of surprising you near launch.
Understand who is actually doing the work.
Ask who will lead the project, who designs, who develops, and who answers questions after the contract is signed. A large team is not automatically better, and a small team is not automatically limited. What matters is clear ownership and access to the people making decisions.
Look for a communication rhythm that fits your business: focused review points, clear next steps, and a practical way to collect feedback. Endless meetings and long periods of silence are both warning signs.
Choose technology around maintenance and business needs.
The platform should fit the content, integrations, editing frequency, performance requirements, and skills of the people maintaining it. Ask why the recommended approach suits your business—not which platform is universally best.
Confirm who owns the domain, hosting account, analytics property, source files, content, and third-party subscriptions. Your business should not become dependent on an unclear account structure or a tool only one vendor can access.
Make search migration part of the scope.
If the current website receives search traffic, the project should include an inventory of useful URLs, redirect mapping, metadata, canonical checks, an XML sitemap, structured data where appropriate, and post-launch monitoring. “SEO-friendly” is too vague to evaluate.
Ask how the partner will preserve valuable content and links while improving the new structure. A redesign should not casually discard pages customers and search engines already use.
Read the scope for what is not included.
Two proposals with different prices may include very different work. Compare discovery, copywriting, page templates, custom functionality, integrations, photography, accessibility, analytics, testing, redirects, training, hosting, and post-launch support.
A clear proposal names assumptions, responsibilities, revision points, payment timing, and what triggers a change in scope. The goal is not the longest document; it is shared expectations.
Look for proof that resembles your decision—not only your industry.
Relevant industry experience is useful, but also look for projects with similar complexity: multiple services, ticketing, e-commerce, local lead generation, a content migration, or an active campaign calendar. Ask what problem changed and what the partner was responsible for.
Pay attention to how former clients describe communication, responsiveness, judgment, and follow-through. A portfolio shows the visible result; the relationship determines whether the project reaches it.