5 AI Tools I Use Every Day as a Designer Who Builds Products
Let me save you some time. I've tried a lot of AI tools. Most of them are shiny toys that solve problems you don't have. A few of them actually changed my life.
I'm a designer. Was a designer. Still am a designer? The lines got blurry when I started building actual software products with AI. No CS degree, no team, just stubbornness and a wifi connection.
Here are the five tools I use every day. Not because they're the trendiest. Because they're the ones I'd genuinely panic without.
## 1. Claude — My co-founder who doesn't want equity
I need to be upfront about this: Claude does most of the heavy lifting in my workflow. Coding, writing, research, strategy — all of it runs through Claude.
I've tried ChatGPT. I've tried Copilot. I keep coming back to Claude. The context window is bigger, the writing sounds like a human wrote it, and it doesn't fight me when I give it complex, multi-step instructions.
How I actually use it on a typical day: I describe a React component by talking about what the user should experience, not what the code should do. Claude translates that into working code. I maintain a knowledge file with all my project details — tech stack, past decisions, things I've already rejected — so every conversation starts with full context instead of explaining everything from scratch.
The difference between Claude with context and Claude without context is like the difference between a coworker who's been on your team for months versus a stranger you grabbed off the street.
Cost: $200/month for Pro Max. Sounds like a lot until you do the math on what a developer, copywriter, and research analyst would cost. Then it sounds like stealing.
## 2. Cursor — The code editor that speaks human
Cursor is VS Code but with AI wired into everything. I can highlight a chunk of code I don't understand, ask "what does this do," and get a plain-English explanation. I can describe what I want changed and watch it happen.
For someone whose brain thinks in layouts and flows, not syntax and semicolons, this is everything.
My workflow usually looks like: Claude writes the big chunks of logic. I paste them into Cursor. Then I use Cursor's inline AI to tweak, debug, and refine — because there's always something that needs tweaking. Always.
It's like having two assistants. One thinks big picture. The other sweats the details.
Cost: Free tier works for getting started. Pro is $20/month and worth every cent.
## 3. Vercel — Deployment for people who hate deployment
I remember when "deploying a website" meant FTP clients and accidentally overwriting the wrong file at 11 PM. That was a dark era. We don't talk about it.
Vercel made deployment boring. In the best way. Push code to GitHub. Vercel notices. Website updates. Done. No servers to manage. No DevOps knowledge required. No 11 PM panic.
For designers crossing into development, this is the bridge that makes the whole journey possible. The gap between "it works on my computer" and "anyone in the world can use it" used to be terrifying. Now it's one git push.
Cost: Free. Genuinely free for indie projects. I've never paid them a dime and I run multiple apps on it.
## 4. Firebase — Backend for people who are scared of backends
Let me tell you about the moment I realized I could build backends. I needed user authentication for an app. In my head, this was weeks of work involving cryptography and server configuration and things I'd need a degree to understand.
Firebase Auth took about 20 minutes. Including the time I spent staring at the screen wondering if it could really be that simple.
Firebase gives you a database (Firestore), serverless functions (Cloud Functions), user management (Auth), and hosting — all without touching a server. Is it the most sophisticated solution? No. Is it the fastest way to go from "I have an idea" to "I have a working product"? Absolutely yes.
Both Hũ Vàng and VocabVault run on Firebase. It's the backend for people who'd rather be designing interfaces than configuring load balancers.
Cost: Free tier is absurdly generous. I haven't paid yet.
## 5. Canva — Don't judge me
Yes. A designer recommending Canva. I can feel the design community cringing.
Here's the thing: when you're a one-person team, you need marketing graphics, social media posts, blog thumbnails, pitch materials, and app store screenshots. I could open Illustrator for each of these. I could also eat soup with a fork. Both work. Neither is efficient.
Canva is for the design work that doesn't matter enough to justify opening professional tools. And when you're solo, "design work that doesn't matter" is about 80% of all the design work you do.
Save your creative energy for the product. Use Canva for everything else.
Cost: Free. The pro plan exists but I've never needed it.
## The truth about tools
Here's what I've learned after two years of building with AI: tools are the least interesting part of the story.
I've watched people with $500/month in AI subscriptions produce absolutely nothing. I've also met makers with just a free ChatGPT account who shipped real products. The difference isn't the tool. It's knowing what to build and caring enough about the user to build it well.
Design thinking — the real kind, not the corporate workshop kind — is the actual superpower here. Understanding users. Structuring information. Making decisions about what to leave out. AI amplifies all of that.
If you have good taste and clear thinking, AI makes you dangerous. If you don't, AI just helps you produce mediocre work faster.
## The monthly damage
| Tool | Cost |
|---|---|
| Claude Pro Max | $200/mo |
| Cursor | $20/mo |
| Vercel | Free |
| Firebase | Free |
| Canva | Free |
| Total | $220/mo |
$220 a month for the capabilities of a small team. That's not a flex — it's a genuine shift in what's possible for solo makers. The barriers to building aren't technical anymore. They're psychological.
The question isn't "can I build this?" anymore. It's "should I build this?" And that's a much better question to be asking.
Want the honest version of building with AI? Subscribe to The AI Builder — weekly insights from a designer lost in the land of code.