
Niched
Niched remembers why you chose a tool and track what changes
Do you remember why you chose the tools you use every day? I just realizef I don't. Picked figma three years ago, price went up twice, killed a feature I loved, and I have no idea if it's still the right call.
Built Niched because I couldn't find anything that actually answered this. Launched it on PH and HN a few weeks back, and I've been asking people on X and Reddit what changes actually matter to them but all I got was silence. Either I'm asking the wrong question, or people genuinely don't think about this stuff.
So I'm asking here, because I know this crowd actually builds and uses tools When something in your stack changes, how do you even know? And when you find out, what do you actually check before deciding to switch?
Niched watches for the changes (pricing, repo quiet, licence flips) and ties them back to why you picked the thing in the first place. Still rough, but I think it's onto something. More interested in hearing if you've felt this same gap than in you trying the product.
Posted about Niched on X and reddit last week. Got two solid responses: people said they wanted to search the tool from the homepage, and they wanted to see if others found a tool useful before diving in.
So I added both. Searchable from the homepage now, and there's a comments/upvote section on each tool page so you can see what actually matters to people using it. Also shipped changelog tracking so you can see what's changed since you picked it.
Still early, still learning what moves the needle. But at least this time I'm not guessing you told me what was missing.
Would love to hear if these actually help or if there's something else that's still off.
Like
Comment
About
I kept watching people pick a tool, get it working, and then stop looking at it. Months later something changes, a price, a licence, a repo going quiet, and nobody remembers why they picked it in the first place.

3 Comments
The part that stands out is the gap between tracking changes and helping someone decide what to do about them. Pricing or a licence change is easy to detect; knowing when it actually justifies switching is much harder. I’d be curious whether users see that decision layer as valuable enough to come back to regularly.
That's exactly the hard part. Detecting "price went up 30%" is easy, but knowing if it actually justifies switching is where most people give up. That's why Niched ties the change back to why you picked it in the first place. If you chose it for speed and the change is just pricing, you already know it doesn't matter. But if they killed the feature you actually needed, now you need to think.
The real question is whether people actually come back to use that layer or if they just tolerate their tools and accept whatever changes come. You might be right that most people don't want to make those decisions at all. When something does change in your stack, do you ever actually investigate it, or does it just become "well, I'm already using it so might as well keep paying"?
Honestly, I think that’s the more interesting question — whether people actually act when the signal appears. I’ve seen pretty different behavior depending on the tool and the cost of switching. What are you seeing so far from Niched users?