Best Practices & Limits

Best practices

• Work inside a Project for anything with more than a handful of documents.
• Pick the right Being: research → Watson · contracts → Jeeves · evidence → Holmes · strategy → Athena.
• Let it cite, then verify.Click through to the source for anything you'll rely on.
• Use Tabular Reviewfor “the same question across many files.”
• Turn repeat work into a Workflow and share it with your team.
• Ask for a Word document explicitly when you want a downloadable draft or redline.
• Use hand-offs — let the legal trio pass a thread between lenses instead of starting over.
• Mind the limits: ≤ 30 MB per file, supported types only, ≤ 10 attachments per standalone message.

What it can do

• Read PDF, DOCX, DOC, XLSX, and PPTX files (up to 30 MB each).
• Ground answers with verifiable citations.
• Generate downloadable Word documents and tracked-changes redlines.
• Extract structured data across many documents and export to Excel.
• Run recurring jobs from reusable, shareable Workflows.
• Offer four specialist Beings with distinct strengths and hand-offs.
• Keep version history and searchable chat history.

What it can't do (by design / today)

• It isn't a lawyer.Olympus supports professional judgment; it doesn't replace it.
• Standalone chats cap at 10 attachments per message — for bigger sets, use a Project.
• Files must be ≤ 30 MB and a supported type.
• No “bring your own model” key — model choice is managed by the platform.
• Access is gated. Sign-up requires an approved / allow-listed email.