The strongest partner is not simply the team with the most dramatic portfolio. Look for a clear process, relevant judgement and evidence that design decisions survive the development stage.
Test the thinking
Ask how the team would learn about your customers, prioritise content and judge whether the website is working. The answer should go beyond colours and page layouts.
A good early conversation should identify uncertainty. Be cautious when a supplier recommends a platform, feature list or redesign direction before understanding the problem.
Review the real work
Open live websites on a phone and a slower connection. Check navigation, accessibility, content clarity and small interaction details, not only portfolio mockups.
- Can you inspect the live website?
- Is the agency role stated accurately?
- Are results attributed and verifiable?
- Does the site still work after the launch moment?
- Is the work relevant to your decision?
Understand who will do the work
Ask who handles strategy, content, design, development, project management and QA. A senior sales conversation is not evidence that the same people will stay involved.
Inspect the process and quality gate
The process should explain decisions, responsibilities and acceptance criteria. Look for realistic content, responsive design, accessibility, browser coverage, form testing, redirects, metadata and a controlled launch.
- Who approves scope changes?
- How is feedback consolidated?
- What must be ready before development?
- What is tested before launch?
- What happens if a deployment fails?
Make ownership explicit
Confirm who owns the design files, code, domains, analytics, third-party accounts and content. A healthy engagement leaves the business with clear access and documentation.
Compare fit, not theatre
The right partner has relevant judgement, a delivery model that matches the risk and communication you can work with. Awards, claims and visual polish can be useful signals, but they are not substitutes for inspectable work and clear responsibility.