Reference doc → Evidence behind Mission Control. The full, fully-cited research is in bakers-dozen/research/bi-democratization-case-studies.md.

Cultivated AI · Mission Control · evidence

What's actually worked.

Real precedents for democratizing business intelligence with AI, and for showing up in AI answers. Sources are tagged by how much to trust them. The honest headline: the warehouse and the semantic layer are the project; the chat is the easy last mile.

13 precedents · sources cited · The Baker's Dozen

Peer-reviewed Company-reported Independently reported Vendor-claimed Secondary

The one number to show leadership

On a real warehouse, plain text-to-SQL answered correctly about 33% of the time (GPT-4, 2023). Grounded in a governed semantic layer, the same questions hit 98 to 100%. Even with today's frontier models (90%+ raw), the semantic layer is still the line between "usually right" and "trustworthy." dbt Labs benchmark, public methodology, built on an academic benchmark.

01

Companies that did it

Organizations that let non-technical people ask their data in plain language. The closest analog to Baker's Dozen is first.

Swiggy · Hermes

Indian quick-commerce Closest precedent

Ask a question in plain English in Slack; Hermes generates SQL, runs it, and answers. V3 became a conversational "AI data analyst" on Snowflake, retrieving past validated queries as few-shot grounding, with an agentic loop and a confidence-plus-explanation layer.

54% → 93%SQL accuracy (V1 to V3)

For Baker's Dozen: same business, same geography, same warehouse choice many D2C brands make. The cheap trick to copy: reverse-generate questions from SQL your analysts already trust, then retrieve those as examples.

Uber · QueryGPT

Mobility / marketplace

Internal natural-language-to-SQL for operators and analysts. A multi-agent pipeline (intent, table, column) with RAG over curated SQL, scoped by 12 business "workspaces," plus an evaluation harness scoring every answer.

~10 min → ~3 minquery authoring, ~300 daily users

For Baker's Dozen: the workspace pattern (scope the model to a domain before it writes SQL) and the eval harness are directly reusable. Note: the viral "140,000 hours saved" figure is a third-party extrapolation, not Uber's.

Company-reporteduber.com/blog/query-gpt

Pinterest · Analytics Agent

Consumer platform

Text-to-SQL inside their open-source Querybook, evolved into an agent that also helps discover tables and reuse past queries. RAG table retrieval (OpenSearch) narrows the schema before generation.

20% → 40%+first-shot SQL acceptance

For Baker's Dozen: proof that table and column retrieval (not a bigger model) moves accuracy, and that "first-shot acceptance" is a more honest success metric than raw benchmark scores.

DoorDash · AskDataAI + Transaxle

Food delivery

A plain-English data assistant plus a SQL-dialect translation service, with a planned MCP bridge so one assistant can target Snowflake, Databricks, and Trino.

In developmentdirectional, no hard self-serve metrics yet

For Baker's Dozen: the multi-engine, MCP-mediated pattern is useful if you end up with more than one store (GobbleCube exports plus a warehouse).

Instacart · Ava  ·  Wealthsimple · LLM Gateway

Adoption + governance

Two adoption templates. Instacart's Ava (general assistant) reached 900+ weekly users by living where people already work. Wealthsimple's open-sourced gateway adds PII redaction, self-hosted models, and audit, used by over half the company.

50%+ of staffinternal adoption, both

For Baker's Dozen: adoption scales when the tool starts small and lives in Slack/Teams; and the gateway is the template for the PII, access, and audit layer that should wrap any leadership-facing assistant.

Company-reportedAggregated
02

The tools that enable it

Every one of these depends on a governed semantic model for quality. The client's existing stack (Power BI) is first.

Microsoft Power BI Copilot + Fabric

Client's existing stack Start here

Copilot in Fabric is generally available: generate report pages from a prompt, write narrative summaries, answer in conversational language. Fabric "data agents" sit over your data and are consumable from Power BI, M365 Copilot, and MCP endpoints. Available from the F2 SKU since April 2025 (far below the old F64 floor).

Lowest frictionreuses existing Power BI datasets

