01
Prepare enough context for a meaningful proposal
Describe the audiences, commercial objective, current problem, required content, essential functionality, deadline drivers and budget range. Share existing analytics, brand material and provider constraints where available. A supplier cannot price risk it has not been allowed to see.
Separate must-haves from ideas and state who will approve content. Ask each company to identify assumptions and exclusions. If proposals solve different problems, comparing only their totals is misleading. A paid discovery phase can be appropriate when requirements are uncertain.
02
Check relevant evidence without accepting invented results
Review live work where possible and ask what the company actually contributed. A redesign, template configuration, concept and full custom platform are different achievements. Verify testimonials and client relationships where they materially influence the decision.
Look for reasoning, not only screenshots: the challenge, audience, content structure, accessibility, technical decisions and measurable evidence available. No company should guarantee rankings, conversions or perfect security. Concepts can still demonstrate thinking when clearly labelled and not presented as client success.
- Confirm the project classification and supplier role
- Ask which outcomes are verified
- Inspect representative mobile and form journeys
- Look for work with comparable complexity, not just industry
03
Examine the process, deliverables and technical boundaries
A credible proposal should cover discovery, content responsibility, page scope, design review, development, integrations, testing, migration, launch, training and support as applicable. It should state what changes cost, who approves stages and how delays are handled.
Ask about accessibility targets, browser support, performance, security responsibilities, backups, hosting, privacy and third-party fees. For integrations, require an explanation of data flow and failure handling. Common warning signs are vague unlimited promises, unexplained proprietary technology and pressure to transfer the domain into an account the business cannot access.
04
Confirm ownership, support and the exit route
The contract should identify ownership or licence terms for the domain, hosting, source code, design files, content, fonts, plugins, analytics and customer data. Confirm account access during the project and what is supplied at handover. Some third-party components remain licensed rather than owned.
Understand post-launch support hours, response scope, backups, updates and charges. Speak with the people who will deliver the work, score proposals against the same criteria and record the decision. Choose the company whose approach reduces uncertainty honestly, not the one promising every feature for the lowest price.
Practical next steps
Checklist
- 01Write objectives, audiences and essential requirements
- 02Give suppliers the same constraints and evidence
- 03Verify project labels, roles and claimed outcomes
- 04Compare discovery, content and testing scope
- 05Review accessibility, security and migration planning
- 06Identify third-party subscriptions and usage charges
- 07Confirm domain, account, source and data access
- 08Understand change control and post-launch support
- 09Score proposals against consistent criteria
Common questions
Questions and answers
How many web design quotes should I get?
Enough to compare credible approaches without turning selection into an unpaid tender. Two or three well-briefed proposals are often more useful than many vague estimates.
Should I choose a company with experience in my industry?
Relevant familiarity can help, but comparable audience, regulation, integration or workflow complexity may matter more than an identical industry label.
Who should own the domain and hosting?
The business should retain clear rights and authorised account access. A supplier may manage services, but ownership, renewal, recovery and handover must be documented.
Is the cheapest quote a warning sign?
Not by itself. It may reflect a smaller scope or simpler method. Compare like-for-like deliverables, assumptions, licences, maintenance and risk before judging value.
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