You'd think this requires a CX analyst and a weekend with a spreadsheet — Tycoon Agent clusters every complaint across every channel and ranks by revenue at risk.
The short answer
Tycoon Agent answers "what are customers complaining about" by ingesting every support ticket (Intercom), every Twitter/X mention of your handle, every App Store and G2 review, and every Discord/Slack message in your community channels. She clusters them by topic (not keywords — semantic clusters), then weighs each cluster by the MRR of the customers who complained. Output is a ranked list: Top 5 complaint themes, # of customers complaining, total MRR represented, sample verbatim quotes, and a verdict (Quick fix / Roadmap / Wontfix). She separates loud-but-low-value (free users on Twitter) from quiet-but-high-value (your $5k/mo customer who emailed once). You stop reacting to whoever yelled loudest and start fixing what's costing you the most actual money.
How Tycoon Agent actually does it
- Ingest every channel
Intercom tickets (last 30 days), Twitter/X mentions of your handle, G2 + App Store reviews, Discord/Slack community channels, NPS verbatims.
IntercomTwitter APIDiscordSlackG2
- Cluster semantically
Group by topic, not keyword. 'Login is broken', 'can't sign in', 'OAuth failed', 'session expires too fast' all collapse into one auth cluster.
- Weight by revenue at risk
Map each complainer to their Stripe MRR. A cluster of 3 enterprise customers = bigger priority than 40 free-tier complaints, even if it looks quieter.
Stripe
- Rank and verdict
Quick fix = ≤1 day eng work. Roadmap = real feature change. Wontfix = legitimate complaint but doesn't fit your strategy. Each verdict comes with reasoning.
- Write the report
Lark message: top 5 clusters, # of customers + MRR per cluster, 1-2 verbatim quotes per cluster, verdict, and the single complaint to fix this week.
Lark
What it looks like in chat
YouWhat are my customers complaining about?
Tycoon AgentTop 5 themes (last 30 days), ranked by MRR at risk: 1. **Slow API responses on Asia traffic** — 11 customers, $24k MRR. Quote: 'Tokyo team sees 3-4s on every call.' **Quick fix**: add Asia-Pacific edge region. ~2 days eng. 2. **No team billing roles** — 7 customers, $19k MRR, 4 are deal-blockers. Quote: 'I can't give finance access without giving them admin.' **Roadmap**: real feature, 2-3 weeks. 3. **Webhook retries silently fail** — 4 customers, $12k MRR. Quote: 'Lost 6 hours of events and no alert.' **Quick fix**: retry alerting, ~1 day. 4. **Onboarding is confusing** — 28 customers, $4k MRR (mostly free tier). **Wontfix-for-now**: real, but smaller money. Schedule for Q3. 5. **Pricing page doesn't show usage tier breakpoints** — 6 customers, $0 MRR (haven't converted). **Quick fix**: 1 hour, update the page. **Fix this week**: #1 (Asia API). Highest MRR at risk + ships in 2 days. I can draft the eng ticket if you want.
What you get back
A weekly Lark message with the top 5 complaint clusters, customers + MRR per cluster, sample verbatims, verdict per cluster, and the single most valuable thing to fix this week.
Cadence: Weekly Tuesday 10am, plus real-time alerts when a single complaint represents >$10k MRR.