The 30-minute RAG setup for your team wiki
A practical walkthrough: connectors, chunking, and the three questions to test first when standing up document Q&A for your team.
Tomás Laifer
Engineering · Lumen
You don't need a platform team to give your company source-backed answers over its own wiki. You need thirty minutes, a connector, and a test plan. Here's the sequence we run with new workspaces.
Minutes 0–10: connect, don't migrate
Start with the source of truth people actually use — usually Notion or Google Drive. Connect it read-only and let the sync run. Resist the urge to clean up documents first; the index will surface exactly which pages are stale or duplicated, which makes cleanup a data-driven task instead of a political one.
Minutes 10–20: watch the index
While documents ingest, watch three numbers: pages indexed, chunks created, and duplicates detected. A healthy index has roughly 4–8 chunks per page and a duplicate rate under 10%. Higher duplicates usually means multiple versions of the same doc live in different folders.
Minutes 20–30: ask the three test questions
- One question with a single canonical answer (a policy, a price).
- One question whose answer spans two documents.
- One trick question the docs don't answer — the system should decline.
If two of three pass on day one, you're ahead of schedule. Publish the workspace to the team with one rule: every answer must include a citation, and every citation must resolve. That single habit is what turns a demo into infrastructure.