- Where it gets stuck
- The partners who bring in mandates are the ones running execution. While a process is live, the long list, the warm introductions and the promised coffees wait, and the pipeline empties just as the deal closes.
- What the workflow does
- An origination brief is prepared from your CRM, public filings, the press and your PitchBook or Capital IQ licence where its terms allow: owners and investors on your origination lists, the recent signals worth a call (a sponsor in year five of its hold, a new CFO, accounts just filed) and a proposed first message. Parties met under a mandate NDA or bound by a non-solicit are filtered out, and each name is checked against your conflict list. The partner decides who to approach and approves each message before it is sent.
AI for M&A advisory firms
Fourteen parties signed the NDA, and the client wants to know by Thursday which of them are still serious.
By Wednesday evening the party-by-party update is ready, each line traced to the data room activity report, the tracker or the call note it came from, and you recommend to the client who stays in the process. We work with Outlook, your CRM or the Excel file that stands in for one, and your virtual data room, by connection or export.
Three jobs cap how many mandates an M&A boutique can run, and AI for M&A advisory firms is built around them: origination during live deals, the weekly process update and the due diligence question log. AI Jungle installs these workflows in your existing tools, the deal lead approves every output, and every message to a buyer, investor or prospect is sent by your bankers.
Today
- Client asks where each party standsData room logins, questions and calls checked party by party, by handAssociate’s evening
- Due diligence questionsQ&A module, request list and inbox out of syncQuestions waiting on management
- Long list for the next mandateUntouched since the current process launchedOrigination stalled
With the workflow
- Party-by-party updateData room activity, questions asked, indication of interest, management meeting requestedDeal lead recommends who stays in
- Question logEach question ready to route to its owner at the client, with the data room index referencesTracked until answered
- Origination briefOwners and investors on the long list, with recent signalsPartner chooses who to call
Three moments when an M&A boutique still carries the process by hand
Each one repeats on every mandate, depends on records the deal team already keeps and ends with a partner’s or the deal lead’s decision.
Origination stops the week a mandate goes live
The client update is rebuilt by hand every week
- Where it gets stuck
- Once the teaser and the process letter are out, the client wants to know every week where each party stands and who is likely to bid. The signs are spread across the data room logs, the tracker, the inbox and call notes, so an associate pieces them together by hand.
- What the workflow does
- A draft update is prepared party by party from the tracker, the data room activity report and your call notes: NDA date, information memorandum opened, questions asked, indication of interest received or not, management meeting requested. The deal lead judges who will reach the bid deadline and decides what the client hears.
The due diligence question log falls behind the data room
- Where it gets stuck
- Questions come through the data room’s Q&A module and by email from advisers who skip it. The answers belong to the client’s management and are chased by email, so the module, the request list and the inbox disagree in the week of the bid deadline.
- What the workflow does
- Each new question is logged, matched to the documents already in the data room and given a proposed owner at the client. The associate routes each question with its index references, so no document leaves the data room. Management answers, and the deal lead checks the answer before releasing it in the Q&A module. Questions still open before a call or a bid deadline are flagged.
Which flow should you start with?
Three questions, about a minute. The answer points to one of the moments above, or to a smaller step when a workflow would be too much.
Answer the three questions to see where to start.
This is an exercise: nothing is sent when you use this selector.
Do we have to change our CRM or data room?
No. The workflow reads the trackers and documents your deal team already keeps, prepares a draft and returns it to the place you work, once the deal lead has approved it.
- A question or a deadline arrivesA due diligence question, Thursday’s update, a bid deadline, a signal on a target.
- Mandate records are readTracker, CRM and data room activity, mandate by mandate, within the access you allow.
- A draft is preparedUpdate, routed question or origination brief, each point linked to its source.
- The deal lead decidesNo update, answer or message leaves without the deal lead’s sign-off, and corrections are kept as format rules for that mandate only: no mandate’s content is reused on another.
- Back into your toolsThe update leaves from Outlook and the tracker is brought up to date.
- Outlook
- Excel
- PowerPoint
- HubSpot
- DealCloud
- Datasite
- Intralinks
- iDeals
Three conditions before anything acts
Your existing tools
The workflow runs inside the tools you already pay for, with the access rights they already have, so the team keeps its usual screens.
A named person approves
Every draft waits for a named person. Nothing goes out in the firm’s name without that approval, and exceptions go back to a human.
Every step leaves a trace
Sources, drafts, corrections and approvals are recorded, so you can see why an output was prepared and improve the next one.
Looking for a specific product?
PitstopThe shared workspace for mandates, relationships, sources and decisions, with access kept separate from one mandate to the next.Discover Pitstop →Managed AI agent serviceWe build, run and maintain one defined workflow, such as the weekly process update, with named approvers, a written scope and handover notes.See the managed service →
No M&A advisory client yet: our only published case is an executive search firm
AI outreach case study: Asia-Connect. Documented outreach at Asia-Connect over three months. One client and one workflow; results depend on context and execution.
“In the last three months, the agent helped me to book more than 90 qualified meetings with executives I would never have had time to reach, and I approved every single message before it went out. It works while I am in meetings.”
That case covers outreach approved by a partner, the closest thing to the origination moment above. That is also where a test can start without any client data: it uses only the firm’s own origination lists and public filings, and contacts or information obtained under a mandate NDA are excluded. For the process update and the question log, we fill your blank tracker template with a fictional mandate and a fictional activity log in your data room’s format, so no real deal, live or closed, is used. Read the case study
Questions M&A partners ask before a call
Which M&A firms is this for?
Owner-led M&A advisory, corporate finance and boutique investment banking firms where the partners who originate mandates also run them, on sell-side, buy-side or fundraising processes. The workflows cover origination, process administration and the question log. Judging bids, valuation, structuring advice and negotiation stay with your bankers.
How is this different from ChatGPT?
Where ChatGPT answers whatever is pasted into it, a workflow starts from an event in your tools, reads only the mandate records you allowed, prepares the draft in your format, waits for the deal lead’s approval and keeps a trace of every correction. Nothing from a mandate is pasted into a consumer chat tool.
Can you connect our CRM and our data room?
Often, through the connections and access rights your CRM and data room provider already offer, and a tracker kept in Excel works too. Whether your data room’s and data providers’ terms allow a third party to process their content is checked before anything is built. When a system has no usable connection, that step works from an export or stays manual.
What about confidentiality and inside information?
Access is set mandate by mandate, so a workflow only has rights on its own deal, and the written access list lets you check it. Before anything is built, a data processing agreement is signed and you receive the written list of every system that will read mandate records: where it is hosted, which model provider processes the text, whether that provider keeps it or may train on it, and the named people at AI Jungle who can open mandate records, bound by the same confidentiality terms as your deal team and added to your insider list when a listed company is involved. Your compliance officer checks it against your confidentiality and insider list obligations and against each engagement letter. Where a letter requires the client’s consent before a subprocessor reads its data room, we ask for it with you, or that step stays manual.
What should we start with?
If the pipeline dries up during execution, start with origination: it runs on the firm’s own records. Otherwise the weekly update, which repeats on every live mandate and which a deal lead can judge in minutes. Use the selector on this page, then bring one example to a 30-minute call.
Will it replace an analyst or an associate?
No. The aim is to run more mandates with the deal team you have and to give analysts and associates back the hours they spend rebuilding trackers and logs.
How much does it cost?
Prices are published on the AI Jungle pricing page and depend on the scope. A paid scoping study of your work and tools comes first (our Leverage Assessment), its fee is credited toward the build if you go ahead, and it can conclude that a smaller change is enough.
In 30 minutes, we choose where the test starts.
Usually your blank tracker template filled with a fictional mandate and a fictional data room activity log, so you see Thursday’s update in your own columns, or your own origination lists. No data from a real mandate is used, and a confidentiality agreement and a data processing agreement are signed before you send anything, even for the test.