Canny vs Featurebase

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Canny✓fullprobed9/10

   A direct probe confirms llms.txt exists and returns 200 with developer documentation content at developers.canny.io/llms.txt, and Canny also publishes agent-oriented docs (MCP server docs, API reference) explicitly designed for LLM/agent consumption. Missing for 10: independent third-party confirmation that agents successfully consume this llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.canny.io/llms.txt # Canny Developer Documentation > Developer resources for integrating with…”
   • [claimed-docs] “Install Docs | Canny”
   • [claimed-docs] “Canny API Reference”
   • [probe] “official MCP server documented at https://canny.io/features/mcp”

   proof ↗⚑ flag

   Featurebase✓fullprobed9/10

   A direct probe confirms Featurebase serves a valid llms.txt at https://developers.featurebase.app/llms.txt returning HTTP 200 with structured docs links, which is exactly what an AI agent would need to consume agent-oriented documentation. missing for 10: no independent third-party corroboration of agent usage beyond the probe itself.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.featurebase.app/llms.txt # Featurebase ## Docs - [featurebase-js](/guides/featurebase-js/in…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Featurebase
   Canny~partialprobed3/10

   Canny exposes a REST API reference and API-driven install/SDK docs, which implies some programmatic/automatable access, but there is no explicit documentation of CI usage, a CLI, or headless automation workflows; the MCP server is described as requiring interactive secure sign-in rather than API-key/CI-friendly auth. missing for 10: explicit CI/headless usage examples, CLI or scriptable automation docs, non-interactive auth for MCP/API use in pipelines.

   • [claimed-docs] “Canny API Reference”
   • [claimed-docs] “Add Canny's MCP server to ChatGPT, Claude, or Cursor with a secure sign-in. No API keys, no engineering.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.canny.io/openapi.json, https://developers.canny.io/swagger.json, https://develope…”

   proof ↗⚑ flag

   Featurebase~partialprobed4/10

   Featurebase exposes an HTTP API reference, a JS SDK, and webhooks that could in principle be scripted from CI/automation pipelines, but there is no explicit documentation, CLI, or example of running Featurebase headlessly in CI, and the OpenAPI spec itself is not discoverable at expected endpoints. Missing for 10: explicit CI/headless usage guide, discoverable OpenAPI/machine-readable spec, and a CLI or automation-first workflow example.

   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”
   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.featurebase.app/llms.txt # Featurebase ## Docs - [featurebase-js](/guides/featurebase-js/in…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.featurebase.app/openapi.json, https://developers.featurebase.app/swagger.json, ht…”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Canny—none0/10

   All evidence shows Canny exposes an MCP *server* that external AI tools (ChatGPT, Claude, Cursor) connect to — the reverse direction. There is no evidence that Canny itself acts as an MCP client that plugs in external MCP servers to use their tools.

   • [claimed-docs] “Add Canny's MCP server to ChatGPT, Claude, or Cursor with a secure sign-in. No API keys, no engineering.”
   • [claimed-docs] “Connect Canny to ChatGPT, Claude, and Cursor. Ask questions about customer feedback, take action on it, and ground your AI workflows in real…”
   • [claimed-docs] “Canny MCP Server: Customer Feedback in Your AI Tools”
   • [probe] “official MCP server documented at https://canny.io/features/mcp”

   proof ↗⚑ flag

   Featurebase—none0/10

   No evidence Featurebase supports MCP server integration as a client to consume external tools; evidence only covers webhooks, integrations, changelog, AI answers, and Fibi agent features, none of which mention MCP.

   ⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Canny
   Canny✓fullprobed8/10

   Canny documents an official MCP server that connects to ChatGPT, Claude, and Cursor via secure sign-in (no API keys), enabling agents to query feedback data and take actions like updating statuses and replying to customers. Missing for 10: independent/hands-on third-party corroboration beyond vendor docs.

   • [claimed-docs] “Add Canny's MCP server to ChatGPT, Claude, or Cursor with a secure sign-in. No API keys, no engineering.”
   • [claimed-docs] “Ask your LLM what customers asked for and understand the context behind each request. Dig into top themes, ARR impact across ideas, and quer…”
   • [claimed-docs] “Move ideas through your workflow without leaving your LLM. Update statuses, link deals, organize requests, and reply to customers.”
   • [claimed-docs] “Connect Canny to ChatGPT, Claude, and Cursor. Ask questions about customer feedback, take action on it, and ground your AI workflows in real…”
   • [claimed-docs] “Use Canny as the data layer for your AI workflows. Draft PRDs from real requests and build the features with Claude, generate reports for le…”
   • [probe] “official MCP server documented at https://canny.io/features/mcp”

   proof ↗⚑ flag

   Featurebase—none0/10

   Featurebase is a feedback/changelog SaaS platform (not an agent), so publishing an official MCP server is a plausible axis, but no evidence mentions an MCP server anywhere—only webhooks, API/SDK reference, and integrations are documented.

   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”
   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”
   • [claimed-docs] “Connect Featurebase with your favorite tools in just a few clicks, with new integrations added constantly.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.featurebase.app/llms.txt # Featurebase ## Docs - [featurebase-js](/guides/featurebase-js/in…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.featurebase.app/openapi.json, https://developers.featurebase.app/swagger.json, ht…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Canny—none0/10

   Evidence shows Canny has a REST API and an official MCP server, but nothing indicates an official CLI tool for AI-native workflows; no mention of any command-line interface anywhere in the docs.

   ⚑ flag

   Featurebase—none0/10

   Evidence shows an API/SDK reference and a typed JS client SDK, but no mention anywhere of an official CLI tool for AI-native workflows.

   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.featurebase.app/llms.txt # Featurebase ## Docs - [featurebase-js](/guides/featurebase-js/in…”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to Canny
   Canny✓fullprobed8/10

   Canny publishes a documented public API Reference (canny-docs-16) with a full developer docs site (canny-docs-15, canny-probe-1 llms.txt confirming developer docs), plus SDK/widget install docs and an official MCP server for LLM-driven interaction (canny-docs-3, canny-docs-9, canny-probe-3), enabling AI-native users to query and act on data programmatically. Missing for 10: an accessible OpenAPI/Swagger spec (canny-probe-2 shows all candidate OpenAPI endpoints 404) and independent hands-on corroboration of API usage.

   • [claimed-docs] “Canny API Reference”
   • [claimed-docs] “Install Docs | Canny”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.canny.io/llms.txt # Canny Developer Documentation > Developer resources for integrating with…”
   • [claimed-docs] “Add Canny's MCP server to ChatGPT, Claude, or Cursor with a secure sign-in. No API keys, no engineering.”
   • [claimed-docs] “Connect Canny to ChatGPT, Claude, and Cursor. Ask questions about customer feedback, take action on it, and ground your AI workflows in real…”
   • [probe] “official MCP server documented at https://canny.io/features/mcp”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.canny.io/openapi.json, https://developers.canny.io/swagger.json, https://develope…”

   proof ↗⚑ flag

   Featurebase✓fullprobed7/10

   Featurebase explicitly documents a full HTTP and SDK API reference plus webhooks for reacting to feedback/status changes, and its developer docs site is crawlable via llms.txt listing SDK guides, indicating a genuine documented public API surface for programmatic/AI-driven use. Missing for 10: a discoverable machine-readable OpenAPI/Swagger spec (probe returned 404s at standard paths) and independent third-party confirmation of API completeness/reliability.

   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”
   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.featurebase.app/llms.txt # Featurebase ## Docs - [featurebase-js](/guides/featurebase-js/in…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.featurebase.app/openapi.json, https://developers.featurebase.app/swagger.json, ht…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Canny—none0/10

   Canny's docs mention a general API Reference and an MCP server that uses 'secure sign-in, no API keys' rather than any scoped or least-privilege credential system for agents; there is no evidence of granular API scopes, role-based tokens, or agent-specific permission controls.

   • [claimed-docs] “Add Canny's MCP server to ChatGPT, Claude, or Cursor with a secure sign-in. No API keys, no engineering.”
   • [claimed-docs] “Canny API Reference”

   proof ↗⚑ flag

   Featurebase—none0/10

   Evidence shows Featurebase has an API/SDK reference and webhooks, but nothing about scoped or least-privilege API credentials, API key permission scoping, or agent-specific credential issuance. No mention of granular token scopes, roles, or restricted keys anywhere in the docs.

   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.featurebase.app/llms.txt # Featurebase ## Docs - [featurebase-js](/guides/featurebase-js/in…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.featurebase.app/openapi.json, https://developers.featurebase.app/swagger.json, ht…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Canny
   Canny~partialprobed6/10

   Canny provides an official JavaScript SDK for identify calls, a documented REST API reference, and even an AI-friendly llms.txt file for developer docs, all of which support building against official SDKs. However, probes show no discoverable OpenAPI/swagger spec (404s across all candidate paths), and evidence only shows one language SDK (JS) rather than a broader official SDK ecosystem. missing for 10: OpenAPI/machine-readable API spec, multi-language SDKs, independent developer corroboration of SDK robustness.

   • [claimed-docs] “Install our JavaScript SDK to identify your users. This way, when they leave feedback on Canny, it'll be tied to their existing user account…”
   • [claimed-docs] “Canny API Reference”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.canny.io/llms.txt # Canny Developer Documentation > Developer resources for integrating with…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.canny.io/openapi.json, https://developers.canny.io/swagger.json, https://develope…”
   • [claimed-docs] “Install Docs | Canny”

   proof ↗⚑ flag

   Featurebase~partialprobed4/10

   Evidence shows a documented 'featurebase-js' typed client SDK for the Messenger widget and a generic API reference tab, indicating some official SDK exists, but the OpenAPI spec 404s and there's no broader SDK ecosystem (e.g., for other languages) or independent corroboration. missing for 10: multi-language SDKs, working OpenAPI/spec discoverability, independent developer confirmation of SDK usage.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.featurebase.app/llms.txt # Featurebase ## Docs - [featurebase-js](/guides/featurebase-js/in…”
   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.featurebase.app/openapi.json, https://developers.featurebase.app/swagger.json, ht…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Featurebase
   Canny—none0/10

   The evidence pack includes API reference, integrations, and MCP server docs but contains no mention of webhooks or event subscription mechanisms anywhere. This is an applicable axis for a feedback platform with an API, but no evidence supports it, so verdict is none.

   ⚑ flag

   Featurebase~partialclaimed5/10

   Docs explicitly mention webhooks that let backend systems react to feedback, conversation activity, and status changes, confirming the capability exists, but there's no evidence of webhook payload schema, event catalog, signing/verification, or setup UI details. missing for 10: documented event types list, payload examples, subscription management UI/API, security/signing verification, independent confirmation of reliability.

   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”
   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Canny
   Canny✓fullprobed7/10

   Canny provides an official MCP server enabling users to ask their LLM for insights (top themes, ARR impact, roadmap queries) directly from feedback data, and to act on it (update statuses, draft PRDs, run agents) — matching the AI-native insight-generation story. missing for 10: no independent/hands-on validation of insight quality or accuracy, and no first-party in-app AI analytics dashboard beyond the MCP-based LLM interaction.

   • [claimed-docs] “Ask your LLM what customers asked for and understand the context behind each request. Dig into top themes, ARR impact across ideas, and quer…”
   • [claimed-docs] “Move ideas through your workflow without leaving your LLM. Update statuses, link deals, organize requests, and reply to customers.”
   • [claimed-docs] “Connect Canny to ChatGPT, Claude, and Cursor. Ask questions about customer feedback, take action on it, and ground your AI workflows in real…”
   • [claimed-docs] “Use Canny as the data layer for your AI workflows. Draft PRDs from real requests and build the features with Claude, generate reports for le…”
   • [probe] “official MCP server documented at https://canny.io/features/mcp”

   proof ↗⚑ flag

   Featurebase~partialclaimed5/10

   Featurebase explicitly claims AI helps 'declutter & find the most impactful opportunities' from feedback data, and separately offers AI-driven search answers and an AI support agent (Fibi), suggesting some AI-generated insight capability inside the product. However, evidence is a single marketing line with no detail on what insights look like, how they're surfaced, or independent/hands-on corroboration. Missing for 10: detailed documentation of the insights feature (e.g., trend detection, sentiment analysis, prioritization scoring), screenshots/demos, and independent user validation.

   • [claimed-docs] “Featurebase helps you declutter & find the most impactful opportunities with AI.”
   • [claimed-docs] “Let Fibi AI agent automatically resolve customer issues and cut down support loads for your team.”
   • [claimed-docs] “Give customers instant AI answers right in the search bar to help them find what they need, fast.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Canny
   Canny~partialclaimed6/10

   Canny's Autopilot feature automatically captures feedback from Gong, Intercom, Slack, Fathom, Fireflies, and review platforms without manual triggering, and native integrations (Jira, Linear, GitHub, etc.) keep statuses synced automatically — these qualify as background automations. However, this is limited to feedback ingestion/sync rather than a general-purpose agentic automation framework the user can configure for arbitrary autonomous tasks, and the MCP-based actions (updating statuses, replying to customers) appear to require active LLM invocation rather than running unattended in the background. Missing for 10: evidence of user-configurable, scheduled/triggered autonomous workflows beyond feedback capture, and confirmation that MCP-driven actions can run without a live agent session.

   • [claimed-docs] “Send new conversations to Autopilot to capture feedback you haven't tracked yet.”
   • [claimed-docs] “Automatically capture feedback from Gong, Intercom, Slack, and dozens of other sources, or directly from customers on your Portal.”
   • [claimed-docs] “Autopilot captures feedback from support, sales, and review platforms automatically. Native integrations keep the rest of your stack in sync…”
   • [claimed-docs] “Autopilot pulls feature requests out of your Fathom call transcripts automatically.”
   • [claimed-docs] “Capture product feedback from your Fireflies sales call transcripts.”
   • [claimed-docs] “Send feedback to Jira, link it to existing issues, and sync statuses. Only for Jira Cloud.”
   • [claimed-docs] “Send feedback to Linear, link it to existing issues, and sync statuses.”
   • [claimed-docs] “Send feedback to GitHub, link it to existing issues, and sync statuses.”

   proof ↗⚑ flag

   Featurebase~partialclaimed5/10

   Featurebase offers built-in 'workflows' for SLAs, trial extensions, and automatic notifications, plus webhooks for backend reactions and an AI agent (Fibi) that can auto-resolve support issues — these could run autonomously in the background. However, there is no explicit documentation of a user-configurable automation/workflow builder exposed as an agentic API, nor evidence of arbitrary background automations triggered by AI-native users beyond these built-in features. missing for 10: documentation of a general-purpose automation/workflow API for AI-native users, evidence of user-defined autonomous triggers beyond fixed built-in workflows, and independent confirmation of these features working end-to-end.

   • [claimed-docs] “Build workflows for SLAs, automatically extending trials, offering discounts, and much more.”
   • [claimed-docs] “Let Fibi AI agent automatically resolve customer issues and cut down support loads for your team.”
   • [claimed-docs] “Featurebase automatically notifies all relevant users when their requests are shipped. No more manual follow-ups.”
   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Featurebase
   Canny~partialclaimed4/10

   Canny ships 'Autopilot,' an automated AI feature that captures and categorizes feedback from support/sales/review sources without user intervention, and users can 'send new conversations to Autopilot' to have it process feedback — a limited form of task delegation to a built-in AI component. However, this is not a general-purpose conversational assistant embedded in the Canny UI; the richer AI interaction (asking questions, taking actions, drafting PRDs) is delivered via MCP connecting to *external* LLMs like ChatGPT/Claude/Cursor, not a native in-product assistant. Missing for 10: evidence of an interactive, conversational built-in assistant UI, an example of delegating arbitrary multi-step tasks to it, and independent/hands-on confirmation of Autopilot's task-delegation behavior beyond marketing copy.

   • [claimed-docs] “Send new conversations to Autopilot to capture feedback you haven't tracked yet.”
   • [claimed-docs] “Automatically capture feedback from Gong, Intercom, Slack, and dozens of other sources, or directly from customers on your Portal.”
   • [claimed-docs] “Autopilot captures feedback from support, sales, and review platforms automatically. Native integrations keep the rest of your stack in sync…”
   • [claimed-docs] “Autopilot pulls feature requests out of your Fathom call transcripts automatically.”
   • [claimed-docs] “Capture product feedback from your Fireflies sales call transcripts.”

   proof ↗⚑ flag

   Featurebase~partialclaimed5/10

   Featurebase advertises 'Fibi AI agent' that can automatically resolve customer issues and provide instant AI answers, which constitutes a built-in AI assistant that can be delegated support tasks. However, evidence is limited to marketing taglines with no detail on task delegation scope, configuration, or hands-on validation. Missing for 10: technical docs on delegating specific tasks to Fibi, independent/hands-on verification of its autonomy, and detail on scope of tasks it can handle beyond support tickets.

   • [claimed-docs] “Featurebase helps you declutter & find the most impactful opportunities with AI.”
   • [claimed-docs] “Let Fibi AI agent automatically resolve customer issues and cut down support loads for your team.”
   • [claimed-docs] “Give customers instant AI answers right in the search bar to help them find what they need, fast.”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Canny
   Canny~partialprobed6/10

   Canny ships an official MCP server enabling natural-language interaction via ChatGPT, Claude, or Cursor—users can ask questions about feedback, update statuses, link deals, and draft PRDs using plain language instead of UI/API calls. However, this is scoped to feedback/roadmap management rather than full product operation, and there's no independent/hands-on verification of the NL command experience quality. missing for 10: independent corroboration of MCP usability, breadth of natural-language commands beyond feedback workflows, evidence of reliability/limitations in practice.

   • [claimed-docs] “Add Canny's MCP server to ChatGPT, Claude, or Cursor with a secure sign-in. No API keys, no engineering.”
   • [claimed-docs] “Ask your LLM what customers asked for and understand the context behind each request. Dig into top themes, ARR impact across ideas, and quer…”
   • [claimed-docs] “Move ideas through your workflow without leaving your LLM. Update statuses, link deals, organize requests, and reply to customers.”
   • [claimed-docs] “Connect Canny to ChatGPT, Claude, and Cursor. Ask questions about customer feedback, take action on it, and ground your AI workflows in real…”
   • [claimed-docs] “Use Canny as the data layer for your AI workflows. Draft PRDs from real requests and build the features with Claude, generate reports for le…”
   • [probe] “official MCP server documented at https://canny.io/features/mcp”

   proof ↗⚑ flag

   Featurebase—none0/10

   Evidence shows Fibi AI answering customer support queries and AI-assisted decluttering of feedback, but nothing indicates an admin/user can operate Featurebase itself (create boards, manage roadmaps, configure settings) via natural-language commands. Missing for 10: any NL command interface, chat-driven admin actions, or agentic control surface for operating the product.

   • [claimed-docs] “Featurebase helps you declutter & find the most impactful opportunities with AI.”
   • [claimed-docs] “Let Fibi AI agent automatically resolve customer issues and cut down support loads for your team.”
   • [claimed-docs] “Give customers instant AI answers right in the search bar to help them find what they need, fast.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Canny—none0/10

   Canny has an API Reference page (canny-docs-16) but there is no evidence it includes runnable/interactive examples (e.g., try-it console, live code execution), and probes for a standard OpenAPI spec file all returned 404, suggesting no discoverable interactive spec.

   • [claimed-docs] “Canny API Reference”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.canny.io/openapi.json, https://developers.canny.io/swagger.json, https://develope…”

   proof ↗⚑ flag

   Featurebase—none0/10

   Evidence confirms an 'API Reference' tab with HTTP/SDK docs exists, but nothing indicates it is interactive or runnable (no try-it console, no live examples), and probes for a standard OpenAPI/Swagger spec (which typically powers such interactive references) returned 404 at all checked paths.

   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.featurebase.app/openapi.json, https://developers.featurebase.app/swagger.json, ht…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Canny—none0/10

   Canny has an API Reference page but there is no evidence of a downloadable OpenAPI/Swagger spec; explicit probes for openapi.json, swagger.json, and similar well-known paths all returned 404.

   • [claimed-docs] “Canny API Reference”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.canny.io/openapi.json, https://developers.canny.io/swagger.json, https://develope…”

   proof ↗⚑ flag

   Featurebase—none0/10

   Docs reference an 'API Reference' tab with HTTP/SDK docs, but there is no evidence of a downloadable OpenAPI/Swagger spec — probes for openapi.json, swagger.json, and well-known variants all returned 404, and llms.txt only lists guide pages, not a machine-readable spec.

   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.featurebase.app/llms.txt # Featurebase ## Docs - [featurebase-js](/guides/featurebase-js/in…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.featurebase.app/openapi.json, https://developers.featurebase.app/swagger.json, ht…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Canny—none0/10

   No evidence of a sandbox/staging environment or test mode separate from production data; all docs reference live API, widgets, and MCP integrations acting on real feedback data.

   ⚑ flag

   Featurebase—none0/10

   No evidence of a sandbox/test environment, staging API keys, or test-mode toggle to isolate testing from production data; evidence only covers general product features and API docs discovery.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Canny—none0/10

   Canny has an API Reference and install docs, but there is no evidence of API versioning or a documented deprecation policy; the OpenAPI spec probe returned 404s at all candidate paths, suggesting no machine-readable versioned spec either.

   • [claimed-docs] “Canny API Reference”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.canny.io/openapi.json, https://developers.canny.io/swagger.json, https://develope…”

   proof ↗⚑ flag

   Featurebase—none0/10

   Evidence shows an API reference and SDK exist, but there is no mention of API versioning scheme or any documented deprecation policy anywhere in the pack, and the OpenAPI probe returned 404s.

   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.featurebase.app/openapi.json, https://developers.featurebase.app/swagger.json, ht…”

   proof ↗⚑ flag

