HN Explorer

6 comments

[ 3.5 ms ] story [ 19.6 ms ] thread
cranberryturkey
too expensive to even test it out tbh
wa5ina
Thanks for the feedback! my justification for the pricing, are backed by the fact that once you purchase a package, you get lifetime access to the problems database, which updates in real time. specifically, we have a cron job that mines data every hour for 24h, which is free but (at least for now), but LLM processing isn’t, so the justification is that u get continuous value after u made one purchase, and your credits are only used for generating reports. u can always add more credits as needed. I’m curious though, does this make sense to you? If not, what price point would feel fair or approachable for testing it out?
cranberryturkey
I know AI isn't free. I just want to see an example or something first before I sign up.

Maybe setup a demo account or something with an example of what we'd get.

wa5ina
on point, this should in the roadmap
codingdave
What is a "validated problem"? Is it just something an LLM gleaned from online content, or did someone verify that the people having the problem would actually pay for a solution, and aren't just venting frustration online? Also, do the reports track when problems were identified and seek out whether solutions have been created since the complaints arose?
wa5ina
> “What is validated problem"?

The way I see it at least is, a validated problem is one that enough people face, frequent and cause a certain level of frustration, currently each problem in broblems have a “frustration level” extracted from language used which serve “problem” and “frustration level”, but “enough people” is not yet in the equation, it’s something i wanted so badly to add, but decided not to in MVP, is to aggregate group of people that faces the same problem, and be able to browse and analyse that in a centralised location , i think that’s valuable , and i see me using that feature frequently, will try to add this feature asap. but what in ur opinion is a “validated problem”.

> “did someone verify that the people having the problem would actually pay for a solution,” ?

Great question, my simple way currently is that each problem have a "context score" that decide to what level this problem is a “productizable problem”, "renting about an analytics tool" have a higher context score while "existential rent about existence" have a lower one, this is simply done by prompting the LLM, only things that above 8 are considered actionable problems.

> “do the reports track when problems were identified and seek out whether solutions have been created since the complaints arose”

the dive-in reports currently show existing players in the space, but i don’t yet track problem timelines or follow up on whether solutions have been created since. sounds like a solid idea, but i guess it’s a bit beyond the scope of this initial version.