Featurebase vs Productboard
free-tier · subscription-per-seat · enterprise-custom
·subscription-per-seat · enterprise-custom
Productboard wins · 17–27 (18 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round drawnA 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…”
A probe confirms Productboard serves a working llms.txt at developer.productboard.com/llms.txt (HTTP 200) with a description of the API and instructions to append .md to any doc page for agent-readable versions, which is exactly the agent-oriented docs pattern the story asks for. Missing for 10: independent/community confirmation that agents actually consume this llms.txt successfully in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.productboard.com/llms.txt # Productboard Public API Documentation > Productboard Public API …”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to ProductboardFeaturebase 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…”
Productboard's REST API supports personal-access-token authentication, cursor-based pagination, and webhooks, all of which enable scripted/headless use in CI or automation pipelines (docs-43, docs-51, docs-5). However, there is no explicit documentation of CI/CD integration, SDKs, or example automation scripts targeting headless pipelines. Missing for 10: explicit CI/CD pipeline examples, official SDK/CLI for automation, and documented rate-limit/queueing guidance for unattended batch jobs.
- [claimed-docs] “Use a personal access token to authenticate API requests. Best for internal tools, scripts, and getting started quickly.”
- [claimed-docs] “Create, search, and manage feedback, documents, customers, and product data through Productboard's REST API.”
- [claimed-docs] “For large result sets, both the list and search endpoints support cursor-based pagination.”
- [claimed-docs] “The Webhooks API allows you to subscribe to events in Productboard and receive real-time notifications when data changes.”
- [claimed-docs] “The Productboard REST API uses cursor-based pagination for all endpoints that return a list of results.”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round drawnFeaturebasenone0/10No 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.
Productboardnone0/10All evidence describes Productboard shipping its own MCP server so external agents/tools can call Productboard's capabilities (docs-10 through docs-13, probe-3) — this is the reverse role. There is no evidence that Productboard itself can act as an MCP client and plug in external MCP servers to use their tools.
- [claimed-docs] “Now you can use any agent to add new features, reschedule an initiative, or start building off a product specification.”
- [claimed-docs] “Update custom drivers and other data fields on features and initiatives (like value, risk, impact, confidence, and effort) to automate prior…”
- [claimed-docs] “Add features to initiatives, move an initiative to a new release, or create key results beneath an objective.”
- [claimed-docs] “Access your latest product specifications from coding agents and AI prototyping tools to initiate the product delivery process.”
- [probe] “official MCP server documented at https://www.productboard.com/integrations/mcp-server/”
ai-native userConnect an agent via an official MCP server
weight 3 · round to ProductboardFeaturebasenone0/10Featurebase 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…”
Productboard ships an official, well-documented MCP server with a single connection endpoint (mcp.productboard.com), browser-based sign-in via existing login, OAuth with PKCE/Dynamic Client Registration, admin controls for enabling MCP and role-based access, and documented use cases for reading/writing features, initiatives, specs, and prioritization data via coding agents and AI tools. Missing for 10: independent/third-party hands-on corroboration beyond vendor docs.
- [claimed-docs] “The Productboard MCP server lets your coding agent read product specs straight from Productboard — and write back to them.”
- [claimed-docs] “You connect your agent to a single address: `https://mcp.productboard.com`. Signing in happens through your browser, using your existing Pro…”
- [claimed-docs] “Under **Who can use it**, choose which roles may connect an agent — for example, makers with admin access, makers, contributors, or viewers.”
- [claimed-docs] “Authenticate MCP (Model Context Protocol) clients using Dynamic Client Registration and the authorization code flow with PKCE. No client sec…”
- [claimed-docs] “Turn on Enable MCP for this workspace.”
- [claimed-docs] “Create and update features, subfeatures, initiatives, releases, objectives, key results, companies, users, feedback, documents, and more dir…”
- [claimed-docs] “The Productboard MCP server bridges those divides by allowing you to employ the AI tools and agents you’re already using to access and updat…”
- [probe] “official MCP server documented at https://www.productboard.com/integrations/mcp-server/”
ai-native userUse an official CLI
weight 2 · round drawnFeaturebasenone0/10Evidence 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…”
ai-native userDrive the product through a documented public API
weight 3 · round to ProductboardFeaturebase 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…”
Productboard documents a comprehensive REST API v2 with authentication (token and OAuth PKCE), cursor-based pagination, CRUD across features, feedback, documents, customers, teams, webhooks, and configuration/discovery endpoints, plus quickstart and Postman guides, and an llms.txt probe confirms machine-readable docs are live. This is a thorough, well-documented public API suitable for AI-native/agent-driven use, reinforced by a dedicated MCP server for agent access. missing for 10: no independent/third-party corroboration of real-world API usage or hands-on developer confirmation beyond vendor docs, and an OpenAPI spec file was not found at expected locations.
- [claimed-docs] “Create, search, and manage feedback, documents, customers, and product data through Productboard's REST API.”
- [claimed-docs] “For large result sets, both the list and search endpoints support cursor-based pagination.”
- [claimed-docs] “Create, read, update, delete, and search customer feedback, complete with text content, tags, owners, source metadata, and customer attribut…”
- [claimed-docs] “List and search feedback with structured filters by owner, creator, tags, date range, and status. For large result sets, both the list and s…”
- [claimed-docs] “Use a personal access token to authenticate API requests. Best for internal tools, scripts, and getting started quickly.”
- [claimed-docs] “Authenticate users via the OAuth 2.0 authorization code flow with consent screens and refreshable tokens.”
- [claimed-docs] “The Productboard REST API uses cursor-based pagination for all endpoints that return a list of results.”
- [claimed-docs] “Get up and running with the Productboard API v2 in Postman in under 5 minutes.”
- [claimed-docs] “This Quickstart walks you through your first API call using Productboard's REST API v2. In just a few steps, you’ll authenticate, send a req…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.productboard.com/llms.txt # Productboard Public API Documentation > Productboard Public API …”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.productboard.com/openapi.json, https://developer.productboard.com/swagger.json, ht…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to ProductboardFeaturebasenone0/10Evidence 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…”
Productboard offers multiple credential types for agents (personal access tokens, OAuth 2.0 authorization-code flow with consent screens, and PKCE-based OAuth for MCP clients) and lets admins restrict which roles may connect an agent, giving some coarse-grained control over agent access. However, there is no documented support for fine-grained scopes (e.g., read-only vs write, per-resource permissions) on tokens or OAuth grants, so true least-privilege credential issuance isn't evidenced. Missing for 10: explicit scoped/permission-limited token or OAuth scope configuration, documentation of granular read/write or resource-level access control for agent credentials, and independent confirmation of scope enforcement.
- [claimed-docs] “Under **Who can use it**, choose which roles may connect an agent — for example, makers with admin access, makers, contributors, or viewers.”
- [claimed-docs] “Authenticate MCP (Model Context Protocol) clients using Dynamic Client Registration and the authorization code flow with PKCE. No client sec…”
- [claimed-docs] “Use a personal access token to authenticate API requests. Best for internal tools, scripts, and getting started quickly.”
- [claimed-docs] “Authenticate users via the OAuth 2.0 authorization code flow with consent screens and refreshable tokens.”
- [claimed-docs] “You connect your agent to a single address: `https://mcp.productboard.com`. Signing in happens through your browser, using your existing Pro…”
ai-native userBuild against official SDKs
weight 2 · round to ProductboardEvidence 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…”
Productboard publishes a well-documented REST API v2 (quickstart, Postman collection, auth via PAT/OAuth, pagination, webhooks) and an MCP server for agent integration, which lets AI-native builders programmatically interact with the product. However, there's no evidence of official language-specific client SDKs (e.g., Python/JS packages) and the OpenAPI spec probe returned 404s, suggesting no auto-generatable SDK artifact. Missing for 10: official SDK packages in common languages, published OpenAPI/swagger spec, independent developer confirmation of SDK usage.
- [claimed-docs] “This Quickstart walks you through your first API call using Productboard's REST API v2. In just a few steps, you’ll authenticate, send a req…”
- [claimed-docs] “Get up and running with the Productboard API v2 in Postman in under 5 minutes.”
- [claimed-docs] “Use a personal access token to authenticate API requests. Best for internal tools, scripts, and getting started quickly.”
- [claimed-docs] “Authenticate users via the OAuth 2.0 authorization code flow with consent screens and refreshable tokens.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.productboard.com/openapi.json, https://developer.productboard.com/swagger.json, ht…”
- [claimed-docs] “The Productboard MCP server lets your coding agent read product specs straight from Productboard — and write back to them.”
- [claimed-docs] “You connect your agent to a single address: `https://mcp.productboard.com`. Signing in happens through your browser, using your existing Pro…”
ai-native userSubscribe to events via webhooks
weight 2 · round to ProductboardDocs 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.”
Productboard documents a dedicated Webhooks API with explicit create/list/delete endpoints for subscribing to entity change events and receiving real-time notifications, matching the story directly. Missing for 10: independent/hands-on corroboration of webhook reliability and payload/event-type documentation depth beyond the reference stubs.
- [claimed-docs] “The Webhooks API allows you to subscribe to events in Productboard and receive real-time notifications when data changes.”
- [claimed-docs] “Subscribe to entity change events and receive real-time notifications at your endpoint.”
- [claimed-docs] “Creates a new webhook subscription to be actively notified on each change in the specified entities.”
- [claimed-docs] “Permanently deletes a webhook subscription. No further notifications will be sent after deletion.”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to ProductboardFeaturebase 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.”
Productboard automatically detects insights within feedback and links them to related feature ideas, showing native AI-generated insight surfacing inside the product, and the MCP server lets AI agents act on that data (prioritization, specs, initiatives). However, evidence is limited to marketing claims with no hands-on validation of insight quality or breadth of AI suggestions beyond feedback-to-feature linking. Missing for 10: independent/hands-on verification of AI insight accuracy, broader AI-generated suggestions (e.g., roadmap prioritization, summarization) beyond feedback linking, and detail on how insights are surfaced in UI.
- [claimed-docs] “Productboard automatically detects insights within feedback that can be linked to related feature ideas.”
- [claimed-docs] “Now you can use any agent to add new features, reschedule an initiative, or start building off a product specification.”
- [claimed-docs] “Update custom drivers and other data fields on features and initiatives (like value, risk, impact, confidence, and effort) to automate prior…”
- [claimed-docs] “Access your latest product specifications from coding agents and AI prototyping tools to initiate the product delivery process.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to FeaturebaseFeaturebase 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.”
Productboard exposes webhooks, a REST API, and an MCP server that let external agents or scripts react to events and modify data, which are the building blocks for automation, but there's no documented native feature for scheduling or running autonomous background workflows within Productboard itself — all examples show agent-initiated or event-triggered actions rather than self-running background automations. missing for 10: a first-party 'automation' or scheduled-agent feature, evidence of unattended/recurring execution, and confirmation that MCP-driven actions can run without a live agent session.
- [claimed-docs] “The Webhooks API allows you to subscribe to events in Productboard and receive real-time notifications when data changes.”
- [claimed-docs] “Now you can use any agent to add new features, reschedule an initiative, or start building off a product specification.”
- [claimed-docs] “Update custom drivers and other data fields on features and initiatives (like value, risk, impact, confidence, and effort) to automate prior…”
- [claimed-docs] “Access your latest product specifications from coding agents and AI prototyping tools to initiate the product delivery process.”
- [probe] “official MCP server documented at https://www.productboard.com/integrations/mcp-server/”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to FeaturebaseFeaturebase 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.”
Productboardnone0/10Evidence covers an MCP server that lets external AI agents (Claude, ChatGPT, coding agents) call into Productboard's data and workflows, plus automatic insight detection — but nothing describes a built-in, in-product AI assistant/chat that a user can delegate tasks to. MCP is an external-agent connector, not an assistant embedded in Productboard's own UI, and insight-detection is automatic, not user-delegated task execution.
- [claimed-docs] “Now you can use any agent to add new features, reschedule an initiative, or start building off a product specification.”
- [claimed-docs] “Update custom drivers and other data fields on features and initiatives (like value, risk, impact, confidence, and effort) to automate prior…”
- [claimed-docs] “Add features to initiatives, move an initiative to a new release, or create key results beneath an objective.”
- [claimed-docs] “Productboard automatically detects insights within feedback that can be linked to related feature ideas.”
- [probe] “official MCP server documented at https://www.productboard.com/integrations/mcp-server/”
ai-native userOperate the product with natural-language commands
weight 2 · round to ProductboardFeaturebasenone0/10Evidence 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.”
Productboard ships an official MCP server (mcp.productboard.com) plus Spark natural-language interface that let any AI agent (Claude, ChatGPT, coding agents) read specs and create/update features, initiatives, releases, and objectives via natural language, and Spark supports natural-language queries against Slack/Amplitude/Notion. This is first-party documented and includes install/auth/OAuth flows and worked examples. Missing for 10: independent/hands-on third-party verification of the natural-language command experience and coverage of edge cases or limitations in real usage.
- [claimed-docs] “Now you can use any agent to add new features, reschedule an initiative, or start building off a product specification.”
- [claimed-docs] “Create and update features, subfeatures, initiatives, releases, objectives, key results, companies, users, feedback, documents, and more dir…”
- [claimed-docs] “The Productboard MCP server lets your coding agent read product specs straight from Productboard — and write back to them.”
- [claimed-docs] “You connect your agent to a single address: `https://mcp.productboard.com`. Signing in happens through your browser, using your existing Pro…”
- [claimed-docs] “Pull a spec, talk through the plan with your agent, and build. No setup beyond the connection.”
- [claimed-docs] “The Productboard MCP server bridges those divides by allowing you to employ the AI tools and agents you’re already using to access and updat…”
- [claimed-docs] “Query Amplitude analytics through natural language in Productboard Spark.”
- [claimed-docs] “Search, message, and act in Slack through natural language in Productboard Spark.”
- [probe] “official MCP server documented at https://www.productboard.com/integrations/mcp-server/”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnFeaturebasenone0/10Evidence 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…”
Productboardnone0/10Evidence confirms Productboard has API documentation (developer.productboard.com, llms.txt) but no mention of an interactive reference with runnable/try-it examples, and probes for an OpenAPI/Swagger spec (which typically power such consoles) all returned 404. Missing for 10: any documentation or screenshot of an interactive console, runnable code snippets, or Swagger/Redoc-style UI.
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.productboard.com/llms.txt # Productboard Public API Documentation > Productboard Public API …”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.productboard.com/openapi.json, https://developer.productboard.com/swagger.json, ht…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnFeaturebasenone0/10Docs 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…”
Productboardnone0/10While Productboard documents a REST API v2 and even a Postman quickstart, no first-party page offers a downloadable OpenAPI/Swagger file, and a direct probe of the standard OpenAPI spec locations (openapi.json, swagger.json, etc.) on developer.productboard.com all returned 404, indicating no machine-readable spec is actually published for retrieval.
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.productboard.com/openapi.json, https://developer.productboard.com/swagger.json, ht…”
- [claimed-docs] “Get up and running with the Productboard API v2 in Postman in under 5 minutes.”
- [claimed-docs] “This Quickstart walks you through your first API call using Productboard's REST API v2. In just a few steps, you’ll authenticate, send a req…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnFeaturebasenone0/10No 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.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnFeaturebasenone0/10Evidence 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…”
Productboardnone0/10Evidence describes REST API features, pagination, webhooks, and MCP server capabilities but contains no mention of API versioning scheme or a documented deprecation policy; OpenAPI spec probes also 404, offering no discoverable version metadata.
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.productboard.com/openapi.json, https://developer.productboard.com/swagger.json, ht…”
Analytics insights — stories about analytics insights in this arenaAnalytics insights
Stories about analytics insights in this arena
Reporting
ai-native userUse AI to declutter raw feedback and surface the most impactful opportunities
weight 3 · round drawnFeaturebase 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.”
Productboard's docs claim automatic AI-driven insight detection linking feedback to feature ideas and a centralized searchable feedback repository, which directly supports decluttering raw feedback, and its MCP/API layer lets automation update prioritization fields (value, risk, impact, effort). However, there is no detailed documentation of an AI feature that explicitly ranks or surfaces 'most impactful opportunities' beyond basic insight linking, and no independent/hands-on evidence validating this capability. Missing for 10: dedicated AI opportunity-scoring/ranking feature documentation, independent user validation of insight quality, and clearer detail on how 'impactful' is determined.
- [claimed-docs] “Productboard automatically detects insights within feedback that can be linked to related feature ideas.”
- [claimed-docs] “Access one searchable repository for all product requests and feedback from colleagues and customers.”
- [claimed-docs] “Ensure developers are working on what really matters by sharing customer context and only sending fully-validated features into delivery.”
- [claimed-docs] “Update custom drivers and other data fields on features and initiatives (like value, risk, impact, confidence, and effort) to automate prior…”
product-managerAccess customer context alongside feedback so I prioritize what really matters
weight 2 · round to ProductboardFeaturebase 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.”
Productboard associates feedback with users/companies and links notes to features to quantify demand, provides a single searchable repository for requests/feedback, and surfaces automatic insight detection with citations tying feedback to evidence, directly supporting customer-context-informed prioritization. missing for 10: independent/hands-on validation from PM users of the customer-context view and quantitative proof of prioritization impact.
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities.”
- [claimed-docs] “Ensure developers are working on what really matters by sharing customer context and only sending fully-validated features into delivery.”
- [claimed-docs] “Access one searchable repository for all product requests and feedback from colleagues and customers.”
- [claimed-docs] “Productboard automatically detects insights within feedback that can be linked to related feature ideas.”
- [claimed-docs] “Understand critical feedback trends and act fast on new opportunities. Productboard includes citations for every finding, so decisions are a…”
- [claimed-docs] “Notes can be linked to features to quantify demand and inform prioritization.”
ai-native userAsk an AI assistant questions about customer feedback themes and their revenue impact
weight 3 · round to ProductboardFeaturebasenone0/10Featurebase'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.”
Productboard's MCP server lets AI agents create/update features and initiatives, and it auto-detects insights linking feedback to features, suggesting some AI-native querying capability over feedback data. However, there is no evidence of an AI assistant answering natural-language questions about feedback themes or their revenue impact—the Analytics API is scoped to workspace usage metrics, not customer feedback/revenue correlation. Missing for 10: evidence of a conversational AI/analytics feature that surfaces feedback theme summaries, revenue impact metrics, or any linkage between feedback and revenue data.
- [claimed-docs] “Now you can use any agent to add new features, reschedule an initiative, or start building off a product specification.”
- [claimed-docs] “Productboard automatically detects insights within feedback that can be linked to related feature ideas.”
- [claimed-docs] “The Analytics API provides access to usage data that helps you understand how Productboard is being adopted and used across your workspace.”
- [probe] “official MCP server documented at https://www.productboard.com/integrations/mcp-server/”
product-managerRetrieve usage analytics to understand how the product is adopted across my workspace
weight 2 · round to ProductboardFeaturebasenone0/10The evidence pack covers webhooks, integrations, changelogs, help center, and AI agents, but contains no mention of an analytics/reporting feature for tracking product adoption or usage across a workspace. Since Featurebase is a feedback/roadmap platform where usage analytics could plausibly be a feature, the lack of any supporting evidence yields 'none' rather than 'na'.
Productboard explicitly documents an Analytics API providing usage data on adoption across the workspace, and notes this can feed internal dashboards, directly matching the story. However, there is no first-party dashboard/report UI evidence, no sample metrics/fields list, and no independent corroboration of what analytics are actually surfaced. missing for 10: details on specific adoption metrics tracked, a native analytics dashboard UI (not just API), and independent/hands-on validation of the Analytics API's output.
- [claimed-docs] “The Analytics API provides access to usage data that helps you understand how Productboard is being adopted and used across your workspace.”
- [claimed-docs] “These metrics can be used to: Build internal dashboards”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to ProductboardFeaturebasenone0/10Evidence 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…”
Productboard's REST API supports cursor-based pagination for list/search endpoints and explicitly mentions 'bulk operations' for document management, plus general create/update/delete across features, feedback, and other entities that an AI-native user (via scripts or MCP-connected agents) could loop through for bulk actions. However, there's no documented native batch/bulk-update endpoint (e.g., a single call to update many items at once) outside of the one document-specific mention, and the MCP server examples focus on single-item actions rather than explicit multi-item bulk operations. Missing for 10: dedicated bulk-update/bulk-create API endpoints across all entity types, explicit bulk-operation support in the MCP tool set, and independent evidence of an AI agent performing true bulk operations at scale.
- [claimed-docs] “Create and manage editor documents and product document boards, with support for bulk operations, document templates, and thread and comment…”
- [claimed-docs] “For large result sets, both the list and search endpoints support cursor-based pagination.”
- [claimed-docs] “List and search feedback with structured filters by owner, creator, tags, date range, and status. For large result sets, both the list and s…”
- [claimed-docs] “The Productboard REST API uses cursor-based pagination for all endpoints that return a list of results.”
- [claimed-docs] “Create and update features, subfeatures, initiatives, releases, objectives, key results, companies, users, feedback, documents, and more dir…”
- [claimed-docs] “The Productboard MCP server lets your coding agent read product specs straight from Productboard — and write back to them.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to FeaturebaseFeaturebase 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.”
Productboard's Webhooks API lets users subscribe to entity-change events and receive real-time notifications, and the REST/MCP APIs allow subsequent actions to be scripted in response — but this requires building custom integration code rather than a native declarative 'if this event then this action' rules engine inside the product. Missing for 10: evidence of a built-in no-code automation/rules builder, conditional logic across multiple triggers, and any UI for defining action chains without custom webhook-consumer code.
- [claimed-docs] “The Webhooks API allows you to subscribe to events in Productboard and receive real-time notifications when data changes.”
- [claimed-docs] “Subscribe to entity change events and receive real-time notifications at your endpoint.”
- [claimed-docs] “Creates a new webhook subscription to be actively notified on each change in the specified entities.”
- [claimed-docs] “Permanently deletes a webhook subscription. No further notifications will be sent after deletion.”
- [claimed-docs] “Create and update features, subfeatures, initiatives, releases, objectives, key results, companies, users, feedback, documents, and more dir…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnFeaturebasenone0/10Evidence 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.”
Productboardnone0/10Evidence shows Productboard has webhooks (event-driven push), a REST API, and an MCP server for agent-driven actions, but nothing describes scheduling recurring jobs, cron-like automation, or timed/repeating workflows. The axis applies (automation platforms commonly offer this) but no supporting evidence exists.
ai-native userVersion, review, and roll back my automations
weight 1 · round drawnFeaturebasenone0/10Featurebase offers basic workflow automation (SLAs, trial extensions) but no evidence of version history, review process, or rollback capability for automations/workflows.
Productboardnone0/10The evidence pack covers Productboard's API, webhooks, MCP server, and integrations for reading/writing product data, but there is no mention of any versioning, review, or rollback mechanism for automations, workflows, or agent actions—no changelog, audit history, undo, or approval-based automation review capability is documented anywhere.
Automation workflows — building automations — triggers, actions, branching, schedulingAutomation workflows
Building automations — triggers, actions, branching, scheduling
Changelog
product-managerServe a fully branded public changelog page on a custom domain
weight 2 · round to FeaturebaseDocs 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.”
Productboardnone0/10No evidence in the pack mentions a public changelog feature, custom domain hosting, or branding for a changelog page; all evidence concerns API, webhooks, MCP server, and integrations. This is a plausible feature for a product management tool (Productboard historically has a Portal/changelog-adjacent feature area), so the axis applies, but nothing in the evidence supports it.
product-managerLet customers subscribe to email updates when new changelog entries are published
weight 1 · round to FeaturebaseFeaturebase 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.”
Productboardnone0/10The evidence pack covers Productboard's API, webhooks, MCP server, and integrations, but contains no mention of a customer-facing changelog feature or an email subscription mechanism for changelog updates. This is a plausible feature for a product-management tool, so the axis applies, but no evidence supports it.
developerShowcase new updates within my product using an embeddable changelog widget
weight 2 · round to FeaturebaseFeaturebase 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.”
Productboardnone0/10Productboard's evidence pack covers REST API, webhooks, MCP server, and integrations for feedback/roadmap data, but there is no mention of a public-facing embeddable changelog widget for showcasing product updates to end users. This is a plausible feature for a product management tool (e.g., similar to 'What's New' widgets), but no evidence shows it exists.
product-managerPublish a changelog announcing shipped features to close the loop with customers
weight 3 · round to FeaturebaseFeaturebase 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.”
Productboardnone0/10While Productboard emphasizes closing the loop between specification, delivery, and outcome (productboard-docs-23) and offers rich APIs/integrations for pushing data to delivery tools, there is no evidence of a dedicated changelog/release-notes publishing feature for announcing shipped features to customers. Missing for 10: any mention of a customer-facing changelog or release-notes publishing tool, templates, or distribution channel (email, in-app, public page).
Lifecycle automation
product-managerBuild automated workflows for SLAs, trial extensions, and discount offers triggered by feedback events
weight 2 · round to FeaturebaseFeaturebase'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.”
Productboardnone0/10Productboard offers generic Webhooks/REST APIs for feedback events, but there is no evidence of built-in or documented workflow automation for SLAs, trial extensions, or discount offers — these are outside Productboard's feedback/roadmap product scope and no such workflow builder or triggers are described.
- [claimed-docs] “The Webhooks API allows you to subscribe to events in Productboard and receive real-time notifications when data changes.”
- [claimed-docs] “Create, search, and manage feedback, documents, customers, and product data through Productboard's REST API.”
product-managerAutomatically notify customers when the status of their requested feature changes
weight 2 · round to FeaturebaseFeaturebase 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.”
Productboard exposes a Webhooks API that fires real-time notifications when entity data (e.g., feature status) changes, and feedback entries can be linked to customers, so a PM could build an automation to notify requesters. However, there is no evidence of a native, built-in 'notify customer when feature status changes' feature — it would require custom integration work using the webhook/API to reach customers. Missing for 10: a documented native customer-notification feature (e.g., automated customer emails on status change), evidence of end-to-end customer messaging rather than just internal event triggers, and any hands-on confirmation this workflow is used in practice.
- [claimed-docs] “The Webhooks API allows you to subscribe to events in Productboard and receive real-time notifications when data changes.”
- [claimed-docs] “Subscribe to entity change events and receive real-time notifications at your endpoint.”
- [claimed-docs] “Creates a new webhook subscription to be actively notified on each change in the specified entities.”
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities.”
- [claimed-docs] “Notes can be linked to features to quantify demand and inform prioritization.”
product-managerSegment product release announcements by user attributes to send targeted release notes
weight 2 · round to FeaturebaseFeaturebase 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.”
Productboardnone0/10Evidence shows release grouping and general product data management, but nothing about segmenting or sending targeted release-note announcements based on user attributes. Productboard's docs cover feedback, integrations, MCP server, and API endpoints, none of which address customer-facing release note personalization or segmentation.
Capture intake — getting things in fast — capture, import, inbox flowsCapture intake
Getting things in fast — capture, import, inbox flows
Centralized repository
product-managerAutomatically capture customer feedback mentioned in sales calls, support tickets, and chat conversations
weight 3 · round drawnFeaturebase'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…”
Productboard's API/webhooks let feedback be routed in from CRMs, internal tools, and other sources, and it offers a single searchable feedback repository with automatic insight detection, but there's no direct evidence of native, purpose-built connectors that auto-capture from sales calls, support tickets, or chat tools (e.g. Gong, Zendesk, Intercom) — only generic API-based ingestion is documented. missing for 10: named native integrations for sales-call/support-ticket/chat capture, evidence of automatic (not developer-built) capture pipelines, and independent confirmation of these integrations working in practice.
- [claimed-docs] “Create, search, and manage feedback, documents, customers, and product data through Productboard's REST API.”
- [claimed-docs] “Developers and technical teams use it to route feedback from proprietary CRMs, internal tools, and other non-native sources into Productboar…”
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities.”
- [claimed-docs] “Access one searchable repository for all product requests and feedback from colleagues and customers.”
- [claimed-docs] “Productboard automatically detects insights within feedback that can be linked to related feature ideas.”
product-managerAccess one searchable repository for all product requests and feedback from colleagues and customers
weight 3 · round to ProductboardFeaturebase 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.”
Productboard's own docs explicitly state the exact capability ("Access one searchable repository for all product requests and feedback from colleagues and customers"), reinforced by feedback API features supporting associating feedback with users/companies and searching across it. missing for 10: independent/hands-on corroboration beyond vendor docs.
- [claimed-docs] “Access one searchable repository for all product requests and feedback from colleagues and customers.”
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities.”
- [claimed-docs] “Productboard automatically detects insights within feedback that can be linked to related feature ideas.”
product-managerLink individual feedback items to the specific customers who submitted them
weight 2 · round to ProductboardFeaturebasenone0/10The 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…”
Productboard's API and product docs explicitly support associating feedback with customers/companies, with dedicated attribution fields and relationship endpoints (create/list/delete), plus UI-level customer attribution on feedback capture. missing for 10: no independent/hands-on corroboration of the linking UX beyond vendor docs, and no explicit detail on how attribution surfaces in the feedback list/search UI.
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities.”
- [claimed-docs] “Create, read, update, delete, and search customer feedback, complete with text content, tags, owners, source metadata, and customer attribut…”
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities. Dedicated endpoin…”
- [claimed-docs] “Access one searchable repository for all product requests and feedback from colleagues and customers.”
product-managerReply to customers directly from within the feedback record to close the loop
weight 2 · round to FeaturebaseFeaturebase'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.”
Productboardnone0/10Evidence covers feedback capture, tagging, linking to features, and API/webhook management, but nothing describes a customer-facing reply mechanism from within a feedback record. The 'close the loop' mention (docs-23) refers to specification-to-shipped tracking, not customer communication, so this specific capability is unevidenced.
Embeddable widget
product-managerCustomize the feedback widget's label and colors to match my brand
weight 1 · round drawnFeaturebasenone0/10The 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.
developerEmbed a feedback widget on my website with a single script tag and no build step
weight 3 · round to FeaturebaseFeaturebase 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…”
developerIdentify logged-in users when they submit feedback so it ties to their existing account
weight 2 · round to ProductboardFeaturebasenone0/10None 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.
Productboard's API explicitly supports associating feedback with existing users and companies, and docs mention routing feedback from CRMs/internal tools into user records (productboard-docs-4, productboard-docs-2), which implies developers can tie submitted feedback to an existing account. However, there is no evidence of a specific mechanism for identifying a 'logged-in' end user at submission time (e.g., SSO/JWT-based identification in a feedback widget or portal). Missing for 10: documentation of end-user authentication/identification flow for feedback submission, widget/portal-specific user linking, and independent confirmation of this behavior.
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities.”
- [claimed-docs] “Developers and technical teams use it to route feedback from proprietary CRMs, internal tools, and other non-native sources into Productboar…”
Public portal
developerAdd a link in my product that directs users to the feedback portal
weight 1 · round to FeaturebaseFeaturebase'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…”
Productboardnone0/10The evidence pack covers Productboard's API, webhooks, MCP server, and third-party integrations, but contains no mention of a customer-facing feedback Portal or an embeddable link/widget that developers could add to their product to direct users to submit feedback. This capability is plausible for a product-feedback tool but is simply unevidenced here.
product-managerHost a public feedback portal where customers submit and vote on ideas
weight 3 · round to FeaturebaseFeaturebase 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…”
Productboardnone0/10The evidence pack covers Productboard's API, webhooks, MCP server, and internal feedback repository, but contains no mention of a public-facing customer portal where customers submit and vote on ideas. Missing for 10: any documentation of a public portal, idea submission form, or voting mechanism for customers.
Feedback to tasks — stories about feedback to tasks in this arenaFeedback to tasks
Stories about feedback to tasks in this arena
Convert to work
ai-native userHave AI turn a plain-language feedback description into a structured set of proposed tasks
weight 3 · round to ProductboardFeaturebasenone0/10Featurebase 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.”
Productboard's auto-insight detection links feedback to feature ideas (docs-16) and its MCP server lets AI agents create features/initiatives from context (docs-10–13), which is adjacent to turning feedback into structured work items, but there is no explicit documentation of AI parsing a plain-language feedback description into a distinct, structured set of proposed tasks. missing for 10: explicit feature/doc showing AI decomposing a single feedback item into multiple structured task proposals, evidence of task granularity (subtasks, acceptance criteria), independent/hands-on confirmation of this specific workflow.
- [claimed-docs] “Productboard automatically detects insights within feedback that can be linked to related feature ideas.”
- [claimed-docs] “Now you can use any agent to add new features, reschedule an initiative, or start building off a product specification.”
- [claimed-docs] “Update custom drivers and other data fields on features and initiatives (like value, risk, impact, confidence, and effort) to automate prior…”
- [claimed-docs] “Access your latest product specifications from coding agents and AI prototyping tools to initiate the product delivery process.”
product-managerReview and approve the scope of a task before any work begins on it
weight 2 · round to ProductboardFeaturebasenone0/10Featurebase'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.
Productboard's docs mention gating delivery on 'fully-validated features' and using specs to 'initiate the product delivery process', implying a review step before work begins, but there's no explicit evidence of a formal approval/sign-off workflow, status gate, or scope-lock mechanism a PM would use to approve a task. missing for 10: explicit approval/status workflow documentation, evidence of a sign-off step or scope lock before handoff to engineering, independent corroboration of this gating in practice.
- [claimed-docs] “Ensure developers are working on what really matters by sharing customer context and only sending fully-validated features into delivery.”
- [claimed-docs] “Access your latest product specifications from coding agents and AI prototyping tools to initiate the product delivery process.”
- [claimed-docs] “Access one searchable repository for all product requests and feedback from colleagues and customers.”
product-managerTurn a customer feedback submission directly into an actionable task or project intention
weight 3 · round to ProductboardFeaturebase 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.”
Productboard has a core feedback repository that automatically detects insights linkable to feature ideas, notes can be linked to features to quantify demand, and features can be pushed into delivery/tracked—directly supporting turning feedback into actionable tasks/initiatives. This is reinforced by API/MCP capabilities to create feedback, link it to features/initiatives, and push prioritized features into delivery. Missing for 10: independent/hands-on verification of the feedback-to-feature workflow UI and any case-study evidence of PM usage in practice.
- [claimed-docs] “Productboard automatically detects insights within feedback that can be linked to related feature ideas.”
- [claimed-docs] “Notes can be linked to features to quantify demand and inform prioritization.”
- [claimed-docs] “Ensure developers are working on what really matters by sharing customer context and only sending fully-validated features into delivery.”
- [claimed-docs] “Push prioritized features into delivery, track their status, and sync key data.”
- [claimed-docs] “Access one searchable repository for all product requests and feedback from colleagues and customers.”
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities.”
- [claimed-docs] “Create, read, update, delete, and search customer feedback, complete with text content, tags, owners, source metadata, and customer attribut…”
developerPull an approved product specification into the delivery workflow to start implementation
weight 2 · round to ProductboardFeaturebase 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.”
Productboard's MCP server explicitly lets coding agents and AI prototyping tools pull approved specs directly into the delivery workflow ('Access your latest product specifications from coding agents... to initiate the product delivery process', 'Pull a spec, talk through the plan with your agent, and build'), plus GitHub/Jira push-to-dev integrations and a REST API for programmatic access. Missing for 10: independent/hands-on developer confirmation that the workflow works smoothly in practice beyond vendor docs.
- [claimed-docs] “Now you can use any agent to add new features, reschedule an initiative, or start building off a product specification.”
- [claimed-docs] “Access your latest product specifications from coding agents and AI prototyping tools to initiate the product delivery process.”
- [claimed-docs] “The Productboard MCP server lets your coding agent read product specs straight from Productboard — and write back to them.”
- [claimed-docs] “Pull a spec, talk through the plan with your agent, and build. No setup beyond the connection.”
- [claimed-docs] “Push prioritized features into delivery, track their status, and sync key data.”
- [claimed-docs] “Push features ready for development into GitHub as issues.”
- [claimed-docs] “Ensure developers are working on what really matters by sharing customer context and only sending fully-validated features into delivery.”
product-managerWatch the real-time status of each in-progress task, including what it's blocked on and its last update
weight 2 · round drawnFeaturebasenone0/10Evidence 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.”
Productboardnone0/10Productboard's evidence covers pushing prioritized features into delivery tools and syncing status/key data (e.g., docs-20, docs-23), but there is no evidence of a real-time view showing what a specific in-progress task is blocked on or its last update timestamp — that granularity lives in delivery tools like Jira that Productboard integrates with, not in Productboard itself.
- [claimed-docs] “Push prioritized features into delivery, track their status, and sync key data.”
- [claimed-docs] “Close the loop between what you specified, what you shipped, and whether it actually worked.”
- [claimed-docs] “Productboard Integrations | Jira, Azure DevOps, Zendesk & More”
- [claimed-docs] “Push features ready for development into GitHub as issues.”
Integrations — connecting to other tools — breadth and depth of built-in integrationsIntegrations
Connecting to other tools — breadth and depth of built-in integrations
Tool connections
product-managerConnect feedback capture to support, sales, and chat tools I already use
weight 3 · round to FeaturebaseFeaturebase 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.”
Productboard's API and webhook capabilities (docs-1, docs-2, docs-5) let feedback be routed in from CRMs and other external systems, and custom integrations can be built into the UI, which technically enables connecting support/sales/chat data sources. However, the evidence pack contains no mention of specific pre-built native connectors for common support, sales, or chat tools (e.g., named integrations), only generic REST/webhook/custom-integration capability. Missing for 10: named native integrations with support/sales/chat platforms, evidence of a marketplace/app directory, and independent confirmation of ease-of-setup for non-technical PMs.
- [claimed-docs] “Create, search, and manage feedback, documents, customers, and product data through Productboard's REST API.”
- [claimed-docs] “Developers and technical teams use it to route feedback from proprietary CRMs, internal tools, and other non-native sources into Productboar…”
- [claimed-docs] “The Webhooks API allows you to subscribe to events in Productboard and receive real-time notifications when data changes.”
- [claimed-docs] “Use this to build custom integrations that appear and operate inside the Productboard UI.”
developerBuild custom integrations that appear and operate directly inside the product's own interface
weight 1 · round to ProductboardFeaturebasenone0/10Evidence 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.”
First-party docs explicitly state you can 'build custom integrations that appear and operate inside the Productboard UI' (docs-7) and describe an API/webhooks platform for extending Productboard (intdir-10, docs-5, docs-31), which supports the core claim. However, there's no detail on an actual UI-extension SDK, embed points, or hands-on/independent confirmation of what such an in-UI integration looks like in practice. Missing for 10: concrete UI-extension developer docs/SDK, third-party example integrations that embed in the Productboard UI, and independent corroboration beyond vendor marketing copy.
- [claimed-docs] “Use this to build custom integrations that appear and operate inside the Productboard UI.”
- [claimed-docs] “Extend Productboard's capabilities, connect it with other tools, update product data programmatically, develop your own integrations, and pr…”
- [claimed-docs] “The Webhooks API allows you to subscribe to events in Productboard and receive real-time notifications when data changes.”
- [claimed-docs] “API v2 introduces a new concept: configuration endpoints that describe the shape of data in your workspace.”
- [claimed-docs] “You can retrieve the ID of any entity from within Productboard without having to call an API endpoint.”
product-managerConnect common third-party tools to my feedback workspace in just a few clicks
weight 2 · round drawnMarketing 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.”
Evidence focuses on API/webhooks/MCP server for building custom integrations, which requires developer effort rather than a few-click connection for a PM. There's no mention of a pre-built integrations marketplace or one-click connectors (e.g., Slack, Jira, Salesforce) that a non-technical PM could enable directly. Missing for 10: evidence of a native integrations directory/marketplace with one-click setup, no-code connector examples, and PM-facing (not developer-facing) setup flow.
- [claimed-docs] “Create, search, and manage feedback, documents, customers, and product data through Productboard's REST API.”
- [claimed-docs] “Developers and technical teams use it to route feedback from proprietary CRMs, internal tools, and other non-native sources into Productboar…”
- [claimed-docs] “Use this to build custom integrations that appear and operate inside the Productboard UI.”
- [probe] “official MCP server documented at https://www.productboard.com/integrations/mcp-server/”
Onboarding — getting started and time-to-first-value storiesOnboarding
Getting started and time-to-first-value stories
Setup
product-managerUse a rich text editor with custom components to format changelog and help content
weight 1 · round to FeaturebaseDocs 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.”
Productboardnone0/10The evidence pack mentions 'editor documents' and document management via the API, but nothing describes a rich text editor with custom components, nor any changelog or help-content authoring feature for product managers. Missing for 10: any documentation of a WYSIWYG/rich text editor, custom embeddable components, or changelog/help-center publishing capability.
product-managerSet up a public-facing feedback portal without engineering help
weight 2 · round to FeaturebaseFeaturebase 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.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to ProductboardFeaturebase 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.”
Productboard's REST API (v2) and MCP server cover most core objects—features, initiatives, releases, objectives, key results, feedback, documents, teams, companies, users, webhooks, and custom fields—letting AI agents create/update/query nearly all major workspace entities also editable in the UI. However, there's no discoverable OpenAPI/swagger spec (probe returned 404s), no vendor claim of 100% UI-API parity, and some UI-only workflows (e.g., insights auto-detection, Spark synthesis agent, deep configuration/admin settings) aren't clearly exposed via API. Missing for 10: a published complete OpenAPI schema, explicit parity statement, and independent confirmation that all UI actions (not just major entities) are API-accessible.
- [claimed-docs] “Create, search, and manage feedback, documents, customers, and product data through Productboard's REST API.”
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities.”
- [claimed-docs] “You can create and update teams, retrieve team details, and manage team membership by adding or removing members.”
- [claimed-docs] “The Teams API allows you to programmatically manage teams in your Productboard workspace.”
- [claimed-docs] “Create and update features, subfeatures, initiatives, releases, objectives, key results, companies, users, feedback, documents, and more dir…”
- [claimed-docs] “Create and manage editor documents and product document boards, with support for bulk operations, document templates, and thread and comment…”
- [claimed-docs] “The Webhooks API allows you to subscribe to events in Productboard and receive real-time notifications when data changes.”
- [claimed-docs] “Sync objectives between Productboard and your OKR tool (e.g., Lattice, Ally.io, Gtmhub) to keep strategy aligned.”
- [claimed-docs] “If you have multiple teams working out of the same workspace, each using a different release system, you can manage each as a separate relea…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.productboard.com/openapi.json, https://developer.productboard.com/swagger.json, ht…”
- [claimed-docs] “The Productboard MCP server lets your coding agent read product specs straight from Productboard — and write back to them.”
ai-native userExport all of my data in open formats and leave
weight 3 · round to ProductboardFeaturebasenone0/10No 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.
Productboard's REST API v2 lets users programmatically read/list virtually all entities (feedback, features, documents, customers, teams) with cursor-based pagination, which effectively enables a full data export via JSON over HTTP — an open, non-proprietary format and mechanism to leave with your data intact. However, there is no documented one-click 'export all my data' feature, no explicit mention of bulk/GDPR-style data export or account-closure export guarantee, and no confirmation of formats beyond implied JSON via REST responses. Missing for 10: a dedicated bulk/full-account export tool, explicit open-format guarantees (e.g., CSV/JSON export docs), and evidence of a data-portability/account-deletion export flow.
- [claimed-docs] “Create, search, and manage feedback, documents, customers, and product data through Productboard's REST API.”
- [claimed-docs] “For large result sets, both the list and search endpoints support cursor-based pagination.”
- [claimed-docs] “Create, read, update, delete, and search customer feedback, complete with text content, tags, owners, source metadata, and customer attribut…”
- [claimed-docs] “List and search feedback with structured filters by owner, creator, tags, date range, and status. For large result sets, both the list and s…”
- [claimed-docs] “Create and manage editor documents and product document boards, with support for bulk operations, document templates, and thread and comment…”
- [claimed-docs] “The Productboard REST API uses cursor-based pagination for all endpoints that return a list of results.”
Prioritization roadmapping — stories about prioritization roadmapping in this arenaPrioritization roadmapping
Stories about prioritization roadmapping in this arena
Insights surfacing
ai-native userRely on AI to automatically detect insights within feedback and link them to related feature ideas
weight 2 · round to ProductboardFeaturebase 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.”
Productboard's marketing docs explicitly claim automatic insight detection linked to feature ideas, with citations for findings, but this is described only at a high marketing level with no technical documentation, independent validation, or hands-on evidence of accuracy/scope. Missing for 10: technical/API documentation of the insight-detection mechanism, independent or hands-on verification of accuracy, and detail on how linking to feature ideas actually works in practice.
- [claimed-docs] “Productboard automatically detects insights within feedback that can be linked to related feature ideas.”
- [claimed-docs] “Understand critical feedback trends and act fast on new opportunities. Productboard includes citations for every finding, so decisions are a…”
- [claimed-docs] “Go from new idea to delivery-ready in a fraction of the time. Productboard's built-in agent handles all the information synthesis”
Scoring
product-managerLink feedback requests to roadmap features, initiatives, and releases
weight 3 · round to ProductboardFeaturebase'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.”
Productboard's core product model explicitly links feedback/notes to features, and the API/MCP docs confirm associating feedback with features, adding features to initiatives, and moving initiatives to releases. This is a core, well-documented native capability, not just a workaround via API. missing for 10: independent/hands-on user corroboration of the linking workflow in the UI (all evidence is vendor documentation).
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities.”
- [claimed-docs] “Add features to initiatives, move an initiative to a new release, or create key results beneath an objective.”
- [claimed-docs] “Notes can be linked to features to quantify demand and inform prioritization.”
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities. Dedicated endpoin…”
- [claimed-docs] “Productboard automatically detects insights within feedback that can be linked to related feature ideas.”
- [claimed-docs] “Create and update features, subfeatures, initiatives, releases, objectives, key results, companies, users, feedback, documents, and more dir…”
product-managerScore feedback and ideas using fields like value, risk, impact, confidence, and effort
weight 3 · round to ProductboardFeaturebasenone0/10No 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.
Productboard's docs explicitly reference custom fields/drivers such as value, risk, impact, confidence, and effort on features/initiatives, and both the product data model and MCP server allow updating these to drive prioritization workflows. Missing for 10: no independent/hands-on corroboration of a dedicated scoring UI or formulaic scoring model, and no direct screenshot/first-party doc showing all five named fields together in a native scorecard.
- [claimed-docs] “Update custom drivers and other data fields on features and initiatives (like value, risk, impact, confidence, and effort) to automate prior…”
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities.”
- [claimed-docs] “Ensure developers are working on what really matters by sharing customer context and only sending fully-validated features into delivery.”
product-managerOrganize requests into a hierarchy of features, components, and initiatives
weight 2 · round to ProductboardFeaturebasenone0/10The 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.
Productboard's core product model natively supports organizing feedback/requests into features, subfeatures, components, initiatives, releases, objectives and key results, with API and MCP evidence confirming these hierarchy entities and the ability to link feedback and features to them (e.g., docs-4, docs-19, docs-29, docs-12, docs-47). This directly matches the story of organizing requests into a feature/component/initiative hierarchy. Missing for 10: independent/hands-on corroboration beyond vendor docs and a clearer description of the component-level UI hierarchy itself (most detail is API/MCP-centric rather than native UI workflow).
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities.”
- [claimed-docs] “Create and update features, subfeatures, initiatives, releases, objectives, key results, companies, users, feedback, documents, and more dir…”
- [claimed-docs] “Associate feedback with users and companies, and connect it to features, components, and other product hierarchy entities. Dedicated endpoin…”
- [claimed-docs] “Add features to initiatives, move an initiative to a new release, or create key results beneath an objective.”
- [claimed-docs] “Notes can be linked to features to quantify demand and inform prioritization.”
- [claimed-docs] “Access one searchable repository for all product requests and feedback from colleagues and customers.”
product-managerReschedule initiatives and move them between releases as priorities change
weight 2 · round to ProductboardFeaturebasenone0/10The 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.
Productboard's core roadmap model explicitly supports releases and initiatives, and both docs and MCP-server pages state you can 'reschedule an initiative' and 'move an initiative to a new release' directly, including via API/agent workflows. This is native product functionality (not just a third-party workaround), covering the exact story described. missing for 10: no independent/hands-on UI walkthrough or screenshot showing the drag-and-drop reschedule experience in the roadmap view, only docs/MCP references.
- [claimed-docs] “Now you can use any agent to add new features, reschedule an initiative, or start building off a product specification.”
- [claimed-docs] “Add features to initiatives, move an initiative to a new release, or create key results beneath an objective.”
- [claimed-docs] “Create and update features, subfeatures, initiatives, releases, objectives, key results, companies, users, feedback, documents, and more dir…”
- [claimed-docs] “If you have multiple teams working out of the same workspace, each using a different release system, you can manage each as a separate relea…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnFeaturebasenone0/10No 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.
Productboardnone0/10No evidence in the pack addresses data residency, region selection, or storage location controls; all evidence concerns API, MCP, and integration capabilities. Missing for 10: any mention of data residency options, EU/US hosting choice, or compliance documentation addressing storage location.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnFeaturebasenone0/10No 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.
ai-native userControl data retention and deletion
weight 2 · round drawnFeaturebasenone0/10No 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.
Productboardnone0/10The evidence pack covers API/webhook/MCP capabilities extensively but contains no mention of data retention policies, deletion of stored customer/product data for privacy purposes, GDPR/right-to-be-forgotten controls, or data export/purge tooling. This axis is applicable to a SaaS platform storing customer feedback data, but no supporting evidence exists.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnFeaturebasenone0/10No 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.
Not comparable on these axes
developerJump directly to any feedback item, task, or initiative by typing its short name
weight 1 · not comparableFeaturebasen/aThis story describes a developer navigation/shortcut feature (jumping to items by short name/ID), which is an IDE or project-management UI convenience, not applicable to Featurebase's feedback/changelog management product category.
Productboardnone0/10No evidence describes a quick-open or 'jump to' navigation feature where a developer types a short name/ID to instantly open a feedback item, task, or initiative. Evidence only covers retrieving entity IDs via the API/UI (docs-46) and general search repositories (docs-15), which is a different capability.
ai-native userRead the product's source under an open license
weight 2 · not comparableFeaturebasenone0/10No 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.
ai-native userSelf-host the core product
weight 3 · not comparableFeaturebasen/aFeaturebase is a hosted SaaS feedback/support platform with no evidence of a self-hosted deployment option; self-hosting is not a claimed or implied capability of this product category as evidenced here, making this a category mismatch rather than a missing feature.