Reporting

1. ai-native userUse AI to declutter raw feedback and surface the most impactful opportunities

   weight 3 · round to Canny
   Canny~partialprobed6/10

   Canny's Autopilot and MCP features let AI surface themes, ARR impact, and top requests from raw feedback across sources (support, sales, reviews), and the MCP integration lets users query/act on this via ChatGPT/Claude. However, evidence is entirely vendor-authored marketing copy with no independent validation of how well the AI actually declutters/prioritizes feedback, no detail on the underlying scoring/impact methodology, and no hands-on or third-party corroboration. missing for 10: independent/hands-on evidence of AI decluttering quality, methodology detail behind 'ARR impact' scoring, third-party validation.

   • [claimed-docs] “Ask your LLM what customers asked for and understand the context behind each request. Dig into top themes, ARR impact across ideas, and quer…”
   • [claimed-docs] “Send new conversations to Autopilot to capture feedback you haven't tracked yet.”
   • [claimed-docs] “Automatically capture feedback from Gong, Intercom, Slack, and dozens of other sources, or directly from customers on your Portal.”
   • [claimed-docs] “Use Canny as the data layer for your AI workflows. Draft PRDs from real requests and build the features with Claude, generate reports for le…”
   • [claimed-docs] “Autopilot captures feedback from support, sales, and review platforms automatically. Native integrations keep the rest of your stack in sync…”
   • [probe] “official MCP server documented at https://canny.io/features/mcp”

   proof ↗⚑ flag

   Featurebase~partialclaimed5/10

   Featurebase explicitly markets an AI feature to 'declutter & find the most impactful opportunities' from feedback, directly matching the story, but only a single marketing tagline exists with no supporting documentation, screenshots, or independent corroboration of how it works. missing for 10: detailed docs/feature walkthrough on the AI decluttering feature, independent or hands-on verification, and technical specifics (e.g., what signals it uses to rank impact).

   • [claimed-docs] “Featurebase helps you declutter & find the most impactful opportunities with AI.”

   proof ↗⚑ flag

