M&A · The first file
Launch an M&A mandate without losing the initial information
Missing information at the beginning becomes re-entered later. BM structures the collection; your team decides what is referred to.

01 / What disperses
Six pieces of information.
A starting point.
The contact is in an email. The target in a file. Access in a conversation. Who carries the sequel?
01Interlocutors
Who responds, who validates, who must be informed?
02Documents
Which version is authentic and where can I find the original?
03Target data
Which existing file should be attached to the mandate?
04Decisions
What scope was agreed, and by whom?
05Access
Who can view, modify or share?
06Actions
Who takes control, over what and for when?
02 / The starting grid
Each element
keeps its origin.
One reference per data, in your existing tools. A person responsible for each shortage. Not a second base to hold.
- Element
- Customer contact
- Source
- Launch email
- Owner
- Deal team
- Status
- Received
- Validation
- To be confirmed
- Next action
- Confirm Referrer
- Element
- Target perimeter
- Source
- Framework note
- Owner
- Mission Director
- Status
- Proposed
- Validation
- Agreement expected
- Next action
- Refereeing the perimeter
- Element
- Financial documents
- Source
- Shared folder
- Owner
- Customer representative
- Status
- Missing
- Validation
- Not examined
- Next action
- Prepare the request
Received does not mean validated. An absent source or unavailable access remains an open point.
03 / From collection to continuation
Collection prepares the file.
Your team authorizes the next step.
BM builds this passage around your sources, your rights and the validations of the mandate.
Framed collection
Gather the authorized elements, with their source.
Human control
Confirm attachment, scope and gaps.
Reference file
Link the selected element to its source and its agreement.
Tasks and CRM
Prepare for the rest. Write according to the validated rule.
An agreement is not a confirmed writing.
The team authorizes the update. The CRM has not yet changed.
The request goes to the CRM. Without feedback, the execution remains unknown.
The trace links source, agreement, request and confirmed result. An error remains visible.
04 / What remains human
The deal file takes shape.
The investment thesis stays yours.
- Mandate Thesis
- Sensitive data
- Arbitrations
- Priorities
- Customer relations
05 / Your next mandate
Let's take your
next launch.
What information should be collected? Who validates them? Where should they live? Let's start from your actual process to define a first tailor-made flow.
Frequently asked questions
Before opening
the file.
Should we change our CRM?
Not necessarily. BM starts from your CRM and your document spaces. The connection possibilities, the reference of each data and the writing rights are checked during scoping.
What do we do with missing information?
It remains visible, with an owner and a next action. A request can be prepared; its validation and its sending are distinct stages.
What happens to sensitive data?
Authorized sources, recipients, hosting and retention are defined with your team before any connection. Collecting does not give the right to share.
Is it also the monitoring of due diligence?
This page covers the start of the mandate. Monitoring of the request list, documents and diligence reminders has its own perimeter.