Start with relevant references. A large gallery means little if the examples do not demonstrate content clarity, responsive behaviour, performance, and the kind of business complexity your project needs.
Ask who owns strategy, content, design, development, analytics, SEO, and launch quality. Projects suffer when these responsibilities are fragmented or silently passed to the client.
Clarify the technology, hosting, source ownership, licences, security, backups, editing experience, documentation, and post-launch support. These decisions determine the real operating cost of the website.
Finally, ask how success will be measured. A credible partner should connect design decisions to qualified enquiries, sales, adoption, search visibility, editorial efficiency, or another observable business outcome.
Evaluate the work in a browser, not only in portfolio thumbnails. Test navigation, mobile layouts, forms, content depth, page speed, and accessibility basics. Ask which parts the agency designed and built, what constraints existed, and how the final result performed after launch.
Request a clear delivery model covering discovery, information architecture, content, visual design, development, migration, quality assurance, analytics, redirects, launch, and warranty. The proposal should identify client responsibilities and decision points so hidden dependencies do not appear late in the schedule.
Discuss editing and governance with the people who will operate the site. Ask for a demonstration of common publishing tasks, role permissions, backups, updates, and recovery. A flexible system without guardrails can become expensive; a rigid system can make every small change dependent on a developer.
Compare total value rather than the opening price alone. Include content work, licences, hosting, maintenance, support response, analytics, search migration, and the cost of internal time. The strongest partner can explain trade-offs plainly and leaves the organisation with ownership, documentation, and a maintainable platform.