Google Cloud Consumer Goods Switzerland

Blackroll

Customer Service Automation

Blackroll needed one cloud environment where commerce, wearable, and app data could be unified to power personalized recovery coaching while also accelerating software delivery for a lean digital team.

140 engineering hours saved in 25 days with
25% lower running costs forecast with

Reported impact

Business outcome

Blackroll built a digital recovery coach, lowered projected operating costs, and dramatically improved developer throughput for its platform refresh.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement

Solution

Blackroll uses Google Cloud to address this challenge: Blackroll needed one cloud environment where commerce, wearable, and app data could be unified to power personalized recovery coaching while also accelerating software delivery for a lean digital team. BigQuery builds a unified view of ecommerce records and mobile app events to inform recovery experiences, serving as the storage layer. Cloud SQL pulls daily wearable data such as sleep patterns and activity loads into the platform, serving as the storage layer. Cloud Run powers the headless platform services and the Antigravity orchestration runtime used to speed software development, serving as the serving layer. Firestore supports the digital ecosystem’s headless application architecture, serving as the storage layer. Gemini powers the AI recovery coach and other automated tools used across the platform, serving as the compute layer.

Data flow

Ecommerce records and app events land in BigQuery, Cloud SQL syncs wearable signals into the platform, Cloud Run and Firestore support the headless application layer, and Gemini uses the combined data to personalize recovery routines and coaching.

Solution architecture

5 components · 3 layers
  1. Compute
    • Gemini powers the AI recovery coach and other automated tools used across the platform
  2. Storage
    • BigQuery builds a unified view of ecommerce records and mobile app events to inform recovery experiences
    • Cloud SQL pulls daily wearable data such as sleep patterns and activity loads into the platform
    • Firestore supports the digital ecosystem’s headless application architecture
  3. Serving
    • Cloud Run powers the headless platform services and the Antigravity orchestration runtime used to speed software development

Architecture clues

  • A single engineer used Antigravity to manage 11 parallel workstreams during a website redesign evaluation
  • Cloud Run-based orchestration reduced root-cause analysis from days to hours
  • The new infrastructure forecast a 25% reduction in running costs

Evidence from the source

140 engineering hours saved in 25 days with
25% lower running costs forecast with
Blackroll then uses Cloud SQL to securely pull daily wearable data like sleep patterns and activity loads into the platform.
Tasks like root cause analysis that used to take our teams days now take just a couple of hours.
The team gathers ecommerce records and mobile app events into BigQuery to build a unified view of customer data and habits.
has always understood the importance of recovery to people's overall wellbeing. Since launching Germany’s first fascia foam roller in 2007, the company has helped millions of people take control of their activation and regeneration to live a pain-free, healthy, and powerful life. Now, as wellness habits shift toward sustainable, lifelong health, Blackroll is evolving from an equipment manufacturer into a complete digital recovery platform for everyday support.
Transparency Evidence & methodology 95/100 reference value · 82% confidence · 2 sources

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 value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/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 impact25/25
    2 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency9/10
    2 source references 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

    Blackroll customer story

    First-party
    https://cloud.google.com/customers/blackroll
    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
  2. BLACKROLL

    Impressum - BLACKROLL

    First-party
    https://blackroll.com/ch/de/service/impressum

    BLACKROLL AG, Hauptstraße 17, CH-8598 Bottighofen, Schweiz; Sitz der Gesellschaft: Bottighofen.

    Source type
    Official company website
    Supports
    • Region

Date evidence

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