IBM Software / SaaS Germany

yappyBuy GmbH

Customer Service Automation · Marketing Personalization

yappyBuy needed an enterprise-grade AI stack for its Buddy shopping assistant so it could personalize search, product support, and checkout interactions while meeting European data-privacy and governance requirements.

analyzed over 1 million online comments

Reported impact

Business outcome

yappyBuy accelerated development of its Buddy assistant, gained a governance- and GDPR-aware AI foundation for open-beta rollout, and built a platform it expects to use for personalized search, support, upsell, and checkout optimization across B2B and B2C commerce clients.

  • Compliance
  • Customer Experience
  • Revenue Growth

Solution

yappyBuy built its Buddy e-commerce assistant platform on the IBM watsonx portfolio to support personalized shopping journeys across online stores. IBM watsonx.ai serves as the enterprise AI studio and model runtime, where the team began with IBM Granite models and Meta Llama 3.1 for conversational and agentic flows. IBM Watson Discovery, watsonx.data, and watsonx.governance extend that core stack so Buddy can ground responses with retrieval-augmented generation and govern how the assistant is used as the startup moves from pilot to open beta. The platform ingests PDFs, JSON files, CSV files, Word documents, databases, and dynamic API responses to provide contextual answers, product guidance, and support during browsing and checkout. IBM also helped yappyBuy tune latency and cost, which matters for real-time commerce interactions, while preserving control over data-storage and processing locations needed for GDPR-sensitive European deployments.

Data flow

Merchant documents and data sources such as PDFs, JSON, CSV, Word files, databases, and live APIs are fed into the Buddy platform, where watsonx.ai uses Granite or Llama models with retrieval-augmented generation to answer shopper questions, guide product discovery, and support checkout interactions with grounded responses.

Solution architecture

6 components · 4 layers
  1. Compute
    • IBM watsonx.ai Provides the enterprise AI studio and runtime for Buddy's conversational and agentic assistant workflows.
    • IBM Granite Supplies low-latency large language models for parts of the shopping assistant workflow.
    • Meta Llama 3.1 Works alongside Granite as one of the selectable models for conversational commerce use cases.
  2. Storage
    • IBM watsonx.data Supports the data layer used to provide contextual information to the assistant.
  3. Serving
    • IBM Watson Discovery Helps the assistant retrieve relevant content from enterprise data sources for grounded responses.
  4. Governance
    • IBM watsonx.governance Provides governance, risk, and compliance controls for the AI assistant platform.

Architecture clues

  • IBM helped optimize latency for e-commerce interactions by increasing use of Granite models in agentic workflows.
  • The platform uses retrieval-augmented generation to inject merchant data into LLM responses.
  • yappyBuy selected IBM in part to control data-storage and processing locations for GDPR compliance.

Evidence from the source

Currently the primary IBM watsonx products of our platform include watsonx.ai, IBM Watson Discovery, watsonx.data and watsonx.governance.
We started off with the IBM Granite models together with Meta Llama 3.1, the next generation of Meta’s open LLM, for our conversational tool with agentic flow capabilities.
parts of our conversational agentic workflows now include extensive use of the IBM Granite models that decrease latency and optimize the user experience.
we analyzed over 1 million online comments
we can now successfully incorporate documents, such as PDFs, JSON files, CSV files, [Microsoft] Word docs and databases, or dynamic API responses to provide contextual information
Transparency Evidence & methodology 71/100 reference value · 87% 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 value71/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 specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • 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 provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/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. IBM

    yappyBuy GmbH customer story

    First-party
    https://www.ibm.com/case-studies/yappybuy
    Source type
    Vendor-published customer story
    Published
    Nov 13, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.