Frill is a SaaS tool for Customer Feedback, Roadmaps and Announcements, from the small company of the same name headquartered in New South Wales.
N/A
productboard
Score 6.6 out of 10
N/A
productboard, from the company of the same name in San Francisco, is a product management system designed to help product managers understand what users need, prioritize what to build, and rally everyone around a roadmap.
Frill is well suited for beginner or mid-level startups looking to get customer feedback on their products. If a business has a really well-suited product pipeline filled with features and is confused which one to build first, Frill is a really nice platform/product to have. You can get direct customer feedback and you can finally work on things that matter the most. It is less appropriate for someone who doesn't have a big product feature pipeline or roadmap in their mind.
The best feature of productboard is organized features, it has a very simple structure and can be read and understood by anyone. If your roadmap is very dynamic and the executive team needs to be on top of it, productboard is the best application out there. But if you have a small product and features do not change very often, then maybe you can look at other alternatives since productboard is expensive.
I have previously used Aha another product road mapping/ insights driven software. Aha had great features for the userbase of my previous products. They were allowed to create their own suggestions for the products and other users could then like or dislike the suggestion. This created a real reflection on need for product enhancements. productboard handles this slightly differently. Each user creates their own suggestions and doesn't necessarily have visibility on other users suggestions. The product/ R&D team can then tag suggestions together into the same overall suggestion. This requires more input from product/R&D with productboard. I would however, suggest that productboard is better than Aha. Aha is great for an external user point of view; however, there may be case for users to not have visibility on wider user requirements. productboard keeps more of this element hidden and would perhaps stir up less negative correlation to seeing a system requirement/suggest having had a lot of traffic and no action, compared to a more closed system that would individually update each user on the enhancement progress.
