sonio
It's just more simple to filter. Therefore, a feedback item with 10 upvotes can have an impact score of 40, while a feedback with 100 upvotes can have an impact score of 3.
I am totally with you when you say that there is a chance that feature voting will backfire for the whole process. It depends on how you use it.
1. You shouldn't rely on up- and downvotes for feature priorisazion for example. Like I did for "impact scoring" at Sleekplan you could use factors like interaction of users, time staying on an item.
2. You shouldn't ask for solutions or features, You should ask for problems, issues missing functionalities and then collaborate (e.g. in the comments) to find a good solution that's satisfying everyone.
I currently writing a best practice (from my point of view) for the Sleekplan docs.
But having been in this orbit for some time I think that's simply a function of how teams want to handle feedback requests since everyone's needs are a little different.
I think a limit on functionality would not go over so well since you have to pay for it and then getting limited by tracked user plus functionality.
You're absolutely right. I have spent a lot of time thinking about pricing. Here is one of my calculations: https://i.imgur.com/sB4CuAf.png I just wanted to give some kind of "discount" for more usage. The higher the number of tracked users, the lower the price will be in the end. In general you can think of a per tricked user pricing.
Prio support is just a "nice to have" addition
Show HN: I made an embeddable user feedback tool – free for open source
Hi HN,After I finished my thesis on feedback management for SaaS at the end of last year, I thought it was time to do something hands-on that topic. Since I like the idea of such feedback tools, that lets you collaborate with users to find solutions together - instead of having a separated feedback from each user - this became my starting point. I also like the approach of the chat widgets as...