Capturing the Senior Banker's Buyer Knowledge as Data

The knowledge that walks out the door

Every boutique bank has a partner who, when the associate brings a buyer list, picks up a pen and does three things in ten minutes. Strikes four names with a comment like they never close or they lowballed us on the last one. Adds three names from memory, a family office that has been asking for exactly this, a strategic whose CEO the partner had dinner with. And circles two names with a note to call directly rather than send the teaser.

That ten minutes is the most valuable thing the partner does on the mandate before the LOI. It is also entirely unrecorded. The marked-up list goes back to the associate, the associate updates the spreadsheet, and the reasons evaporate. Next year, on a mandate in the same vertical, a different associate brings a list to a different partner, and the four buyers who never close are on it again.

When that partner retires or leaves, the firm loses the pen. The relationships stay with the partner. The judgment stays with the partner. What the firm keeps is a stack of old buyer spreadsheets with no reasons on them. That is the continuity problem knowledge-transfer programs are designed to address: capture experience and preserve it when a key position is vacated. [1]

Why the markup moment is the only one that works

Banks have tried to capture this knowledge before, usually by asking partners to fill in a CRM or sit for an interview about which buyers are good. Both fail, for the same reason. The knowledge is not organized in the partner's head by buyer. It is organized by situation. The partner does not know in the abstract that a given sponsor retrades. The partner remembers, when they see that sponsor's name on a list for a client with customer concentration, that the sponsor retraded on a similar client two years ago.

So the knowledge only surfaces when the partner is looking at a specific list for a specific client. That is the markup moment, and it happens on every mandate, so the firm does not have to create an occasion. It has to capture the one that already exists. A systematic review of organizational knowledge-transfer procedures likewise finds that organizations use communication and digital methods to retain both tacit and explicit knowledge. [2]

The capture is simple. The associate sits with the partner during the markup, or receives the marked-up list and follows up within the hour. For every strike, one line: why. For every addition, one line: who the relationship is with and why this client. For every direct-call note, one line: what the partner knows that makes a call better than a teaser. The associate logs all of it against the buyer, not against the mandate, so it is there the next time the buyer appears on any list.

What the log looks like after a year

After one mandate, the log has perhaps fifteen entries from one partner. Useful, but thin.

After a year of six or eight mandates across three or four partners, the log has several hundred entries and starts to show things no partner knew alone. The sponsor that one partner struck as slow is the one another partner added as a relationship. The strategic that two partners both circled for a direct call in different verticals is a buyer the firm should be talking to about its whole pipeline, not one deal. The family office that never appears in the database because it has not closed in two years but that three partners have added from memory is either about to buy or has changed strategy, and either way the firm should know which. These staffing and volume figures are illustrative scenarios, not measured results.

The log also becomes the first thing the associate checks when the database list comes back. Before the partner's markup, the associate applies last year's strikes and flags last year's additions, so the partner's ten minutes go to new judgment rather than repeating old judgment. The partner notices the list is better before they touch it, which is the moment they start trusting the log.

Keeping the log honest and useful

Three rules keep the log from decaying into a list of names with no meaning.

Every entry has a reason, a partner, and a date. An entry that says struck, no reason, is worse than no entry, because the next associate will not know whether to apply it. The partner's name matters because partners disagree, and the date matters because a sponsor that retraded in one year may have new leadership now.

Strikes expire. A buyer struck for a reason tied to a specific situation, they lowballed on a client with concentration, should be flagged for re-evaluation, not permanently excluded. The associate asks the partner at the next markup whether the strike still holds. Most do. Some do not, and a buyer that was wrong for one client is sometimes right for the next.

Additions get checked against outcome. When a partner adds a buyer from memory and that buyer signs an NDA, submits an IOI, or goes quiet, the associate notes it. Over a year, the firm learns which partners' additions convert, which is useful for the partners and more useful for the firm. If a prospective buyer is also a competitor, the bank should coordinate the information shared with counsel and use only what is needed for the diligence purpose. The FTC recommends narrowly tailoring pre-merger information sharing and using safeguards for competitively sensitive information. [3]

The partner whose knowledge is being logged will sometimes object, not in words, but by giving thinner reasons or skipping the markup. The underlying concern is that the log makes the partner replaceable.

The honest answer is that the log makes the partner's judgment more valuable, not less. A partner whose strikes are applied on every mandate in the firm is shaping deals they never touch. A partner whose additions are tracked against outcome has a record of being right. And a partner who retires with their knowledge in the log leaves something the firm can use, which is a different kind of legacy than a stack of old spreadsheets.

The sponsor should say this to the partner directly, once, before the first markup. After that, the log speaks for itself. On the next mandate that reaches the buyer-list phase, have the associate sit in the room for the partner's markup with a notebook open. Every strike, every addition, every circle: one line. Log it against the buyer that afternoon. That is the whole system, started.

How Acquivo Pro fits

Acquivo Pro builds the starting prospect list from buyer data with documented acquisition criteria, so the senior banker's markup begins from a structured starting point rather than a static directory. The list lives in the same pipeline as the client's NDA, IOI, and LOI flow, so the associate can see which of the partner's additions signed, offered, or went quiet without leaving the mandate. One login carries every client's list, which is where a firm-wide buyer log belongs. To see it on a live mandate, request a demo through the Contact page.