Building a Self-Service Data Analytics Platform with Generative AI and RAG

zeb · Tech · 2024 · source Agentic: no · promotional bias: high · source-backed · extracted with prompt 0.5.4 (schema v2)

Generated from extraction.json — do not edit by hand. Every claim cites verbatim source evidence; stated means the quote directly asserts the claim, implied means it supports it indirectly.

Problem

Domain: Enterprise self-service data analytics

zeb needed to reduce the manual workload on data analysts by letting business users request reports, forecasts, and insights in natural language through existing communication tools while preserving enterprise governance and industry-specific context.

Constraints:

Architecture

SuperInsight is a compound AI system built on the Databricks Data Intelligence Platform. End users send requests through email, Slack, Teams, or other channels. A DBRX model classifies intent, Databricks AI Search retrieves knowledge-base context stored in Unity Catalog, and a Model Serving endpoint combines DBRX with a fine-tuned industry adapter. The final output routes to a data warehouse for CSV generation, an AutoML endpoint for forecasts, or a reporting tool for visual reports.

Diagram confidence: explicit (topology described by the source).

flowchart LR
  user-channels[User Channels] --> dbrx-intent-classifier[DBRX Intent Classifier]
  dbrx-intent-classifier[DBRX Intent Classifier] --> databricks-ai-search[Databricks AI Search]
  dbrx-intent-classifier[DBRX Intent Classifier] --> model-serving-endpoint[Model Serving Endpoint]
  databricks-ai-search[Databricks AI Search] --> unity-catalog[Unity Catalog]
  model-serving-endpoint[Model Serving Endpoint] --> unity-catalog[Unity Catalog]
  model-serving-endpoint[Model Serving Endpoint] --> data-warehouse[Data Warehouse]
  model-serving-endpoint[Model Serving Endpoint] --> automl-endpoint[AutoML Endpoint]
  model-serving-endpoint[Model Serving Endpoint] --> reporting-tool[Reporting Tool]
Drag to pan · scroll or use +/− to zoom · reconstructed from the source's described component topology

Components

Component Role Interacts with
User Channels Slack, Teams, email, and other communication platforms where business users submit requests. DBRX Intent Classifier
DBRX Intent Classifier DBRX model that classifies request intent. User Channels, Databricks AI Search, Model Serving Endpoint
Databricks AI Search Retrieval layer that provides relevant knowledge-base context. DBRX Intent Classifier, Unity Catalog
Unity Catalog Governed store for knowledge base, data, model assets, federation, and security. Databricks AI Search, Model Serving Endpoint
Model Serving Endpoint Production endpoint combining DBRX with customer-industry fine-tuned adapters. DBRX Intent Classifier, Unity Catalog, Data Warehouse, AutoML Endpoint, Reporting Tool
Data Warehouse Destination for generated CSV outputs. Model Serving Endpoint
AutoML Endpoint Deployed forecasting endpoint used when requests require predictions. Model Serving Endpoint
Reporting Tool Destination for visual report generation. Model Serving Endpoint

Data flow

A user submits a natural-language data request through a familiar channel. The request goes to a DBRX classifier, then Databricks AI Search retrieves relevant context from Unity Catalog. Model Serving combines another DBRX model with a fine-tuned adapter for the customer's industry. Depending on the intent, SuperInsight sends output to the data warehouse, AutoML forecasting endpoint, or reporting tool.

4 supporting quotes
“End users can send a request through email, Slack or other communication channels. The request is fed through a DBRX model that classifies the intent”article, stated
“Databricks AI Search provides relevant context from a knowledge base stored in Unity Catalog.”article, stated
“The Model Serving endpoint combines another DBRX model with a fine-tuned adapter based on the customer’s industry.”article, stated
“The final output is then either sent to a data warehouse to generate a CSV file, to a deployed AutoML endpoint or to a reporting tool to generate a visual report.”article, stated

Why this architecture

zeb used a compound AI architecture because fine-tuning and RAG solved different parts of the analytics problem: fine-tuning adapted model behavior to industry context, while RAG grounded the model in each customer's schema and data context. Keeping the stack inside Databricks consolidated model serving, security, federation, RAG, and training instead of stitching many systems together.

3 supporting quotes
“With fine-tuning, we’re trying to change the behavior and scope of the model itself and put it within the context understanding of a specific industry.”article, stated
“With RAG, we assume that the model is already trained for an industry, but now we’re trying to understand a particular organization’s data schema and context.”article, stated
“If we didn’t use the Databricks Data Intelligence Platform, we would have 30 different solutions to piece together.”article, stated

Models used: DBRX · DBRX Mixture-of-Experts · fine-tuned industry adapters · AutoML models

Scale

Alternatives considered (roads not taken)

Keep manual analyst request processing

Rejected because: Analysts had a substantial backlog, and SuperInsight could turn natural-language requests into actionable insights.

“zeb initially developed a generative AI–based system for a large enterprise logistics company, where data plays a critical role. Prior to the implementation, a team of several data analysts managed a substantial backlog of data requests.”article, stated
“Rather than manually processing data requests, the system transformed user requests into actionable insights, significantly reducing the workload on data analysts by up to 80–90%.”article, stated

