Canny

What it is

Canny is a customer-feedback platform: public or private feedback boards, feature-request voting, a roadmap, and a changelog to close the loop. Customers post ideas, upvote each other’s, and watch them move from “under review” to “shipped” — and your team gets a demand-ranked backlog instead of requests scattered across Slack, support tickets, and sales-call notes. Its Autopilot AI layer reads support and sales conversations, pulls the requests buried in them, and merges duplicates. Understand the meter before anything else: Canny charges for tracked users — the people who give feedback — not for admin seats. Your PMs sit on free seats while your user base moves the bill.

Why it shows up in Customer Success stacks

• It is the loop-closer. CS teams field “when are you going to build X” constantly. Canny links a customer to a request and auto-notifies everyone who voted the moment it ships, turning a backlog item into a retention touchpoint without a CSM writing a follow-up.
• Voting surfaces demand, not the loudest account. A deduplicated, ranked request list beats a spreadsheet of anecdotes when CS and product argue over the roadmap.
• The intake AI is unmetered on every plan, including Free. Autopilot’s feedback discovery and deduplication carry no credit counter, which is the sharp contrast with Productboard, where the equivalent analysis draws down AI credits every time it runs. Its capture surface widened through 2026: Fathom and Grain call capture on 30 July, Fireflies.ai on 11 August, and @Canny mentions inside any Slack thread on 13 August.
• Agent access sits at the paid floor. The Canny MCP server passed 55 tools on 11 June — moving ideas, creating insights, linking opportunities, managing portal comments — and it ships on Pro at $79/month rather than behind an enterprise quote.

Pricing

Canny sells three plans, and the Core tier that used to sit between Free and Pro is gone.

• Free — $0, for 25 tracked users, 5 managers, and unlimited contributors, boards, and feedback. Autopilot discovery and deduplication are included.
• Pro — from $79/month billed yearly at 100 tracked users, and it is a ladder rather than a flat price: $129 at 200, $279 at 500, $529 at 1,000, $829 at 2,500, and $1,079 at 5,000. Month-to-month runs about 25% higher — $99, $349, and $661 at the first three rungs. Adds 10 managers, API and webhooks, MCP connectors, automation rules, smart replies, custom fields, and user segmentation.
• Business — custom quote, for 5,000+ tracked users. SSO and the Salesforce/HubSpot CRM sync live here, not on Pro.

A tracked user is anyone who posts, votes, or comments, including users Autopilot discovers on your behalf. Canny’s own planning number is that 1-5% of a B2B SaaS user base becomes tracked, so model the count you expect after a launch instead of today’s. At procurement scale the published ladder stops being the number that matters: Vendr puts Canny’s median contract at $20,000/year.

Best for

B2B SaaS product and CS teams in the 5-200 employee band who want a public roadmap and a demand-ranked board live this week with no implementation project. It fits when you want customers voting in the open, the loop closed automatically, and your PM headcount off the bill.

Do not buy Canny if your core need is in-product usage analytics and guided onboarding — that is Pendo’s job, and Canny does not touch it. Pick Productboard instead when your quarter has to survive a steering committee: it gives you scored prioritization formulas, feature hierarchies, and spec drafting, where Canny gives you statuses and a vote count; the full routing rule is in the head-to-head. And if your board is public, large, and mostly consumer, price out Featurebase, the fastest-growing entrant in the segment — it charges per seat and does not meter end users at all, which inverts Canny’s entire cost curve.

Watch-outs

• Success moves the bill, and the AI is what moves it. Autopilot-discovered users count toward the tracked-user limit, and crossing a rung auto-upgrades you with a prorated charge. Switching on Fireflies and Fathom capture across a sales team can move a rung in a week. Guard: set the monthly spend limit in settings before you enable call capture — once the limit is hit, Canny stops tracking new users instead of upgrading you.
• ARR-weighted triage is a Business-tier feature. Weighting requests by account value is the reason most CS teams buy this, and the Salesforce/HubSpot sync that does it sits on Business, behind a quote at 5,000+ tracked users. Guard: do not design your triage process around CRM weighting while you are pricing Pro; on Pro, weight by segment with custom fields instead.
• A public board needs moderation, not just setup. An unmanaged board fills with duplicates and stale requests and starts to look abandoned. Guard: assign a named owner to triage weekly and lean on Autopilot’s auto-merge, but spot-check it — AI grouping mislabels edge-case requests.
• It is feedback, not delivery. Canny ranks demand; it does not manage the engineering work. Guard: wire the Linear, Jira, or GitHub two-way sync so status flows back to voters automatically, or the “shipped” loop depends on someone remembering to update Canny by hand.

For the CS platforms that consume this demand signal alongside health scores see Gainsight, Vitally, and ChurnZero.