Designers are building their own AI tools now. That is the real shift
The AI in Design 2026 report from Designer Fund found that half of the designers they surveyed have shipped AI-generated code to production. Weekly AI use jumped from 54% to 91% in a year. And the tell that something structural changed? A growing share of designers are building their own tools — microtools that automate their repetitive work and encode their own judgment. That is the same instinct I described in design taste infrastructure: a taste layer is not a file you buy. It is a tool you build for yourself and refine every week.
I keep a small drawer of these things myself. Each one exists because a generic tool asked me to compromise on how I work, and I got tired of saying yes. That pattern — noticing what the market does not serve and building the fix — is exactly what a solo founder needs to survive in 2026.
Why are designers suddenly building their own tools?
Because the stack stopped fitting the workflow. The State of AI Design report shows the average designer now uses 7 off-the-shelf AI tools, more than double last year, yet nearly half are still searching for a go-to set. When the tool you need does not exist, and an AI assistant can scaffold it in an hour, the rational move is to build it.
The stronger point is qualitative. Designers are not building because the tools are bad. They are building because they can, and because what they encode stays theirs. Ryan Mather of Anthropic put it plainly: "Need a quick dark mode simulator? Sure, just ask for one." That freedom — asking instead of searching — is new, and it is changing who owns the design process.
What kinds of tools are designers building?
Small, disposable, opinionated ones. A component variant generator. A workflow step that turns drafts into design-token-compliant styles. A simulator the market would never ship because it is too niche to sell.
The defining trait is not size. It is that each tool encodes a judgment: this is the workflow step worth automating, and this is what good looks like. UX Tools' State of Prototyping survey found Figma is still the most-used tool, but its role is shifting — often into a finishing tool behind an AI-first process. The platform is no longer the point. The judgment is.
How do you build your first microtool?
Start with the step you repeat most, not the cleverest idea. List the last five things you did twice this week. Pick the one where you already know what "good" looks like. Then ask the model to build it and iterate like you would on any other feature.
Three rules keep these tools honest. Scope them to one step — a growing suite is how you end up re-building Photoshop. Default them to your taste, so every output already matches your tokens and spacing before you look at it. And throw them away freely. The tool is not the asset. The habit of encoding your judgment is.
What does the toolmaker shift mean for solo founders?
It means the winning designer is no longer the one who masters 10 apps. It is the one who can make the 11th belong to them. When taste can be embedded in a tool and replayed without effort, the founder who builds even one small utility ships a more consistent product than the founder who keeps adjusting a generic one by hand.
That is the real shift behind the report. Not "designers can code now." It is: judgment became tooling. The microtool is taste you can run, and once you can run it, you can trust it on days your energy is low.
The solo founder version of this is smaller scale but the same game. You are not going to rival a product. You just need the workflow that belongs to you, the defaults that keep your taste intact, and the habit of taking an afternoon to build the tool that saves your taste every day after. Designers proving they can do this is the signal that you can too.
Frequently asked questions
Because the off-the-shelf stack stopped fitting their workflow. Designers now use an average of 7 AI tools, nearly half are still searching for a go-to set, and AI has made it cheap enough to build what is missing. When a tool does not exist, a designer with an AI coding assistant can make it in an afternoon.
About the author
mosh
mosh is a product designer and design engineer working with design systems, LLM-powered prototypes, agent-safe interfaces, production UI, and automated workflows.
Keep reading
- Google spam policies, fake freshness, and why your dates matter more than you think
We audited our own sites for Google publication-dates compliance and found sitemap lies, back-dated pillars, and silent parseDate fallbacks. What Google actually checks and how we fixed it.
- A demo proves nothing. Ship on an eval gate instead
A weekend AI demo hides its failure rate. An eval gate — a quality bar your changes must clear before shipping — is what turns a prototype into a product you can trust at scale.
- Building got easy. Distribution didn’t — and that’s the real problem now
AI collapsed the cost of building a product, so the scarce thing in 2026 is a first user who comes back. Distribution, not development, is the bottleneck for solo founders and small teams.