Website advice
How to choose a web designer without comparing price alone.
A useful proposal explains the problem, scope, responsibilities, ownership and support—not only the page count and final figure.
Start with what the business needs the website to change.
A designer cannot recommend the right build without understanding the audience, current problem, content, required functionality and next action. Be cautious when every enquiry receives the same package.
Questions worth asking
- What is included and explicitly excluded?
- Who writes, supplies and approves the content?
- Who owns the domain, hosting, licences and administrator access?
- How will mobile, forms and accessibility be tested?
- What happens if the scope changes?
- What support exists after launch?
Look for relevant evidence.
A screenshot alone does not explain the work. Useful evidence connects a genuine requirement to the structure, functionality or decision that addressed it. Numerical claims should be verifiable.
Compare responsibilities and risk, not only aesthetics.
Choosing a designer questions
Should I choose the cheapest quote?+
Only after checking that it includes the same responsibilities. Content, migration, mobile refinement, licences, SEO setup, training and support are often treated differently.
Do I need a local designer?+
Not always. What matters is a reliable communication and approval process. Local knowledge can help when location and service area are commercially important.
Should I ask for administrator access?+
Yes. The proposal should explain ownership and access clearly, including any limits caused by licensed tools or third-party services.
Want a clearly scoped alternative?
Share the business goal and any proposal you are comparing.
Request a WBYD quote