Roadmap

What works today, and what's next

The design-partner pilot is how you influence what lands in Next.

Now

Working today, across every document population

  • Ingest any corpus.

    PDF, DOCX, PPTX, XLSX. Long documents, mixed formats, multi-language. The same pipeline whether the population is a hundred contracts or ten thousand.

  • Cited extraction on every claim.

    Every value links to the exact clause it came from. Nothing implied, nothing paraphrased.

  • Cross-document comparison and divergence.

    Side-by-side analysis at corpus scale, not one document at a time. The output is a cited table, not a chat answer.

  • Queryable through MCP.

    Connect Claude, Claude Code, or any MCP-aware client to your corpus and ask questions that span every document. The analyst web UI ships in Next.

Next

Actively building

  • An analyst web UI.

    A guided experience so legal, compliance, finance, and audit teams can ask questions across the corpus, navigate cited findings, accept or correct values, and share results — without an MCP client.

  • Starter question libraries.

    Pre-built question sets for the domains most enterprises start with — legal, finance, compliance, operations, engineering.

  • Direct-source connectors.

    SharePoint, Google Drive, Box, and the systems your corpus actually lives in. Documents flow in continuously instead of in batches.

  • Scheduled and agent-driven runs.

    Recurring analysis over evolving populations. Multi-step workflows that explore the corpus the way a senior analyst would.

Later

Directional

  • Customer-defined question sets, with versioning.

    Author your own questions and analysis logic, version them, and share them across business units.

  • Broader connector surface.

    Across the document estates an enterprise actually has — contract systems, e-signature archives, regulatory submissions, board-pack repositories.

  • Scheduled population reports.

    Cited findings delivered on a cadence to the people who need them — board, audit committee, regional GC, engineering leadership.

  • Closed-loop integrations.

    Push findings back into the systems where work happens, so divergence detection isn't a report — it's a trigger.

We'd rather shape the right product with the right partner than polish the wrong one.

Start a design-partner pilot → Back to overview