2. product-managerAccess customer context alongside feedback so I prioritize what really matters

   weight 2 · round to Canny
   Canny✓fullclaimed8/10

   Canny lets PMs identify users/companies via SDK, attach custom fields, and view ARR impact and themes alongside feedback, plus MCP integration lets PMs query customer context (themes, ARR impact, roadmap) directly from LLM tools. Missing for 10: independent/hands-on validation of how customer context is surfaced in the actual UI (only docs/marketing evidence, no third-party corroboration).

   • [claimed-docs] “Install our JavaScript SDK to identify your users. This way, when they leave feedback on Canny, it'll be tied to their existing user account…”
   • [claimed-docs] “Ask your LLM what customers asked for and understand the context behind each request. Dig into top themes, ARR impact across ideas, and quer…”
   • [claimed-docs] “Custom Fields | Canny”
   • [claimed-docs] “Install Companies | Canny”
   • [claimed-docs] “Connect Canny to ChatGPT, Claude, and Cursor. Ask questions about customer feedback, take action on it, and ground your AI workflows in real…”
   • [claimed-docs] “Use Canny as the data layer for your AI workflows. Draft PRDs from real requests and build the features with Claude, generate reports for le…”

   proof ↗⚑ flag

   Featurebase~partialclaimed4/10

   Featurebase centralizes feedback with a portal, integrations, and user-attribute segmentation, and uses AI to surface 'impactful opportunities,' which loosely supports contextualizing feedback for prioritization. However, there is no explicit evidence of surfacing customer-level context (e.g., account value, plan, company data) alongside individual feedback items to aid prioritization decisions. Missing for 10: direct documentation of customer/account context displayed next to feedback items, and any prioritization scoring tied to customer attributes.

   • [claimed-docs] “Segment your product releases by user attributes to always send out targeted release notes.”
   • [claimed-docs] “Centralize insights to a single source of truth with a feedback portal, in-app widgets, and integrations. Let users vote on each other's ide…”
   • [claimed-docs] “Featurebase helps you declutter & find the most impactful opportunities with AI.”
   • [claimed-docs] “Connect Featurebase with your favorite tools in just a few clicks, with new integrations added constantly.”

   proof ↗⚑ flag

3. ai-native userAsk an AI assistant questions about customer feedback themes and their revenue impact

   weight 3 · round to Canny
   Canny✓fullprobed8/10

   Canny's MCP server explicitly lets users ask their LLM about customer feedback themes and ARR/revenue impact ('Dig into top themes, ARR impact across ideas'), connecting via ChatGPT/Claude/Cursor without engineering work. This directly matches the story's ask-AI-about-feedback-and-revenue-impact use case. Missing for 10: independent/hands-on verification beyond vendor docs, and concrete examples of the AI answering real revenue-impact queries.

   • [claimed-docs] “Add Canny's MCP server to ChatGPT, Claude, or Cursor with a secure sign-in. No API keys, no engineering.”
   • [claimed-docs] “Ask your LLM what customers asked for and understand the context behind each request. Dig into top themes, ARR impact across ideas, and quer…”
   • [claimed-docs] “Connect Canny to ChatGPT, Claude, and Cursor. Ask questions about customer feedback, take action on it, and ground your AI workflows in real…”
   • [claimed-docs] “Use Canny as the data layer for your AI workflows. Draft PRDs from real requests and build the features with Claude, generate reports for le…”
   • [probe] “official MCP server documented at https://canny.io/features/mcp”

   proof ↗⚑ flag

   Featurebase—none0/10

   Featurebase's AI features documented are Fibi (support ticket resolution) and AI-powered search for customers, plus general 'declutter with AI' framing—none evidence a conversational assistant that analyzes feedback themes and ties them to revenue impact.

   • [claimed-docs] “Featurebase helps you declutter & find the most impactful opportunities with AI.”
   • [claimed-docs] “Let Fibi AI agent automatically resolve customer issues and cut down support loads for your team.”
   • [claimed-docs] “Give customers instant AI answers right in the search bar to help them find what they need, fast.”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Canny—none0/10

   Canny's docs show per-item actions (update status, link deals, sync to trackers) via its API and MCP server, but no evidence of any batch/bulk endpoint or MCP action that operates across many items at once — missing for 10: bulk update/merge API, batch MCP tool calls, any documented multi-item operation.

   ⚑ flag

   Featurebase—none0/10

   Evidence shows Featurebase has an API/SDK and webhooks but no documentation or reference to any bulk/batch operation endpoints for updating, tagging, or managing many items at once. The openapi probe even failed to resolve a schema, so no detail on bulk operation support is available.

   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.featurebase.app/llms.txt # Featurebase ## Docs - [featurebase-js](/guides/featurebase-js/in…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.featurebase.app/openapi.json, https://developers.featurebase.app/swagger.json, ht…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Featurebase
   Canny—none0/10

   Evidence shows Canny automatically captures feedback from integrations and syncs statuses, but there is no documentation of user-defined rules/triggers that fire actions on specific events (e.g., an automation/workflow rule engine). Missing for 10: explicit rule-builder or trigger-condition-action documentation, evidence of customizable automation logic, examples of event-based automation beyond passive data capture.

   • [claimed-docs] “Automatically capture feedback from Gong, Intercom, Slack, and dozens of other sources, or directly from customers on your Portal.”
   • [claimed-docs] “Autopilot captures feedback from support, sales, and review platforms automatically. Native integrations keep the rest of your stack in sync…”

   proof ↗⚑ flag

   Featurebase~partialclaimed5/10

   Featurebase docs mention webhooks that react instantly to feedback/status events and a 'workflows' feature for SLAs, auto-extending trials, and offering discounts, indicating rule-based automation tied to events. However, there is no detailed documentation of a rule-builder UI, condition/trigger types, or examples showing how a user defines custom automation logic beyond the marketing blurb. Missing for 10: dedicated workflow/rule-builder documentation, concrete trigger-condition-action examples, independent or hands-on verification of the automation engine's flexibility.

   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”
   • [claimed-docs] “Build workflows for SLAs, automatically extending trials, offering discounts, and much more.”
   • [claimed-docs] “Featurebase automatically notifies all relevant users when their requests are shipped. No more manual follow-ups.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Canny—none0/10

   Canny's evidence covers feedback capture, integrations, and an MCP server for querying/acting on feedback via LLM tools, but there is no mention of scheduling recurring jobs, cron-like automation, or persistent scheduled workflows. Autopilot automates capture but this is event-triggered, not schedule-based recurring automation.

   ⚑ flag

   Featurebase—none0/10

   Evidence shows webhooks (reactive, event-driven), workflows for SLAs/trials, and an API/SDK, but nothing about scheduling recurring jobs or cron-like automation. No mention of scheduled triggers, recurring tasks, or job scheduling capabilities anywhere in the docs pack.

   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”
   • [claimed-docs] “Build workflows for SLAs, automatically extending trials, offering discounts, and much more.”

   proof ↗⚑ flag

Changelog

