CRM · Emails · Files
Stop rebuilding deal reports across CRM, email and files
When the status lives in an email and the rest in a note, the reporting is reconstructed by hand. BM connects useful facts; the team keeps the decision.

The committee sees a status.
The team picks up the pieces.
CRM is aging while exchanges are progressing. Before the committee, the team collects the sources and sometimes guesses the next action.
The risk: take a guess for a status.
A message received
does not update a CRM.
Six distinct states. This illustration does not affect any tool.
Observation · two sources
Two sentences. Two states.
The CRM says “In preparation”; the email says “Offer received”. The link with Orme and the reach of the message must be verified.
CRM status: unchanged.Proposal · to be validated
“Offer transmitted”?
This wording is a proposed update, based on the reconciled elements. It is neither a fact observed in the CRM, nor a status applied.
CRM status: still “In preparation”.Human decision
The team agrees.
An authorized person validates the proposal and its sources. This agreement authorizes a change request; it does not prove that the CRM has changed.
Agreement registered. Execution not requested.Request sent
The CRM has yet to respond.
The request to apply “Offer transmitted” is issued according to the validated rule. Without feedback from the system, we cannot conclude anything about the execution.
Execution: unknown.Return of execution
Confirmed, not yet logged.
Explicit feedback confirms the CRM update. The trace of this feedback and the link to the decision remains to be recorded for reporting.
Execution confirmed · traceability pending.Reporting trace
The decision becomes readable.
The file keeps the source, the agreement, the request and the return of execution. Reporting can distinguish the initial fact from the confirmed update.
Confirmed and recorded.If a supporting document becomes unavailable, the historical confirmation remains recorded; the evidence is marked as not searchable. We do not retroactively erase what has been confirmed.
Two sources diverge.
The system stops there.
Two attributed assertions diverge. Bringing them together reveals the conflict; only the team can referee it.

CRM · deal team“In negotiation”
Report · mission manager“Waiting for agreement to move forward”
To be refereed by the team→Which definition of stage and which source are authentic?
First the flow.
Then the code.
BM starts from your tools, access rights and business rules.
Explore the M&A approach- 01
Choose what is authentic.
Map sources; define the reference of each data.
- 02
Write the step criteria.
Share the meaning, evidence and access to each step.
- 03
Link under authorization.
Reconcile the facts, propose updates, show exceptions and validations.
- 04
Check the return.
Separate agreement, request, execution and trace; measure usage.
Less collection.
More context.
The team sees the elements to be judged, without a hypothesis becoming a status.
- Defined step and last verifiable fact
- Source, date and access required
- Responsible, next action and deadline
- Shortcomings, discrepancies or decisions to be arbitrated
CRM can stay. Each piece of data has a reference and a validation rule.
A real perimeter.
Results to measure.
Starting point: Numbers files, emails, double entry to DealCloud and unconsolidated view.
Targets · customer portal · reminders · reporting · CRM synchronization
Scope confirmed. Unconsolidated economic gains and recurring use.
Let’s start with a real
pipeline review.
What statutes are reconstructed before the committee? Where do we re-enter the information? What first rule would make monitoring verifiable?
Talk about your firm Or write to BM →Before connecting
the tools.
Should we replace our CRM?
Not necessarily. We start from existing tools and define which data is authentic. A connection depends on the access and rules validated during scoping.
Can an email change a status alone?
Only if an explicit rule allows it. In the Orme scenario, the email first leads to a proposal; the team validates before any update request.
What if two sources contradict each other?
The conflict remains visible with its attributions. An authorized person arbitrates the definition of the step and the source chosen.
Is it a data room or M&A software?
BM designs the process between existing tools. The data room retains its specific role for transaction documents; documents tracking is treated separately.