Skip to content
BM Automation
FR Book a call

Due diligence M&A · Tailor-made systems

A missing document makes no noise.

Until the wrong time. Request list, data room, emails: we connect what your due diligence disperses. Each expected document maintains a sourced status, a manager and its next follow-up.

Talk about your request list Follow a request

Designed around your request list. Not one more data room.

Illustration: extract from a request list. Three arrivals are reported. Line 4.2, commercial leases, remains partial: two sites are missing and no notification says so, until monitoring gives it a deadline, a person in charge and a reminder to validate.

For the deal teams who maintain the request list, on both the transferor and acquirer sides. The missing, line by line

01Where the missing hides

What arrives is visible.
What is missing takes work to identify.

Between the request list, the data room, the assignor's emails and the advice lists, the missing person has no address. It lives in a hand-held chart, accurate as of the day it is updated.

A file is placed in the data room.

Does it respond to the right request?

The DAF responds with three attachments.

Which ones are complete?

The buyer’s counsel sends its list.

What is already being asked elsewhere?

The progress point is tomorrow.

Who's doing the counting again this evening?

A document does not arrive.

Nothing indicates it.

An arrival triggers a notification. An absence doesn't warn anyone.

Your analysts keep the list. Your associates discover the holes.

02The actual status of a request

“Provided” is not a status.
It's a hypothesis.

A document may be received and incomplete: two exercises instead of three, a forgotten subsidiary, an unsigned version, an absent annex. Useful tracking distinguishes what has happened from what actually meets the request.

The status

Six statuses.
Not a box checked.

Partial

4.2 Commercial leases, all sites

Three sites out of five. Metz and Tours are missing.

What it triggersA targeted follow-up on both sites.

The system
Proposed, with its controls
Your team
Statue

Doubt has its own box. The statuses are defined with your team.

Source

Each status has its proof.

The email, the file, the data room reference, the date: the status refers to what justifies it.

The deadline

A date transforms an absence into a signal.

Without a deadline, a lack remains silent. With her, he goes back on the planned day.

The manager

Opposite each lack, a name.

Not “the customer”. The person who holds the item, with the transferor or with an advisor.

The follow-up

Prepared with what is already received.

It reminds us of what is missing, what is partial and the deadline. It leaves when you send it.

History

Each step keeps its date.

Requested, received, completed, communicated: the thread remains datable.

What is missing. Whose home? Since when.

Illustrative representation · statuses to be defined with your team

03From list to progress point

The system keeps watch.
Your team decides.

AI agents with defined roles monitor, reconcile and prepare. They don't decide what is complete. They don't send anything.

Illustrative scenario. Monitoring is built according to your tools, your lists and your rules; it is neither a standard product nor a customer file.

Skip the demonstration

Step 01The list enters.

The system

Reads the request list, identifies what overlaps with the lists already received, suggests a category and a manager per line.

Your team

Validates structure, priorities and what falls outside the scope.

Step 02The documents are arriving.

The system

Identifies what arrives by email or in the data room and suggests an attachment to one or more lines.

Your team

Confirm what is ambiguous.

Step 03The lack takes place.

The system

Compares the expected with the receipt, checks what can be done according to your criteria, brings up what is slipping.

Your team

Statue on completeness.

Step 04The follow-up is being prepared.

The system

Write a reminder by manager: what is missing, what is partial, what has already been received, the deadline.

Your team

Adjust the tone, choose the moment, send.

Step 05The point stands.

The system

Produces the missing state, each line connected to its source.

Your team

Rereads and decides what is shared, with the client or the counterparty.

01/ 05

Scroll or choose a step

Each role is delimited.
No one inherits the rights of the next.

See what remains human

04Around your tools

Each tool holds part of the picture.
None shows everything that is missing.

We are not replacing your data room, your tracking file, or your CRM. We connect what everyone knows, where the reconciliation is still done by hand.

4.2Commercial leases, all sites

Cèdre Project · same request

What your tools know

Request list

Requested

Commercial leases, all sites · September 12

Data room

Filed

Three files in folder 4.2

Emails

Promised

“The last two follow next week. ” DAF, September 19

CRM

File

Cèdre Project · due diligence in progress

What only linked tracking knows

