By Mehdi HassanHow do you find a design partner for complex products?
You find a design partner for complex products by testing for clarity directly instead of judging portfolios on looks. The right partner can listen to an hour of technical detail and come back with the one sentence, the three sections and the single diagram that make a buyer understand it.
"Complex products made clear" is the work we do every day, for AI, developer, fintech and data products. This guide gives you the tests we'd want a buyer to run on us. It sits within our wider guide to hiring a web design agency, which covers shortlisting, contracts and budgets.
Why do technical products need a different kind of designer?
Technical products need a designer who can understand the product deeply enough to simplify it without making it wrong. Most designers can make a page attractive; far fewer can decide which nine of your ten features to leave out of the hero, and defend that choice to your CTO.
The failure mode is familiar. A team hires a strong visual designer, gets a beautiful site and still hears "so what do you actually do?" on every sales call. The design improved, but the message stayed as complex as the product. That's because the real problem was never visual. It was deciding what to say first, what to prove and what to leave for the docs.
For the page-level craft, see our guide to website design for complex products. This article is about finding the people who can do it.
How do you test a designer's clarity skills?
You test clarity skills with short, practical exercises during the hiring process, not by asking whether they're good at simplifying. Everyone says yes to that question. These five tests show it.
The explain-back test
After your first call, ask them to describe your product in one sentence, as they'd say it to your buyer. If the sentence is accurate and plain, that's a strong sign. If it's jargon or vague, keep looking.
The cut test
Ask what they'd remove from your current homepage. Good partners answer confidently and explain why. Weak ones say everything is important.
The first-screen test
Ask them to sketch, in words or a rough wireframe, what your first screen should say. You're judging the hierarchy, not the art.
The diagram test
Ask how they'd show how your product works in one visual. Listen for a clear sequence of inputs, steps and outcomes.
The engineer test
Put them in a room with one of your engineers for 20 minutes. Watch whether they ask good questions and whether the engineer trusts them afterward.
What should a complex-product designer's portfolio prove?
Their portfolio should prove they've made technical products easier to understand, which means showing the words and structure, not just the visuals. Look for work where the messaging changed, not only the colors.
Signal | What it proves | Weak version |
|---|---|---|
Before-and-after headlines | They changed what the page says, not just how it looks | Same copy in a new design |
Product diagrams or explainer visuals | They can show how something works | Abstract 3D shapes and gradients |
Technical clients | They've learned hard domains before | Only lifestyle and consumer brands |
Docs, pricing or integration pages | They handle the pages technical buyers really read | Homepage only |
A clear rationale | They can explain choices to engineers | Mood words like bold and modern |
If you're a developer tools company, the bar is higher still, because your buyers read code. Our guide to choosing an agency that speaks code covers what to add to this list.
What questions show whether a partner will understand your product?
The questions that matter are the ones they ask you, not the ones you ask them. A partner who understands complex products spends the first call asking about buyers, alternatives and how deals are won.
- Who is the buyer, and who is the user? In technical products they're often different people.
- What do buyers compare you to? Including building it themselves or doing nothing.
- Where do deals stall? That's usually where the website should do more work.
- What do your best customers say you do? Their words are often clearer than yours.
- What's true but too detailed for the homepage? A sign they're already thinking about what to cut.
If a partner spends the call showing their own portfolio and talking about trends, they're selling, not learning. That's not a crime, but it's a poor predictor of clarity work.
Where do complex-product design projects usually go wrong?
These projects usually go wrong at the handoff between the people who understand the product and the people writing and designing the page. Information gets lost, the team fills gaps with generic claims, and the site ends up vague.
Hypothetical example: a data infrastructure startup's homepage
For example, suppose a startup sells a tool that syncs data between warehouses and business apps. Its homepage leads with "The modern data activation platform", followed by twelve feature cards.
A clarity-focused partner would start by asking sales what buyers actually say. They might hear: "We just want our CRM to have the same numbers as the warehouse." That sentence, lightly edited, becomes a much clearer headline than the category name.
The twelve cards would then shrink to the three outcomes buyers care about, with one diagram showing data moving from the warehouse to the CRM. The other nine features move to a product page. The site says less, and buyers understand more. This is an illustration of the process, not a real client result.
For the full method, see how to explain a complex product on your website.
Should you use an agency, a freelancer or an AI builder for a technical product?
For a technical product, choose the option that can do the thinking, not just the production. AI builders and template sites are fast but can't decide what your product should lead with; that decision is the whole job.
Option | Good at | Weak at |
|---|---|---|
Small studio that writes, designs and builds | Owning clarity end to end | Very large, multi-site programs |
Freelance designer | Visuals and speed on a defined page | Messaging and technical depth, unless they also write |
Large agency | Scale, process, many stakeholders | Speed and senior attention on small budgets |
AI website builder | Fast first drafts and simple sites | Deciding what a technical product should say |
Our comparison of AI website builders and a design studio covers where AI tools fit and where you still need people.
