You have raised a round. Enterprise deals are on the table. The product works, but it looks like something built by engineers who were solving a technical problem, because it was. The board wants to see what the next version looks like. So you start talking to design agencies.
Three conversations in, you might notice something. Every agency says roughly the same things. They show you portfolios that look good, they talk about process, and they mention design thinking and user-centred approaches. But none of them has asked a question yet that suggests they understand how enterprise software actually gets bought, or what it means to design for a product where the user and the decision-maker are rarely the same person.
Choosing the wrong design partner at this stage costs more than the invoice. It costs the time it takes to find out they were wrong, replace them, and start again, usually months in, when the board is asking why nothing has shipped.
Here is what to look for before you commit.
Does the studio look beyond the brief?
Almost every client who comes to Up Strategy Lab arrives thinking they need a new website or a product redesign. Sometimes that is true. More often, the brief they have written is a symptom, not a diagnosis. The real problem sits upstream: A value proposition that means different things to different people inside the company, a product designed around what the team wanted to build rather than what the enterprise buyer needs to understand, or an ICP that has never been defined precisely enough to make design decisions from.
A design partner who takes the brief at face value and starts designing will produce something that looks like what you asked for. But whether it solves the actual problem, getting enterprise clients, is a different question. By the time you find out, you have spent the budget.
The first signal to look for in any design partner is whether they question the brief before they respond to it.
Built for simple, applied to complex
Most design studios are optimised for simple products. When the brief arrives, they get started with their process and a few weeks later, there is something to show for it.
The problem is that this process is designed for a different kind of product: consumer apps with a single user and a clear task, marketing sites with one message to land, e-commerce flows with a beginning and an end.
But complex B2B products are none of those things. They have multiple user roles with conflicting needs. They have buyers who will never log in and users who log in every day. They have enterprise procurement requirements, compliance certifications, security reviews, multi-stakeholder sign-off, that most designers have never been near.
The simple process cannot scale for a complex B2B product.
When a complex product goes to such an agency, the agency uses the simple process. That is why the result looks polished but still loses the enterprise deals it was meant to win.
Has your design partner built a product of their own?
There is one test that matters more than portfolio quality, process documentation, or case study results: has the studio built a product of their own?
Not just designed one, but built it, from concept to market, with their own money and their own reputation at risk.
A team that has shipped a product understands things that cannot be learned from client work alone. They know what it feels like when a design decision that looked right in a prototype creates problems in production six months later. They understand the gap between a product that users find intuitive and one that procurement is willing to sign off on, because both questions landed on their desk at the same time. They have had the conversation where enterprise trust and end-user utility are pulling in opposite directions, and they have had to find an answer that serves both.
Enterprise buying is almost never the outcome of a single person's decision. Procurement, compliance, leadership, and the people who will actually use the product every day all need to be convinced, and they need different things from the same product. A design partner who has only ever designed for clients, and has never had to make that work commercially on their own product, is likely to optimise for one layer of that problem and miss the others.
Ask any studio you are evaluating: what product did you build, how far did it go, and what did it teach you that client work had not? The answer will tell you more than the portfolio.
The team at Up Strategy Lab built MuchSkills. It started as a colour-coded Google Sheets prototype and became a Red Dot Award-winning platform, recognised as a Major Contender in the Everest Group PEAK Matrix® 2026. When Up Strategy Lab designs your product, that history comes with it. The team has likely seen the problems your product runs into before, and knows what they look like when they show up.

