A strong website supplier should be able to explain how their process meets your particular requirements. Attractive examples help you shortlist, but the selection decision also needs evidence of content planning, functional checks, ownership and support. Use a structured conversation so you compare more than visual taste.

This guide covers supplier suitability, project scope, editing requirements and evidence-based selection criteria. Discuss the relevant requirements through ITZ’s Website Design service.

Review relevant examples

Inspect live websites on desktop and mobile. Consider navigation, readability and how the site supports its audience. Ask the supplier to explain its role in each example rather than inferring responsibility from a portfolio image.

Select examples that resemble the tasks your customers need, not simply your industry colours. Ask who created the copy, implemented the functionality and maintains the result. Review a service-to-contact journey on your own phone. A supplier should be able to discuss constraints and choices rather than taking credit for an entire project without qualification.

Compare equivalent scope

Request clarity on design, development, content, integrations and launch checks. A quotation should identify revision limits, dependencies and recurring services so that proposals can be compared meaningfully.

Issue the same brief to shortlisted suppliers and request written assumptions. Compare page structure, content work, mobile treatment, integrations and acceptance testing. When one proposal omits an item, ask whether it is excluded or supplied by another party. This prevents a misunderstanding being discovered only after the project has started.

Discuss Your Website Partner Brief to discuss supplier suitability, project scope, editing requirements and evidence-based selection criteria.

Confirm access and ownership

Establish who controls the domain, hosting and website administration. Document ownership of bespoke deliverables and any third-party licence restrictions. Handover requirements should be agreed before work begins.

Clarify administrative access, account registration and the editable materials included at handover. Understand restrictions attached to commercial templates, fonts and hosted platforms. Ask for a demonstration of a routine update your team will need. Ownership language in an agreement should translate into practical access and an understandable maintenance process.

Assess communication and continuity

Identify the delivery contact, approval process and support arrangements after launch. The relevant factors are capability, accountability and continuity, whether the supplier is an individual or an agency.

Meet the person responsible for delivery and agree how feedback is consolidated. Ask how defects, scope changes and post-launch requests are handled. A useful supplier can distinguish a required fix from a new feature and explain the impact without vague promises. Keep important decisions in a shared record accessible to the business.

A practical example

Illustrative example: a prospective supplier shows an impressive ecommerce project, but your priority is a multilingual service site maintained by office staff. Ask them to demonstrate the editing and translation workflow relevant to you. Evidence aligned with your requirements is more informative than a generally impressive portfolio.

Your review checklist

  • Review relevant tasks and establish the supplier's actual role.
  • Compare written scope, assumptions and testing obligations.
  • Confirm account control and practical editing access.
  • Agree the delivery owner and post-launch support route.

Frequently asked questions

What is the most useful question before accepting a proposal?

Ask exactly what will be delivered, how completion will be assessed and what access and documentation will be provided at handover.

References and further reading

Related services and guides

Discuss the next step

Discuss Your Website Partner Brief. Use the form below to discuss supplier suitability, project scope, editing requirements and evidence-based selection criteria. Share the relevant goals and existing arrangements; do not include passwords, private records or access tokens.

Discuss Your Website Partner Brief ↗

Reviewed and expanded on 15 October 2026. Examples are illustrative; the appropriate approach depends on your business requirements and existing systems.