Canny

Canny is the customer feedback management platform built for product teams, founded in 2017 by Andrew Rasmussen and Sarah Hum as a bootstrapped side project that became one of the most-recommended SaaS tools for product feedback workflows. The pitch is direct: customer feedback is one of the highest-leverage inputs for product decisions, but most teams collect it in scattered Slack/email/calls/Twitter where it gets lost. Canny captures, organises, and prioritises feedback into a structured public + private board your team can actually act on. What makes Canny different from generic product management tools is the customer-facing + voting + transparency philosophy. Canny boards can be public — your users see all feedback, vote on what matters to them, and watch you ship roadmap items. This transparency creates a feedback loop competitors miss: users feel heard + invested, product teams get prioritisation signal from actual users (not just internal opinions), and shipped features have built-in advocates. For SaaS startups + product teams wanting to systematise feedback, Canny is the category default. The core features: • **Feedback boards** — public + private boards organising feedback by category/topic • **Voting** — users upvote feedback they care about; signal for prioritisation • **Comments + discussion** — users + team can discuss requests in detail • **Roadmap** — public + private roadmaps showing planned/in-progress/shipped items • **Changelog** — public changelog announcing shipped features • **Custom domain** — host Canny on yourcompany.com/feedback for branding • **Custom theming** — match Canny's visual style to your brand • **Single sign-on (SSO)** — let users authenticate via your existing auth • **User segmentation** — segment by plan, role, custom attributes (MRR, NPS score, etc.) • **Customer insights** — see which customers requested + voted for each item • **Roadmap announcements** — automatic notifications when feedback ships • **Integrations** — Intercom, Zendesk, Slack, Linear, Jira, Asana, GitHub, Salesforce, HubSpot, Segment • **AI features (recent)** — auto-categorisation, duplicate detection, sentiment analysis • **API + webhooks** — for custom workflows and integrations • **Private posts** — for sensitive enterprise feedback or feature requests • **Email digests + notifications** — keep users + team informed For product teams + founders + customer success the use cases: • **SaaS product feedback collection** — replace scattered Slack/email/calls with structured board • **Public roadmap transparency** — show customers + prospects what's coming • **Feature prioritisation signal** — let user votes inform roadmap decisions • **Customer-facing changelog** — communicate updates to users systematically • **Enterprise customer requests** — track + respond to high-value customer asks • **Bug tracking with user context** — internal bug reports tied to specific users for follow-up • **Beta program feedback** — gather structured feedback during beta phases • **Product team alignment** — single source of truth for what users want • **Customer success workflows** — CS teams capture feedback during calls; sync to Canny The pricing scales by users + features. Free tier covers 100 tracked users + 1 board + basic features — useful for evaluation but limiting for active SaaS. Starter at $79/month covers 1,000 users + 3 boards + integrations + custom domain. Growth at $359/month covers 10,000 users + unlimited boards + advanced features (AI, segmentation, SSO). Business at $999/month for large customer bases. Pricing has increased meaningfully over the years which has caused some controversy in indie community. Where Canny wins clearly: it's the category default for SaaS feedback management — most peer SaaS founders use Canny; the public board + voting + transparency philosophy creates genuine user engagement loops; the integrations (Intercom, Linear, Jira, GitHub) mean feedback flows into your existing tools; the roadmap + changelog features make customer communication systematic; the AI features (duplicate detection, sentiment) save real time at scale. Where it loses: pricing has scaled meaningfully ($79-$999/month) — feels expensive vs free alternatives (Nolt, FeatureBase) for indie + early-stage SaaS; the public board approach doesn't fit all products (security-sensitive industries, B2B sales-focused products); some founders prefer simpler Notion-based feedback boards for early stages; the voting mechanism can become a popularity contest disconnected from strategic priorities. My take: for funded SaaS startups (Series A+) with active customer bases who want to systematise feedback management — Canny is the right call and pays for itself by reducing scattered feedback collection. The category default status means integrations + community knowledge + best practices are well-documented. For indie + bootstrap startups under $10K MRR, free alternatives (Nolt, FeatureBase, or even a Notion database with Tally form input) cover most needs at a fraction of the cost. The transition usually makes sense around the time customer feedback volume exceeds what 1-2 people can mentally track — typically Series A or earlier for product-led companies. Worth evaluating Canny + a few free alternatives during your switching moment to find the right fit.