1. product-managerServe a fully branded public changelog page on a custom domain

   weight 2 · round to Featurebase
   Canny~partialclaimed4/10

   Canny explicitly offers a Changelog product for announcing shipped features (canny-docs-8, canny-docs-14, canny-docs-26), confirming the axis applies, but none of the evidence describes custom-domain hosting or brand customization (logo, colors, CSS) for the changelog page. Missing for 10: explicit documentation of custom domain support, branding/theming options, and any independent confirmation of a fully white-labeled changelog experience.

   • [claimed-docs] “Announce what you shipped, show customers you heard them, and turn closed feedback into retention and upgrades.”
   • [claimed-docs] “Product Changelog Software and Release Notes Tool”
   • [claimed-docs] “Product Changelog Software and Release Notes Tool | Canny”

   proof ↗⚑ flag

   Featurebase✓fullclaimed9/10

   Docs explicitly state changelogs can be served from a standalone page with a custom domain and fully branded, plus email subscription support, directly matching the story. Missing for 10: independent/hands-on verification beyond vendor docs.

   • [claimed-docs] “Serve your changelogs from a standalone page with a custom domain and fully brand it. Subscribe users to email updates.”

   proof ↗⚑ flag

2. product-managerLet customers subscribe to email updates when new changelog entries are published

   weight 1 · round to Featurebase
   Canny—none0/10

   Evidence confirms Canny has a Changelog feature for announcing shipped updates (canny-docs-8, canny-docs-14, canny-docs-26), but none of the evidence describes a customer-facing email subscription mechanism for new changelog entries. Missing for 10: any documentation of an email subscribe/opt-in feature tied to changelog publishing.

   • [claimed-docs] “Announce what you shipped, show customers you heard them, and turn closed feedback into retention and upgrades.”
   • [claimed-docs] “Product Changelog Software and Release Notes Tool”
   • [claimed-docs] “Product Changelog Software and Release Notes Tool | Canny”

   proof ↗⚑ flag

   Featurebase✓fullclaimed8/10

   Featurebase explicitly documents a standalone changelog page where 'Subscribe users to email updates' is offered, directly matching the story, and also supports segmenting release notes by user attributes for targeted notifications. missing for 10: independent/hands-on confirmation of the subscription flow and details on subscription management (opt-out, frequency).

   • [claimed-docs] “Serve your changelogs from a standalone page with a custom domain and fully brand it. Subscribe users to email updates.”
   • [claimed-docs] “Segment your product releases by user attributes to always send out targeted release notes.”
   • [claimed-docs] “Featurebase automatically notifies all relevant users when their requests are shipped. No more manual follow-ups.”

   proof ↗⚑ flag

3. developerShowcase new updates within my product using an embeddable changelog widget

   weight 2 · round drawn
   Canny✓fullclaimed8/10

   Canny explicitly offers a Changelog product for announcing shipped updates plus documented widget embed guides for web and mobile, directly matching the story. Missing for 10: independent/hands-on corroboration of the widget's ease-of-use and no evidence of changelog-specific widget customization details beyond general docs.

   • [claimed-docs] “Announce what you shipped, show customers you heard them, and turn closed feedback into retention and upgrades.”
   • [claimed-docs] “Product Changelog Software and Release Notes Tool”
   • [claimed-docs] “Embed a Canny widget into your website”
   • [claimed-docs] “Embed a Canny widget into your mobile app”
   • [claimed-docs] “Product Changelog Software and Release Notes Tool | Canny”

   proof ↗⚑ flag

   Featurebase✓fullclaimed8/10

   Featurebase explicitly advertises embeddable changelog widgets to showcase updates directly in-product and on websites, plus a standalone branded changelog page with email subscriptions. Missing for 10: independent/hands-on verification of the widget embed process and customization depth.

   • [claimed-docs] “Showcase new updates directly within your product and website with our embeddable changelog widgets.”
   • [claimed-docs] “Serve your changelogs from a standalone page with a custom domain and fully brand it. Subscribe users to email updates.”

   proof ↗⚑ flag

4. product-managerPublish a changelog announcing shipped features to close the loop with customers

   weight 3 · round drawn
   Canny✓fullclaimed7/10

   Canny explicitly offers a Changelog product ('Announce what you shipped, show customers you heard them, and turn closed feedback into retention and upgrades') as a dedicated feature area, directly matching the story of closing the loop with customers on shipped features. Missing for 10: no evidence of workflow automation linking closed feedback items to changelog entries, no screenshots/hands-on detail on publishing flow, and no independent/user corroboration beyond marketing copy.

   • [claimed-docs] “Announce what you shipped, show customers you heard them, and turn closed feedback into retention and upgrades.”
   • [claimed-docs] “Product Changelog Software and Release Notes Tool”
   • [claimed-docs] “Product Changelog Software and Release Notes Tool | Canny”

   proof ↗⚑ flag

   Featurebase✓fullclaimed7/10

   Featurebase explicitly supports publishing changelogs with a Notion-like editor, custom domain/branding, embeddable widgets, email subscriptions, audience segmentation, and automatic notifications to users when their requests ship — directly closing the loop with customers. missing for 10: independent/hands-on corroboration beyond vendor marketing pages, and no detailed workflow documentation on drafting/approval process for changelog publishing.

   • [claimed-docs] “Notion-like editor experience with tons of formatting options and custom components to make your docs stand out.”
   • [claimed-docs] “Segment your product releases by user attributes to always send out targeted release notes.”
   • [claimed-docs] “Showcase new updates directly within your product and website with our embeddable changelog widgets.”
   • [claimed-docs] “Serve your changelogs from a standalone page with a custom domain and fully brand it. Subscribe users to email updates.”
   • [claimed-docs] “Featurebase automatically notifies all relevant users when their requests are shipped. No more manual follow-ups.”

   proof ↗⚑ flag

Lifecycle automation

1. product-managerBuild automated workflows for SLAs, trial extensions, and discount offers triggered by feedback events

   weight 2 · round to Featurebase
   Canny—none0/10

   Canny's evidence covers feedback capture, integrations (Jira, Linear, GitHub, etc.), changelog, and an MCP server for querying/acting on feedback data, but there is no mention of automated workflow builders for SLAs, trial extensions, or discount offers triggered by feedback events. Missing for 10: any SLA automation, trial-extension logic, discount-offer triggers, or general conditional workflow/rules engine tied to feedback events.

   ⚑ flag

   Featurebase~partialclaimed6/10

   Featurebase's own marketing explicitly promises workflow automation for SLAs, trial extensions, and discount offers (featurebase-docs-3), backed by webhook support that reacts to feedback/status events (featurebase-docs-1). However, there is no documentation of the actual workflow builder UI, trigger/condition/action configuration, or independent/hands-on confirmation that these automations work as advertised. Missing for 10: detailed workflow-builder documentation, example configurations, and independent or hands-on verification of SLA/trial/discount automation in practice.

   • [claimed-docs] “Build workflows for SLAs, automatically extending trials, offering discounts, and much more.”
   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”

   proof ↗⚑ flag

2. product-managerAutomatically notify customers when the status of their requested feature changes

   weight 2 · round to Featurebase
   Canny~partialclaimed4/10

   Canny's changelog feature is described as a way to 'show customers you heard them' when shipping features (canny-docs-8), which implies some notification workflow, but the evidence never explicitly confirms an automated per-voter email/notification triggered specifically when a status changes on their requested feature — the closest matches are Discord alerts for team feedback (canny-intdir-1) and changelog publishing, not confirmed automatic customer-facing status-change alerts. Missing for 10: explicit documentation of automatic subscriber/voter notifications tied to individual status transitions, and any independent/hands-on confirmation of this workflow.

   • [claimed-docs] “Announce what you shipped, show customers you heard them, and turn closed feedback into retention and upgrades.”
   • [claimed-docs] “Get instant notifications in Discord about your feedback.”

   proof ↗⚑ flag

   Featurebase✓fullclaimed8/10

   Featurebase explicitly documents automatic notification to users when their requested feature/status ships ('automatically notifies all relevant users when their requests are shipped. No more manual follow-ups'), directly matching the story, supplemented by webhooks reacting to status changes for further automation. Missing for 10: independent/hands-on confirmation of the notification triggering correctly and detail on configuring which status changes trigger alerts.

   • [claimed-docs] “Featurebase automatically notifies all relevant users when their requests are shipped. No more manual follow-ups.”
   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”

   proof ↗⚑ flag

3. product-managerSegment product release announcements by user attributes to send targeted release notes

   weight 2 · round to Featurebase
   Canny—none0/10

   Canny's changelog feature (canny-docs-8, canny-docs-14) covers publishing release notes, and separate docs mention custom fields and company identification (canny-docs-20, canny-docs-23), but no evidence ties these together to show audience segmentation of changelog/release announcements by user attributes for targeted delivery.

   • [claimed-docs] “Announce what you shipped, show customers you heard them, and turn closed feedback into retention and upgrades.”
   • [claimed-docs] “Product Changelog Software and Release Notes Tool”
   • [claimed-docs] “Custom Fields | Canny”
   • [claimed-docs] “Install Companies | Canny”

   proof ↗⚑ flag

   Featurebase✓fullclaimed8/10

   Featurebase explicitly advertises segmenting product release announcements by user attributes for targeted release notes, directly matching the story, plus supporting notification automation for shipped requests. Missing for 10: independent/hands-on corroboration of this specific segmentation feature and technical detail on how attribute-based targeting is configured.

   • [claimed-docs] “Segment your product releases by user attributes to always send out targeted release notes.”
   • [claimed-docs] “Featurebase automatically notifies all relevant users when their requests are shipped. No more manual follow-ups.”

   proof ↗⚑ flag

Centralized repository

1. product-managerAutomatically capture customer feedback mentioned in sales calls, support tickets, and chat conversations

   weight 3 · round to Canny
   Canny✓fullclaimed8/10

   Canny's Autopilot feature explicitly automates capturing feedback from sales calls (Gong, Fireflies, Fathom transcripts), support tickets (Intercom, support platforms), and chat (Slack, Discord), aggregating them into Canny as a unified feedback layer. This directly matches the story's capture-intake theme across multiple channel types with named integrations. Missing for 10: independent/hands-on verification of Autopilot's accuracy or reliability in practice, and clearer detail on chat conversation capture beyond Slack/Discord notifications.

   • [claimed-docs] “Automatically capture feedback from Gong, Intercom, Slack, and dozens of other sources, or directly from customers on your Portal.”
   • [claimed-docs] “Autopilot captures feedback from support, sales, and review platforms automatically. Native integrations keep the rest of your stack in sync…”
   • [claimed-docs] “Autopilot pulls feature requests out of your Fathom call transcripts automatically.”
   • [claimed-docs] “Capture product feedback from your Fireflies sales call transcripts.”
   • [claimed-docs] “Send new conversations to Autopilot to capture feedback you haven't tracked yet.”

   proof ↗⚑ flag

   Featurebase~partialclaimed5/10

   Featurebase's unified inbox and integrations support capturing feedback from in-app, Slack, Discord, and email conversations, and webhooks can react to new feedback/conversation activity, which covers chat and support-ticket-like channels. However, there is no evidence of any sales-call integration (e.g., call transcription tools like Gong) or automatic extraction of feedback from sales conversations specifically. Missing for 10: sales-call capture integration, evidence of automatic parsing/extraction of feedback content from tickets/calls rather than just channel presence.

   • [claimed-docs] “Support customers wherever they are: In-app, Slack, Discord, Emails, and more from a single powerful inbox.”
   • [claimed-docs] “Connect Featurebase with your favorite tools in just a few clicks, with new integrations added constantly.”
   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”
   • [claimed-docs] “Centralize insights to a single source of truth with a feedback portal, in-app widgets, and integrations. Let users vote on each other's ide…”

   proof ↗⚑ flag

