Start with the work the website needs to do
Write down the main things a customer should be able to do. That might be finding a service, requesting a quote, making a booking, paying for an order or contacting the right person.
Then check that the proposal connects those needs to specific pages and functions. A broad phrase such as “modern website” is not a substitute for agreeing what will actually be delivered.
- Which pages and page types are included?
- Are enquiry forms, booking tools, payments or a shop part of the price?
- Are customer accounts, integrations or data migration required?
- Who writes the content and supplies the photographs?
Check how the website will be designed and reviewed
Ask when you will see the design, how feedback is collected and how many review rounds are included. Clarify what happens if you change direction or add a feature after approving the agreed scope.
The site should be planned for mobile screens and keyboard use as well as desktop. If you have particular accessibility requirements, include them in the brief before comparing proposals.
Understand ownership and ongoing costs
The build price is only one part of the arrangement. Domain registration, hosting, email, paid software, payment processing and ongoing support may be separate costs.
Confirm who owns and can access the domain, website files, content, accounts and any custom work. Ask how you would move to another provider and what information you would receive if the arrangement ended.
- One-off build fees and payment milestones
- Monthly or annual hosting, licence and support fees
- Backup, update, security and recovery responsibilities
- Account access, handover and cancellation arrangements
Compare proposals on the same scope
Before choosing a quote, list the differences. One proposal may include writing, product entry or a booking integration while another leaves those tasks to you. Delivery dates and support boundaries also affect the comparison.
Ask each provider to make exclusions and assumptions clear in writing. A lower figure is only useful if the deliverables suit the business and you understand what will remain your responsibility.
A useful next step
If a proposal leaves important questions open, ask for clarification before accepting it. A short, specific project brief helps a developer identify unknowns and prepare a more useful response.