For twelve months, I worked on my first product almost every day.

    It was a tool meant to help people move more during desk work. I believed in it because I needed it myself. I refined the flows, improved the reminders, redesigned parts of the interface more times than I want to admit, and kept adding features that I thought would make it more complete.

    I worked on it early in the morning before my job and late at night after my family went to bed. From the outside, it probably looked like discipline. I was consistent. I was shipping. I was improving things constantly.

    But the truth is that I was building in silence.

    People signed up. Some told me it was a good idea. A few tried it briefly. But nobody was asking for specific improvements. Nobody was pushing me for features. Nobody was waiting for updates.

    And nobody paid.

    After twelve months, the revenue was €0.

    What hurt was not just the number. It was the realization that I had spent an entire year building based on my own assumptions. Every feature felt logical to me. I had reasons for all of it. The problem was that those reasons lived only in my head.

    I had a roadmap for that product, but it was my roadmap. It was basically a structured list of guesses.

    At some point, I had to admit that I did not have a feedback problem. I had a visibility problem. I had no real way of seeing what people actually cared about before I built it.

    That frustration led me to build something else.

    Not another feature for the first product, but a tool I personally needed: a way to make a roadmap public, to let users submit ideas, to let them upvote what mattered to them, and to create real signal before writing code.

    I built that after the twelve months of silence.

    Ironically, the second product took a fraction of the time. And it generated revenue.

    Not because I suddenly became better at marketing or more disciplined. I was already disciplined. The difference was that I stopped deciding alone.

    What surprised me most was how wrong I had been about priorities. Features I thought were essential barely received attention. Ideas I would have postponed quickly rose to the top when users could vote.

    That shift changed how I think about building.

    The first product failed financially, but it exposed the flaw in how I was making decisions. The second product exists because the first one forced me to confront that I was guessing in isolation.

    I am still trying to figure out how to consistently build with real pull instead of self-generated momentum.

    Curious how others realize they are building in silence before a year goes by.

    I spent 12 months building something no one paid for
    byu/d_uk3 inEntrepreneur



    Posted by d_uk3

    7 Comments

    1. No_Boysenberry_6827 on

      the 12 months of silence thing hits hard because I lived it

      built a product with 8M lines of code in 63 days. talked to 100+ potential customers. technically it was insane. but I couldn’t scale it because I had zero sales infrastructure. the product was ready – distribution wasn’t.

      the painful realization was that building and selling are completely different skill sets and most of us are only good at one. the founders who win aren’t the best builders. they’re the ones who figure out distribution before they finish building.

      second time around I literally built the sales engine before the product was complete. revenue showed up in weeks instead of months. same builder, same work ethic – completely different outcome because the selling started day 1.

      the question that changed everything for me: “would anyone be upset if this didn’t exist tomorrow?” if the answer is no, you don’t have a product – you have a project.

      what are you building now? and more importantly – are people already asking for it?

    2. Budget-Scheme-4927 on

      Building in silence, is exactly it. You weren’t undisciplined, you were just solving a problem nobody confirmed they had! The part that gets me is most people don’t even question the idea itself. They just start building. The ones who spend time first understanding what’s actually broken in a space they know deeply, they seem to have a completely different experience!

    3. AffectionateRow3173 on

      Hey man! I’m really understand you !it’s very hard to believe that app you have developed no one need it. We all go through it. You need to change a your strategy – Validate an idea first before build it

    4. Minute-Line2712 on

      You have to verify things first before building. You build after observing real life situations and real life people interacting with things or products or whatever it is. When you know you know.

      If you don’t know… Then you should think how to verify this before building. It’s good to self support and self drive, but reasonably … Not every idea you have will truly be good unless you’ve seen it. Take a more scientific approach to it is all I can say

      And, learn to pivot as necessary quickly. Don’t spend so long building. Most things are not that complicated. Most services and products can be set up fairly easily in less than 3 months. By month 3 you need to be getting some movement.

      At the minimum a landing page with clear demonstrated interest by people, whether its views or signups or pre orders or some kind of MVP. That’s the more practical answer.

    5. Chupacabra1987 on

      Best advice in life is, always try to get feedback whatever you do. People will help you or you ask questions.

    Leave A Reply
    Share via