For Baker's Dozen: the fastest on-ramp, but quality depends entirely on well-modeled, well-named semantic models. The "3-5x analyst productivity" claim is vendor-ecosystem, not verified. The warehouse and semantic-layer work is a prerequisite, not optional.

Databricks · AI/BI Genie

Lakehouse · best customer proof

Conversational analytics over a lakehouse, embeddable into Teams, governed by Unity Catalog. The AA trained it on "golden questions," validated answers against existing Power BI dashboards, and used catalog RBAC.

up to 70%less time on routine queries (The AA, vendor-claimed)

For Baker's Dozen: The AA's recipe is directly copyable: golden questions, validation against trusted dashboards, governance from the catalog, delivered in the chat tool people already use.

Snowflake Cortex · Looker + Gemini · ThoughtSpot · Tableau

The semantic-layer field

Four ways to buy the same idea. Cortex Analyst answers plain-language questions against a semantic model written as YAML, inheriting RBAC. Looker + Gemini grounds answers in the LookML semantic layer. ThoughtSpot Spotter is retail/CPG-specific (inventory, sell-through, promotions). Tableau Pulse pushes metric digests and anomaly explanations without being asked.

"Define once"the semantic layer is the moat

For Baker's Dozen: ThoughtSpot's promotion-lift and sell-through use cases map almost one-to-one onto quick-commerce questions. Pulse's push model fits a leadership team that won't log in daily.

dbt · Semantic Layer vs text-to-SQL

The architecture proof

A public benchmark (built on an academic one) comparing raw text-to-SQL against semantic-layer-grounded querying, each question run 20 times across models.

32.7% → 60.5%GPT-4, 2023 · and 84% → 100% with GPT-5.3 Codex, 2026

For Baker's Dozen: this is the line to put in front of leadership. For questions inside the semantic model's scope, accuracy approaches 100% because SQL is generated from governed definitions, not inferred.

03

The pattern that works

Every success above shares the same skeleton, in this order. The order is the lesson.

  1. Central warehouse as the single source

    One governed store the GobbleCube and Power BI telemetry feed into. Without it, the AI is querying inconsistent silos.

  2. A semantic / metrics layer on top

    Business definitions (revenue, active SKU, fill rate, incremental lift) encoded once, centrally. The highest-leverage component.

  3. Retrieval of curated example queries

    Ground the model in validated past queries and the right tables before it generates anything. Moves accuracy more than a bigger model.

  4. Domain scoping

    Narrow the model to a business area before it answers (Uber's "workspaces"). Less ambiguity, fewer tokens.

  5. Agentic orchestration

    Break a complex question into steps rather than one-shot generation.

  6. Governance and access, inherited

    RBAC, row-level security, masking, SSO, and audit logs, all from the warehouse layer.

  7. A trust surface

    Show the query or assumptions, attach a confidence score, validate against an already-trusted dashboard. This is what makes leadership act.

  8. An evaluation harness

    A golden-question test set scored continuously. You cannot improve what you do not measure.

  9. Delivery where people already work

    Slack, Teams, or the existing BI tool. Adoption follows convenience.

04

Why some fail

05

Showing up in AI answers

When a shopper asks an AI "best protein chips in India," the answer is assembled, not ranked. The job shifts from ranking one page to being mentioned consistently across the sources AI trusts.

The credible source

"GEO: Generative Engine Optimization" (Princeton, Georgia Tech, Allen Institute, IIT Delhi; KDD 2024) tested content tactics on a 10,000-query benchmark. Optimizations lifted source visibility by up to 40%. Best low-effort moves: quotations (~28%), statistics (~26%), fluency (~25%), citing sources (~25%). Keyword stuffing did almost nothing.

Honest limitation

Outside the Princeton paper, most AEO numbers come from vendors and aggregators, not peer-reviewed work. Use the academic study for credibility and the tactics as a checklist, not a guarantee. AI shopping referrals are small today (around 1% of web traffic) but growing fast and converting well, so it's worth starting now, cheaply.

06

Takeaways for Baker's Dozen

Full research

Every claim above is cited in full in bakers-dozen/research/bi-democratization-case-studies.md, with source URLs and credibility tags.