Why I Killed Niriv to Build Niguro

For years I ran a platform called Niriv. It did thirteen things. News, jobs, classifieds, tools, directories, a little of everything a Nepali internet user might need in a day. One morning I sat down and deleted twelve of them. Then I renamed what was left and called it Niguro.

People ask me why I killed something I spent years building. The honest answer is that keeping it alive was the thing that was killing my work.

What Niriv was

Niriv started with a big, generous idea: Nepal deserved its own internet platform, not a patchwork of foreign apps that half worked here. So I built one service, then another, then another. Each one made sense on its own. Together they became thirteen services under one roof.

I told myself this was ambition. A Nepali super app. One login, everything you need. It sounded good in my head and it sounded good when I explained it to people. Nobody ever told me it was a bad idea, which should have been my first warning. People rarely argue with a founder’s dream to his face.

The quiet years went into it. Design, code, fixes, relaunches. Thirteen front doors to maintain, thirteen back ends to keep from breaking, thirteen small piles of complaints.

Thirteen services, zero identity

Here is the question that ended Niriv: what is it for?

I could not answer that in one sentence. Not really. I had thirteen answers, one per service, and none of them were good. When I tried to explain Niriv to someone new, I watched their eyes glaze over by service number three. A product you cannot explain is a product nobody can recommend to a friend.

Every service was shallow, because my attention was split thirteen ways. Each one got a thirteenth of my time, a thirteenth of my care, a thirteenth of my thinking. Users could feel it. The front door promised everything and delivered a menu. People came, clicked around, and left, because nothing was deep enough to become a habit.

Maintenance ate building. Most weeks I was not improving anything. I was keeping thirteen plates spinning: a bug here, a broken integration there, a server bill that kept growing while no single service earned its keep. I was busy every day and going nowhere.

The question I kept avoiding

Founders love to add. Adding feels like progress. A new service is a press release, a launch, a small dopamine hit. Choosing feels like loss. Choosing means saying no to twelve good ideas, and saying no does not photograph well.

But breadth was not strategy. It was fear of choosing. Every new service was a way to avoid the hard question: which one of these actually matters? I kept the question at bay by staying busy. Busy is the best hiding place a founder has.

The usage pattern was obvious to anyone who looked honestly, and I had stopped looking honestly. A couple of services got the repeat visits. The rest were rooms I kept cleaning for guests who never came. I knew this. I knew it for a long time before I acted on it.

Knowing and doing are different muscles. I had to train the second one.

The kill list

Killing Niriv did not happen in one dramatic night. It happened service by service, and each one hurt a little.

I started with the ones nobody would miss. The tools with single digit weekly users. The directory nobody had updated in a year. Each shutdown was small and unremarkable, and each one gave me back a slice of my week. That was the first surprise: deleting things felt like getting a raise.

Then came the harder ones. Services with real users, small but loyal. I wrote to them plainly, told them what was shutting down and when, and pointed them to alternatives. Almost nobody was angry. That was the second surprise. I had imagined an uproar. What I got was a shrug. The uproar had been in my head, and it had been keeping thirteen services alive.

The last cut was the name itself. Niriv had been my identity as a builder for years. Letting go of the name felt like admitting the years were wasted. They were not wasted. They were tuition. But you do not frame a tuition receipt and hang it on the wall. You pay it, learn, and move on.

If you have never killed a product you built, here is what it actually feels like: grief, then relief, then energy. In that order. Do not skip the grief. It is the receipt that proves you cared.

Why search and news

When twelve services were gone, the choice that remained was almost embarrassingly clear. Search and news. The two things Nepali internet users do every single day, and the two lanes I actually understood.

Nepal had no native search engine. Every Nepali searching in Nepali was renting space on someone else’s index, built for someone else’s language and someone else’s advertisers. And news was the lane I knew in my bones. I had run Scriling since 2019. I knew what it took to go from 50,000 rupees a month in early 2021 to a peak of 13,000 US dollars a month, all from advertising, on one lane: news. One lane, done deeply, had already paid for everything the thirteen lanes never could.

So Niriv became Niguro. Nepal’s own search engine and news portal. Launched on the first day of 2026. One thing to explain, one thing to improve, one thing to be known for.

Notice what I did not do: I did not bolt new ideas onto Niguro afterward. When I built Sisnoo, the news aggregator, I gave it its own home at sisnoo.com instead of making it service number fourteen. Focus is not a one time decision. It is a habit of saying no, repeated forever.

What changed after the cut

Everything got simpler, and simple compounds.

One product means one roadmap. Every hour I work goes into the same pile instead of thirteen thin ones. Bugs get fixed instead of triaged. Features get finished instead of started. I can hold the whole product in my head, which means I can actually think about it instead of just maintaining it.

One product means one story. When someone asks what Niguro is, I say it in one sentence: Nepal’s own search engine and news portal. No glaze. Sometimes they argue with the sentence, which is wonderful. You cannot argue with a menu.

One product means honest numbers. There is nowhere to hide a failing service behind a successful one. If the numbers are bad, they are bad, and I know exactly where to work. That clarity is uncomfortable and it is the whole point.

Five signs it is time to kill your own product

If you are running something broad and feeling the same slow drag I felt, check yourself against these five signs. Two or more means you have a Niriv on your hands.

You cannot explain it in one sentence. If your explanation needs the word “and” more than once, you do not have a product. You have a portfolio. Portfolios are for investors, not users.
You dread your own dashboard. When opening your analytics feels like opening a bill, it is because some part of what you built is a bill. A cost with no return. Founders avoid the dashboard for the same reason people avoid the weighing scale.
Maintenance eats more than half your building time. Keeping the lights on is not building. If most of your week goes to thirteen small fires, you are a firefighter with a founder title. Count your hours for two weeks. The number will not lie even if you do.
Your best feature lives inside your worst product. This was my clearest signal. The search box people actually used was buried inside a platform nobody could describe. Great features die inside confusing products. Set the feature free.
You keep adding instead of choosing. Every new feature is a vote to avoid the decision. If your roadmap is all additions and no subtractions, you are not strategizing. You are decorating.

Killing is building

We celebrate launches and we whisper about shutdowns, as if ending something were the opposite of building. It is not. Subtraction is the most underrated product skill there is.

Every service I killed gave me back time, attention, and clarity. Those three things built Niguro. The thirteen services did not fail all at once in some dramatic collapse. They faded, one honest decision at a time, and what grew in the cleared ground was the one thing worth building.

If you are holding onto a product out of loyalty to the years you spent on it, hear this from someone who did it: the years are not wasted if you learned. They are only wasted if you let them chain you to a menu nobody ordered from.

Kill the menu. Build the one dish.