2. product-managerAccess one searchable repository for all product requests and feedback from colleagues and customers

   weight 3 · round to Featurebase
   Canny✓fullclaimed7/10

   Canny's core product is a centralized feedback repository: it captures requests directly from customers via Portal/widgets and automatically ingests feedback from Gong, Intercom, Slack, Fathom, Fireflies, and other tools via Autopilot, consolidating everything with statuses, syncing, and MCP-based query access for PMs to interrogate the whole feedback base. Missing for 10: explicit documentation of a search feature/UI within the repository, and independent/hands-on corroboration beyond vendor docs.

   • [claimed-docs] “Automatically capture feedback from Gong, Intercom, Slack, and dozens of other sources, or directly from customers on your Portal.”
   • [claimed-docs] “Autopilot captures feedback from support, sales, and review platforms automatically. Native integrations keep the rest of your stack in sync…”
   • [claimed-docs] “Autopilot pulls feature requests out of your Fathom call transcripts automatically.”
   • [claimed-docs] “Capture product feedback from your Fireflies sales call transcripts.”
   • [claimed-docs] “Ask your LLM what customers asked for and understand the context behind each request. Dig into top themes, ARR impact across ideas, and quer…”
   • [claimed-docs] “Connect Canny to ChatGPT, Claude, and Cursor. Ask questions about customer feedback, take action on it, and ground your AI workflows in real…”
   • [claimed-docs] “Embed a Canny widget into your website”
   • [claimed-docs] “Embed a Canny widget into your mobile app”

   proof ↗⚑ flag

   Featurebase✓fullclaimed8/10

   Featurebase explicitly markets a feedback portal that centralizes insights from customers and colleagues into a single searchable source of truth, with voting and public roadmap features, plus integrations to pull in requests from multiple channels. Missing for 10: independent/hands-on corroboration of search functionality quality and no explicit detail on internal colleague-only submission workflows.

   • [claimed-docs] “Centralize insights to a single source of truth with a feedback portal, in-app widgets, and integrations. Let users vote on each other's ide…”
   • [claimed-docs] “Support customers wherever they are: In-app, Slack, Discord, Emails, and more from a single powerful inbox.”
   • [claimed-docs] “Connect Featurebase with your favorite tools in just a few clicks, with new integrations added constantly.”

   proof ↗⚑ flag

3. product-managerLink individual feedback items to the specific customers who submitted them

   weight 2 · round to Canny
   Canny✓fullclaimed8/10

   Canny's JS SDK identifies users so feedback is tied to their existing account (canny-docs-2), and Install Companies docs support linking feedback to customer/company records (canny-docs-23). SSO and secure identify further ensure feedback is authenticated to real customers (canny-docs-19, canny-docs-21, canny-docs-27, canny-docs-28). Missing for 10: independent/hands-on corroboration beyond vendor docs, and explicit UI screenshots showing a feedback item's linked customer profile.

   • [claimed-docs] “Install our JavaScript SDK to identify your users. This way, when they leave feedback on Canny, it'll be tied to their existing user account…”
   • [claimed-docs] “Install Companies | Canny”
   • [claimed-docs] “How to Implement Single Sign-On”
   • [claimed-docs] “Secure Identify Requests Install Docs”

   proof ↗⚑ flag

   Featurebase—none0/10

   The evidence pack does not directly describe any capability for tagging or linking feedback submissions to individual customer identities/profiles (e.g., CRM records, customer attributes). Only tangential mentions of notifying 'relevant users' or workflow automation exist, not the specific submitter-linking capability.

   • [claimed-docs] “Featurebase automatically notifies all relevant users when their requests are shipped. No more manual follow-ups.”
   • [claimed-docs] “Centralize insights to a single source of truth with a feedback portal, in-app widgets, and integrations. Let users vote on each other's ide…”

   proof ↗⚑ flag

4. product-managerReply to customers directly from within the feedback record to close the loop

   weight 2 · round drawn
   Canny~partialclaimed5/10

   Evidence confirms replying to customers is possible via the MCP integration ("reply to customers" listed as an action from LLM tools), implying the underlying feedback record supports replies, but there is no direct documentation of the native in-app reply-to-customer workflow within the feedback record itself. missing for 10: direct product docs/screenshots of replying to a commenter within the Canny feedback record UI, evidence of email/notification triggered to the customer, and independent/hands-on confirmation of this closing-the-loop workflow.

   • [claimed-docs] “Move ideas through your workflow without leaving your LLM. Update statuses, link deals, organize requests, and reply to customers.”
   • [claimed-docs] “Connect Canny to ChatGPT, Claude, and Cursor. Ask questions about customer feedback, take action on it, and ground your AI workflows in real…”

   proof ↗⚑ flag

   Featurebase~partialclaimed5/10

   Featurebase's 'single powerful inbox' (docs-11) and automatic shipped-notifications (docs-12) imply admins can communicate with customers from a centralized feedback/support view, which aligns with the story's intent, but no evidence explicitly shows replying inline within a feedback record's comment thread to close the loop. missing for 10: explicit documentation or screenshot of replying to a specific feedback post/comment, confirmation that replies notify the customer directly, and any independent/hands-on corroboration.

   • [claimed-docs] “Support customers wherever they are: In-app, Slack, Discord, Emails, and more from a single powerful inbox.”
   • [claimed-docs] “Featurebase automatically notifies all relevant users when their requests are shipped. No more manual follow-ups.”

   proof ↗⚑ flag

Embeddable widget

1. product-managerCustomize the feedback widget's label and colors to match my brand

   weight 1 · round to Canny
   Canny~partialprobed5/10

   Canny provides docs for embedding a web/mobile feedback widget (canny-docs-17, canny-docs-18) and its dev docs index mentions 'widget customization' (canny-probe-1), implying some branding controls, but no evidence explicitly confirms label text or color customization options. missing for 10: explicit documentation of label/text customization, explicit color/theme customization settings, and independent confirmation of brand-matching capability.

   • [claimed-docs] “Embed a Canny widget into your website”
   • [claimed-docs] “Embed a Canny widget into your mobile app”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.canny.io/llms.txt # Canny Developer Documentation > Developer resources for integrating with…”

   proof ↗⚑ flag

   Featurebase—none0/10

   The evidence pack mentions embeddable widgets, custom domains, and branding for changelogs, but there is no mention of customizing the feedback widget's label text or color scheme specifically. Missing for 10: any documentation of widget label/text customization, color/theme customization options for the feedback capture widget.

   ⚑ flag

2. developerEmbed a feedback widget on my website with a single script tag and no build step

   weight 3 · round to Canny
   Canny~partialclaimed6/10

   Canny documents a website widget install page (canny-docs-17) confirming embeddable widget support, but the evidence doesn't specify a single-script-tag, no-build-step method — docs also mention SDK install, SSO, and security/identify requests that suggest additional setup steps beyond a trivial snippet. missing for 10: actual snippet/code sample showing single script tag, confirmation that no build step or bundler is required, independent/hands-on verification of ease of embed.

   • [claimed-docs] “Embed a Canny widget into your website”
   • [claimed-docs] “Install our JavaScript SDK to identify your users. This way, when they leave feedback on Canny, it'll be tied to their existing user account…”
   • [claimed-docs] “Install Docs | Canny”

   proof ↗⚑ flag

   Featurebase~partialprobed4/10

   Featurebase advertises embeddable widgets (changelog and in-app feedback widgets) and a typed JS SDK, implying some form of client-side embed capability, but no evidence explicitly confirms a single script-tag, no-build-step integration for the feedback widget specifically. missing for 10: explicit script-tag embed instructions, confirmation of zero build step, and hands-on/independent verification of the feedback widget embed process.

   • [claimed-docs] “Showcase new updates directly within your product and website with our embeddable changelog widgets.”
   • [claimed-docs] “Centralize insights to a single source of truth with a feedback portal, in-app widgets, and integrations. Let users vote on each other's ide…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.featurebase.app/llms.txt # Featurebase ## Docs - [featurebase-js](/guides/featurebase-js/in…”

   proof ↗⚑ flag

3. developerIdentify logged-in users when they submit feedback so it ties to their existing account

   weight 2 · round to Canny
   Canny✓fullclaimed9/10

   Canny's JS SDK explicitly identifies users so feedback ties to their existing account (canny-docs-2), backed by dedicated SSO and secure identify-request docs (canny-docs-19, canny-docs-21/28) plus widget/mobile install docs (canny-docs-17,18). Missing for 10: independent/hands-on verification beyond vendor docs.

   • [claimed-docs] “Install our JavaScript SDK to identify your users. This way, when they leave feedback on Canny, it'll be tied to their existing user account…”
   • [claimed-docs] “How to Implement Single Sign-On”
   • [claimed-docs] “Secure Identify Requests Install Docs”
   • [claimed-docs] “Embed a Canny widget into your website”
   • [claimed-docs] “Embed a Canny widget into your mobile app”

   proof ↗⚑ flag

   Featurebase—none0/10

   None of the evidence describes identifying logged-in users (e.g., SSO/JWT identity verification tying feedback to an existing account); only generic SDK, webhook, and integration mentions are present with no user-identification specifics.

   ⚑ flag

Public portal

