My Failed Products Paid for Niguro
Founders love to talk about what worked. Scriling News went from zero to 13,000 USD a month at its peak, and I will talk about that all day if you let me. But the successes were maybe a third of what I built. The rest failed, quietly, and those quiet failures are the reason Niguro exists at all.
I keep a mental list of everything I built that did not work. YukeshMedia in 2018. The Kirib. Manoble. A handful of smaller experiments I do not even name anymore. None of them made money. Each one of them taught me something I still use.
This is the list, and the honest accounting of what each failure cost and what it paid.
Failure one: YukeshMedia (2018)
YukeshMedia was my first venture, a media and advertising initiative I started right after finishing my programming programme. My plan, to the extent I had one, was simple: build a website, publish content, and the advertisers would come.
The advertisers did not come. That is the entire story of the business, and it taught me the first lesson every builder in Nepal eventually learns the hard way: the market here does not behave the way the global playbooks say it does. Advertisers buy relationships, not impressions. A media business without distribution is just a website with opinions. I wrote more about this in my playbook for starting a news website in Nepal (link: https://www.yukesh.com.np/start-news-website-nepal/), because the lesson kept repeating itself for years.
What the failure cost me was a year of effort and some money I could barely afford to lose. What it paid me was my first real understanding of how Nepali audiences actually move online. That understanding is still doing work for me today, inside Niguro’s news and search products.
Failure two: The Kirib
After YukeshMedia, I tried The Kirib, a media platform aimed at Gen Z. On paper it made sense. Young people were the most active online audience in Nepal, short attention spans, new formats, a lane that nobody was really owning.
It did not work. I do not dress this up, because there is no glamorous lesson in it. The honest version is that I built something for an audience I understood in theory but not in practice. I knew what young Nepalis clicked on. I did not know what they would come back to, day after day, and that is the only question that matters for a media product.
The Kirib taught me the difference between attention and habit. Attention is what gets you a traffic spike. Habit is what gets you a business. I had been chasing attention since YukeshMedia, and it took a failed Gen Z platform to make me see that attention without habit is just a sugar rush. Scriling, which I was running in parallel, worked precisely because it built habit: people came back every day to see what was new. The Kirib never got there.
Failure three: Manoble
Manoble was not a product that failed. It was a partnership that failed, which in some ways is worse, because a bad product just costs you time. A bad partnership costs you time, trust, and the willingness to try the next thing.
I do not talk about the details, because the details were specific to the people and they do not generalize. What generalizes is the lesson: a partnership fails when the two sides want different things and neither says so out loud. Misaligned expectations do not get better with time. They get more expensive.
After Manoble, I made a rule for myself that I have kept ever since. Before starting anything with anyone, I write down what each side expects, what each side is putting in, and what happens if it does not work. It takes an hour. It has saved me from at least three bad deals since. The most important skill in a partnership is not trust, it is clarity. Trust without clarity is just optimism with a signature.
The three ways things fail
After enough failures, you start to see the patterns. In my experience, products fail for three reasons, and knowing which one killed yours matters, because each one asks a different question of you.
First, wrong timing. The Kirib was probably this. The audience existed, the idea was not crazy, but I was early in my understanding and the market was early in its habits. Timing failures are the kindest kind, because they tell you to come back later, smarter. Niguro is, in a sense, a timing answer to questions I was asking as far back as 2018.
Second, wrong partnership. Manoble. The idea can be fine and the execution can be fine and the whole thing still dies because the people building it are pulling in different directions. These failures teach you about selection: choose people slowly, align on the boring stuff first.
Third, the wrong version of you. Some things fail because you are not yet the person who can make them work. This is the hardest one to admit, because it feels like an excuse, but it is usually the truth. The Kirib needed a founder who lived inside Gen Z culture. I was adjacent to it, not inside it. Admitting that is not self-doubt, it is data.
What failure actually costs
Here is what nobody tells you about failing at small products in Nepal: it is cheap, and that is the point.
None of my failures involved investor money, because I never raised any. They cost time, small amounts of cash, and pride. Because the bets were small, I could afford to place several of them, and because I could place several of them, I learned fast. This is the part of my story that contradicts the startup mythology: I did not bet big and win. I bet small and lost repeatedly, and the losses compounded into competence.
I have written about how I decide what to build next (link: https://www.yukesh.com.np/decide-what-to-build-next/), and the killing rule lives inside that process. A small bet that fails is tuition. A big bet that fails is a funeral. The skill is keeping your experiments small enough that the failures teach instead of bury.
How I decide to kill something
People ask when to quit a product, and I have a practical answer now, earned the hard way.
First, I ask whether the failure is in the product or in me. If it is a timing or skill problem, I can fix it or wait. If the market genuinely does not want the thing, no amount of effort fixes that.
Second, I ask what it is teaching me. If a failing project is still generating new information, it is still worth running. The day it starts repeating the same lesson is the day I kill it. The Kirib kept teaching me about habit until it did not. Then I shut it down.
Third, I protect the quiet project. While the public experiments were failing, I was building Niriv in the background, slowly, with no launch pressure. That quiet project eventually became Niguro. My failures never touched it, because I never let a failing experiment borrow resources from the thing that mattered most. Keep one quiet project running at all times, funded by the work that pays the bills, and never let a loud failure kill it.
The accounting
So here is the final accounting of my failed products, the honest version.
YukeshMedia cost me a year and taught me how Nepal’s audience actually behaves. The Kirib cost me months and taught me that habit matters more than attention. Manoble cost me trust and taught me that partnerships run on clarity, not chemistry.
Total cost: a few years, some money, some pride. Total return: every lesson Niguro is built on.
Most founders present their history as a straight line of wins. Mine is a list of things that did not work, with one thing at the end that does. If you are staring at a failed product of your own right now, here is what I would tell you: fold it honestly, write down what it taught you in one paragraph, and make sure the next thing you build uses at least one sentence from that paragraph.
The failures were not detours. They were the tuition. Niguro is what I bought with it.
If you want the full timeline, I told the three-company version here (link: https://www.yukesh.com.np/three-companies-before-niguro/).