Explain the goal of the website
Start by describing the audience and the action you want visitors to take. A shop selling products, a trades business requesting calls and a professional service gathering enquiries have different priorities.
Ask the provider how they will translate those priorities into page structure, mobile navigation and contact paths. A good explanation should make sense even if you are not technical.
Ask to see suitable, authorised work
Look for examples of similar requirements rather than relying on generic claims about how many sites have been built. Ask about the provider's role in each example, and whether they can explain the design and development choices.
Treat awards, glowing anonymous testimonials and impressive statistics carefully unless there is a way to verify them. Genuine client feedback can be helpful when the source and context are clear.
Review the proposal and ownership
A useful proposal specifies pages, content responsibilities, revision rounds, functionality, project stages and payment terms. It should also explain what happens when new requirements arise.
Clarify who will own the domain, website content, source files and any licences. Ask how you will make future edits and whether your site can be moved to another provider.
Understand support and renewal costs
Look beyond the launch price. Hosting, domain renewal, maintenance, software updates and security responsibilities should be clear. Find out how support requests are handled and what work is charged separately.
If you are evaluating a new project, see our website cost guide and web design service overview. Then request a written quote you can compare fairly.
