01
Ask how they will understand the business problem
A designer should be able to explain discovery in plain language: audiences, customer questions, business goals, existing evidence, internal constraints and the actions the website should support. A proposal based only on page count may miss the work that makes those pages useful.
Ask which parts of the project they will perform, which they will subcontract and which require input from you. This reveals whether content, photography, accessibility, integrations and migration are genuinely covered.
- What do you need to learn before proposing a solution?
- Who will write and approve the content?
- How will you decide which pages and features are necessary?
02
Example: compare decisions rather than headline prices
One proposal may include content workshops, redirect planning, accessible components, form testing and a supported launch. Another may offer the same number of pages but expect finished copy, omit migration and end at deployment. The second is not necessarily wrong, but it is not the same scope.
Ask each supplier to mark assumptions and exclusions. A lower figure based on unspoken assumptions can grow later or leave essential work with a team that did not expect it.
- Compare deliverables and acceptance criteria
- Identify third-party subscriptions and renewal owners
- Confirm how changes to scope are approved and priced
03
Ask actionable technical and operational questions
Confirm who will control the domain, hosting, analytics, repository, content system and supplier accounts. Ask how backups, software updates, form delivery, spam protection, performance and mobile testing will be handled.
Accessibility and security answers should describe a process and its limits. Be cautious if a supplier promises complete compliance, an unhackable website or a guaranteed Lighthouse score without knowing the final content and integrations.
- Will accounts be registered in the client’s name where appropriate?
- What browsers, devices and keyboard journeys will be tested?
- What happens if a form, deployment or integration fails?
- What support is available after launch?
04
Common mistakes when selecting a web designer
A polished portfolio does not by itself prove that the supplier can handle your content, data or operating model. Check whether examples are real client work, internal products or concepts, and ask what the supplier actually delivered.
Do not choose solely on price, personality or a promised launch date. Evaluate clarity, written scope, ownership, communication and how honestly the supplier handles uncertainty.
- Do not accept invented results or unverifiable testimonials
- Do not leave domain and account ownership until launch
- Do not assume maintenance is included
Practical next steps
Checklist
- 01Write the business objective before requesting proposals
- 02Ask who owns content, accounts and intellectual property
- 03Compare scope, assumptions and exclusions
- 04Discuss accessibility, security and privacy responsibilities
- 05Confirm testing, launch and handover
- 06Review ongoing support and third-party costs
Common questions
Questions and answers
Should I ask for references?
Yes, where appropriate, while respecting client confidentiality. Also inspect live work and ask what the supplier was responsible for.
Who should own the domain name?
The business should normally retain appropriate control of its domain and understand the registrar, renewal and recovery arrangements.
Should a web designer guarantee first place on Google?
No. A supplier can improve technical and content foundations but cannot ethically guarantee a particular organic ranking.
Is the cheapest quote a warning sign?
Not automatically. It may reflect a smaller scope or simpler approach. The warning is a price that cannot be connected to clear deliverables and responsibilities.
Need a considered recommendation?
Discuss the website, not just the symptom.
AHANIX reviews each requirement manually. Technical recommendations may depend on access to the website, hosting or DNS configuration.
Continue learning