Google Cloud Retail Australia

Kogan.com

Enterprise Knowledge Search · IT Operations Automation · Real-time Analytics

Kogan.com needed to eliminate brittle export-based BI pipelines, shorten slow answer cycles for business users, and expose analytics conversationally without losing semantic consistency or data-level security.

150 non-technical team members
Data turnaround dropped from 40 minutes to under 60 seconds

Reported impact

Business outcome

Kogan.com cut data turnaround to seconds, turned more than a hundred non-technical users into self-service analysts, and reduced maintenance burden by grounding conversational analytics in a tested semantic model instead of fragile export scripts.

  • Cost Reduction
  • Productivity Improvement
  • Risk Reduction

Solution

Kogan.com reorganized around a data-engineering-first analytics stack on Google Cloud, using BigQuery, dbt, and Looker as the governed core and then exposing that core through conversational AI. Raw staging data is funneled into BigQuery, where dbt builds tested fact and dimension tables and manages metadata that automatically surfaces inside Looker. Looker supplies the semantic layer and row-level permissions, while an internal enterprise MCP fleet server with OAuth wraps the open Model Context Protocol architecture so AI agents can query only the data a user is authorized to see. Batch jobs and transformations also run directly in BigQuery to keep costs controlled. The result is an environment where non-technical teams can ask questions through text, get secure instant answers from curated datasets, and hand dashboards back into Looker for shared use, rather than waiting on a reactive BI ticket queue.

Data flow

Operational retail data is loaded into BigQuery, transformed by dbt into facts and dimensions, and surfaced in Looker. Employees then query that semantic layer through an OAuth-protected MCP fleet server, which enforces Looker permissions before returning conversational answers or dashboards.

Solution architecture

4 components · 3 layers
  1. Storage
    • BigQuery Stores Kogan.com's curated retail datasets and runs batch transformations directly in the warehouse.
  2. Serving
    • Looker Provides the semantic layer, permission model, and dashboarding environment for governed self-service analytics.
  3. Orchestration
    • dbt Builds tested facts, dimensions, and metadata definitions that structure Kogan.com's analytics layer.
    • Model Context Protocol (MCP) fleet server Connects internal AI agents to Looker and BigQuery through an OAuth-secured conversational interface.

Architecture clues

  • Looker executes native row-level permissions
  • The MCP fleet server is wrapped with an OAuth security layer
  • Transformations run directly under BigQuery to keep processing costs optimized
  • dbt metadata and column definitions flow directly into BigQuery and surface in Looker

Evidence from the source

By unifying dbt and Looker, Kogan.com created a highly optimized, cost-effective data pipeline.
Data turnaround dropped from 40 minutes to under 60 seconds
This zero-trust approach mandates user authentication before granting server access
connected their curated BigQuery datasets and Looker’s semantic layer directly to internal AI agents through an enterprise Model Context Protocol (MCP) fleet server
transforming 150 non-technical team members into independent, data-driven vibe coders
Transparency Evidence & methodology 85/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value85/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Google Cloud

    Kogan.com customer story

    First-party
    https://cloud.google.com/customers/kogan-looker
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • Sitemap last modified Jun 26, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
  • Unverified extracted date Jun 26, 2026 · Google Cloud · Unknown Legacy extracted date without source-page confirmation.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.