Skip to content
agentusehub
Sign in+ Submit
Sales, Marketing & SupportAny

Do sales research and compare app to mock-ups

Commenters use Claude in Chrome for sales research and to compare an app against mock-ups across tabs, producing a UX/UI differences document.

Read the experience
Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

Commenters use Claude in Chrome for sales research and to compare an app against mock-ups across tabs, producing a UX/UI differences document.

Read the original report ↗

Reported experience

  1. What they did

    In the thread, one commenter describes opening two Chrome tabs—an HTML mockups file and the live app—and asking Claude in Chrome to move through both and produce a document listing UX/UI differences. They then used that feedback in Claude Code to fix issues; another commenter says they use the extension for sales research, including quick company research before outreach and drafting personalized LinkedIn messages and emails.

  2. How it went

    The source presents both as practical, repeated uses rather than experiments, but gives no quantified results. The only stated limitation is that the comparison output still needed a person to take the findings into Claude Code and make fixes.

  3. Worth knowing

    The useful catch is the workflow split: Claude in Chrome gathered differences or prospect research in-browser, then the person switched to Claude Code to apply the fixes.

Example prompts

Try with Claude in Chrome
Compare my app at [URL] with the mock-ups open in my other tabs, screen by screen. Write a document listing every UX and UI difference, with the screen name, what the mock-up shows, and what the app shows. Finished means one document covering all [number] screens, ordered by how noticeable each difference is. Don't change anything in the app.

Related use cases