Home/Platform/Integrations and vertical apps
CONNECT & APP · inside the work

Intelligence goes where people already work.

DBRAINS does not ask you to change tools. The knowledge in the Brains reaches the place where the work already happens: inside the CRM, ERP, mail, chat and drive with CONNECT, or in a dedicated APP when a process needs a place of its own. Underneath, it is always the same knowledge.

How it connects

Two routes, one body of knowledge.

CONNECT and APP both draw on the Brains: the same company knowledge, organised by department and governed by the same permissions. Only the place where the work happens changes, inside your tools or in a dedicated environment.

knowledge from the Brains reaches the tools outcomes and new data return to the Brains

CONNECT · the links

It connects to the tools you already use and works both ways: knowledge reaches the CRM, ERP, mail, chat and drive, and what happens there returns to the Brains, which stay current without manual work. Through MCP where it is available, otherwise REST APIs and webhooks.

APP · the processes

An environment built around a single process, from start to finish, and fed by the Brains: this is where AI actually does the work. It is needed when the tool you use cannot be connected, or when a process deserves an interface of its own.

The order we try

Your tools first, a new environment second.

We do not move people onto new software: we bring the intelligence to where they already work. It is tried in this order.

01

It connects on its own

If the tool supports MCP, it attaches to DBRAINS carrying each Brain's permissions. No custom integration.

02

It integrates directly

If it has REST APIs or webhooks: context and drafts go out, outcomes and results come back.

The goal: mail, chat and drive connected in minutes, with no manual data entry.

03

A dedicated app is created

If there are no connectors, an APP is activated: an environment for that process, on the same knowledge.

The APPs · one app per process

An environment dedicated to a single process.

Not one app per department, but one app per process: the place where that activity happens from beginning to end. For each one, what changes compared with today.

Quote preparation

Sales · Operations
Today

Part numbers looked up by hand in catalogues and price lists.

With the app

Request parsed, part numbers proposed, quote already drafted.

CV screening

HR
Today

CVs opened one by one, the comparison held in your head.

With the app

Every application with a summary, matches and gaps.

Order handling

Operations · Sales
Today

Availability in one system, lead times in another.

With the app

Order checked against the real times for that part number.

Contract review

Legal · Finance
Today

Line-by-line reading, precedents recalled from memory.

With the app

Differences from the standard highlighted, with the precedent.

Ticket handling

Support · IT
Today

Every ticket starts from nothing.

With the app

The answer starts from the precedent, and recurring cases become a signal.

Content creation

Marketing · Sales
Today

Blank page, then rewriting to sound like the company.

With the app

A draft already in the approved language and arguments.

The list is not a closed catalogue: an app comes from a mapped process, not from a price list.

Which process do you want to put into production?

We map it, automate it and bring it to where your team already works: inside your tools, or in a dedicated app.