TrueCount: Accurate X Notification Tracker + Mutual Mention
X displays inaccurate/low notification counts (e.g. 21 shown vs 52 actual), forcing manual scrolling, and lacks any one-click way to mention all mutuals.
Is the problem real?
X shows incorrect/low notification count (e.g. 21) while actual unread notifications are higher (e.g. 52), requiring manual scrolling.
EVIDENCE
X was showing me 21 notifications, only for me to come here and I'm scrolling to 52 notifications 😂
postIt happens all the time 😩
commentIt happens all the time 😩
Who feels this pain?
TARGET USERS
Frequent posters and engagers with many mutual follows who check notifications multiple times daily for replies, mentions, and interactions.
Context
Current Workarounds
Where's the gap?
EXISTING SOLUTION GAPS
OPPORTUNITY & VALUE
Clear repeated confirmation of inaccurate count bug occurring frequently plus explicit wish for mutual mention feature.
Hyper-focused on fixing X's native notification count bug and adding mutual mass-mention unavailable in any official tool.
Browser extension that overlays accurate real-time notification count on X and provides a one-click 'Mention All Mutuals' composer with smart selection.
How does it make money?
MONETIZATION
Model
Users repeatedly complain about the count discrepancy happening 'all the time' and express frustration with manual workarounds; power users already invest time daily in X engagement where even small friction wastes minutes per session.
How do you ship it?
MVP PLAN
“See your real notification count and mention all mutuals instantly.”
Browser extension that overlays accurate real-time notification count on X and provides a one-click 'Mention All Mutuals' composer with smart selection.
Core Features
Weekly Roadmap
- •Chrome extension skeleton with X.com content script
- •DOM observer to detect and correct displayed notification badge
- •Local storage for last known accurate count
- •Implement mutuals fetch via X web scraping or limited API
- •Build floating composer button with @all mutuals insert
- •Basic post preview and send integration
- •UI polish and error handling for count mismatches
- •Settings panel for refresh intervals
- •Recruit 10 beta X power users via X posts
- •Stripe integration for subscriptions
- •Launch post and Product Hunt submission
- •Track activation and first payments
Launch on Product Hunt, X power user communities, and relevant Reddit subs like r/Twitter or r/socialmedia
RISKS & ASSUMPTIONS
Top Risks
X frequently changes UI/DOM or restricts extensions, potentially breaking core count overlay functionality overnight.
Power users are fragmented and wary of new third-party tools after previous Twitter API crackdowns.
Reliably fetching and caching accurate mutuals list without full API access may require scraping that risks rate limits or bans.
Free workaround of manual scrolling may limit willingness to pay even among frustrated users.
Should you build it?
Run an Investment Memo to get a structured Go / No-Go verdict, competitor landscape, unit economics, and a 90-day validation roadmap for this opportunity.
Generate an investment memoWhat this score means
This idea scores in the upper-middle range of opportunities surfaced by MonetScope, with a validation sub-score of 8/10 against 3 independently sourced evidence signals. A "promising" rating usually indicates a real pain has been detected and discussed in the open, but the pipeline did not find enough signal to flag it as urgent or high-frequency. These opportunities can still produce excellent businesses — they often correspond to "boring" problems that established players have ignored — but the founder should expect a longer customer-development cycle to confirm willingness to pay.
Why this matters for SaaS founders
It sits at the intersection of "automation", "chrome-extension", "creators", which makes it relevant to a specific subset of founders rather than a generic horizontal opportunity. SaaS opportunities at this stage tend to win on the strength of their initial wedge — a single workflow that the target user runs every week, where the existing solution is either spreadsheets, a clunky incumbent feature, or a manual process they hate. The build cost is moderate; the distribution cost is everything. The MonetScope pipeline surfaces this category alongside other saas signals, which is why it appears here rather than in a generic "trending ideas" feed.
Scores are derived from real forum discussions across Reddit, Hacker News and X, weighted by evidence volume and signal quality. How scoring works
Frequently asked questions
Is "TrueCount: Accurate X Notification Tracker + Mutual Mention" a real validated startup idea or just an AI-generated suggestion?
MonetScope does not generate ideas from a language model's imagination. Every opportunity on this site is anchored to specific source posts and comments from real public discussions — typically on Reddit, Hacker News, or X — where actual users describe the pain in their own words. The AI's role is structuring, scoring, and grouping those signals into a navigable opportunity, not inventing the problem.
How recent is the underlying data for automation?
MonetScope's spider pipeline runs continuously and surfaces opportunities as new evidence accumulates. The "Updated" date in the header reflects the most recent re-scoring of this specific opportunity. Most saas opportunities visible in the public catalog draw from discussions in the last 30-60 days; older signals are de-prioritized because user pain shifts faster than most founders assume.
What's the difference between "overall score" and "validation score"?
Overall score is a composite across six dimensions — pain, urgency, willingness to pay, market size, defensibility, and execution ease — designed to give a single number for triage. Validation score is narrower: it asks "how cleanly does the same signal repeat across independent sources?" An opportunity can score high on overall but lower on validation when one or two large discussions dominate the evidence; conversely, validation can be high on a smaller-overall idea where the signal is consistent but the addressable market is modest.