MCP

AI-agent format

Benchmark your onboarding against rivals' tutorials

Collect competitors' getting-started videos and query them side by side: where do users need hand-holding your flow avoids — or shares?

PMMarket & Competitor Researchdeep_searchlibrary_import_youtube_videodeep_context
The use case

The problem

Every getting-started tutorial is an involuntary confession. When a competitor's own video says "don't worry if the dashboard looks overwhelming at first," that's their onboarding admitting it overwhelms. When a third-party creator makes "the setup guide <rival> should have made," someone found the official path bad enough to fix for free. Minute-by-minute, tutorials document exactly where products need explaining — which is exactly where they failed to be self-explanatory.

Your rivals' confessions are all published. So are yours. A benchmark built from them answers the question your funnel data can't: not where users drop off, but what the drop-off feels like from the chair — and whether the competitor you're losing deals to has the same scar tissue or has actually solved it.

The mechanics

How veridive MCP helps

deep_search assembles the confession corpus: tutorial-type content for each rival product (and yours), both official and third-party — the third-party ones matter most, because nobody makes a workaround video for a flow that works. Evidence timestamps mark where each setup step gets explained.

library_import_youtube_video pins the shortlist into your library so the comparison has a stable base, and deep_context runs the side-by-side: your assistant lists the imported set, passes the item IDs, and asks like a UX researcher: where do tutorials slow down and over-explain? Which steps need a "common mistakes" section? What does the first ten minutes look like, product by product? Answers come back with citations to the exact moments, so the benchmark that lands in your onboarding review quotes the tape — including the uncomfortable clips about your own product.

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
    Collect the tutorial corpus

    Getting-started content per product — official channels and, crucially, third-party fills.

    Find getting-started tutorials for <your product>, <rival A> and <rival B> — official and third-party — use veridive's deep_search.
  3. 3
    Pin the shortlist

    Import the strongest tutorials per product into your library, tagged, so the comparison has a stable, re-queryable base.

    Import the best of those into my veridive library, tagged per product: <video links> — use veridive's library_import_youtube_video.
  4. 4
    Interrogate the friction

    Your assistant lists the imported set and scopes deep_context to those items — asking where the hand-holding concentrates, which is where each product's onboarding actually hurts.

    Across the imported tutorials: where does each product's setup need the most explanation? Which steps get warnings or 'common mistakes' asides? Cite the moments per product.
  5. 5
    Turn it into the benchmark doc

    Have your assistant assemble the comparison: first-run friction by product, who solved what, and the two fixes your flow should steal.

    Draft an onboarding benchmark from these findings: per product, the friction points with citations — and the practices worth adopting in <your product>.
Before vs after

Problems it solves

  • Funnel analytics show where users quit, never what the confusion felt like or how rivals handle the same step.
  • Competitor onboarding is experienced secondhand — a sales-demo memory, not a documented flow.
  • Third-party "how to actually set up X" videos are the strongest UX signal available and completely unmined.
  • Onboarding reviews argue opinions because nobody brings comparable evidence across products.
The payoff

Why it's valuable

  • A benchmark grounded in what tutorials must explain — the closest public proxy to rivals' usability sessions.
  • Your own product gets the same treatment, so the review starts honest.
  • Every friction claim cites a moment on tape; the roadmap conversation skips the anecdote phase.
  • Re-runnable after each rival's redesign — the benchmark stays current for a prompt, not a project.
Copy & paste

Example prompts

Find getting-started tutorials for <your product> and <rivals>, official and third-party — use veridive's deep_search.
Across these tutorials, where does each product need the most hand-holding? Cite moments.
Draft an onboarding benchmark: friction per product, cited, plus practices worth adopting.
Questions

FAQ

Why do third-party tutorials matter more than official ones?

Official videos show the flow the company wishes users had; third-party ones exist because the real flow needed rescuing. The gap between the two is your clearest read on actual friction.

How is the side-by-side comparison scoped?

The shortlisted tutorials are imported into your library and deep_context runs across that selection (up to 20 videos per question), answering with citations to the exact chunks — so per-product comparisons stay traceable.

Can support tickets do this instead?

Tickets cover your product only, post-frustration. Tutorials cover every rival with narrated context — and the two together (their confessions, your tickets) make the strongest onboarding case you can bring.

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.