1. developerAdd a link in my product that directs users to the feedback portal

   weight 1 · round to Canny
   Canny✓fullclaimed9/10

   Canny's docs explicitly instruct developers to add a link to the Canny feedback site in their app, plus provide widget embed options for web and mobile as alternatives/complements to a plain link. Missing for 10: independent/hands-on confirmation beyond first-party docs.

   • [claimed-docs] “In your application, add a link to your Canny feedback site. Put the link somewhere it's easy to find.”
   • [claimed-docs] “Embed a Canny widget into your website”
   • [claimed-docs] “Embed a Canny widget into your mobile app”
   • [claimed-docs] “Install Docs | Canny”

   proof ↗⚑ flag

   Featurebase~partialclaimed6/10

   Featurebase's product centers on a hosted feedback portal with embeddable in-app widgets (featurebase-docs-15), which implies developers can link/embed the portal in their product, but there's no explicit documentation snippet showing a code sample, widget script, or direct 'add this link' instructions. Missing for 10: explicit widget/embed code documentation, confirmation of a direct portal URL/link feature, and independent evidence of ease of integration.

   • [claimed-docs] “Centralize insights to a single source of truth with a feedback portal, in-app widgets, and integrations. Let users vote on each other's ide…”

   proof ↗⚑ flag

2. product-managerHost a public feedback portal where customers submit and vote on ideas

   weight 3 · round to Featurebase
   Canny✓fullclaimed8/10

   Canny's core product is a public feedback portal embeddable via widget (web/mobile) where customers submit and vote on ideas, with SSO/identify integration and a changelog to close the loop; this is well documented across install and widget docs. Missing for 10: no independent/hands-on third-party review confirming the voting/portal UX in practice, and no explicit customer-facing voting mechanic quote (only 'submit feedback on your Portal').

   • [claimed-docs] “Embed a Canny widget into your website”
   • [claimed-docs] “Embed a Canny widget into your mobile app”
   • [claimed-docs] “In your application, add a link to your Canny feedback site. Put the link somewhere it's easy to find.”
   • [claimed-docs] “Automatically capture feedback from Gong, Intercom, Slack, and dozens of other sources, or directly from customers on your Portal.”
   • [claimed-docs] “Announce what you shipped, show customers you heard them, and turn closed feedback into retention and upgrades.”
   • [claimed-docs] “How to Implement Single Sign-On”

   proof ↗⚑ flag

   Featurebase✓fullclaimed9/10

   Featurebase explicitly offers a public feedback portal where users vote on each other's ideas and view a public roadmap, directly matching the story. Missing for 10: independent/hands-on third-party corroboration beyond vendor docs.

   • [claimed-docs] “Centralize insights to a single source of truth with a feedback portal, in-app widgets, and integrations. Let users vote on each other's ide…”

   proof ↗⚑ flag

Convert to work

1. ai-native userHave AI turn a plain-language feedback description into a structured set of proposed tasks

   weight 3 · round to Canny
   Canny~partialclaimed4/10

   Canny's MCP lets an LLM query and act on feedback, including drafting PRDs and organizing/linking requests, which implies AI could turn feedback into structured tasks, but there's no explicit feature or workflow described that ingests a plain-language feedback description and outputs a structured task list. Missing for 10: a dedicated 'feedback-to-task' generation feature, hands-on example of the described workflow, and evidence of structured task output format.

   • [claimed-docs] “Use Canny as the data layer for your AI workflows. Draft PRDs from real requests and build the features with Claude, generate reports for le…”
   • [claimed-docs] “Move ideas through your workflow without leaving your LLM. Update statuses, link deals, organize requests, and reply to customers.”
   • [claimed-docs] “Connect Canny to ChatGPT, Claude, and Cursor. Ask questions about customer feedback, take action on it, and ground your AI workflows in real…”
   • [claimed-docs] “Ask your LLM what customers asked for and understand the context behind each request. Dig into top themes, ARR impact across ideas, and quer…”

   proof ↗⚑ flag

   Featurebase—none0/10

   Featurebase advertises AI features like decluttering feedback (featurebase-docs-7) and an AI agent for resolving support issues (featurebase-docs-10), but none of the evidence describes AI converting a plain-language feedback description into a structured set of proposed tasks. Missing for 10: any documentation of AI generating structured task/action breakdowns from feedback text, UI screenshots or workflow examples of this specific capability.

   • [claimed-docs] “Featurebase helps you declutter & find the most impactful opportunities with AI.”
   • [claimed-docs] “Let Fibi AI agent automatically resolve customer issues and cut down support loads for your team.”
   • [claimed-docs] “Give customers instant AI answers right in the search bar to help them find what they need, fast.”

   proof ↗⚑ flag

2. product-managerReview and approve the scope of a task before any work begins on it

   weight 2 · round drawn
   Canny—none0/10

   Canny's evidence covers feedback collection, roadmap status workflows, and syncing to task trackers (Jira, Linear, GitHub, etc.), but there is no documented feature for a PM to formally review/approve a task's scope before work starts — Canny hands off to the external tracker once linked, and no approval gate is described.

   ⚑ flag

   Featurebase—none0/10

   Featurebase's evidence covers feedback collection, roadmapping, changelog, integrations, webhooks, and support inbox, but nothing describes a workflow where a PM reviews or approves the scope of a task before work begins. Missing for 10: any task/scope definition step, an approval gate or sign-off mechanism, or documentation of a pre-work review process.

   ⚑ flag

3. product-managerTurn a customer feedback submission directly into an actionable task or project intention

   weight 3 · round to Canny
   Canny✓fullclaimed8/10

   Canny lets PMs directly convert feedback into actionable work: integrations sync feedback to Jira, Linear, GitHub, ClickUp, and Asana as tasks/issues with status sync, and the MCP server allows updating statuses, linking deals, organizing requests, and even drafting PRDs from real requests directly from an LLM workflow. This covers the feedback-to-task pipeline end-to-end with both native integrations and AI-assisted workflows. Missing for 10: independent/hands-on corroboration beyond vendor docs, and more detail on native in-app task/project creation without third-party tool integration.

   • [claimed-docs] “Send feedback to Jira, link it to existing issues, and sync statuses. Only for Jira Cloud.”
   • [claimed-docs] “Send feedback to Linear, link it to existing issues, and sync statuses.”
   • [claimed-docs] “Send feedback to GitHub, link it to existing issues, and sync statuses.”
   • [claimed-docs] “Send feedback to ClickUp, link it to existing tasks, and sync statuses.”
   • [claimed-docs] “Send feedback to Asana, link it to existing tasks, and sync statuses.”
   • [claimed-docs] “Move ideas through your workflow without leaving your LLM. Update statuses, link deals, organize requests, and reply to customers.”
   • [claimed-docs] “Use Canny as the data layer for your AI workflows. Draft PRDs from real requests and build the features with Claude, generate reports for le…”

   proof ↗⚑ flag

   Featurebase~partialclaimed5/10

   Featurebase supports centralizing feedback into a roadmap/prioritization view (docs-15), general third-party integrations (docs-4), and webhooks for backend automation (docs-1), which together imply feedback can be routed into external task/project tools, but there is no explicit documentation of a native 'convert feedback to task' action or named integration (e.g., Jira/Linear/Asana) confirming this workflow. missing for 10: explicit feature/documentation showing one-click conversion of a feedback item into a task/issue in a project-management tool, named PM tool integrations, and independent confirmation of this workflow in practice.

   • [claimed-docs] “Centralize insights to a single source of truth with a feedback portal, in-app widgets, and integrations. Let users vote on each other's ide…”
   • [claimed-docs] “Connect Featurebase with your favorite tools in just a few clicks, with new integrations added constantly.”
   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”

   proof ↗⚑ flag

4. developerPull an approved product specification into the delivery workflow to start implementation

   weight 2 · round to Canny
   Canny~partialclaimed6/10

   Canny lets teams sync feedback/roadmap items into delivery tools like Jira, Linear, GitHub, ClickUp and Asana (linking issues, syncing statuses), and its MCP integration explicitly supports drafting PRDs from real requests and building features with Claude, which maps to pulling an approved spec into implementation. However, this relies on third-party issue trackers rather than a native 'approved spec' handoff step, and there's no dedicated documentation of an approval gate or spec format being pulled into a dev workflow. missing for 10: a native concept of an 'approved' spec/status gate, first-party workflow docs showing the full approve-to-implement handoff, and independent/hands-on confirmation beyond vendor pages.

   • [claimed-docs] “Use Canny as the data layer for your AI workflows. Draft PRDs from real requests and build the features with Claude, generate reports for le…”
   • [claimed-docs] “Send feedback to Jira, link it to existing issues, and sync statuses. Only for Jira Cloud.”
   • [claimed-docs] “Send feedback to Linear, link it to existing issues, and sync statuses.”
   • [claimed-docs] “Send feedback to GitHub, link it to existing issues, and sync statuses.”
   • [claimed-docs] “Send feedback to ClickUp, link it to existing tasks, and sync statuses.”
   • [claimed-docs] “Send feedback to Asana, link it to existing tasks, and sync statuses.”
   • [claimed-docs] “Move ideas through your workflow without leaving your LLM. Update statuses, link deals, organize requests, and reply to customers.”

   proof ↗⚑ flag

   Featurebase~partialclaimed4/10

   Featurebase advertises webhooks and generic third-party integrations that could relay approved feedback/specs into other systems, but there is no concrete evidence of a specific integration (e.g., Jira/Linear/GitHub) that pulls an approved spec into a delivery workflow for implementation. Missing for 10: documented integration with issue trackers/dev tools, evidence of spec-to-ticket sync, and any developer-facing workflow showing implementation kickoff from an approved post.

   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”
   • [claimed-docs] “Build workflows for SLAs, automatically extending trials, offering discounts, and much more.”
   • [claimed-docs] “Connect Featurebase with your favorite tools in just a few clicks, with new integrations added constantly.”

   proof ↗⚑ flag

5. product-managerWatch the real-time status of each in-progress task, including what it's blocked on and its last update

   weight 2 · round to Canny
   Canny~partialclaimed3/10

   Canny syncs statuses with tools like Jira, Linear, GitHub, ClickUp, and Asana, so a PM could see a high-level status label update via those integrations, but there is no evidence of a dedicated real-time view showing why a task is blocked or a detailed 'last update' timeline. missing for 10: explicit blocked-reason field, real-time update timestamps/activity feed, dedicated in-progress task dashboard.

   • [claimed-docs] “Send feedback to Jira, link it to existing issues, and sync statuses. Only for Jira Cloud.”
   • [claimed-docs] “Send feedback to Linear, link it to existing issues, and sync statuses.”
   • [claimed-docs] “Send feedback to GitHub, link it to existing issues, and sync statuses.”
   • [claimed-docs] “Send feedback to ClickUp, link it to existing tasks, and sync statuses.”
   • [claimed-docs] “Send feedback to Asana, link it to existing tasks, and sync statuses.”

   proof ↗⚑ flag

   Featurebase—none0/10

   Evidence shows Featurebase has status change notifications and webhooks for feedback/roadmap items, but nothing describes per-task 'blocked on' fields or granular real-time task status views expected by a PM tracking in-progress work. missing for 10: any mention of blocked-status tracking, task-level detail views, or real-time in-progress dashboards.

   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”
   • [claimed-docs] “Featurebase automatically notifies all relevant users when their requests are shipped. No more manual follow-ups.”

   proof ↗⚑ flag

