// sales & gtm
Turn competitor complaints into sales angles
Name competitors or describe your app to discover similar Android apps and recurring frustrations in their reviews. Use the evidence to choose a product improvement or landing-page message to test with prospects.
You get A verified competitor shortlist and complaint themes with feature and landing-page tests to validate.
Find product and messaging opportunities in competing apps’ reviews. Use https://litescrape.com/blog/mine-competitor-review-gaps.md
From one instruction to a useful result
Up to three discovery searches, three app checks and six review pages
- Step 1$0.00045
Discover competing apps
GET /api/google/search, 3 calls
Start with competitor names or your app’s core job and audience. Restrict searches with as_sitesearch=play.google.com, validate direct detail URLs, extract package IDs and deduplicate candidates. Off-domain results are a discovery failure, not no competitors.
- Step 2$0.00045
Verify the shortlist
GET /api/google/play/product, 3 calls
Check up to three candidates against returned title, developer and app description. Record the fit evidence; skip mismatches and unresolved names before spending review calls.
- Step 3$0.0009
Sample recent reviews
GET /api/google/play/reviews, 6 calls
Read up to two recent pages per verified app. Keep pagination tokens bound to the same app and locale, and stop exhausted feeds.
- Step 4$0.00
Choose messages to test
Your agent, 0 calls
Report a complaint theme only when at least two distinct sampled reviews support it. Retain developer replies, resolutions and contradictory evidence. Flag historical reports before proposing product or landing-page tests.
Example API budget
Up to three discovery searches, three app checks and six review pages
- Discover competing apps, 3 calls
- $0.00045
- Verify the shortlist, 3 calls
- $0.00045
- Sample recent reviews, 6 calls
- $0.0009
- Choose messages to test, 0 calls
- $0.00
- Total
- $0.0018
Budget at $0.15 per 1,000 successful calls, not a measured receipt. Actual usage depends on matches and available pages. Retries count toward the attempt cap. Agent costs are separate.
What you get back
| File | Contents | Use it to |
|---|---|---|
| competitors.csv | search query, app ID, title, developer, Play URL, fit evidence, verification status | Review which competitors were selected |
| competitor-gap-hypotheses.csv | competitor, unmet job, distinct sample IDs, support status, evidence links | Choose a positioning test |
| angles-and-questions.md | feature/landing-page test, contradictions, unknowns, validation questions | Run customer discovery |
| manifest.json | discovery queries, app IDs, pages, actual calls, cost, stop reasons | Judge discovery and sample coverage |
Only verified matches proceed to reviews. Counts describe the collected sample; fewer than three relevant apps may be found.
Put the result to work
Review the selected competitors and validate each hypothesis with prospects before publishing a claim.
Search may miss apps or surface namesakes. Competitor complaints do not prove your product solves the issue.