Actual Status

Partial · 3 sites out of 5

Responsible

Transferor's lawyer

Deadline

October 3

Follow-up

Draft ready · to validate

Each tool knows a fragment of the request 4.2. Connected, the monitoring also knows its real status, its manager, its deadline and its follow-up.

05Confidentiality & control

The rules of the file
also apply to the system.

Confidentiality agreement, access rights to the data room, information communicated in stages: the framework of the process precedes any connection.

Who does what

The system

Your team

Suggest · “Partial” status: three sites out of five, periods compliant.

The system observes and suggests. Your team decides and sends.

Framework to define togetherBM / Due diligence
01SourcesWhat is the system reading?

The agreed scope: the request list, authorized folders and boxes. Not all of your folders, nor all of your messaging.

02AccessWho sees what?

The rights follow those of the file. Information reserved for certain people does not become visible for convenience.

In a process with several buyers, the requests of one must never appear at another: this is a rule to be constructed and tested. hosting, conservation and traceability are defined according to your constraints; no universal device is presumed.

03ActionsWhat requires validation?

Send a reminder, submit a document, modify a shared status: each action is a separate authorization.

04The exceptionsWhen does the team take over?

Ambiguous connection, contradictory document, sensitive request, refusal to communicate: the system signals, it does not decide.

A proposed status may be false. Sources, testing on a known file and team validation reduce this risk. They do not replace judgment.

Another need?

Find out, three months later, why a document was deemed not applicable.

Discover Company Brain

06Experience in M&A consulting

A real experience.
Not a promised result.

For an international player in M&A consulting, we designed an internal application and a client area which centralize missions, targets, reminders, documents and reporting.

Customized design · M&A operational monitoring

What this experience brings

Structuring M&A files, monitoring follow-ups and sharing information with a client, between several tools and several stakeholders.

What it doesn't prove

A request list follow-up already delivered identically, a quantified time saving or shorter due diligence. Your first perimeter is verified in your context.

See the case on the M&A page

07A first perimeter

A closed file to test.
The next one to use it.

You don’t change tools in the middle of due diligence. We start from a real request list and, if a usable closed file is available, we test the follow-up on it before the next process. Otherwise, we agree on another verification set.

  1. 01

    Choose list.

    A real request list and the tools surrounding it.

  2. 02

    Borner.

    The sources read, the statuses, who validates what.

  3. 03

    Replay a closed case.

    Does the follow-up find what was missing, and when?

  4. 04

    Proceed to the next process.

    Agreed criteria, monitoring, corrections.

How to measure success

On a known file: the gaps found, the accuracy of the statuses, reminders without context errors, the time to produce a progress update.

Outside this first perimeter

  • Automatic sending of reminders
  • Review of the contents of the documents
  • Risk analysis

04weeks

Our MVP aims for a first value in four weeks, on an agreed scope. The cost estimate depends on the sources, access and rules used.

Starting from your request list

Practical questions

Before the next request list.

For which teams is this tracking of missing documents designed?

On the seller side, the M&A advisors and corporate finance firms who run the data room and collect the documents. On the buyer side, the funds, advisors and M&A departments who send the lists and must know, before the offer, what has not been communicated.

Our data room already has a request list. Why go further?

If it covers your tracking, keep it: we start by checking what it already does. The subject begins where the list, emails and customer intersect. If there is nothing left to connect, there is no project.

Should we change the tracking file, data room or CRM?

No. Monitoring starts from your tools and formats, including the list sent by the counterparty. The possible connections are verified in the scoping; no integration is assumed to be available until it has been reviewed.

Can AI declare a complete document?

No. It checks what is verifiable according to your written criteria, such as period, entity or version, proposes a status and reports its doubts. Completeness remains a team decision.

Do reminders go away on their own?

No. They are prepared by the manager, with the context of the file, then validated and sent by the team. An automated sending would be a separate permission, to be framed separately.

What to prepare for a first exchange?

A request list, even anonymized, or simply its structure. The tools involved and the people involved. No confidential documents are necessary.

Let's start from your list

What is still missing
from your current deal file?

Come with a request list, even anonymized. We look at where the missing is lost and what is worth connecting. No confidential documents are necessary.

Talk about your request list Or write to us