UX research is one of those things every product team knows they should be doing more of. The problem isn't intent — it's time. Recruiting users, watching recordings, pulling screenshots, writing up findings, turning it all into a document the team will actually read. It eats your week before you've even started building anything.
I found a faster way. Not a shortcut — a genuinely better process. And it runs on Manus.
The Three Ways We Used It for UX Research
1. Competitor Experience Teardowns
The most time-consuming part of competitive UX research isn't forming opinions — it's gathering the raw material. Screenshots of every key screen, notes on each flow, comparisons across tools. Doing this manually for five competitors takes a full day.
Here's the prompt we used in Manus:
Go to [Competitor URL] and do a full UX teardown of their product experience. Focus on: onboarding flow, key navigation patterns, how they handle empty states, and their primary CTA placement on each main screen. Take screenshots of each key moment and annotate what's working, what's confusing, and what mental model they're designing for. Compile everything into a structured report I can share with my design team.
Manus browsed the product, captured screens, and delivered a structured teardown. What normally takes a day took under an hour.
2. Social Content Research — Scene by Scene
We needed to understand how other products in our space were presenting themselves on Instagram Reels and X — specifically, what made certain demo videos actually drive signups.
The prompt:
Search Instagram and X.com for product demo videos from [your category] SaaS tools that got high engagement in the past 12 months. For each one, break it down scene by scene: what happens in the first 3 seconds, how they show the product, whether they use voiceover or text overlays, how they end, and what the caption says. Identify the patterns across at least 15 examples and summarise into a report with a swipe file of hooks I can adapt.
This gave us both a pattern report and a ready-to-use swipe file. Two deliverables that would normally require a dedicated research session and a separate synthesis session — done in one go.
3. User Mental Model Research
We were redesigning a complex feature and needed to understand how our non-technical users think about the problem — not how we think they think about it.
The prompt:
Research how small business owners (non-technical, service industry) mentally model [the specific task we were designing for]. Look at forum discussions, Reddit threads, Facebook group posts, product reviews, and support documentation. What language do they use? What do they compare it to? Where do they get confused? Compile findings into a report with direct quotes grouped by theme.
The output was a themed findings document with real quotes pulled from public sources — the kind of thing that would normally take a researcher two days of desk research to compile.
What You Get at the End
Every Manus research task delivers a document. Not bullet points in a chat window — an actual shareable file with screenshots, quotes, annotations, and structured sections your team can read and reference.
This matters more than it sounds. The reason research doesn't influence decisions in most teams isn't that people don't believe in it. It's that the findings live in someone's head, or in a messy folder of screenshots nobody opens. A clean document that's ready to share means the work actually lands.
The Honest Limitations
Manus can't talk to your users. It can't watch session recordings or run usability tests. The research it produces is desk research — publicly available information, synthesised fast.
That's not a limitation to apologise for. Desk research is genuinely underused in most product teams, especially early in a project. Knowing what's already out there before you spend time in discovery sessions makes every conversation sharper.
Think of it as the foundation layer. You do this first, then you know exactly what questions to bring to your users.
Where to Start
If you've never used Manus for research, start with a competitor teardown. Pick one competitor, write a specific prompt (the more specific, the better), and see what comes back. You'll know within one session whether this fits your workflow.
The prompt format that works best every time:
Go to [specific place]. Look specifically at [specific thing]. Document [what you want captured]. Compile into [the format you need].
Four parts. That's it.
The Bigger Shift
The bottleneck in most product research isn't insight — it's throughput. There are only so many hours in a week, and research tends to lose out to building. Manus doesn't replace the judgment of a great researcher. But it removes the part that was eating the time — the gathering, the screenshotting, the compiling — so you can spend your hours on what actually needs a human: making sense of what it all means.
I'll be sharing the exact prompts we use for competitor teardowns, content research, and user mental model mapping. You can subscribe to my newsletter to get them when they're ready.