Write the brief before comparing proposals
List the services you actually deliver, the customers you serve, the questions your team answers, and the evidence you can publish. Ask each vendor to price the same scope. Specify who writes the copy, supplies images, approves revisions, and maintains the site. Keep optional integrations separate so you can decide what to build first.
Make the enquiry path reviewable
Choose a primary action for each page. Ask to see that path on a phone: opening the page, understanding the service, finding the contact option, and seeing the confirmation. Define who receives an enquiry and how your team handles it. A page is not ready just because it looks finished.
Include search access in acceptance criteria
Google recommends making important content available as text, providing crawlable internal links, and keeping structured data consistent with visible content. Ask for a check of the actual HTML, page titles, canonical URLs, and redirects before replacing an existing site.
Agree ownership and maintenance
Ask who controls the domain, hosting account, website files, business email, and analytics. Document the handover and ongoing editing process. For payments, compare hosted and embedded checkout against your actual order flow and maintenance capacity.
Questions to explore next
Frequently asked questions
Can I get a useful proposal without naming a budget?
You can start by defining the required outcome and scope. Ask the vendor to separate essentials from optional features so you can compare like-for-like proposals.
Should I rebuild every page at once?
Review existing pages and enquiry paths first. Decide what to retain, improve, consolidate, or redirect before approving a replacement.