How to Choose a UX Agency

Every UX agency shows off pretty pictures. That’s the actual problem: on the surface, insight-driven design work and skilled surface work look identical. The difference only shows up months later – in products users understand, flows that convert, and features that actually get used. Here’s how to tell the agencies apart before you sign.

Surface or insight – the decisive difference

An insight-driven agency starts with questions: Who are the users? What do they need to succeed at? How do we know the design works? The work is built on research, prototypes are tested against real users, and design decisions are backed by observations rather than taste and opinion.

A surface agency moves faster to high-fidelity mockups. It looks productive – beautiful deliverables early on – but the decisions rest on assumptions. If the assumptions are wrong, the wrong product gets built, and that’s discovered when it’s most expensive to fix.

The questions that reveal the process

Ask these questions during procurement and listen for concrete answers:

• “What does your design process look like for a project like ours?” Good answers describe steps, decision points, and what you’ll get to see along the way. Weak answers jump straight to deliverables.
• “How do you work with usability testing?” Good answer: when in the process, how often, how participants are recruited, and how the results influence the design. Weak answer: “as needed.”
• “How do you know the design works after launch?” Listen for measurable goals and follow-up – not just “the client was happy.”
• “Tell me about a project where research changed the direction.” An agency that has never changed course based on research either isn’t doing real research or isn’t listening to it.
• “Which people will work on our project?” Make sure the expertise you’re buying is the expertise that delivers – not just the expertise that sells.

How to read a portfolio critically

A portfolio should be read as an argument, not as a photo gallery:

1. Look for the chain problem–insight–solution–outcome. Cases that only show the end result hide the process, and it’s the process you’re buying.
2. Ask what the agency actually did. Big brands in the portfolio are impressive, but the role might have been a small part of a large team.
3. Watch out for sameness. If every case looks the same regardless of industry and target group, the agency has a style rather than a process.
4. Ask for a reference. A short conversation with a past client says more than ten case study pages – ask in particular how the agency handled setbacks and changing conditions.

The interplay with the development team

A design that can’t be built within budget isn’t a good design, no matter how elegant it is. Agencies experienced with development design with components and design systems instead of loose images, think about load times, empty states and error messages, and stay involved during the build when reality demands adjustments.

So ask how the agency works during the development phase. Handoff-and-goodbye is a bad sign; iterating together with the developers is a good one. At Weapp, designers and developers sit on the same team – that way of working is behind products like Sejfa, a digital home insurance product for young adults, and it’s worth requiring no matter which vendor you choose.

Warning flags

• The quote lacks research and testing entirely – or cuts them first “to stay on budget”
• The agency promises results before it knows anything about your users
• The portfolio shows pictures but no reasoning
• You don’t get to meet the people who will do the work
• Everything sounds like a yes – no follow-up questions, no objections

Checklist before the decision

Can the agency describe its process concretely? Has it shown how research shaped real design decisions? Does it test with real users? Does the interplay with development work? And do you trust the people – not just the brand? Five yeses is an agency worth moving forward with.