The right start: A knowledge transfer
A design partner who understands complex B2B products does not start designing in the first two weeks. They spend those weeks trying to understand the product as well as you do.
The opening phase of every Up Strategy Lab engagement is a knowledge transfer. The goal is to reach a point where design decisions can be grounded in a real understanding of the product, the ICP, the sales process, the commercial limitations, the gaps in the current product that the roadmap is trying to close. Early design visualisations happen during this phase, but their purpose is to surface misalignments and get everyone on the same page, not to lock in a direction. A visualisation that produces disagreement in week two is more valuable than one that produces consensus, because the disagreement means something important has been found.
If a studio you are evaluating moves straight from initial conversations to concepts, that is worth noting. Speed in the first two weeks usually means skipping the work that makes the next twelve months easier.
What nobody tells you about agency pitches
Most agencies pitch with their best people and deliver with whoever is available. This is common enough in professional services that it has become the default assumption in client-agency relationships, even though almost nobody says it out loud.
The senior designer who walked you through the portfolio, who asked the right questions, who seemed to understand the complexity of what you are building, they may not stay closely involved once the work begins. They appear at the kick-off and at the final presentation. In between, the work is often done by people at a different level of experience, with different levels of investment in the outcome.
Ask the question directly before you sign anything: who exactly will be working on this project, and can you meet them before you commit? A studio that is reluctant to answer that clearly is telling you something.
What to look for in the work itself
When evaluating a portfolio for a complex B2B product, the visual output is the least useful thing to look at. What matters is what the actual problem was, how the studio handled the moments when things got complicated, and what changed commercially as a result.
When Up Strategy Lab rebuilt MultiViz 2.0 with Viking Analytics, the design process involved bringing real users, reliability engineers who used the platform daily, directly into the exploration, not just for validation at the end but while ideas were still being formed. Syncing early concepts with the people who would actually use the product changed what was being built. The result was software designed around how those engineers work, not how the team assumed they worked. That distinction matters commercially: software that fits real work gets adopted; software that fits a design brief gets ignored.

