Canny Pricing Overview

Canny's product is simple and clean, which we appreciated. It served us well for a considerable period. The straightforward design of the platform is a significant strength, and its initial effectiveness for our business needs was commendable.

Our main gripe with Canny is its sudden and substantial change in pricing. It initially cost us $200 a month, a price we already found steep for this type of service. This amount then unexpectedly doubled, increasing our monthly expense to $400. Additionally, the cancellation process was frustrating, as it required us to contact their support team. This became more problematic when our subscription wasn't canceled as requested, resulting in us being charged again. We found this level of customer service to be underwhelming and it increased our overall dissatisfaction with the platform.

Canny was useful as it consolidated our feedback and helped us prioritize based on user votes. It boosted transparency and engagement with our users. However, the excessive pricing and poor customer service outweighed these benefits, forcing us to seek alternatives.

It has a simple UX for customers and companies. They make it easy to collect all sorts of feedback. If you need a tool to collect bug reports or any feedback in general, Canny is the place.

Sometimes the user interface can feel boxy. It is very sharp in some parts, which isn't awful but could be improved. Also, the pricing is pretty high, so it's not really a suitable tool for smaller businesses.

It helps us insure that we are providing our customers with a great experience across our platform. We are much more productive when using the platform as it helps us view all of our feedback in one place.

I like the simplicity of being able to capture feedback and categorise them, as well as link them to Jira tickets. The public page for receiving feedback, and sharing updates on roadmap with a nice, clean UI is fantastic.

The roadmap and release functionality could be a bit better. Aha Roadmaps is a bit better functionality wise, but then Canny is about simplicity so it's a delicate balance. Overall I find Canny great for managing and capturing feedback, but I don't use it for planning releases and roadmaps, as it doesn't feel as refined in that area. Perhaps this is something I should look back into again however...

To capture feedback and feature requests from customers, and have a public forum to communicate updates on those individual requests. I feel the Roadmap feature in theory is really powerful, but I have yet to find a way to integrate it better into my workflows.

I love that Canny allows you to create private or public boards for any feature! This allows users to proactively send us feedback and feel a bit exclusive having their own portal to submit and upvote on feedback.

Nothing! I wish you could add multiple owners to a feedback post, but that's about it.

We had a huge disconnect between research and product/design. There was no formal place to track feedback and make sure that these changes were being implemented within the feature. We all feel very much connected now and on the same page, especially being in very different time zones.

I like that you can tie feedback back to a user or account to see how many users/accounts it affects and tie that back to different criteria of each (like TCV, size, etc) -- I also like that clients and prospects can upvote feature requests so that we have a better idea of market demand.

I find that because feedback comes in un-uniform format that it becomes a little more work/tricky to use it's Roadmap feature. Roadmaps typically are higher level than the individual posts and the Roadmap feature on Canny can begin to look long if there isn't someone strategically managing, merging and editing the posts.

Canny allows us to solicit market feedback and feature requests in one place so that they do not get lost and can be evaluated and analyzed in one space. We also use it to keep our Sales and Account Management teams informed of what is coming soon so that they can drive conversations in the market around our product's current and future value.

We used to collect user feedback via e-mail and spend hours keeping users updated on the progress of their development requests. Canny has automated this for us, and we can now manage user feedback with less struggle and better quality. Another benefit is the release log, where we have been surprised to see how many users interact and reach out to us after reading releases.

We want to integrate canny better with our tech stack and would have appreciated the Hubspot integration as part of the growth package. The price for upgrading to business exceeds the benefits of this single add-on we want.

We communicated better with our userbase and saw massive time-savings in handling user feedback and development requests. Customers are happier and we have gotten much more positive dialog with them than ever before

Over the last month, we have been using Canny for product reviews and were very impressed with its outstanding user-friendliness. The frequency with which we have used Canny for product reviews throughout the past month has highlighted its user-friendliness. Canny exhibits an amiable design, with an intuitive interface that provides detailed feedback and is easy to use Integration with the main application is easy, if for a simple reason for one insertion. Additionally, Canny allows customization of the visual, allowing easy customization to the main application and although the auto-population feature is useful, it does not block requests which is the path of two to come. Customer support is excellent.

Being a recently established company, the pipeline has a great deal of value, and the Canny's team displays a strong sense of priorities One thing we didn't like about Canny was that what the requestor cannot obtain a summary of the requests that are sent. Users are faced with the challenge of having to manually track each request to see their sending history. Everything else is there, and the platform is proving increasingly useful.

We use Canny as a central hub for monitoring usage issues, especially in the areas of requests and error reporting. The main challenge we face in manufacturing is the volume of features required by our users. Canny addresses this by providing a system that allows users to submit and upvote feature requests. In addition to tracking deficiencies, Canny simplifies the process of identifying and solving problems. Users can effortlessly report bugs through the platform, allowing our development team to quickly replicate and address reported issues. This early exploitation of imperfections not only creates a superior product but also gives our users a sense of trust and confidence. Additionally, Canny is a powerful tool for user engagement and data collection. The user-friendly interface encourages users to actively participate in discussions about proposed features and improvements. This real-time interaction not only strengthens our relationship with our users but also provides invaluable insight into their expectations and preferences.

The option to test with a free license. We use it for internal IT-planning and for a small group of people. We do consider opening it to our customers and candidates for a broader feedback system. The ease of use makes this a pure strategic decision and not an "IT-issue".

So far I found nothing that detracts from the value created by Canny.

Internal IT planning is now structured and streamlined.