Founders Hire Designers for the Wrong Reason
Most founders hire a designer when the product looks bad. That's too late. And it's the wrong problem.
The products that actually need design help
The products that are genuinely hard to use, the dashboards, the SaaS platforms, the IoT tools, the agtech systems, they don't fail because of aesthetics. They fail because nobody thought about how a real human would move through a complex system.
That's a different skill. And most designers don't have it.
A consumer app needs to look good and feel intuitive. A complex B2B platform needs to make sense to five different user types, each with different permissions, different workflows, and different mental models of what the product is for. The person doing data entry has a completely different relationship with the product than the person running reports, and both are different from the admin configuring the system.
Making all of that work isn't an aesthetic challenge. It's a structural one. And it's the kind of challenge that most design portfolios don't prepare you for.
The portfolio problem
The portfolio you see when you go looking for a designer is full of polished consumer apps and clean marketing sites. Beautiful, sometimes. But none of it tells you whether the person can sit inside a complex operational product and make it usable for the five different user types who depend on it.
Consumer design and complex product design look similar on the surface. Both produce interfaces. Both involve user research. Both care about usability. But the depth of the problem is completely different.
A consumer app might have three user flows. This is why I design business apps: the depth of the problem is where the real design challenge lives. A complex SaaS product might have thirty user flows, with dependencies between them, edge cases that only appear at scale, and domain-specific logic that the designer needs to understand before they can even begin to design.
The designer who made a beautiful food delivery app isn't necessarily equipped to design a construction management platform. The skills transfer, but the gap is bigger than most founders realise.
What to look for instead
Ask the designer to walk you through a project where the product had real operational depth. Not a redesign. Not a brand refresh. Something where the workflow itself was the design challenge.
Listen for how they talk about the users. In complex products, the users are specialists who already know their domain better than the designer ever will. The good designers will talk about earning the right to design for that user, spending time understanding the domain, shadowing real workflows, learning the language of the industry before proposing changes.
The wrong ones will start describing the colour palette.
Aesthetics vs. structure
The visible layer of your product is the smallest part of the design work. By the time it looks polished, the structural decisions have already been made: the information architecture, the navigation model, the permission logic, the workflow sequencing, the error handling, the empty states, the edge cases.
Those structural decisions determine whether your product is actually usable. A beautiful interface on top of a broken structure is worse than an ugly interface on top of a solid one. The beautiful version looks like it should work, which makes the frustration worse when it doesn't.
The cost of hiring for the wrong thing
If you hire a designer to make it look good, you get a coat of paint. If you hire one to make it work, you get a product. The question of freelancer vs agency matters far less than whether you're hiring for the right skill.
Most founders don't know they should be hiring for the second thing until they've paid for the first. They bring in a designer, get a polished UI, launch it, and then watch users struggle with the same problems they had before, just with nicer icons.
The fix at that point is expensive. You're not redesigning the surface. You're rethinking the structure underneath it. That's the work that should have happened first, and it's the work that requires a designer who understands complex systems, not just clean aesthetics. The best design work is usually this kind of invisible structural work.
Hire for clarity in complexity. Everything else follows from that.
---
