Demonstrations

Prototypes and concepts, clearly labelled.

None of these are client deployments. Every demonstration uses fictional or synthetic data and shows its current maturity: Concept, Prototype, Pilot or Production.

PROTOTYPEFictional / synthetic data

Relationship & Operations Intelligence

Problem: Customer, product and transaction data sit in separate systems, so relationship and operations teams lack one joined-up view.
For whom: Executives, relationship managers and operations leads in retail and private banking.
What you can try: Browse an executive overview, open a Client 360 view, review opportunity signals, mortgages, investments and transactions.
Data used: A fictional Swiss regional bank with 1,000 synthetic customers generated deterministically.
Systems that could connect: Core banking, CRM, payments, portfolio and mortgage systems — via read-only integration.
Limitations: No live data or integrations. Signals are illustrative rules, not validated models.

Open demonstration

PROTOTYPEFictional / synthetic data

Ask the Data

Problem: Simple questions about a portfolio or segment often require an analyst and a report request.
For whom: Relationship managers, analysts and management.
What you can try: Ask natural-language questions about the synthetic bank and see the answer with its basis.
Data used: The same synthetic regional-bank dataset.
Systems that could connect: Data platform or reporting layer, with role-based access.
Limitations: Rule-based question matching over synthetic data; not connected to any real source.

Open demonstration

CONCEPTFictional / synthetic data

FX Exposure View

Problem: Foreign-currency activity across clients is hard to see in one place.
For whom: Treasury, corporate banking and advisory teams.
What you can try: Explore a synthetic view of client FX activity by currency and segment.
Data used: Synthetic transaction data; no market data feed.
Systems that could connect: Payments, core banking, treasury systems.
Limitations: Illustrative only. No pricing, execution or advice.

Open demonstration

CONCEPTFictional / synthetic data

Connected Banking Journey

Problem: One apparently simple customer request can cross many people, systems, documents and controls.
For whom: Banking leadership, operations, compliance and technology teams.
What you can try: Follow one request through the customer view and the bank operations view side by side.
Data used: Conceptual structure only — no data.
Systems that could connect: Identity/KYC, onboarding, workflow, document generation, core banking, notification, reporting.
Limitations: Concept structure. No backend integration exists.

Open demonstration