Teams waste time answering the same questions repeatedly and doing manual processes that should be automated, but nobody tracks what's repeated
Monitors Slack/Teams for repeated questions and patterns, flags them with frequency data, auto-drafts FAQ entries or runbook snippets, and suggests automation opportunities
SaaS $10/user/month with Slack/Teams integration
Extremely real pain. The Reddit thread (564 upvotes, 200 comments) confirms engineers viscerally hate answering the same questions. Every engineering team above 10 people experiences this. The pain is daily, interrupts deep work, and compounds as teams grow. However, many teams have learned to live with it — it's a chronic ache, not an acute emergency, which slightly limits urgency to buy.
TAM: ~$2-4B. There are roughly 30M+ professional Slack/Teams users in engineering/DevOps roles globally. At $10/user/month, even capturing 1% of addressable users (300K) = $36M ARR. The broader knowledge management market is $50B+, but RepeatRadar targets a specific slice. Strong enough for a venture-scale outcome, excellent for a bootstrapped business.
$10/user/month is reasonable but faces headwinds: (1) Engineering managers are the buyer, not individual devs. (2) Competing for budget against established tools like Guru/Confluence. (3) ROI is real but hard to quantify upfront — 'we saved X hours of repeated answers' is squishy. (4) Many teams will try to solve this with a wiki + discipline first. Price point works, but sales cycle may be longer than expected. Consider usage-based or team-flat pricing to reduce friction.
Core NLP/embedding similarity for question detection is well-understood (sentence transformers, cosine similarity). Slack API is mature and well-documented. Auto-generating FAQ drafts is straightforward with LLMs. HOWEVER: (1) Semantic similarity at scale across months of messages requires real infrastructure. (2) Handling noise (not every similar message is a 'repeated question') needs good filtering. (3) Slack API rate limits and message history access (especially on free Slack plans) add complexity. (4) Privacy/security concerns with reading all messages. A solo dev can build an MVP in 6-8 weeks, but it'll be rough — polished version needs more time.
This is the strongest signal. Every existing tool is REACTIVE — they help answer questions faster but none proactively detect patterns and say 'document this.' The gap between 'here's a knowledge base' and 'here's what your knowledge base is missing based on actual team behavior' is massive and unoccupied. Guru, Tettra, and Dashworks could build this feature, but it's not their core focus. First-mover advantage is real here.
Extremely strong subscription fit. The value compounds over time — the longer it monitors, the better its pattern detection becomes. Teams won't want to lose historical pattern data. Monthly insights/reports create habitual engagement. Natural expansion within orgs (one team adopts, others see the value). Low churn potential once embedded in workflow.
- +Clear competitive gap: no existing tool does proactive repeated-question detection — every competitor is reactive
- +Pain is validated by real engagement (564 upvotes) and is universal across engineering teams of any size
- +Strong recurring/retention dynamics — value compounds over time as more patterns are detected
- +Natural land-and-expand: one team adopts, pattern data demonstrates value, spreads to other teams
- +AI/LLM capabilities make the core feature (semantic similarity + doc generation) far more feasible now than 3 years ago
- !Slack/Microsoft could build this natively — Slack AI and Copilot are investing heavily in workspace intelligence, and 'repeated question detection' is an obvious feature addition
- !Privacy concerns: reading all team messages is a hard sell for security-conscious engineering orgs. SOC2 and enterprise security reviews will be required early
- !Cold start problem: needs weeks of message history to show value, meaning time-to-wow is slow. First demo may underwhelm
- !Buyer complexity: individual devs feel the pain but engineering managers/VPs hold the budget. The person who suffers isn't the person who pays
- !Signal-to-noise ratio: distinguishing genuinely repeated questions from similar-but-different discussions is hard. Too many false positives will kill trust fast
AI-powered enterprise knowledge management platform that integrates with Slack/Teams. Surfaces verified knowledge cards when employees ask questions. Has AI-assisted authoring and verification workflows.
Internal knowledge base for teams with Slack integration. Lets team members ask questions in Slack and routes them to subject matter experts. Has AI answers from existing docs.
Slack's built-in AI features including channel summaries, thread summaries, and search answers. Pulls from conversation history to answer questions. Atlas provides org chart and people profiles.
Conversational ticketing system inside Slack/Teams. Turns messages into tickets, routes to the right team, tracks resolution. Integrates with Jira and other Atlassian products.
AI-powered workplace search and knowledge assistant. Connects to 50+ apps
Slack bot that connects to 2-3 channels, runs nightly batch analysis using embedding similarity to cluster repeated questions, and posts a weekly digest: 'Top 5 repeated questions this week, asked X times each, here are draft FAQ entries.' No real-time monitoring needed for MVP — batch is simpler and avoids rate limit issues. Include a one-click 'publish to Notion/Confluence' for generated FAQ drafts. Skip Teams integration for MVP — Slack-only.
Free: connect 1 channel, weekly digest, up to 50 users → Paid ($8-10/user/month): unlimited channels, daily digests, auto-draft docs, automation suggestions, Notion/Confluence export → Enterprise ($15+/user/month): SSO, SOC2, custom integrations, API access, admin analytics dashboard. Consider flat team pricing ($99-299/team/month) instead of per-user to reduce procurement friction.
8-12 weeks. 6-8 weeks to build Slack-only MVP with batch analysis and weekly digest. 2-4 weeks of beta with 5-10 teams (offer free during beta). First paying customers at week 10-12. Target $1K MRR by month 4, $5K MRR by month 6 if distribution is solid (Product Hunt launch, dev community seeding, content marketing around the pain point).
- “If you ask me 3 times the same thing? Document and automate”
- “Automate, automate, automate”
- “cut the number of 'why does this work like this?' questions”