How to choose a design partner for a complex B2B product

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.

That work is also harder to do – and easier to skip – if the design investment itself 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.

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.

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.

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.

Frequently asked questions

What makes a B2B product design partner different from a general design agency? 

The difference is in what happens before any design work begins. A B2B product design partner starts by understanding the commercial system the product lives inside: who the buyers are, how they evaluate software, what compliance requirements will slow an enterprise deal, and how the product needs to behave as it scales across user roles. A general agency starts with the brief. Those are not the same starting point, and the gap between them shows up in the work.

When should a funded B2B company invest seriously in design? 

Before the architecture is locked, not after. Design decisions made early – about information hierarchy, user roles, how the product handles different levels of access and complexity – are cheap to make and expensive to undo. The companies that wait until they have lost a few enterprise deals to underinvestment in design find themselves paying twice: once to fix the product and once in the sales momentum they lost while it was wrong.

How do I evaluate a design agency's portfolio for a complex B2B product? 

Skip the visual output and ask about the decision-making. What was the underlying commercial problem? What happened when user research and stakeholder requirements pulled in opposite directions? What does the design system they delivered look like twelve months later – is it still in use, or did the product evolve past it? A studio that can answer those questions with specifics has been inside the kind of problem you are trying to solve. One that redirects to how things looked has not.

How important is a design system when building a complex B2B product? 

More important than most founders realise until they do not have one. Every new feature built without a design system adds visual and technical debt that compounds quietly – until the product looks inconsistent across surfaces and gives enterprise procurement a reason to pause. A well-built design system does not just keep things tidy. It signals to buyers that the product has been built to last, not just to demo.

If your product is more complex than most agencies are built for, see how we work.