Skip to content
Method·October 2026·8 min read

Connecting AI to your email, your ERP and your documents

An assistant that doesn’t know your business stays an intern. How to give it the memory of your clients, parts and prices, without opening a security hole.

Two people looking at data on screens in an office

Your best employee knows what was promised to each client, the price of the last order and which part caused a return last year. An AI assistant connected to nothing knows none of that. The day it gets access to that memory, it becomes truly useful. Here is what it takes to connect AI to your business data, and to do it properly.

What it looks like when it is done right

Group NDL bridges Canadian manufacturers and factories in Asia. Its history is 20 years of email in French and English. Today, AI has read and sorted close to 240,000 of those emails, and it finds 352 part numbers with their exchanges and prices. Every morning, the inbox is sorted and replies to clients are already drafted.

For the team, a question like “what did we promise this client on this part?” takes a few seconds, with the emails that prove it. The full case study tells how.

Connecting AI to your data
The three memories of a business.
01

Email

The real history of every client: what was promised, the prices negotiated, the quality issues.
Connects through Microsoft 365 or Google Workspace
02

The ERP

Parts, materials, prices, orders and lead times. Structured, rarely as clean as people think.
Connects through the ERP’s API
03

Documents

Technical drawings, quotes, procedures, reports, Excel files passed from one inbox to the next.
Connects through SharePoint, OneDrive or the server
Group NDL turned 20 years of email into the memory of an ecosystem of AI solutions.
In production
Emails240,000read and sorted
The history made usable by AI
Parts352part numbers
Found with their exchanges and their prices
Migration20 yearsof email
To Microsoft 365, without a minute of downtime
Group NDL case study
The three places where what your company knows lives.

Your company’s three memories

In almost every business we visit, what the company knows lives in three places: email, the ERP or management software, and the documents that circulate. Email is often the richest source, because that is where the real conversations with clients are.

An AI project that really changes something connects to at least two of those memories. An assistant that only sees what you paste into its window helps you write. It does not yet help you work.

Before AI, put your data in the right place

This is the step nobody sees, and sometimes the longest one. At Group NDL, email had lived for nearly 20 years on an old server at a web host, and AI tools do not connect to that kind of server cleanly. We first moved it to Microsoft 365, without a minute of downtime for the team.

What we learned doing these moves for more than one client:

  • Inventory before copying. Mailbox by mailbox, folder by folder. We almost always find working folders in the wrong place, sometimes even in the trash.
  • Look for forgotten rules. An automatic copy set up ten years ago does not follow the move, and nobody notices until an important email goes missing.
  • Copy first, switch later. Until the switch is made, the old server keeps receiving. Nothing is irreversible.
  • Use the move for security. Two-factor sign-in and phishing protection, which old servers did not offer.

If your email is already on Microsoft 365 or Google Workspace, this step is done.

How AI connects, without the jargon

For a long time, every connection required hand-written code. Since late 2024, there is a standard plug, the Model Context Protocol (MCP). Anthropic created it, and it is now run by a Linux Foundation project with OpenAI, Microsoft and GitHub at the table.

What matters for you is that we decide exactly what AI is allowed to do: search an email, read an order, prepare a draft. Nothing more, and it can all be cut off at once.

The ERP connects through its API, the door the vendor provides for other software. A tip from a current project: ask what the API really allows before signing anything. At one manufacturer, it could read production but not reschedule it directly. Better to know at the diagnostic than halfway through.

Read, prepare, act: in that order

Connecting AI to your data
We open access in this order, always.
Step 1

Read

AI searches, summarizes, sorts and finds.
Every exchange about a part, with the latest price, in ten seconds.
Step 2

Prepare

AI writes the draft, with the right signature and the attachments.
A person reviews and sends.
Step 3

Act

Create an order, change a date, update a record.
Only once it has proven itself, with a trace of every action.
Sending: never alone.
A badly worded draft costs thirty seconds. An email sent to the wrong client costs a relationship.
The method we follow on every engagement
We open access one level at a time.

First reading: AI searches, summarizes and finds. Then drafts: it prepares the reply, with the right signature and attachments, and a person sends it. Direct actions, like creating an order or changing a date, only come once the first two levels have proven themselves.

A draft to fix costs thirty seconds. An email sent on its own to the wrong client can cost a relationship. That is also how our service connecting Claude to Outlook works: Claude prepares, it never sends.

Security, in practice

  • An account reserved for AI, with no admin rights. We know what it sees, and we can cut it off without touching employee accounts.
  • What does not belong stays out. Management mailboxes, payroll and HR are excluded from the start.
  • A Law 25 assessment before connecting. It is required when personal information leaves Quebec, which happens with most AI services. Our Law 25 guide walks through it.
  • The team is told. A simple notice: what AI reads, what it does and what it does not do. People get on board better when they do not find out by accident.

What it changes for your team

Before, you search Outlook with three keywords, open twelve emails and ask a colleague whether they remember last year’s price. After, you ask the question and the answer comes with its proof.

And the day an experienced employee retires, what they knew stays in the company.

Where to start

Pick one memory and one question that comes back every week, often “find everything about this client or this part”. We connect read-only, measure search time before and after, then open up drafts. That is our four-step approach, applied to your data. And if your data is not ready yet, we start there: here is why.

Frequently asked questions

Do we need Microsoft 365 to connect AI to our email?

No, Google Workspace connects too. What makes things harder is an old email server at a web host. In that case, a move to Microsoft 365 or Google often comes first.

Can AI send emails on its own?

Technically, yes. We don’t do it: AI prepares drafts, and a person reviews and sends them.

What is MCP?

A standard plug that lets an AI tool use specific actions inside a piece of software, such as searching, reading or preparing a draft. We choose which actions are allowed.

Does our data leave the company?

It is sent to the AI service when it is processed. That is why a business contract, which excludes training on your data, and a privacy impact assessment in Quebec matter.

Can we connect our ERP to AI?

Most recent ERPs have an API. The real question is what it lets you read and write, and the state of the data behind it.

Source on MCP: GitHub, announcement of the Model Context Protocol moving to the Linux Foundation, December 9, 2025.

This work falls under our AI acceleration and automation service: we automate, one task at a time, the work your team keeps redoing, inside the tools you already use.

Your email and your ERP know a lot

In 30 minutes, we look at where your information lives and what AI could do with it. No commitment.

Group NDL turned 20 years of email into the memory of an ecosystem of AI solutions
This one was delivered
Group NDL

What this article argues, we put into production for a client. The case walks through what was built, how, and what changed.

Read the case study →