Skip to content
BM Automation

Anonymized case study M&A

An M&A case: structure the deal workflow and give clients the visibility they need

A mandate cannot be managed by exposing everything to the client. BM has framed two distinct spaces to connect internal monitoring to truly shareable information.

Confirmed scope: two spaces, 15 workflows in the defined MVP · Economic results and recurring use not consolidated

Conceptual installation: paper shapes pass through a controlled opening in a purple partition, while others remain on the internal side.
Internal → customer
The internal flowThe choice to shareThe customer view
01The starting point

A real, confidential case

A mandate divided between files, emails and tools.

The follow-up existed, but it had to be reconstructed to know where the mandate was and what needed to be transmitted.

01 / SourcesMultiple Numbers filesScattered targets, statuses and information
02 / ExchangesEmails and manual remindersFollow-up to redial between exchanges
03 / CRMDouble entry to DealCloudLack of consolidated view
04 / CustomerNo dedicated portalHistory to be kept over several years
02The visibility boundary

Two spaces, two responsibilities

The customer sees what moves the engagement forward. Internal operations keep their own access controls.

Selection depends on the role, mandate and confidentiality requirements. The team decides what becomes shareable.

Explore a type of information
Team space Internal

Work information

Statuses, exchanges and exceptions

The progress of the file is compared to the facts, reminders and arbitrations of the team.

Remains internal: notes, decisions and sensitive context
Sharing choiceHuman validation
Customer area Shared

Adapted view

Progress and next step

The client sees the state intended for him and what calls for his action, without internal management notes.

Visible only after validation

Illustration based on the perimeter of the case. This is not a capture of the project nor a BM interface available. Access, data and validations are defined for each mandate.

03Flow logic

From signal to sharing

Information is circulating.
Its visibility is decided.

The portal is just one view of this flow. The team maintains decisions and handles exceptions.

  1. 01
    Mandate Entries

    Emails, documents, actions

    Useful elements are attached to the file and its history.

  2. 02
    Internal space

    Monitoring and preparation

    Targets, statuses, reports, reminders and reporting feed the team’s work.

  3. 03
    Human threshold

    Choose, check, authorize

    Rights, visible content, wording and sensitive communications are validated before sharing.

  4. 04
    Customer area

    Progress and requests

    The customer finds the expected elements, the useful steps and the documents made visible.

  5. 05
    Back to the team

    Response or exception

    New information returns to internal monitoring for processing and judgment.

Illustrative sequence, based on the confirmed perimeter. It does not describe automation without human control or real-time synchronization.

04What was framed

Scope of this case

A system built around a real engagement workflow.

Two distinct spaces connect internal work to chosen customer visibility. This is not a catalog product.

15workflows in the framed MVP

Target identified: 20 workflows. These numbers describe the perimeter, not a gain or a level of use.

A / File

Targets · statutes · documents · reports

B / Coordination

Reminders · reporting · multi-year history

C / Connection

Synchronization with the existing CRM, according to the mandate rules

D / Access

Separate internal and client views, rights and sharing to be defined

05The scope of the proof

What this case does not demonstrate

The perimeter is confirmed.
The results remain to be measured.

No time saved, ROI, adoption rate, financial result or effect on closing is claimed here. The operation shown is illustrative; it does not expose any screen or client document.

For tracking diligence documents, see the dedicated use case

And in your team?

Where is the sharing threshold in your mandate?

Let's start with your files, tools and exchanges. We map the re-entries, the internal view, the information showable to the customer and the human validations.

Talk about your firm
06Useful questions

Before scoping

Some points to clarify.

Each mandate sets its own boundary between internal work and client information.

Is it a data room or a VDR?

No. A VDR manages transactional document sharing according to its own function. Here, BM describes a mandate flow, two views and sharing decisions around the client's tools.

Does the portal replace the existing CRM?

The case provides synchronization with DealCloud to avoid double entry. The exact role of the CRM and the data exchanges are defined based on the existing process.

What can be shown to the client?

Shared progress, requests, next steps and some documents can be shared. The team determines the rights, precise content and validations according to the mandate.

Can we start from our current tools?

Yes. The scoping begins with the files, emails, CRM and practices already in place, then identifies the useful connections and human arbitrations to be retained.