How to choose a UI/UX agency for your stage
Choose a UI/UX agency by matching three things: your company stage, how much of the work is design versus build, and how long you will need the team. Decide first whether you need an agency at all, because in some situations a freelancer or an in-house hire is the better answer.
Agency vs in-house vs freelancer
These options combine well. A common pattern is an agency for the first version and the design system, then an in-house designer who takes over while the agency stays on a small retainer.
| Option | Best when | Strengths | Limits |
|---|---|---|---|
| Agency | You need a full team for a defined period: research, UX, UI and often build | Starts within weeks and brings process and several skills at once | Costs more per hour than a freelancer, and knowledge leaves unless handoff is planned |
| In-house designer | Design is a permanent daily need and the product is your core business | Deep product knowledge and constant availability | Hiring takes months, and one person rarely covers research, UI and systems equally well |
| Freelancer | The task is well defined and one skill is enough | Lowest cost and direct contact with the person doing the work | A single point of failure with limited capacity, and you manage the work yourself |
Match the agency type to your stage
Most disappointing engagements come from a size mismatch, not from weak design. A startup inside an enterprise consultancy gets too much process. An enterprise inside a five-person studio gets too little capacity.
| Your situation | Look for | Examples from this guide |
|---|---|---|
| Startup or SME with no product team | One senior team that designs and builds | BlackCard, Ramotion |
| SaaS scale-up with engineers but too few designers | Embedded designers on subscription or sprint terms | Eleken, Netguru, Bakken & Bæck |
| Brand that sells online | A commerce specialist that knows your platform | Build in Amsterdam, Domaine |
| Enterprise with many stakeholders or complex software | A consultancy with research, accessibility and governance practice | ustwo, Ergosign, frog |
Seven questions to ask before you sign
- Who exactly will work on our account, and how senior are they?
- Can we see a case study from a company at our stage, including what did not go to plan?
- What happens in the first two weeks?
- How do you hand off to developers, and do you build as well?
- Who owns the design files, research data and any code?
- How are changes to scope priced?
- What happens when the engagement ends, and what will our own team need to run with it?
Signals of a good fit
- Their case studies show shipped products you can open and use, not only concept shots.
- They ask about your users and your business model before they talk about visuals.
- They propose a smaller first step than you asked for.
- The people in the pitch are the people who will do the work.
- They are clear about what they do not do.
Red flags
- A fixed price for a scope nobody has written down.
- No discovery step and no contact with real users.
- No mention of accessibility or usability testing anywhere in the proposal.
- Reluctance to hand over source files.
- A portfolio in which every project looks the same regardless of the client.
Where BlackCard fits
BlackCard, the studio behind this guide, belongs in the first row of the table above: small and mid-size companies that want one senior team to design, build and automate instead of hiring a large consultancy. It is managed from Germany and works in English and German.
It is a boutique. It is the wrong choice for a programme that needs twenty designers at once or for staff augmentation, and for those needs the larger firms in this guide are a better match.
Common questions
How many agencies should I shortlist?
Three is enough. Pick them from the same tier so the proposals are comparable, send each the same one-page brief and ask the same questions. A fourth or fifth candidate rarely changes the decision and mostly adds meetings for your team.
Should the agency be in my time zone?
Some overlap matters more than full overlap. Three to four shared working hours a day is usually enough for reviews and quick decisions. For workshops and user research in a local language, a nearby team has a real advantage, which is one reason this guide leans European.