Knowledge base articles exist but underperforming staff don't read them fully or can't translate written docs into actual troubleshooting steps, so they default to asking a senior person.
Ingests a team's existing KB, runbooks, and vendor docs. When a tech encounters an issue, they describe it in natural language and RunbookAI walks them through a decision-tree style flow: 'Check X → if result is Y, do Z → if that fails, try W.' Learns from resolved tickets to improve suggestions. Acts as the patient senior coworker who never gets annoyed.
This is a top-3 complaint in every IT management forum. The Reddit post with 116 upvotes and 72 comments is not an outlier — search r/sysadmin, r/msp, or r/ITManagers and you'll find this exact frustration weekly. The pain is visceral: senior staff lose hours daily hand-holding juniors through documented procedures. It causes burnout, resentment, and turnover of your BEST people. The cost is quantifiable: a senior engineer at $80/hr spending 2hr/day on this = $41K/year wasted per senior person. This isn't a nice-to-have — it's a burning problem that directly impacts retention of expensive talent.
TAM estimate: ~40,000 MSPs in North America alone, average 8-15 technicians each. At $15/user/month, full MSP penetration = ~$720M/year (40K × 10 users × $15 × 12). Internal IT teams at mid-market companies (10K-100K companies with 5+ IT staff) add another comparable segment. Realistic SAM for an early-stage startup focusing on MSPs: $50-100M. Not a billion-dollar market on day one, but large enough to build a very profitable business. Docked slightly because the buyer (IT manager/MSP owner) is cost-conscious and tool-fatigued.
MSPs already pay $29-39/user/month for IT Glue (documentation), $50-150/user/month for PSA tools, and $100+/month per endpoint for RMM. $15/user/month is well within their software budget tolerance. The ROI pitch is concrete and easy to calculate: 'Your $80/hr senior engineer spends 2 hours/day hand-holding. RunbookAI costs $15/user/month and gives them back 1 hour/day. That's a 35x ROI.' However, docked because: (1) MSPs have severe tool fatigue and resist adding 'yet another tool,' (2) the freemium-to-paid conversion in IT tools is historically low (~2-5%), and (3) proving AI accuracy enough to justify paid tier requires significant trust-building.
Core architecture is well-understood: RAG pipeline (ingest docs → chunk → embed → vector store) + LLM for generating step-by-step guidance + simple decision tree UI. All components have mature open-source options (LangChain/LlamaIndex, pgvector/Pinecone, GPT-4o/Claude). A competent solo dev can build an MVP in 6-8 weeks. Docked 2 points because: (1) the QUALITY of decision-tree generation from messy, inconsistent KB articles is the hard part — garbage in, garbage out — and tuning this well requires significant prompt engineering and testing, (2) hallucination in troubleshooting contexts is dangerous (telling a junior tech to delete the wrong thing), and (3) integrating with the MSP ecosystem (IT Glue API, ConnectWise, etc.) adds complexity beyond the core AI.
This is the strongest signal. Nobody occupies the exact intersection of: (a) AI-powered, (b) ingests EXISTING unstructured docs, (c) generates INTERACTIVE decision-tree flows, (d) targeted at IT/MSP, (e) priced for SMB. Moveworks is enterprise-only and replaces humans instead of guiding them. Stonly requires manual guide authoring. Guru surfaces but doesn't transform docs. IT Glue stores but doesn't activate docs. Shoreline automates but targets DevOps. The gap is clear and the positioning is sharp. Risk: this gap exists because it's genuinely hard to do well (AI quality), not because nobody thought of it. Large ITSM vendors (ServiceNow, Freshworks) could add this as a feature within 12-18 months.
Extremely strong subscription dynamics. (1) Data moat: as the system ingests more docs and learns from resolved tickets, it becomes more valuable and harder to leave. (2) Daily active use: technicians would use this multiple times per day, making it workflow-embedded. (3) Growing value: new KB articles, new team members, new resolved tickets all compound the system's utility. (4) Seat-based expansion: as teams grow, revenue grows automatically. (5) Low churn risk once adopted because the alternative is going back to 'reading docs manually' — nobody wants that regression. This has the profile of a tool with <5% monthly churn once properly onboarded.
- +Pain is visceral, frequent, and expensive — senior engineer time wasted on hand-holding is easily quantifiable, making the ROI pitch concrete
- +Clear competition gap: nobody does AI-powered 'turn existing messy docs into interactive troubleshooting flows' at SMB/MSP pricing
- +Strong data moat potential — every resolved ticket and every ingested doc makes the system smarter and stickier
- +Natural wedge into the massive MSP ecosystem by positioning as a complement to IT Glue (not a replacement), which lowers adoption friction
- +The Reddit pain signals are organic and emotionally charged — this isn't a fabricated problem, it's a daily source of frustration and burnout for IT leaders
- !AI hallucination in troubleshooting is HIGH-STAKES — telling a junior tech to run the wrong command could cause an outage, and one bad incident could destroy trust permanently. You need guardrails, confidence scoring, and human-in-the-loop confirmation for destructive actions.
- !MSP tool fatigue is severe — convincing an IT manager to adopt 'yet another tool' when they already have 8-12 tools is the biggest go-to-market challenge. Distribution, not product, may be the bottleneck.
- !Large incumbents (ServiceNow, Freshworks, ConnectWise) could ship a 'good enough' version as a feature within their existing platforms, neutralizing the standalone value prop for customers already in those ecosystems.
- !Quality of generated decision trees depends heavily on quality of input docs — many MSPs have poorly written, outdated, or incomplete KB articles. AI amplifying bad documentation could make things worse, not better.
- !The $15/user/month price point at 50-article free tier may be too generous — you might train the market to expect this for free, especially as general-purpose AI chatbots (ChatGPT, Copilot) improve at document Q&A
Enterprise AI copilot for IT support. Auto-resolves common IT issues
Interactive knowledge base platform that transforms static articles into step-by-step, branching guides. Users click through decision trees to find the right answer. Embeds in help centers, chatbots, and internal portals.
Runbook automation platform for DevOps and SRE teams. Automatically detects incidents and executes predefined remediation steps. Codifies tribal knowledge into automated Op Packs.
AI-powered knowledge management platform. Uses AI to surface the right knowledge card at the right time, integrates with Slack/Teams/browsers. Verifies knowledge freshness and assigns expert owners.
The dominant documentation platform for MSPs. Centralizes passwords, configurations, SOPs, and runbooks. Integrates with major PSA and RMM tools. The de facto standard for MSP documentation.
Week 1-2: Build a simple web app where users paste or upload KB articles (Markdown, PDF, or plain text). Use RAG + GPT-4o/Claude to generate an interactive troubleshooting flow from the content. Week 3-4: Add natural language issue description input ('user can't connect to VPN') that matches to relevant KB articles and generates a step-by-step decision tree with branching ('Did the ping succeed? Yes → Check firewall rules. No → Verify NIC status'). Week 5-6: Add a feedback loop — tech marks steps as helpful/unhelpful, and resolution notes feed back into the system. Ship with a 'paste your KB article URL' bookmarklet for instant conversion. Skip integrations, skip ticket system connections, skip IT Glue API — just nail the core experience of 'describe problem → get guided troubleshooting flow' first. Target 5-10 MSP beta users from r/msp.
Free tier: 50 KB articles, 100 guided sessions/month, single user — enough to prove value on one problem domain. Paid ($15/user/month): unlimited articles, unlimited sessions, team management, custom doc ingestion (IT Glue, Confluence, SharePoint connectors), ticket system integration, analytics dashboard showing 'time saved' and 'escalations avoided.' Enterprise ($25/user/month): SSO, audit logs, custom LLM deployment (on-prem for security-sensitive orgs), API access, priority support. Scale play: once you have thousands of MSPs using the platform, aggregate anonymized troubleshooting patterns into a 'community knowledge graph' — effectively crowd-sourced best practices that make every MSP's troubleshooting better. This becomes a proprietary dataset moat.
8-12 weeks to first paying customer. Weeks 1-6 for MVP build. Weeks 6-8 for beta testing with 5-10 MSPs recruited from r/msp and MSP-focused communities. Weeks 8-10 for iteration based on beta feedback. Weeks 10-12 for converting 2-3 beta users to paid plans. Realistic first-year target: $5-15K MRR (30-80 paying users across 10-20 MSPs). The MSP community is tight-knit — one enthusiastic MSP owner posting about it on r/msp or in a peer group like TruMethods or IT Nation can drive meaningful early adoption.
- “Unless google literally spell out the solution or someone walk him through it he wouldn't get how to begin troubleshooting”
- “doesn't even bother to look through directory structure to find docs, or even finish reading a knowledge base article”
- “The time for the training wheels is off and this guy is in my office for about half the day”