Ask any studio you are evaluating what the most complex B2B product they have worked on was, and what made it hard. Ask how they handled a situation where user research pointed one way and stakeholder requirements pointed another. Ask what the design system they delivered looks like twelve months after the engagement ended, is it still being used, or has it been abandoned because it was too rigid for a product that kept evolving?
You are not looking for perfect answers. You are looking for partners who have encountered these problems before and who can be specific when you push them on what actually happened.
What it costs and how long it takes
Once a studio's work holds up, the next questions are cost and time, and most agencies stay vague on both until the proposal arrives. That makes it hard to compare studios, or to know whether your budget buys a redesign or only a review.
For a complex B2B product the range is wide, because the work is. At Up Strategy Lab, a website usually costs €11,000 to €36,000, and the largest product projects have reached about €90,000. A review of the live product takes a couple of weeks. A full engagement, from strategy through to delivery, usually runs three to six months, although published projects have taken anything from one month, for Lolo's visual editor, to more than a year for CapillaryFlow and Freepower. Designers embedded in your team are billed monthly, usually about €3,000 to €4,500 a month.
What those numbers hide is that the shape of the work matters as much as its size. There are broadly three ways in. A product review gives you a prioritised list of what to fix and one key screen redesigned to show the direction, which is often enough to decide whether to go further. An embedded designer works half-time or full-time in your sprints, next to your developers, which suits a live product that ships every few weeks. A full redesign hands one team the whole job, from strategy to launch, and suits work with a clear finish line. A partner worth hiring will tell you which of the three fits, and will say so when a smaller first step makes more sense than the one you asked for.
How to brief agencies before they pitch
Knowing roughly what design work costs also changes how you brief agencies. Most briefs describe the deliverable, a new product interface or a redesigned dashboard, and say little about the business around it, so every agency fills the gap with its own assumptions and the proposals become impossible to compare.
A brief that gets useful answers covers five things: what the product does and who uses it, who buys it and how that decision gets made, where deals or adoption currently stall, the deadline that matters (an enterprise demo or a board meeting, say), and a budget range. The budget is the one founders most often leave out, usually to avoid anchoring the price. In practice, leaving it out means agencies guess, and you get one proposal sized for a review and another sized for a rebuild.
Then be specific about what you want back. Ask each studio how they understand the problem, who exactly would do the work, what they would do in the first two weeks, which past project is closest to yours and how they price. Avoid asking for free design concepts as part of the pitch. Concepts made before anyone understands your product only show how fast an agency can work. A short paid review is a better test, because you see how the team works on your actual product before you commit to the full engagement.
Questions worth asking the design studio before you decide
Before committing to a design partner for a complex B2B product, these are the questions that tend to surface the right information:
- What product have you built yourselves, how far did it go, and what did it teach you?
- What is the most technically or commercially complex B2B product you have worked on, and what made it hard?
- How do you approach the first two weeks of an engagement? What are you trying to find out, and how do you know when you have found it?
- What does your design system delivery look like, and how is it maintained after the engagement ends?
- Can you show me a case where the design work changed a commercial outcome, not just a product outcome, but something that moved a number that mattered to the business?
The answers matter less than the specificity. A partner who can be precise about what went wrong in a past engagement, and what they did about it, is a partner who has been paying attention.
What procurement will ask
Your own questions are only half of the evaluation, because in a larger company the person who chooses the design partner is rarely the only one who has to agree. Procurement, legal, finance and leadership all look at the decision, and each asks something different. It helps to know those questions before the shortlist goes in, because a studio that cannot answer them slows the whole decision down, however good its work is.
Expect procurement to ask who is on the team and how senior they are, whether the studio has references from work of similar complexity, what the process and deliverables are at each stage, who owns the work and the design files at the end, how access to your product and data will be handled, and how changes to scope are priced. These are commercial questions, and any one of them can hold up a signature. A good partner answers them in writing, early, so the person making the case internally does not have to chase them.
Ownership is the one that most often surprises people late. At Up Strategy Lab, whatever the team builds belongs to the client, and the design system is documented so the client's developers can keep using it after the engagement ends. Whoever you choose, get that in writing before the work starts.
When to bring in a design partner
Once you know who has to agree, the next question is when to start looking for a design partner, and most companies leave it later than they should. They usually start at a predictable moment: after a funding round, before an important enterprise demo, when a board member says the product does not look ready for the next stage, or when a competitor ships a redesign that makes their own product look dated. Each of those moments comes with a deadline, and a deadline is the worst time to find out that the partner you picked needs three months to understand your product. So if one of those moments is coming, start the conversations a few months ahead of it.
The knowledge transfer described above is also harder to do, and easier to skip, when the design investment has been left too late. The right time to invest seriously in design is before the architecture is locked, not after. Retrofitting a design system into a product after the deed is done is almost always harder and more often deprioritised, because the value does not show up in a metric that management can point to immediately. It shows up in long-term retention and low churn, attributed vaguely to customer satisfaction rather than to a specific design decision. By the time the ceiling becomes visible, the cost of clearing it has increased significantly.
Red flags to watch for
Most of the warning signs that a studio is wrong for your product show up before anything is signed, in the pitch and the first few conversations:
- The studio starts designing before it has asked how your product is bought.
- The portfolio shows polished screens but no sense of what the problem was or what changed afterwards.
- The people pitching are not the people who will do the work, and nobody will say who is.
- Concepts are promised in the first week or two.
- They cannot show you a design system still in use a year after they handed it over.
Any one of these is worth a direct question. Two or three together usually mean the studio is built for a different kind of product than yours.
Choosing is hard to reverse
Choosing a design partner for a complex B2B product is one of the few decisions at the funded stage that is genuinely hard to reverse. A bad hire can be replaced. A bad agency engagement, twelve-odd months in, budget spent, product still not where it needs to be for the enterprise deals on the table, costs more than the invoice. It costs the window.
The questions above are not a checklist but a filter. A studio that can answer them with specifics, that can tell you what went wrong on a past engagement and what they did about it, that can show you the work that changed a commercial outcome rather than just a product outcome, that is a studio that has been inside the kind of problem you are trying to solve. The ones that redirect to the portfolio are telling you something too.
Understanding what that work is trying to prevent is worth reading about separately, why most B2B product design fails enterprise buyers gets into the specific ways complex products lose deals they should have won.
If you are still deciding whether you need an agency at all, rather than a freelancer or an in-house designer, the comparison of a fractional design team, an agency and a freelancer sets out when each one fits.
For a second opinion before you choose a design partner, Noel Braganza, who leads design at Up Strategy Lab, offers a free one-hour product review. He walks through your product the way a new user would and sends you the three changes that matter most, written down so you can share them with your team or your board.
If your product is more complex than most agencies are built for, see how we work.


