A useful quote tells you what will be delivered, what you must provide and how the result will be accepted. Compare proposals against the same written need, then ask about items that seem cheaper because they have been left out.
Compare an equivalent scope
Specify pages, templates, languages, forms, content migration, integrations and mobile behaviour. Distinguish a design mock-up, an implemented template and a fully populated page. If photographs or copy still need producing, the quote should say who creates and approves them. The website brief guide helps you give each supplier the same starting point.
Identify deliverables that can be checked
Ask what will be supplied at each stage: site map, copy, designs, testing site, redirects, documentation and training. A phrase such as « SEO included » is too broad: which pages, checks and observable deliverables does it cover? A search ranking cannot be guaranteed by one line in a proposal.
Assign responsibilities and rights
Record who provides the domain, hosting, media and third-party services, who holds them and who pays renewals. Clarify rights to use the work and how content will be handed over. Access methods belong in appropriate procedures and should not be copied into a quote comparison worksheet.
Read the cost over time
Separate design and build, subscriptions, licences, maintenance, later changes and possible transaction fees. Something free at launch may create a recurring cost. Compare the number of revision rounds included and how changes requested after approval will be priced.
Plan acceptance and handover
The quote should explain how forms, key pages, mobile use, practical accessibility, images and redirects will be tested. Decide who accepts each stage and what happens when a defect is found. Before signing, write down three pages, two user journeys and one maintenance responsibility that both parties understand in the same way.