Tool connections

1. product-managerConnect feedback capture to support, sales, and chat tools I already use

   weight 3 · round to Canny
   Canny✓fullclaimed8/10

   Canny documents native integrations explicitly aimed at support, sales, and chat sources (Gong, Intercom, Slack, Fathom, Fireflies) via Autopilot, plus a broader integrations directory and MCP access from chat-based AI tools, directly matching the PM's need to connect feedback capture to existing tools. Missing for 10: independent/hands-on verification of these integrations working in practice and more detail on setup/configuration beyond marketing copy.

   • [claimed-docs] “Automatically capture feedback from Gong, Intercom, Slack, and dozens of other sources, or directly from customers on your Portal.”
   • [claimed-docs] “Autopilot captures feedback from support, sales, and review platforms automatically. Native integrations keep the rest of your stack in sync…”
   • [claimed-docs] “Autopilot pulls feature requests out of your Fathom call transcripts automatically.”
   • [claimed-docs] “Capture product feedback from your Fireflies sales call transcripts.”
   • [claimed-docs] “Get instant notifications in Discord about your feedback.”
   • [claimed-docs] “Integrations | Canny”

   proof ↗⚑ flag

   Featurebase~partialclaimed6/10

   Featurebase advertises multi-channel support inboxes (in-app, Slack, Discord, Email) and generic 'connect with your favorite tools' integrations plus webhooks/workflows for backend automation, which supports connecting feedback to support and chat tools. However, evidence never names specific sales-tool integrations (e.g., CRM/Salesforce/HubSpot) or provides a concrete integrations list/marketplace beyond vague marketing language, and there's no independent confirmation of integration depth. missing for 10: named sales-tool integrations, a documented integrations directory/marketplace, and third-party verification of real-world connections.

   • [claimed-docs] “Connect Featurebase with your favorite tools in just a few clicks, with new integrations added constantly.”
   • [claimed-docs] “Support customers wherever they are: In-app, Slack, Discord, Emails, and more from a single powerful inbox.”
   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”
   • [claimed-docs] “Build workflows for SLAs, automatically extending trials, offering discounts, and much more.”

   proof ↗⚑ flag

2. developerBuild custom integrations that appear and operate directly inside the product's own interface

   weight 1 · round drawn
   Canny—none0/10

   Canny's developer docs cover embedding Canny's own widget into a customer's app, its API/SDK, and native integrations that push feedback out to third-party tools (Jira, Linear, GitHub, etc.) or connect via MCP to external AI tools — but there is no evidence of a platform, app marketplace, or extension framework letting developers build custom integrations that run/appear directly inside Canny's own interface (dashboard, portal, or admin UI).

   ⚑ flag

   Featurebase—none0/10

   Evidence shows webhooks, an API/SDK, and integrations connecting Featurebase to external tools, plus embeddable widgets for putting Featurebase content into a customer's own product — but nothing about a plugin/app framework that lets developers build custom functionality that runs inside Featurebase's own interface. Missing for 10: any documented app/plugin marketplace, custom UI extension points, or SDK for embedding third-party functionality within Featurebase's own dashboard.

   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”
   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”
   • [claimed-docs] “Connect Featurebase with your favorite tools in just a few clicks, with new integrations added constantly.”
   • [claimed-docs] “Showcase new updates directly within your product and website with our embeddable changelog widgets.”

   proof ↗⚑ flag

3. product-managerConnect common third-party tools to my feedback workspace in just a few clicks

   weight 2 · round to Canny
   Canny✓fullclaimed8/10

   Canny documents a native integrations directory covering Jira, Linear, GitHub, ClickUp, Asana, Slack, Discord, Intercom, Gong, Fathom, Fireflies and others, described as easy native connections that sync statuses and capture feedback automatically, plus a low-friction MCP connection to ChatGPT/Claude/Cursor with 'no API keys, no engineering.' Missing for 10: independent hands-on confirmation of the actual click-count/setup friction and no evidence of a broader app marketplace beyond the listed integrations.

   • [claimed-docs] “Automatically capture feedback from Gong, Intercom, Slack, and dozens of other sources, or directly from customers on your Portal.”
   • [claimed-docs] “Autopilot captures feedback from support, sales, and review platforms automatically. Native integrations keep the rest of your stack in sync…”
   • [claimed-docs] “Get instant notifications in Discord about your feedback.”
   • [claimed-docs] “Autopilot pulls feature requests out of your Fathom call transcripts automatically.”
   • [claimed-docs] “Capture product feedback from your Fireflies sales call transcripts.”
   • [claimed-docs] “Send feedback to Jira, link it to existing issues, and sync statuses. Only for Jira Cloud.”
   • [claimed-docs] “Send feedback to Linear, link it to existing issues, and sync statuses.”
   • [claimed-docs] “Send feedback to GitHub, link it to existing issues, and sync statuses.”
   • [claimed-docs] “Send feedback to ClickUp, link it to existing tasks, and sync statuses.”
   • [claimed-docs] “Send feedback to Asana, link it to existing tasks, and sync statuses.”
   • [claimed-docs] “Add Canny's MCP server to ChatGPT, Claude, or Cursor with a secure sign-in. No API keys, no engineering.”
   • [claimed-docs] “Integrations | Canny”

   proof ↗⚑ flag

   Featurebase~partialclaimed5/10

   Marketing copy explicitly claims one-click integrations with popular tools ('Connect Featurebase with your favorite tools in just a few clicks'), but there's no evidence pack listing which specific third-party tools (Slack, Jira, Intercom, etc.) are supported or showing the actual connection flow/UI. missing for 10: list of specific supported integrations, screenshots/docs of the setup flow, independent confirmation of ease-of-use.

   • [claimed-docs] “Connect Featurebase with your favorite tools in just a few clicks, with new integrations added constantly.”
   • [claimed-docs] “Support customers wherever they are: In-app, Slack, Discord, Emails, and more from a single powerful inbox.”

   proof ↗⚑ flag

Setup

1. product-managerUse a rich text editor with custom components to format changelog and help content

   weight 1 · round to Featurebase
   Canny—none0/10

   Evidence covers Canny's changelog feature, MCP integration, feedback capture and integrations, but nothing describes a rich text editor with custom components for authoring changelog/help content. Missing for 10: any mention of an editor, rich text formatting capabilities, custom components/blocks, or help-content authoring tools.

   ⚑ flag

   Featurebase✓fullclaimed7/10

   Docs explicitly describe a 'Notion-like editor experience with tons of formatting options and custom components' for changelogs/help docs, directly matching the story. missing for 10: independent/hands-on corroboration of the editor, and no detail on which specific custom components are available.

   • [claimed-docs] “Notion-like editor experience with tons of formatting options and custom components to make your docs stand out.”
   • [claimed-docs] “Serve your changelogs from a standalone page with a custom domain and fully brand it. Subscribe users to email updates.”
   • [claimed-docs] “Scale your help content to global audiences in different brands, and 40+ languages.”

   proof ↗⚑ flag

2. product-managerSet up a public-facing feedback portal without engineering help

   weight 2 · round drawn
   Canny~partialclaimed6/10

   Canny's core product is a hosted feedback portal, and docs describe simply linking to 'your Canny feedback site' (canny-docs-1) plus a changelog tool (canny-docs-8/14) that require no code to use. However, deeper setup steps described (SDK install, widget embedding, SSO, custom fields) are aimed at developers, and there's no explicit documentation walking a non-technical PM through portal creation without engineering. Missing for 10: explicit no-code onboarding wizard documentation, independent PM testimonials confirming self-serve setup without engineering.

   • [claimed-docs] “In your application, add a link to your Canny feedback site. Put the link somewhere it's easy to find.”
   • [claimed-docs] “Announce what you shipped, show customers you heard them, and turn closed feedback into retention and upgrades.”
   • [claimed-docs] “Product Changelog Software and Release Notes Tool”
   • [claimed-docs] “Embed a Canny widget into your website”

   proof ↗⚑ flag

   Featurebase~partialclaimed6/10

   Featurebase is explicitly a no-code feedback portal product ('feedback portal, in-app widgets... let users vote on ideas & show a public roadmap') with custom domain and branding options for changelogs, suggesting a self-serve setup without engineering. However, there is no explicit walkthrough or evidence describing the actual portal setup flow, time-to-launch, or confirmation that no code/dev work is required for the core portal (only for changelog/domain features). missing for 10: explicit onboarding/setup documentation for the feedback portal itself, confirmation of no-code setup, independent user testimony on ease of setup without engineering.

   • [claimed-docs] “Centralize insights to a single source of truth with a feedback portal, in-app widgets, and integrations. Let users vote on each other's ide…”
   • [claimed-docs] “Serve your changelogs from a standalone page with a custom domain and fully brand it. Subscribe users to email updates.”
   • [claimed-docs] “Connect Featurebase with your favorite tools in just a few clicks, with new integrations added constantly.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Canny~partialprobed4/10

   Canny publishes a public API reference and an MCP server that lets AI tools query and act on feedback data (statuses, replies, linking), suggesting meaningful API coverage, but no evidence establishes full parity between the API/MCP surface and everything available in the Canny UI (e.g., admin settings, roadmap customization, changelog publishing, integrations config). Missing for 10: explicit documentation or independent confirmation of complete UI-API parity, and an OpenAPI spec (probe found only 404s) that would demonstrate full endpoint coverage.

   • [claimed-docs] “Canny API Reference”
   • [claimed-docs] “Connect Canny to ChatGPT, Claude, and Cursor. Ask questions about customer feedback, take action on it, and ground your AI workflows in real…”
   • [claimed-docs] “Move ideas through your workflow without leaving your LLM. Update statuses, link deals, organize requests, and reply to customers.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.canny.io/openapi.json, https://developers.canny.io/swagger.json, https://develope…”
   • [probe] “official MCP server documented at https://canny.io/features/mcp”

   proof ↗⚑ flag

   Featurebase~partialprobed4/10

   Featurebase documents an API reference, SDK, and webhooks (developers.featurebase.app), showing a real API surface exists, but there is no evidence claiming or demonstrating full feature parity between the UI and API — no OpenAPI spec was found (404s on all candidate paths), and admin/workflow/changelog features are described only as UI capabilities. Missing for 10: explicit parity documentation, published OpenAPI spec, and evidence that UI-only features (workflows, changelog widgets, integrations) are also exposed via API.

   • [claimed-docs] “Looking for the full HTTP and SDK reference? Switch to the API Reference tab in the top navigation.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.featurebase.app/llms.txt # Featurebase ## Docs - [featurebase-js](/guides/featurebase-js/in…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.featurebase.app/openapi.json, https://developers.featurebase.app/swagger.json, ht…”
   • [claimed-docs] “Webhooks allow your backend systems to react instantly to user feedback, conversation activity, status changes, and more.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Canny—none0/10

   While Canny provides an API reference and developer docs, there is no evidence of a bulk data export feature, open-format export (CSV/JSON dump of feedback, users, etc.), or any documented data-portability/account-closure workflow. The axis applies to a SaaS feedback platform, but no capability is evidenced.

   ⚑ flag

   Featurebase—none0/10

   No evidence of a bulk data-export feature, open-format export, or data-portability tooling; only webhooks, an API reference, and unrelated feature docs are provided. missing for 10: documented full data export tool, open format (CSV/JSON) export, account data portability guarantee.

   ⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Canny—none0/10

   Canny is a closed, proprietary SaaS product with no evidence of any open-source license or public source code repository; all evidence concerns hosted feedback/MCP/integration features, not source availability.

   ⚑ flag

   Featurebase—none0/10

   No evidence Featurebase's source code is available under any open license; it is a closed SaaS product with only API docs, SDKs, and integrations mentioned.

   ⚑ flag

