Early-stage startup discount, cheap plan, or free tier | Feature Requests

Early-stage startup discount, cheap plan, or free tier

Gray Clownfish

I know you guys offer a 14 day free trial, but a cheaper or free hobbyist tier with some QOL features cut would be great.
I really like this project, but I can't justify spending $50 a month as a hobbyist.
I suppose your target demographic is probably businesses, rather than individuals or small teams.

Healthy Hookworm

Andrew Rasmussen This would also be of great value for me as well. I am in the early MVP stage and would greatly value an affordable tier. I use Canny through clickup religiously and really think the same workflow would drastically improve the speed that I can get features to my customers. Thanks

Ivory Bobolink

I also found out about Canny from an OSS project (react-navigation) and was hoping to use it for my own project (ember-cli-mirage).

Canny seems like a great alternative to using github issues for project management. Using it on my OSS projects would help me understand how it works & how valuable it is, and I could then see advocating for it on private projects and consulting gigs (similar to how Github/heroku/etc. work).

Andrew Rasmussen

Hey Sam! Thanks for chiming in here -- I just shot you an email.

Andrew Rasmussen

Merged in a post:

Make Canny more affordable

Ivory Orangutan

$50/mo/100 users is ~~$2~~ $0.50/mo/person who upvotes a feature request. 😑
I'm not saying make it dirt cheap. I understand a majority of users won't use a product, but this really hurts MVPs (who are usually poor and really need user feedback).
Maybe a free tier of 50 users? Or just decrease the price a little. Canny looks great and I'd love to use it.

Andrew Rasmussen

Hey Cory, thanks for taking the time to leave feedback on our pricing. The vast majority of people don't tell us what they think about our pricing, so this is particularly valuable.
I definitely understand that $50/mo can be a lot for people who are just getting started. We would love to support more of these products.
The reason we chose not to, is because we're an early-stage startup ourselves, and we have to make sure we have product-market fit. Do people really need what we're building? Someone using Canny for free / cheap isn't as strong of signal as someone using it for $50/mo+.
Things are going pretty well, so there's a good chance we'll introduce a free tier with our next pricing model.
In the meantime, we do offer some discounts to qualified early-stage startups, non-profits, and open source projects (including react-native-firebase). We don't advertise this publicly (yet), so reach out via live chat and we'll set you up.
Also $50/mo for 100 users is $0.50/user, not $2/user. This pricing is targeted as SaaS companies, where you're talking about 100 customers/prospects, so feedback is quite valuable for driving your business.
Finally, Sarah just wrote a great blog post on our journey through pricing Canny, and you can read it here: https://blog.canny.io/saas-pricing-lessons/

Ivory Orangutan

Andrew Rasmussen: "Also $50/mo for 100 users is $0.50/user, not $2/user." How to math? XD
Thanks for the quick response. Talking to my client now about using your service (your design is on point).
re: the blog post. The only fair pricing model is an autoscaling one. Price per event maybe.
I would have no problem paying $1 feature request/upvote/comment, but paying $0.50/mo/user when 99% of them could be completely inactive is brutal.
Anyway, excited to hear about the OSS stuff. Hope to see you guys on every GitHub README soon! :D

Ivory Orangutan

Another thought: make it free for OSS projects. This is just good marketing.
Example: the only reason I ever heard of Canny is from https://github.com/invertase/react-native-firebase now I'm considering spending $50/mo on it for an app I'm building.
Many
 services do this (TravisCI, etc.).

Andrew Rasmussen

Hey Dylan, thanks for the feedback on our pricing. I sent you an email. 🙂
We've toyed with the idea of introducing a free/hobbyist tier. We'd need to make sure that there are feature/user limits such that it wouldn't work for teams.
Will probably do something official next year, but may be able to make something else work in the meantime.