There's a narrative going around right now that goes something like this:
Come up with an idea. Describe it to an AI. Ship a startup. Profit.
I get why it's appealing. Tools like Lovable, Bolt, and v0 are genuinely impressive. You can go from a blank page to a working UI in under an hour. That's real, and it's remarkable.
But I've been building my own product — IdeaPick, an AI-powered idea validation platform for indie hackers — for a while now. And I can tell you with some confidence: the idea is the easy part. What comes after is a different story.
This isn't a discouragement piece. Building something of your own is one of the best things you can do as a developer right now. But if you walk in expecting AI to carry you, you're going to hit a wall fast. Better to know what's actually ahead.
The myth: AI is the co-founder you never had
The pitch is seductive. You have an idea, you have AI, what else do you need?
In practice: quite a lot.
AI is an extraordinary tool for moving faster. It's not a replacement for understanding what you're building, why it matters, or how to make it work reliably. The developers who get the most out of AI tools are the ones who know enough to direct them, catch their mistakes, and step in when the generated output isn't good enough.
Which means the skills still matter. They've just changed shape.
Here's what building IdeaPick actually required — none of which "just have an idea" prepares you for.
Design — more than making things look pretty
You don't need to be a designer. But you do need to understand design well enough to make decisions.
What is the hierarchy on this page? Where does the user's eye go first? Is this button obvious enough that someone who has never seen your product before will know to click it? Does this empty state tell the user what to do next, or does it just look empty?
AI can generate a UI. It cannot tell you whether that UI actually guides a user through your product effectively. That judgment is yours. And if you don't develop it, your product will feel confusing in ways you won't be able to diagnose — because every screen looks fine in isolation and broken as a flow.
Design is also your first trust signal. Users decide within seconds whether your product feels credible. A generic, unpolished interface says "someone made this quickly and didn't care enough to finish it." That impression is hard to recover from.
Cybersecurity — the thing everyone skips until it's too late
This one is unglamorous and easy to defer. Don't.
If you're building any product that handles user accounts, you're responsible for those users' data. That means understanding authentication properly, not just copying an auth flow from a tutorial. It means Row Level Security on your database so users can only access their own data. It means rate limiting your API endpoints so someone can't hammer your LLM calls and run up your bill. It means input validation on everything that touches your backend.
I use Supabase with RLS on every table, Upstash Redis for rate limiting, and Zod to validate every single piece of data that comes back from an AI model — because AI outputs can be malformed, unexpected, or just wrong. None of that is optional. None of it is exciting. All of it is the difference between a product and a liability.
AI will generate code that looks correct and has security holes in it. Knowing enough to spot them is on you.
Business — because a product nobody pays for is a hobby
Building is the part developers are comfortable with. Figuring out who your user is, why they would pay, and how to reach them is the part most developers avoid — and it's the part that determines whether any of the building was worth it.
Some questions you need real answers to:
- Who specifically is this for? Not "developers" — which developers, with which problem, in which context?
- What would make them pay rather than use a free alternative?
- How do you reach them? Where do they spend time, what do they read, who do they trust?
- What does success look like in 90 days — and how will you know if you're on track? I built IdeaPick for indie hackers and solo founders because I am one. That specificity matters. "Everyone" is not a target audience. Trying to serve everyone is how you build a product that resonates with nobody.
You don't need an MBA. But you do need to spend serious time on these questions before you write the first line of code, and revisit them regularly as you build.
Programming — yes, still
This might be the most controversial point given the current hype cycle, so let me be precise.
You don't need to be a senior engineer to build a startup solo. But you do need enough programming knowledge to understand what your AI tools are generating, debug it when it breaks, and make architectural decisions that won't collapse under you six months later.
AI-generated code has a shelf life. It works for the happy path. The moment something unexpected happens — an edge case, a performance issue, a dependency conflict, an API change — you need to be able to read the code and understand what's actually going on.
In IdeaPick, I have 13+ LLM API calls, a streaming NDJSON architecture, a hybrid scoring system that combines deterministic algorithms with AI narrative generation, and state management that handles conversation history, partial streaming tokens, and multiple request states simultaneously. No AI tool designed that system end to end. I designed it, made the decisions, and used AI to move faster within those decisions.
If I didn't understand what I was building, I wouldn't have been able to make those decisions at all.
AI skills — yes, this is its own category now
Knowing how to use AI tools well is genuinely a skill, and most people using them are leaving a lot on the table.
Understanding how to write a prompt that gets a reliable, structured response. Knowing when to use streaming versus a single response. Understanding tool calling, structured outputs, and how to validate AI responses so your app doesn't break when the model returns something unexpected. Knowing which model to use for which task — and why using gpt-4o-mini for everything in IdeaPick made sense cost and quality-wise.
These aren't advanced concepts, but they're not obvious either. Treating AI as a magic box you talk to is how you end up with a fragile product that works in demos and breaks in production.
So why bother?
Because all of this is learnable. And learning it by building something real is the fastest and most durable way to actually learn it.
Every skill gap I listed above is one I've been closing while building IdeaPick. I didn't have all of it figured out when I started. I had enough to begin, and the product taught me the rest.
That's the honest case for building your own thing — not that it's easy, but that it's one of the few contexts where you learn all of these skills together, under real conditions, with real stakes. No tutorial gives you that. No junior job gives you the full picture that fast.
The idea gets you to the starting line. Everything else gets you across it.
Start with what you know. Build toward what you don't. Ship something — even rough, even incomplete. The skills accumulate faster than you think.
What's been the hardest skill gap to close in your own building journey — design, business, security, something else? Drop it in the comments.
Top comments (0)