Akshay

After launching RunEvr, we started getting a lot of offers related to blog post creation.

But we had already designed our own blog mechanism earlier, even before the launch.

We re working on this ourselves right now. We even built our own CMS to make it easy to create, review, and publish posts directly to our blog.

But one thing is important to us: the blog belongs to us.

I've been on Product Hunt a lot lately, mostly trying free tiers of stuff that launches here, and it's made me realize our whole team's subscription list is a mess.
I run a small 5-person team doing marketing and reporting for a few client accounts. Half our stack is stuff I actually found on PH over the years, some free, some paid, picked up whenever something looked useful at the time and never really reviewed since.
Went through it recently and found we're paying for at least 2 tools nobody's touched in months, tools I remember being excited about on their launch day here, while some of our free tools are quietly hitting real limits every week.
So I've been trying to change how I evaluate PH launches specifically. Instead of signing up the moment something looks good in the comments, I wait and actually watch usage. If a free tool hits its limit consistently for a few weeks, that's a real signal to upgrade. If something I signed up for during a launch goes untouched for a month, that's a signal to cut it.
How do you approach this?
When you find a tool here that you use regularly, what makes you decide to pay for it?
Do you track usage limits directly?
Do you run a periodic audit of everything you've signed up for from PH launches?
Do you just wait until something breaks or gets annoying enough?
Or something else entirely?
What's the ONE thing that convinces you: "yeah, this is worth paying for" versus "this one's getting cut," especially for stuff you find here versus tools you already knew about?
Would love to hear how other PH regulars handle this.

For me, it's usually Downloads.

Thousands of screenshots, random PDFs, ZIP files, invoices, images, and files named things like:

final_v2_FINAL_really_final.pdf