AI wiki generator from internal documents with citations

What to build

A SaaS tool that ingests bulk internal documents — emails, Slack exports, Confluence dumps, meeting transcripts — and auto-generates a structured, cited wiki where every claim links back to the original source. Target ops, engineering, and HR teams at SMBs that lose institutional knowledge when people leave or onboard slowly.

Large language models can now turn a 45,000-email corpus into a fully cited knowledge base, making it practical to productise institutional memory extraction for the first time. The opportunity is a lightweight SaaS layer on top of that capability, aimed at teams that bleed productivity during onboarding and offboarding.

Demand

Ops and engineering leads at growing SMBs are the immediate buyer — they feel the pain acutely when a senior employee leaves and their knowledge walks out the door. The timing is right because foundation models have only recently become reliable enough to produce source-attributed summaries at scale, lowering the technical bar to ship a credible product.

• Hacker News – Show HN submission (thisandthat.chat/enron)News

  Show HN: We had AI write a wiki from 45k Enron emails, every fact cited — 57 points and 53 comments on Hacker News, indicating strong organic interest from a technical audience in cited AI-generated knowledge bases from internal document corpora.

• Enron Email Dataset (Carnegie Mellon University)Research

  The Enron email corpus (~45k commonly used emails) is a well-known public dataset of real corporate internal communications, demonstrating that large-scale enterprise email corpora are a realistic and credible input for automated knowledge extraction tools.

• Industry research on employee onboarding costsResearch

  Multiple studies show slow or ineffective onboarding costs organisations significant productivity; automated, cited knowledge bases could accelerate time-to-productivity for new hires by surfacing institutional knowledge locked in emails and internal documents.

Stack

• OpenAI GPT-4o (with function calling for citation grounding)
• LlamaIndex or LangChain (document ingestion + retrieval pipeline)
• Supabase (vector store via pgvector + auth + storage)
• Next.js (wiki UI + upload flow)
• Unstructured.io (parsing PDFs, .eml, Slack JSON exports)
• Stripe (per-seat or per-corpus billing)

Solo + AI difficulty

The core RAG-to-wiki pipeline is achievable in 2–3 weeks with AI assistance; the hard parts are citation fidelity (ensuring every claim truly traces to the right source chunk), handling messy real-world file formats, and building a readable wiki UI. A functional MVP that handles email + Slack exports with a clean cited-output view is realistic in 4–6 weeks solo.

Entry threshold

Requires integrating an LLM with RAG pipelines and a citation/source-linking layer; buildable solo in a few weeks using OpenAI or similar APIs plus a vector store. No licences needed, but the citation-accuracy UX is the hard differentiator.

Window

6-12 months

Where to find first users

• Post a public demo on Hacker News (Show HN) with a real document corpus — the Enron demo proved this audience responds strongly
• Target r/sysadmin, r/devops, and r/ProductManagement with a concrete pain-point post about knowledge loss during offboarding
• Reach out directly to ops and engineering managers in Slack communities (e.g., Rands Leadership Slack, Software Lead Weekly audience)
• Product Hunt launch timed around a polished demo video showing before/after: raw email dump → structured cited wiki

Competitors

• Notion AI
• Confluence AI (Atlassian Intelligence)
• Microsoft Copilot for SharePoint
• Glean

Counter-signals & risks

• LLMs can hallucinate or misattribute citations even when a citation is generated, so the output wiki may contain plausible-sounding but inaccurate claims that are difficult to detect at scale — undermining the core value proposition of a trustworthy cited knowledge base.

• Enterprise buyers with sensitive internal communications (legal, HR, finance) face strict GDPR, attorney-client privilege, and data residency constraints that make uploading documents to a third-party SaaS legally or politically untenable, significantly narrowing the addressable market.

• Notion AI, Confluence AI, and Microsoft Copilot for SharePoint already target institutional knowledge management with massive distribution advantages and existing user trust, making it hard for a solo-built tool to win on breadth — a narrow niche (e.g., offboarding runbooks, email-only corpora) may be required to find a defensible wedge.