Enterprise system ยท Retail and commerce

Multi-agent retail intelligence on a knowledge graph

A multi-agent system that answers business questions, forecasts and draws its own charts by reasoning over a retail property graph.

Client
An enterprise retail organization
Engagement
Multi-agent system design and delivery
Our role
Agent architecture, graph modeling, forecasting, visualization
Status
Delivered
Specialized agents: query, insight, forecast, charts

4

Neo4j property graph as the shared source

Graph

Charts generated per question, not picked from a fixed set

Programmatic

Deployed on Google Cloud with Redis

GCP

In brief

Retail questions depend on relationships between products, stores, customer segments and time periods, and flat tables with a generic chatbot give answers that fall apart under follow-up questions. Involabs built a multi-agent system for an enterprise retail organization on a Neo4j knowledge graph, with four specialized agents for graph queries, financial insight, forecasting and chart generation. Each agent has one job, which makes it testable and failures easy to trace, and the system runs on Google Cloud with Redis.

Architecture

How it works

  1. Ask

    Business question

    • Natural language
    • Conversation context
  2. Query

    Cypher agent

    • Generates graph queries
    • Over the property graph
  3. Analyze

    Insight and forecast agents

    • Financial insight
    • Forecasting
  4. Show

    Chart agent

    • React charts generated programmatically
    • Explained answer

The situation

Retail questions are relationship questions: which products, in which stores, for which customer segments, over which periods. Flat tables and a generic chatbot give plausible answers that fall apart under follow-up.

What we built

A multi-agent question answering and intelligence system on a Neo4j knowledge graph. Separate agents handle graph query generation in Cypher, financial insight, forecasting and chart generation. Visualizations are produced programmatically as React charts for each question, rather than chosen from a fixed set.

How it is engineered

  • The graph is the shared source. Entities and relationships are modelled explicitly, so an agent can traverse a business question instead of guessing across a flat table.
  • Narrow agents, explicit hand-offs. Each agent has one responsibility, which makes each one testable and makes failures easy to locate. The agents are built with LangChain Deep Agents.
  • Deployed on Google Cloud, with Redis alongside the graph and the agents.

Why it matters

The same pattern, agents reasoning over a graph with narrow responsibilities, suits any domain where relationships carry most of the meaning, such as provider and expert networks in life sciences.

Have a similar problem?

Send us the problem and the constraints. We will tell you what it would actually take, starting with a fixed-scope assessment.