Running Five Mandates With the Team That Used to Run Three

Why three is the number most boutiques get stuck at

Ask a managing director at a ten-person bank how many mandates the firm can run at once and the answer is usually three or four, with a pause before the four. The pause is where the real answer lives.

At three mandates, each associate owns one process and can hold its full state in her head: where every buyer is, what the owner still owes, and which section of the CIM is in its second draft. At four, one associate owns two, and the state leaks. Buyer follow-ups slip a week. A data room request gets answered twice. The owner on the fourth deal notices that the weekly update arrived on Monday instead of Friday.

The partner feels this as a quality problem and responds by capping the firm at three. The cap is rational. What is not rational is treating it as a fact about the team rather than a fact about the workload. The associate is not out of judgment at four mandates. She is out of hours, and the hours are going to production.

Three things eat the hours. First drafts of teasers and CIMs take days each and arrive in waves. Buyer-list assembly means pulling names from several sources and cleaning the result before anyone decides who to call. The Friday reconciliation rebuilds the state of each deal from email, the data room log, and the tracker so the owner update is accurate. None of these three is judgment work. Each adds work as mandate count rises.

What has to change for the fourth and fifth mandate to fit

The jump from three to five does not come from one change. It comes from removing each of the three production loads in turn and watching the associate's week open up.

Start with the Friday reconciliation, because it is the most frequent and the most invisible. If every NDA, IOI, data room request, and buyer status lives in one pipeline rather than across inboxes and spreadsheets, the state of a deal is already assembled on Friday morning. The associate reads it instead of rebuilding it. Across five deals, that could return meaningful time to the team, but the amount depends on the bank's existing process.

Next, the first draft. A CIM drafted from the questionnaire and data room arrives as a document to edit rather than a blank page to fill. The associate's job becomes reading for accuracy and tone, cutting what does not belong, and adding the three or four insights only a banker who has talked to the owner can add. A first draft that used to take a week may become two days of editing in a particular workflow, but that is an operating example, not a measured result.

Last, the buyer list. If the first cut comes from documented acquisition criteria in the right sector and size, the associate starts with a working list rather than an empty spreadsheet. The partner adds relationship buyers, strikes names that do not fit, and reorders by priority. The list can exist early in the marketing phase instead of late, but the bank still decides who to contact and how.

With those three changes, an associate who could hold one process at full attention may hold two without the state leaking, because the state is no longer in her head. Three associates then carrying five or six mandates is a scenario to test, not a capacity result established by this article.

The operating rhythm that keeps five from becoming chaos

Capacity is not only hours. It is also rhythm. A bank that adds mandates without changing its weekly cadence will find that the hours it saved on production get spent on coordination.

Set one weekly pipeline meeting that covers every live mandate in under an hour. This only works if everyone is looking at the same screen rather than at five separate trackers. Each process gets a few minutes: phase, next milestone, blockers, and what the owner needs to hear on Friday.

Assign one named reviewer to every artifact before it leaves the firm. At three mandates, the partner reviewed everything. At five, the partner cannot, and the firm needs a rule that an associate reviews the analyst's work and a partner reviews what goes to buyers and the owner. Documentation and defined responsibilities support transparency and accountability in AI-assisted workflows, while process controls and regular review are standard quality-management practices. [1] [2] The named-reviewer rule is therefore a control the bank chooses to operate, not a guarantee that quality will stay constant.

Stagger phases where you can. Five mandates all in marketing materials at the same time will strain any team. Five mandates spread across discovery, valuation, marketing, offers, and negotiation are easier to carry, because the senior-heavy phases and the production-heavy phases do not collide. A partner who sees the whole pipeline can sequence engagements so the firm is not drafting three CIMs in the same fortnight.

What the partner gives up and what she gets back

Running five instead of three changes the partner's job too, and it is worth naming the trade.

The partner gives up touching every page. On three mandates she read every CIM draft and approved every buyer. On five she reads the final draft and approves the priority tier of the buyer list, trusting the associate's review for the rest. For a partner who built the firm on personal attention, that is uncomfortable, and it should be, because the named-reviewer rule makes the delegation explicit rather than making it invisible.

She also gives up some of the slack that let the firm absorb a difficult owner or a buyer who wanted a second management meeting on short notice. At five mandates the team is fuller, and the partner has to be deliberate about where surge capacity comes from.

What she gets back is a firm less dependent on three deals closing on schedule. A slipped closing on one of five mandates is a smaller concentration problem than the same slip on one of three, but the financial effect depends on fees, timing, and the firm's economics. She also gets the ability to evaluate a fourth mandate that walks in during a busy quarter, instead of rejecting it automatically.

A concrete week to try this

Pick the mandate with the heaviest Friday. Have the associate who runs it log, for one week, every hour spent reconciling state across tools versus every hour spent on judgment: calls with the owner, decisions about buyers, and edits that changed the story. The ratio will give the partner evidence about this bank's workload, not a universal benchmark.

Then ask what a Friday looks like when reconciliation time is near zero, and what the associate would do with that time if a fourth mandate arrived on Monday. Use the answer to set a staffing limit, a review rule, and a phase-staggering plan before accepting more work.

How Acquivo Pro fits

Acquivo Pro is built for this capacity problem. One login holds each client's process in a single pipeline, so NDA, IOI, and LOI flow across mandates can be viewed together rather than rebuilt from separate trackers. Teasers and CIMs generate from the client questionnaire and data room as drafts for the associate to edit, and buyer matching can use documented acquisition criteria while the bank controls outreach and prioritization. Pricing is per seat on a flat monthly subscription with no per-deal fees, and one seat runs multiple concurrent processes. Those facts make the platform relevant to a capacity experiment, not proof that a bank will reach five mandates. To see it on a live mandate, request a demo through the Contact page.