Competitive intelligence
Interview your competitor's users, because their reviews are public.
Why this is hard today.
You can research your own customers. You cannot survey somebody else's, which means the most useful audience in your market is the one you have no access to. Competitor analysis ends up being feature lists and screenshots.
Four steps.
- Build an audience from a competitor's reviews, or from the category minus your own app.
- Ask the questions you would ask in a win loss interview: what nearly made you leave, what would you miss, what is still missing.
- Compare the same question across two audiences side by side.
- Track how the answers move after a competitor ships something.
ask_audience
Any question, pointed at a competitor audience.
query_context
Grounding pass: matches, themes, sentiment and personas for a topic.
get_industry_topics
Topic clusters discovered across every app in a category.
Tool names are the MCP tools and in-app templates. The same engines power both.
What a run looks like.
Illustration: two browsers compared on sync
- Audiences: reviewers of browser A and reviewers of browser B.
- Question: how well does syncing between your devices work, and what breaks?
- What you would read: the two distributions next to each other, and the verbatims that name the specific failure each audience keeps hitting.
Reviewers skew toward people with something to say. Read the gap between two audiences rather than the absolute level of either.
Next door to this.
Run a competitive intelligence on your category.
Accounts are provisioned by hand during early access. Tell us the question and the category and we will set you up.