The return of the generalist
For a decade we were told to specialize. AI just changed the math.
- Note
- June 2026
- 2 min read
For small SaaS and AI teams, one senior designer who can also build is often more useful than three specialists, because most of the time goes into handoffs. AI coding tools have made that combination much more practical.
For years the standard advice to designers was to specialize: pick UX, or brand, or front-end, and go deep. That made sense when each step needed a different person and a different tool. A product designer handed off to a developer, a brand designer handed off to a web agency, and everyone worked from files.
That’s changing quickly. In August, Joel answered a thread about whether designers should code, as he put it on X: “At this point, and even more so in the future, the act of coding will become irrelevant. So that question should be reframed as “Should designers build?” and yes, they should.”
What a generalist actually does here
For us it means one person who can:
- design the product UI and the system behind it,
- design the brand and the marketing site in the same visual language,
- build and ship that work, using Claude Code in your repo or in our own projects.
The connective work is the valuable part: linking strategy to form, knowing which problem is worth solving first, and keeping the product, the brand and the site consistent with each other. That used to require meetings between three teams. Now it can live in one head.
Depth still matters
This isn’t a case for being shallow everywhere. You can’t connect things you don’t understand. A generalist without real depth in design just produces faster slop. What changed is that the cost of reaching into the next discipline went down, so the person with depth in one area can now carry the work further before handing it off, or skip the handoff entirely.
The trade-offs
One person can only do one thing at a time. That’s why Partner works one focus at a time, from US$6k/mo, and why bigger teams with several tracks running at once need Director, from US$18k/mo, or more people. A generalist is also not a replacement for a specialist when a problem really needs one, like 3D animation, shaders or complex data visualization. In those cases we bring in someone who does only that.
When this setup fits
Early-stage teams, products where the brand and the product need to feel like one thing, and anything built with AI coding tools where design changes go straight into code. That’s most of what we see from SaaS and AI founders right now.
If that sounds like your team, send your brief.
Asked & Answered
For small SaaS and AI teams, a senior generalist who can design and build usually saves the most time, because it removes handoffs. Bring in specialists for problems that really need deep, narrow expertise.
The better question is whether designers should build. With AI coding tools, a designer can take work much further into production without becoming a full-time developer.
Keep reading
- Design for technical founders: work your engineers can buildHow technical founders can judge design work, and how design should reach engineering without a translation step: tokens, components and code.
- The maker who became a managerI spent a decade moving away from the work I loved. Here is why I came back.
- When should a startup hire its first product designer?When a startup should hire its first product designer, what to have in place before that hire, and how a design partner can bridge the gap until then.