Use only fine-tuning or only RAG

Rejected because: Fine-tuning and RAG addressed different context layers: industry behavior and organization-specific schema/data.

“Sid Vivek explained why they chose this compound solution, “With fine-tuning, we’re trying to change the behavior and scope of the model itself and put it within the context understanding of a specific industry.”article, stated
“With RAG, we assume that the model is already trained for an industry, but now we’re trying to understand a particular organization’s data schema and context.”article, stated

Assemble many separate LLMOps products

Rejected because: Databricks consolidated data, fine-tuning, model serving, security, and federation in one platform.

“Our fine-tuning, model serving, security and federation are all consolidated within Databricks. If we didn’t use the Databricks Data Intelligence Platform, we would have 30 different solutions to piece together.””article, stated
“If we didn’t use the Databricks Data Intelligence Platform, we would have 30 different solutions to piece together.”article, stated

Patterns

rag-retrieval (retrieval)

SuperInsight retrieves organization-specific context from a Unity Catalog knowledge base.

“Databricks AI Search provides relevant context from a knowledge base stored in Unity Catalog.”article, stated

fine-tuning-adaptation (model adaptation)

zeb uses fine-tuned adapters to adapt DBRX to specific customer industries.

“The Model Serving endpoint combines another DBRX model with a fine-tuned adapter based on the customer’s industry.”article, stated

model-routing (platform)

The pipeline classifies intent and routes output to CSV generation, AutoML forecasting, or report generation.

“The final output is then either sent to a data warehouse to generate a CSV file, to a deployed AutoML endpoint or to a reporting tool to generate a visual report.”article, stated

tool-use-orchestration (integration)

Natural language requests are converted into actions across Databricks search, model serving, warehouses, AutoML, and reporting tools.

“Users can ask questions and make forecasts based on their internal data, and the system can even generate ML models to fulfill forecasting requests.”article, stated

Tradeoffs

Build a compound AI system

Chose RAG plus fine-tuning on Databricks over A single plain LLM endpoint.

Rationale: The model needed both industry behavior adaptation and customer-specific schema/context grounding.

“They decided to apply a compound AI system that could leverage internal canonical data models”article, stated
“With fine-tuning, we’re trying to change the behavior and scope of the model itself”article, stated

Use DBRX

Chose Open-source DBRX with Mixture-of-Experts architecture over An unspecified generic model stack.

Rationale: zeb valued instruction fine-tuning, reduced latency, fast inference, and accuracy.

“The reason we chose DBRX is because we saw its ability to take instruction-based fine-tuning with reduced latency.”article, stated
“The DBRX Mixture-of-Experts (MoE) architecture is really unique and able to deliver accurate results extremely quickly.”article, stated

Meet users in existing communication tools

Chose Slack, Teams, email, and other channels over A separate analytics request interface.

Rationale: The customer workflows already lived in these channels, so integrating there reduced adoption friction.

“It seamlessly integrated with the customer’s existing workflow, such as Slack channels, where data requests were already managed.”article, stated

Gotchas (what bit them)

Self-service analytics can increase demand.

Root cause: Making reports easier to request led more end users to interact with data.

Resolution: The platform treated increased request volume as a positive outcome and used the Databricks stack to support the demand.

“Another beneficial outcome was that more end users began interacting with their data to gain insights as they realized the effectiveness of the tool.”article, stated
“We actually saw a 72% uptake in the number of reports requested from our generative AI solution vs. the previous manual process”article, stated

A unified platform simplifies operations but creates ecosystem dependence.

Root cause: SuperInsight consolidates fine-tuning, serving, security, federation, and data inside Databricks.

Resolution: zeb accepted the consolidation because it reduced implementation complexity and time.

“Our fine-tuning, model serving, security and federation are all consolidated within Databricks.”article, stated
“If we didn’t use the Databricks Data Intelligence Platform, we would have 30 different solutions to piece together.”article, stated

Evaluation

zeb reports workload reduction, development-time savings, customer cost savings, increased report requests, and continued implementation feedback into canonical data models.

Metrics: 80-90% analyst workload reduction · 40% development-time reduction · 40% customer cost savings · 72% increase in report requests · four industry-aligned canonical data model families

3 supporting quotes
“significantly reducing the workload on data analysts by up to 80–90%.”article, stated
“We can confidently say we reduced the time to develop our solution by 40% using the Databricks Platform.”article, stated
“We actually saw a 72% uptake in the number of reports requested from our generative AI solution vs. the previous manual process”article, stated

Outcomes

The source describes zeb as a 1,500+ expert consultancy and SuperInsight as a multi-industry product spanning logistics/supply chain, retail, fintech, and health/life sciences.

3 supporting quotes
“significantly reducing the workload on data analysts by up to 80–90%.”article, stated
“customers are seeing a 40% cost savings while their data analysts are able to focus on more critical tasks.”article, stated
“We’re also getting more data understanding and more knowledge that we can feed back into our canonical data models.”article, stated