Use cases / Clawbrowser demo / 1:01

Build competitive intelligence from customer reviews

Compare public DuoPlus and GeeLark feedback to identify complaints, strengths, sentiment, and competitive opportunities.

Published · @next_ossaiWatch on YouTube ↗

Overview

Customer feedback can explain why buyers choose or leave products, but isolated comments are easy to overinterpret. This Clawbrowser demo compares public feedback about DuoPlus and GeeLark across multiple platforms.

What happens in the video

The agent researches DuoPlus and GeeLark through G2, Reddit, and Google, then displays an opinions spreadsheet and comparison dashboard. It reports 126 opinions against a target of 300 and says Trustpilot and Product Hunt returned no useful material. The dashboard shows 26 DuoPlus and 101 GeeLark opinions, so the visible totals need reconciliation before reuse.

Before you start

  • Competitors and public review sources.
  • A collection scope and report structure.

Step-by-step guide

Practical steps for adapting the recorded task. The video summary above describes the demonstrated result; these checks guide your own run.

  1. Collect feedback

    Find public opinions for each competitor and retain product and source URLs. In the recording, G2, Reddit, and Google supply material while Trustpilot and Product Hunt return no useful results. Report the achieved coverage instead of assuming the requested target was met.

  2. Group recurring themes

    Organize strengths, complaints, and sentiment by topic. Retain contradictory experiences instead of forcing all reviews into one conclusion.

  3. Write the comparison

    Link themes to source observations and separate strategic recommendations from evidence. Reconcile totals before reusing the dashboard: the agent reports 126 opinions, while the visible product counts are 26 and 101. Treat the displayed synthesis as a draft until that discrepancy is resolved.

Try this prompt

Suggested prompt

Compare public customer feedback about [competitors] from [sources]. Preserve URLs, group recurring strengths and complaints, and compare sentiment. Separate observed evidence from inferred risks and recommendations.

Adapt the placeholders to your task. This is an example prompt, not a transcript of the recording.

Results

  • An opinions spreadsheet and competitor comparison dashboard.
  • Sentiment and theme summaries with a visible count discrepancy that needs reconciliation.

Questions about this workflow

Does this prove market-wide sentiment?

No. Reviews reflect the collected sources and participants. State coverage and preserve conflicting feedback.

Why retain original sources?

They make it possible to distinguish a recurring issue from a single anecdote and inspect its context.

Put the workflow to work

Prepare the browser connection, then adapt the guide to your task and check its output.

Set up Clawbrowser →

Explore the broader use case

Guide reviewed . Source: published video and description.

Related video guides