MCP

AI-agent format

Prioritize features by what reviewers praise vs pan

A cited digest of what gets celebrated and what gets roasted across rival products — prioritization with receipts.

PMProduct & UX Researchdeep_searchdeep_query
The use case

The problem

Every prioritization meeting has the same ghost at the table: "the market." Features get argued for because "the market expects it" and against because "nobody cares about that" — claims about an external reality nobody in the room has measured. The loudest ghost-summoner wins, and the roadmap inherits their guess.

The market's actual opinion is on the record: across your category's review corpus, some capabilities get consistently celebrated (table stakes and delight factors), some get consistently roasted (the pain the category hasn't solved), and some get ignored (checkbox features nobody mentions). That distribution — praise, pan, silence — is the market's feature-level verdict, and it's queryable.

The mechanics

How veridive MCP helps

deep_search assembles the verdict corpus: the category's substantive reviews and comparisons, quality-filtered so the analysis runs over credible assessments rather than spec recitals.

deep_query extracts the distribution: "across reviews of <category>, which capabilities draw consistent praise, which draw criticism, and which go unmentioned?" — answered with citations to the reviews, so the prioritization meeting sees the market's verdict with receipts. Suddenly "the market expects it" is checkable: the feature either recurs in praise, recurs in pans, or lives in the silence column — and the silence column is where checkbox roadmap items go to be exposed.

Step by step

How to run it

  1. 1
    Connect veridive MCP

    One-time setup: add the veridive MCP server to Claude, ChatGPT, Cursor or any MCP client and generate your API key. Takes about two minutes.

  2. 2
    Assemble the verdict corpus

    The category's credible reviews and head-to-heads — quality verdicts filter the spec-readers out.

    Find substantive reviews and comparisons of <category> products — hands-on, credible assessments — use veridive's deep_search.
  3. 3
    Extract the praise/pan/silence map

    The market's feature-level verdict, cited per column.

    Across <category> reviews: which capabilities get consistently praised, which get criticized, and which are never mentioned? Cite the reviews behind each — use veridive's deep_query.
  4. 4
    Cross-examine the roadmap

    Each candidate feature placed on the map — with the receipts attached for the meeting.

    Here's our candidate roadmap: <features>. Place each on the praise/pan/silence map and flag where our internal priority disagrees with the market's verdict.
Before vs after

Problems it solves

  • Prioritization runs on unmeasured claims about 'the market' — the loudest guess wins.
  • The review corpus holds the feature-level verdict and nobody aggregates it.
  • Checkbox features survive on roadmaps because their irrelevance was never demonstrated.
  • Praise patterns (what actually delights) get discovered post-launch instead of pre-roadmap.
The payoff

Why it's valuable

  • The ghost at the table gets replaced by a cited verdict map.
  • The silence column exposes checkbox features before they cost a quarter.
  • Pan patterns show where the category under-delivers — differentiation with demand receipts.
  • Re-runnable per planning cycle; the market's verdict stays current as reviews accumulate.
Copy & paste

Example prompts

Substantive <category> reviews and comparisons — use veridive's deep_search.
Praise vs pan vs never-mentioned across <category>, cited — use veridive's deep_query.
Place our roadmap on that map; flag internal-vs-market disagreements.
Questions

FAQ

Reviews skew toward power users — doesn't that bias the map?

It biases toward articulate, comparative judgment — which is exactly what feature-level verdicts need. Pair with your own user data for the mainstream weight; the map supplies the cross-product view your data can't.

How is this different from the user-pain mining use case?

Pain mining harvests friction moments (usability layer); this aggregates feature-level verdicts (prioritization layer). One feeds UX fixes, the other feeds roadmap bets — teams typically run both.

Can it compare our product's verdict to rivals'?

Directly — ask for the praise/pan split per product. Where you're panned and a rival is praised is your gap list; the reverse is your marketing's underused ammunition.

Keep going

Related use cases

Run this in your own assistant

Connect the veridive MCP server to Claude, ChatGPT or Cursor and paste the prompts above — setup takes about two minutes.