Find an Idea That Solves a Real Problem
Why the desire to simply build something does not necessarily mean it will become a strong product. In this text, I explore how a pet project differs from a project with real product potential, and why everything starts not with technology, but with a problem.

Very often, I simply want to create some kind of project — not because it solves an important need, but because I am interested in building it. And there is actually nothing wrong with that. This is how pet projects are born: projects where you can learn, test new approaches, or simply enjoy the process.
But if you look at a project not as entertainment or a technical experiment, but as a future product that should grow, attract an audience, and generate revenue, then the desire to “just build something” is no longer enough.
An interesting project and a strong product are not the same thing
A good example for me is the idea of creating a Telegram bot for playing Mafia. I genuinely wanted to build a project like that myself. But if I look at it objectively, there are already enough solutions on the market that cover the main needs of users. Yes, you can add your own features to such a product, make it more convenient, or make some details more interesting. But that alone is not enough to automatically turn it into a strong business project.
Why simply making something a little better is not enough
If people are already using a solution they are familiar with, it is not that easy to move them to another one. Even if your product is better in some ways, that may not be enough for people to want to switch. Users already have an established habit, and most of them will not change it without a strong enough reason.
That is why it is important for me to separate two things: a project that is interesting to build, and a project that has real product potential. These are not always the same thing.
The idea must solve a real problem
When I think about an idea for my own product, it is important for me to look not just for something I can technically build, but for something that solves a real problem. A problem that people face regularly, that annoys them, wastes their time or money, or creates unnecessary complexity. Even better, if people are already trying to solve it somehow, but the current options do it inconveniently, incompletely, or just badly.
So the question is not only whether you can come up with a new idea, but whether there is a real need behind that idea. Even if similar products already exist, it does not mean it is too late to enter the market. But in that case, you need to clearly understand what will make the new product better, simpler, more convenient, or more accurately aligned with the needs of a specific audience.
Conclusion
At this stage, the main conclusion for me is this: if I want to create not just another pet project, but something that has a chance to grow into a real product, I should start not with technologies and not even with features, but with the problem this product is going to solve.
Comments 0
to post
No comments yet. Be the first to share your thoughts.
