Brain

Integrations: the systems Brain reads from

Brain answers from your own material, and most of it already lives in the tools your company runs. A connection brings it in, keeps it current, and attaches the source to every answer. Nobody keys anything in twice.

Tell us what you run

See every module

Your own installation, in the EU Connected once, reused by every module The source attached to every answer

How a connection works

Read, kept current, cited

Three things every connection does, whichever system sits at the other end.

Brain reads

A connection pulls what a module needs: figures, records, documents. They land in Memory with the date and the system they came from.
Kept current

Each connection refreshes on a schedule set for that system. Every record carries the time it was last read, so you know how fresh an answer is.
The source attached

Every answer names the system and the date it drew on. You can open the source before you act on it.

What it reads

Four kinds of source

Which connections get built is part of solving your problem. These are the families we connect most, and the modules each one feeds.

Business intelligence

Your live figures already sit in the BI stack. Brain reads the same numbers your team works from, so a brief and a dashboard show the same figure.

Among them: Power BI Tableau Snowflake
Feeds: KPI Dashboards Morning Brief Foresight

Operations tools

Budget actuals, orders, and costs live in the operations tools. Brain reads them, so a strategic call sits on what is actually happening.

Among them: SAP Dynamics 365 Odoo
Feeds: KPI Dashboards Risk Register Foresight

CRM

The pipeline lives in the CRM. Brain reads deals, stages, and notes. Advisory Chat can reason about them, and the Morning Brief flags what moved.

Among them: Salesforce HubSpot Pipedrive
Feeds: Sales Pipeline Relationships Morning Brief

Documents and files

Board packs, plans, contracts, and minutes. Uploaded as they are, indexed, and kept with their dates. They come back exactly as you gave them.

Among them: Board packs Contracts Minutes
Feeds: Core Memory Advisory Chat Meetings

See every module it feeds

The outside view

Competitors, markets, and regulation come in through Wisdom, scoped to your industry and geography. They land next to your own numbers, filtered to the objectives you actually hold.

See what each shape includes

Built once

Stood up once, reused after

A connection is part of the ground under the first problem. Everything built later uses the same one.

Built during the first problem

The connections a problem needs are stood up in the first weeks, inside your own environment. Nothing is connected on faith.
Inside your own installation

Every connection runs in your deployment, in the EU. Credentials sit in a managed store, per customer, never in a spreadsheet.
The narrowest access that works

We ask for the least access the connection needs, and we name it before it is granted. Read access is the default. A write back into your system is a decision you make, never a default.
Yours to keep, yours to switch off

The connection is a tool we built, so you own it. Revoking access is a change inside your installation. If Brain stops, everything exports in open formats.