Insights surfacing

1. ai-native userRely on AI to automatically detect insights within feedback and link them to related feature ideas

   weight 2 · round to Canny
   Canny~partialclaimed5/10

   Canny's Autopilot automatically captures feedback from calls, support, and sales tools, and its MCP server lets an LLM be asked about 'top themes' and context behind requests, suggesting some AI-driven insight surfacing (canny-docs-4, canny-docs-11, canny-intdir-2/3). However, there is no evidence of the AI proactively detecting insights and automatically linking them to existing/related feature ideas within Canny itself — the linking features shown (Jira, Linear, GitHub, ClickUp, Asana) are manual issue-tracker syncs, not AI-detected relations between feedback and ideas. Missing for 10: evidence of automatic duplicate/related-idea detection, proof of unsupervised insight-to-idea linking (vs. on-demand LLM queries), and independent validation of this capability.

   • [claimed-docs] “Ask your LLM what customers asked for and understand the context behind each request. Dig into top themes, ARR impact across ideas, and quer…”
   • [claimed-docs] “Autopilot captures feedback from support, sales, and review platforms automatically. Native integrations keep the rest of your stack in sync…”
   • [claimed-docs] “Autopilot pulls feature requests out of your Fathom call transcripts automatically.”
   • [claimed-docs] “Capture product feedback from your Fireflies sales call transcripts.”
   • [claimed-docs] “Use Canny as the data layer for your AI workflows. Draft PRDs from real requests and build the features with Claude, generate reports for le…”

   proof ↗⚑ flag

   Featurebase~partialclaimed3/10

   Featurebase claims AI helps 'declutter & find the most impactful opportunities' (docs-7) and offers AI search answers (docs-14) and an AI support agent (docs-10), suggesting some AI-driven feedback analysis, but there is no explicit evidence of automatic insight detection or automatic linking of feedback to related feature ideas. Missing for 10: documentation of duplicate/similarity detection, insight extraction from feedback text, and automatic linking mechanics to roadmap items.

   • [claimed-docs] “Featurebase helps you declutter & find the most impactful opportunities with AI.”
   • [claimed-docs] “Give customers instant AI answers right in the search bar to help them find what they need, fast.”
   • [claimed-docs] “Let Fibi AI agent automatically resolve customer issues and cut down support loads for your team.”

   proof ↗⚑ flag

Scoring

1. product-managerLink feedback requests to roadmap features, initiatives, and releases

   weight 3 · round to Featurebase
   Canny~partialclaimed4/10

   Evidence shows Canny's MCP layer lets teams 'query your team's roadmap,' 'update statuses, link deals, organize requests,' and the changelog feature turns closed feedback into shipped announcements, implying some link between feedback and roadmap/release stages, but there is no explicit documentation of a native roadmap board where feedback items are directly attached to specific initiatives or releases. Missing for 10: dedicated docs on roadmap board structure, initiative/epic linking, and release-tagging of feedback items beyond generic issue-tracker sync (Jira/Linear/GitHub).

   • [claimed-docs] “Ask your LLM what customers asked for and understand the context behind each request. Dig into top themes, ARR impact across ideas, and quer…”
   • [claimed-docs] “Move ideas through your workflow without leaving your LLM. Update statuses, link deals, organize requests, and reply to customers.”
   • [claimed-docs] “Announce what you shipped, show customers you heard them, and turn closed feedback into retention and upgrades.”
   • [claimed-docs] “Send feedback to Jira, link it to existing issues, and sync statuses. Only for Jira Cloud.”
   • [claimed-docs] “Send feedback to Linear, link it to existing issues, and sync statuses.”

   proof ↗⚑ flag

   Featurebase~partialclaimed5/10

   Featurebase's public roadmap and feedback portal (featurebase-docs-15) let users vote on ideas and see a roadmap, and shipped requests automatically notify relevant users (featurebase-docs-12), implying feedback items are tied to roadmap statuses/releases. However, there's no explicit documentation of linking feedback to 'initiatives' or granular release notes tied to specific feedback items. Missing for 10: explicit initiative/epic linking feature, documentation of feedback-to-release mapping UI, and independent confirmation of this workflow.

   • [claimed-docs] “Centralize insights to a single source of truth with a feedback portal, in-app widgets, and integrations. Let users vote on each other's ide…”
   • [claimed-docs] “Featurebase automatically notifies all relevant users when their requests are shipped. No more manual follow-ups.”

   proof ↗⚑ flag

2. product-managerScore feedback and ideas using fields like value, risk, impact, confidence, and effort

   weight 3 · round to Canny
   Canny~partialclaimed4/10

   Canny's Custom Fields feature (canny-docs-20) would let a PM add fields such as value, risk, impact, confidence, or effort to ideas, but the evidence pack contains no documentation of a purpose-built scoring/prioritization framework (e.g., RICE/ICE formulas, weighted score calculation, or a dedicated prioritization view). Missing for 10: evidence of built-in scoring formulas or automated priority-score calculation, evidence of a dedicated prioritization board/view using these fields.

   • [claimed-docs] “Custom Fields | Canny”

   proof ↗⚑ flag

   Featurebase—none0/10

   No evidence of custom scoring fields (value, risk, impact, confidence, effort) or a prioritization scoring framework anywhere in the docs; the pack only covers feedback collection, changelogs, support inbox, and integrations.

   ⚑ flag

3. product-managerOrganize requests into a hierarchy of features, components, and initiatives

   weight 2 · round drawn
   Canny—none0/10

   The evidence pack contains no mention of hierarchical organization of feedback into features, components, or initiatives (e.g., no reference to Canny's category/board structure or initiative grouping) — only integrations, MCP, changelog, and SDK install docs are present. Missing for 10: any docs on categories, tagging hierarchy, or initiative/epic grouping features.

   ⚑ flag

   Featurebase—none0/10

   The evidence pack covers feedback portals, roadmaps, changelogs, integrations, and AI support tools, but none of it mentions organizing requests into a hierarchy of features, components, and initiatives. Missing for 10: any mention of parent-child feature grouping, initiative-level rollups, or component hierarchies.

   ⚑ flag

4. product-managerReschedule initiatives and move them between releases as priorities change

   weight 2 · round drawn
   Canny—none0/10

   Evidence covers feedback capture, integrations, MCP/AI tooling, and changelog features but nothing about roadmap/release planning, initiative scheduling, or moving items between releases. Missing for 10: any mention of a roadmap tool, release/version grouping, or drag-and-drop scheduling of initiatives.

   ⚑ flag

   Featurebase—none0/10

   The evidence pack shows Featurebase has roadmap, changelog, and release notes features, but there is no mention of rescheduling initiatives or moving items between releases as priorities shift. missing for 10: any documentation of drag-and-drop or timeline rescheduling, release reassignment, or initiative status/date change functionality.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Canny—none0/10

   No evidence in the pack mentions data residency, regional storage options, or any control over where customer data is hosted; Canny's docs focus on install, SDKs, MCP, and integrations only.

   ⚑ flag

   Featurebase—none0/10

   No evidence pack item mentions data residency, region selection, or data storage location options; the docs cover integrations, changelogs, AI search, and support features but say nothing about where data is hosted or a choice of region.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Canny—none0/10

   No evidence in the pack addresses AI training data opt-out, data usage policies for model training, or privacy controls preventing Canny from using customer data to train AI models; the pack only covers MCP feedback tooling and integrations. missing for 10: any privacy policy, ToS clause, or admin setting about excluding data from AI/ML training.

   ⚑ flag

   Featurebase—none0/10

   No evidence pack item mentions any AI training data opt-out, privacy policy on model training, or data usage controls for AI features like Fibi or AI search; the docs focus on product features (webhooks, integrations, changelogs) with no privacy-posture statements.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Canny—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or privacy/data-lifecycle management for user or feedback data; the docs cover SSO, install, widgets, MCP, and integrations but nothing about retention/deletion mechanisms.

   ⚑ flag

   Featurebase—none0/10

   No evidence of data retention controls, deletion APIs, or privacy/data-lifecycle policies anywhere in the docs; evidence only covers feedback, changelog, and support features unrelated to data retention/deletion.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Canny—none0/10

   No evidence pack items mention telemetry, usage tracking, analytics opt-out, or any privacy/data-collection controls for AI-native or MCP usage; the documentation focuses on feedback collection, integrations, and MCP feature capabilities rather than telemetry controls. missing for 10: any mention of telemetry/usage-data collection, an opt-out mechanism, or privacy settings related to AI tool usage.

   ⚑ flag

   Featurebase—none0/10

   No evidence in the pack mentions telemetry, usage tracking, or an opt-out mechanism for Featurebase itself; all items describe feedback/roadmap/support features unrelated to privacy controls.

   ⚑ flag