The short answer

The right agency for a large organization has done work of similar scale and complexity, starts with research, runs design and software in the same team, can work within enterprise processes, and stands behind the product after launch. The 12 criteria below are a way of testing that. If you’re a growing business, we cover how the priorities change in a separate article.

We wrote this as a team that has been on the other side of many agency selections. The criteria apply to any agency.

Why think about UX/UI and software together?

Many organizations give design to one agency and development to another firm or an in-house team. Sometimes that is the right call. But every hand-off between design and development is a point of loss: technical constraints surface late, design decisions quietly change in implementation, and when something goes wrong, responsibility falls between two parties.

So the first decision is whether design and software will sit in the same team. Even if they won’t, most of the criteria below apply to both sides.

12 criteria for choosing an agency

1. Work of similar scale and complexity

A few projects that resemble yours matter more than a long client list: similar numbers of users, similar integrations, similar approval processes. Ask the agency what exactly it was responsible for on those projects; “we contributed” and “we did it end to end” are very different things.

2. A process that starts with research

A good agency asks questions in the first meeting rather than selling a solution. A proposal that goes straight to design without understanding your users, your business goals and where things stand today often solves the wrong problem well. Look at how much of the proposal is given to research and discovery.

3. Design and engineering at the same table

Ask whether designers and developers work together from the start of the project. Being in the same team keeps what gets designed the same as what gets built. At Efabrika, research, UX/UI design, front-end, back-end and API development are in one team; Digital Products & Platforms explains how we run it.

4. Technical depth

Enterprise products rarely stand alone: authentication, existing systems, data sources, third-party services. Ask for concrete examples of the agency’s experience with software architecture, integration and data migration. A team that can’t manage the complexity behind the interface can’t deliver what it promises in front of it either.

5. Accessibility and standards

Accessibility isn’t a feature to add later; it is part of the design and the code from the start. Ask which standards the agency works to (WCAG, for example) and how it tests against them. For public bodies and companies serving broad audiences, it is a responsibility, not an option.

6. A design system approach

In organizations with several products or channels, consistency comes from systems, not screens. Ask whether the agency builds design systems, how it keeps them in step with the code, and how it hands them over to your team.

7. Fit with enterprise processes

Procurement, information security reviews, personal data protection, layered approvals: these are the realities of enterprise projects. Ask whether the agency has worked within them before, for example in regulated sectors such as banking or the public sector.

8. Team continuity

Will you work with the people you met in the pitch? Ask how involved senior people will be and how stable the team will remain through the project. In enterprise products, knowledge builds up in people; a team that keeps changing has to relearn everything each time.

9. What happens after launch

A digital product isn’t finished the day it launches; that is when it starts living. Ask whether the agency offers maintenance, support and ongoing development, and how that is planned.

10. Ownership and hand-over

Agree before signing who will own the source code, design files and documentation. One day you may want to hand the product to another team or to your own; how that will work should be discussed at the outset.

11. How success will be measured

“A nice website” isn’t a goal. Ask how the agency defines success: which tasks will become easier, which indicators will be tracked, and how they will be reviewed after launch. A good agency sets measurable goals together with you.

12. Experience of owning a product

A team that has run its own product knows what product decisions cost. Ask whether the agency only does client projects, or has also operated a product of its own over time.

Questions to ask in the proposal stage

  • Which projects like ours have you done, and what exactly were you responsible for?
  • What happens in the first four weeks of the project?
  • How and when will you talk to our users?
  • At what stage do designers and developers start working together?
  • Who will be on the team, and will that change during the project?
  • How do you test for accessibility?
  • How do you support the product after launch?
  • Who will own the source code and design files?
  • How will we know the project has succeeded?
  • Who is your longest-standing client, and why do they stay?

Warning signs

  • A firm solution and price in the first meeting, before the agency knows you.
  • No mention at all of the problem, the process or the outcome.
  • Senior people from the pitch who won’t be on the project.
  • Research and testing cut from the proposal “to save time”.
  • No plan at all for after launch.
  • No clear answers on ownership and hand-over.

An agency, a large consultancy or an in-house team?

All three can be the right choice. Large consultancies are strong on broad organizational transformation; in-house teams know the product best and stay with it longest. An independent design and technology agency offers a senior team directly involved in the work, able to take end-to-end responsibility from research to software. In most organizations, the best results come from an agency working alongside the in-house team and passing its knowledge on. We look at when an independent agency is the right choice in a separate article.

In short

  • Look for work of similar scale, a process that starts with research, and design and software in the same team.
  • Test technical depth, accessibility and fit with enterprise processes with concrete examples.
  • Settle team continuity, life after launch and ownership before signing.
  • Define together how success will be measured.

If you’d like to test these criteria on us, have a look at our work and our approach, or get in touch.