PulseBot
Public AI product signal

Public feedback around 'feature request tracking' is really a story about scattered, tool-agnostic knowledge management: users praise Notion's flexibility but describe prototype and decision context living in docs, spreadsheets, and memory. The signal matters because the friction is not a missing tracker field but the absence of a single source of truth across teams.

The most decision-relevant takeaway is that users are not asking for a better feature-request form; they are struggling with fragmented knowledge where decisions and prototype context are reconstructed in every meeting, which is the real bottleneck.

9
Evidence
reddit + g2
Sources
Last 15 days
Window
high
Severity
low
Confidence

Snapshot context

Report date
Sep 10, 2026
Evidence window
Last 15 days
Category
Feature requests
Related products
feature request tracking

What makes this snapshot distinct

This snapshot is distinct because it combines g2 + reddit evidence within last 15 days, with 4 quote-backed signals around Feature Request Tracking remains a workflow bottleneck. It also references related products such as feature request tracking.

g2: 3 quotesreddit: 1 quotes

Most important finding

The most decision-relevant takeaway is that users are not asking for a better feature-request form; they are struggling with fragmented knowledge where decisions and prototype context are reconstructed in every meeting, which is the real bottleneck.

Suggested focus

Watch whether users start explicitly naming dedicated feature-request or product-feedback tools as replacements, or whether they continue to stretch general-purpose knowledge bases like Notion to cover this workflow.

AI feedback clusters

Scattered prototype and decision context

Users describe prototype knowledge and decisions living in docs, spreadsheets, or individual memory, so meetings begin with reconstructing context instead of acting on it.

Before this, prototype knowledge lived wherever a given team member kept it: a doc here, a spreadsheet there, decisions that only existed in someone's memory. With four or five prototypes running at once, that meant every meeting started with reconstructing
feature request tracking· g2

Tool consolidation and switching tension

One user frames Notion as a long-term organizing hub while canceling, and another praises its free-plan generosity and customization, showing that even satisfied users weigh whether a general tool is enough for their workflow.

https://preview.redd.it/971ty99jfkoh1.png?width=1919&format=png&auto=webp&s=43bc0c7363afcc5375c6d922b4d7975b30ce1d49 I've been a big Notion fan for about 6 years now. It's been a great place to dump and organize idea and whatever. I actually just canceled my
feature request tracking· redditOpen source
Notion is an indispensable tool in all my activities - personal and business. The fact that I can create a digital platform that is customized to my organizational and workflow needs is unparalleled. Notion is also generous in its features on the free plan
feature request tracking· g2

AI root-cause hypothesis

Hypothesis: feature request tracking is painful because the underlying knowledge is distributed across docs, spreadsheets, and individual memory, so tracking requests without consolidating the surrounding context still forces teams to reconstruct decisions manually.

Product implications

For product teams

Build or position around consolidating request context—decisions, prototype status, and related knowledge—into one searchable place rather than adding another isolated tracking board.

For competitors

Competitors that already own knowledge management or CRM workflows can differentiate by making feature-request context searchable alongside customer and support data, as one quote explicitly compares Notion favorably to Salesforce for finding task-related information.

For startups

A focused startup opportunity is a lightweight layer that connects feature requests to the scattered docs, spreadsheets, and meeting decisions where the real context lives, instead of competing head-on with full knowledge platforms.

Source evidence supporting this signal

https://preview.redd.it/971ty99jfkoh1.png?width=1919&format=png&auto=webp&s=43bc0c7363afcc5375c6d922b4d7975b30ce1d49 I've been a big Notion fan for about 6 years now. It's been a great place to dump and organize idea and whatever. I actually just canceled my
feature request tracking· redditOpen source
Notion is an indispensable tool in all my activities - personal and business. The fact that I can create a digital platform that is customized to my organizational and workflow needs is unparalleled. Notion is also generous in its features on the free plan
feature request tracking· g2
Before this, prototype knowledge lived wherever a given team member kept it: a doc here, a spreadsheet there, decisions that only existed in someone's memory. With four or five prototypes running at once, that meant every meeting started with reconstructing
feature request tracking· g2
Notion is a great knowledge database, and it feels far superior to Salesforce when it comes to quickly finding information or related articles for specific tasks in the customer support and insights industry. My company is paying for Notion, and so far, my
feature request tracking· g2