← All articles Guide

Guide: a phased adoption plan for the Insight platform

Where to start and what to add next: a first phase with Ask, RAG and Lense, a second with Catalog and Prompts, and a third with domain models and domain solutions, with the questions that decide when to move on.

The InsightLake suite has more than thirty products. Nobody should start with thirty. The suite's own guidance is that most enterprises start with Ask, RAG and Lense, then add Catalog, Prompts and DLM as the programme matures. This guide turns that into a plan with gates, so each phase earns the next.

Phase 1: prove value with one team

Pick one team with a clear, frequent question that today takes too long to answer: on-call engineers, a member-services desk, an underwriting team. Connect two or three sources they already trust. Deploy Insight RAG behind Insight Ask, and trace every answer in Insight Lense from day one.

  • Build a test set first: forty to a hundred real questions with the document that answers each. It's how you'll know whether retrieval works, before anyone has an opinion.
  • Review permissions by role with security before launch.
  • Read the traces weekly: wrong answers are either a retrieval problem or a model problem, and the trace says which.

Gate: the team uses it without being asked, and the answers it gets wrong are understood.

Phase 2: make it governable

More sources and more teams mean more risk. Add Insight Catalog so every source has an owner, lineage and sensitivity classes, and so RAG's access rules have something reliable to enforce. Move prompts into Insight Prompts: versioned, tested against datasets, approved before they ship, and promoted only when a new version beats the old one. Lense links each trace to the prompt version that produced it.

Gate: no prompt or source change reaches users without review, and cost and quality are reviewed on a schedule.

Phase 3: specialise

With a governed base, go deeper where the business case is strongest:

  • Insight DLM for domain-specific small models trained on your data, for tasks where a smaller model you own is faster, cheaper or more accurate than a general one, trained and served inside your environment.
  • A domain solution such as Insight UW for underwriting, Carts for retail or Variant for genomics, built for the people who do the work.
  • Agents that act, through Insight AI Assist, with authority levels recorded in Lense: what each agent may do alone, and what needs a person.

Gate: for every action an agent can take, you can show what it did, what it was allowed to do, and who approved it.

Example · a made-up bank

Eighteen months, three phases

A made-up regional bank started Phase 1 with its IT service desk: ServiceNow and Confluence, about 60 test questions, Lense from day one. Six months later, Phase 2 brought in the operations and compliance teams, the Catalog for data owners and lineage, and Prompts with a two-step approval. In Phase 3 it built a small domain model for classifying customer complaints with DLM, and only then let an assistant draft responses, with every draft approved by a person and traced.

Plans are local. Timelines depend on your data, your security reviews and your teams; the phases are an order, not a schedule. Talk to us about which products fit your first phase.

Signs you're moving too fast

  • Adding sources nobody owns. Every source needs someone who can say who should see it and whether it's current.
  • Changing prompts directly in code. If a prompt change can ship without review, you're not in Phase 2 yet.
  • Agents with no authority levels. If you can't say what an agent may do alone, it shouldn't act yet.
  • No test set. Without real questions and known answers, "it seems better" is the only measure.

Signs you're ready for the next phase

  • The first team asks for more sources rather than better answers.
  • Traces are being read, and wrong answers have known causes.
  • Other teams are asking for the same thing for their own knowledge.

Related: the reference architecture · running AI inside your environment.

See the right Insight products in your environment

Tell us what you're trying to build, and we'll walk you through the products that fit, with your data, where it lives.

Request a demo

Keep reading

Use case
Insight CatalogAutomation HubInsightKafkaInsight Dataflow

Use case: moving a data platform without losing track of what depends on what

A made-up retailer's data team migrates warehouses and Kafka clusters with Insight Catalog for lineage and impact analysis, Insight Automation Hub for validated migration runs, InsightKafka for cluster health, and Insight Dataflow for the new pipelines.

November 15, 2026 · 8 min read
Use case
Insight AskInsight RAGInsight Lense

Use case: one search box for IT operations, across tickets, wikis and code

How a made-up manufacturer's IT operations team uses Insight Ask on top of Insight RAG: connect ServiceNow, Confluence, Jira, Slack and Git, keep permissions intact, and trace every answer with Insight Lense.

November 13, 2026 · 7 min read
Use case
Insight UWInsight ExtractInsight Lense

Use case: commercial insurance submissions, from broker email to underwriter decision

How a made-up specialty insurer combines Insight Extract and Insight UW: broker emails and attachments become validated data, each submission is assessed against guidelines and appetite, and the underwriter decides with the evidence in front of them.

November 11, 2026 · 8 min read