A professional website helps the right visitor understand an offer, assess its credibility and complete a relevant task. Animation, page count and technical terminology cannot establish that by themselves.
Before paying, ask how the supplier will demonstrate clarity, usability and reliable operation. Portfolio screenshots show appearance; they do not establish that your project has an appropriate scope or a maintainable delivery plan.
Six outcomes you can assess
- Clarity: a new visitor can explain what the business offers and who it serves.
- Task completion: important actions are findable and can actually be completed.
- Credibility: claims have relevant evidence and visible boundaries.
- Usability: the important tasks work on the devices and in the situations visitors use.
- Maintainability: content and technology have named owners and workable upkeep.
- Ownership: access, control and transferable rights are clear.
Show a concept to someone unfamiliar with the business. Ask what the company provides, which problem it addresses and what they would do next. If a lengthy explanation from the designer is necessary, the page still needs work. A slogan that could describe any business is rarely enough.
Check mobile tasks, accessibility and performance
Ask for a demonstration of the main task on a small screen. Can someone navigate, read the offer, complete a form and understand an error without guessing? Check readable text, sensible hierarchy and controls that do not overlap or require precision taps.
Keyboard access, meaningful labels, contrast and understandable feedback belong in the design and testing plan. Important meaning should not depend solely on colour, movement or an image. Ask which checks are included and what unresolved limitations will be disclosed.
Heavy media needs a purpose. Ask what makes the page slow, what is essential and how performance will be checked after launch. A general promise to optimise later does not explain how the proposed design will perform for real visitors.
Match proof and commercial terms to the project
Look for identifiable business and contact details, relevant projects, a clear process and honest descriptions of what is included. A row of client logos does not tell you what work was performed. A demonstration should be labelled as such, rather than presented as a customer outcome.
Read the commercial scope alongside the design
In the proposal, establish who supplies text and images, how many review stages are included, which delays affect the plan and which costs recur. Detailed exclusions help you compare offers more reliably than an undefined “complete website” promise.
Check ownership before signing
Who owns the domain and manages DNS, hosting and email? Which administrator accounts will you receive? Can content and data be exported? Which paid licences are involved? What remains operational if a maintenance agreement ends?
Confirm the contractual position of custom code and design files. Support can be valuable, but dependence should be a conscious choice. Allocate updates, security checks, backups, forms and integrations explicitly.
Supplier comparison scorecard
Score each area from zero to two. Zero means no usable explanation, one means a partial or general answer and two means specific responsibilities and checks.
| Area | Evidence for a score of two |
|---|---|
| Problem understanding | Visitor needs, business goals and scope connect |
| Content | Deliverables and content owners are named |
| User experience | Important tasks and review moments are specified |
| Technology | Choices follow requirements and maintenance needs |
| Accessibility | Concrete design and verification work is included |
| Ownership | Domain, accounts, data and transfer arrangements are clear |
| Scope and price | Deliverables, exclusions and recurring charges are explicit |
| Handover and support | Responsibilities and recovery information are documented |
The highest total is not automatically the right supplier. Use the differences to ask questions about the areas that matter most to your business.
Turn an observation into a checkable requirement
If the contact path is confusing, name the visitor, the missing information and the expected next step. Add it to your website brief. If the path is clear but nobody checks whether it still works, define maintenance responsibilities before commissioning a redesign.
Compare our website development approach, when a one-page website fits, and the decisions visible in our work.