What we actually sell
If you cannot say what a thing does and which records it holds, you are selling a category rather than a product — and the buyer can tell. One sentence each, and the entities behind them.
01 The shape of it
Six things, in buyer language
The order matters: the hub connects, resolution makes the records mean something, governance makes them defensible, and only then does anything agentic work.
Data Hub
Connects SAP, cloud apps, legacy systems and files into one governed layer without moving or replacing a source. 187+ connectors, no-code, on-prem and cloud.
Holds: sources, pipelines, schemasEnterprise 360 and entity resolution
Dedups and matches records across systems and survives the best values into a golden record — global parent and local site — then puts a live view on top.
Holds: Customer, Supplier, Legal entity, Item, EmployeeData Governance
Glossary, quality rules, lineage and policy in one place, so a number can be traced to source and an AI answer can be signed off rather than trusted.
Holds: terms, rules, lineage graph, policies, stewardsData Product Factory
Packages data like a product — owned, documented, governed — and ships it as a dashboard, an API or a feed from sources that already exist.
Holds: data products, contracts, consumersData Fabric
Activates data where it already lives rather than demanding a multi-year migration onto one cloud. Vendor-neutral, no-code, business-led.
Holds: the estate as it is, virtualisedKnowledge Graph, Copilot and Agent Factory
The graph gives an agent the relationships between entities; the copilot answers from governed data; the factory builds and runs the agents. Nothing here works on ungoverned inputs.
Holds: entities, relationships, agents, runs02 Questions
Six things to answer without opening a slide
If any of these needs a deck, it needs practice instead.
- What does the hub do that an ELT tool does not, in one sentence?
- Which entities do we resolve, and what does "survivorship" mean to a business audience?
- What has to be true before an agent can answer a question the business will act on?
- Where does the customer's existing warehouse sit in our architecture — replaced, fed, or left alone?
- What does a deployment actually deliver in the first 60 days?
- Which of the four layers did each published study use, and why does that matter to this buyer?
03 Sequence
How a deployment sequences
Six stages. The reason to know them is that buyers ask what happens after signature, and a vague answer there costs more deals than a feature gap.
04 Reference
The four layers, and what each one holds
Eight published deployments, the same four layers in different combinations. Buyers recognise their own problem in the middle column faster than in a product name.
| Layer | What it does | The records it holds |
|---|---|---|
| Enterprise 360 | Resolves entities across systems into governed golden records with a live view on top | Customer, Supplier, Legal entity, Item, Employee |
| Knowledge Graph | Holds the relationships between those entities so questions can traverse them rather than join them by hand | Entities, relationships, attributes, provenance |
| AI Copilot | Answers business questions from governed data, with the lineage to show where the answer came from | Questions, governed metrics, answer provenance |
| Agent Factory | Builds and runs agents against those governed records, with policy applied at the point of action | Agents, tools, runs, approvals |
05 Language
Say this, not that
The right-hand column is what gets said when the seller is describing a category instead of a product.
It connects the systems that hold your records, resolves them into one governed version, and makes every number traceable back to source.
It is an end-to-end AI-powered data management platform.
It stays. The hub connects the sources and governs the definitions; the warehouse keeps doing what it is good at.
You would migrate off it eventually.
A live 360 on one domain in about 60 days, which is deliberately one domain rather than the estate.
It depends entirely on scope.
06 Questions
Frequently asked
Do we replace the customer's existing stack?
Almost never, and saying otherwise loses technical credibility in the first meeting. The hub connects sources without moving or replacing them; the warehouse, the BI tool and the ERP all stay where they are.
What is the honest difference from an integration tool?
An integration tool moves data and stops. The hub governs what the data means once it arrives — resolution, glossary, lineage and policy on the same records — which is the part that decides whether an AI answer can be signed off.
See what the buyer sees
Every claim in this module traces back to a page the customer can read for themselves.