Why I prefer building small products

A few years ago, I thought the goal was to build one big product.
The kind of product that tries to solve everything, scale massively, and become your entire identity.

Now I think differently.

I’d rather build many small products.

Small products move faster. They let me test ideas in public, learn from real users, and stay close to the actual problem instead of spending months planning the “perfect” solution. Some fail quickly. Some unexpectedly work. But every single one teaches me something valuable about design, systems, behavior, or distribution.

AI changed the game for me.

As a designer, I no longer need a large engineering team to bring ideas to life. I can design, prototype, build, and ship tools myself. That shift made me realize something important: execution is no longer the bottleneck — clarity is.

So now I focus on building tools that are focused, useful, and opinionated.

A small product can solve one painful workflow better than a giant platform trying to do twenty things at once. It can feel more human. More intentional. More alive.

This approach also keeps me creatively sharp. Instead of waiting years for validation, I get constant feedback loops. I can experiment with interfaces, AI workflows, storytelling, automation, and product thinking in real time.

Some of these tools stay small forever.
Some grow into something bigger.

But the goal is no longer “build one huge thing.”
The goal is to keep building things people genuinely find useful.