Refresh an Account Contact Map After a Faculty Merger

A faculty merger rewrites the map you have been using for months, sometimes overnight. Two labs become one program, a chair changes, and the person who used to sign off on purchases may no longer hold that authority. As a strategic account manager, your job is not to referee who reports to whom inside the institution. Your job is to get a clear, current picture of decision makers, users, procurement contacts, and technical contacts, and to get that picture from the account itself, not from guesswork or old email threads.

Why This Conversation Goes Wrong

Most account managers handle a merger badly in one of two ways. Either they keep working the old contacts out of habit, which annoys the new leadership and slows down every request, or they overcorrect and start asking so many organizational questions that the sponsor feels interrogated about internal politics that are none of your business.

There is also a trust problem. When a senior leader says something like work through me for everything, that statement often reflects what is comfortable for them in a chaotic moment, not what will actually happen once the dust settles. If you take it at face value and stop building other relationships, you end up with a single point of contact who cannot answer procurement questions or technical ones, and every request routes through someone who has no time for it.

Rumors make this worse. Staff hear that a merger is happening long before anything is confirmed, and secondhand information about who is taking over which function moves fast in a department that people care about. If you build a contact map on rumor, you will assign responsibilities to people who never accepted them, and you will look careless when the account corrects you in a meeting.

How to Prepare Before You Ask

Before you raise the topic with anyone at the account, pull your existing contact map and mark every open item tied to it. That means active contracts, pending renewals, open support cases, and any pricing or scope conversation still in motion. You need this list because the first useful question you can ask is which of these still belongs to the people currently listed.

Check for any public statement from the institution about the merger. Universities and research institutes often post faculty announcements or press releases when departments combine, and that gives you confirmed facts to work from instead of hallway talk. Note the date of the announcement, since effective dates for staffing changes often lag the announcement itself by months.

Write down the specific roles you need to confirm rather than trying to remap the entire organization in one conversation. You need a decision maker for budget, a day to day user or lab contact, a procurement contact, and a technical contact for each shared platform or service you support. Four roles, confirmed and dated, beat a long list of guesses.

Decide who you are asking. The sponsoring leader, often a department chair or a principal investigator, is the right first call, but do not assume they know every detail. Plan to follow up with the people they name, since interim assignments are common and those people may not stay in the role once the merger settles.

What to Say When the Sponsor Wants to Own Everything

In a review meeting, Dr. Patel, the department chair, opens with a common line. He says, "The two labs are merging, so for now just route everything through me." That instinct is understandable. He is trying to reduce confusion during a messy transition, and he does not want three vendors asking three different staff members the same questions.

The account manager does not push back on his intent, but does not accept the offer as a complete answer either. She says, "That helps, and I will keep you as the main point of contact for now. To keep support requests and orders moving without waiting on you for every detail, could we name a lab operations contact, a procurement contact, and a scientific sponsor for each shared platform? I only need names and whether these are interim or permanent."

Patel thinks it over and gives a real answer instead of a vague one. He says, "Fine. Maria Chen is running lab operations on an interim basis until we finish the reorganization. Procurement stays split between the two original departments until the new fiscal year starts in July." The account manager writes this down with the date attached and responds, "That is exactly what I needed. I will note July as a checkpoint and reach out again once the new procurement structure is in place, rather than assuming it has already changed."

That exchange works because the account manager accepted the sponsor's authority without treating his offer as a substitute for real information. She asked for names, she asked whether each one was permanent, and she set a date to revisit the map instead of treating today's answer as final.

Mistakes to Avoid

Do not assign budget authority or purchasing power to someone based on their title alone. A new department head does not automatically inherit procurement sign off, and guessing wrong here can stall an order for weeks while the account sorts out who actually has to approve it.

Do not treat an interim contact as a permanent one. Write the word interim next to any name given to you as temporary, and set a specific date to check whether that person is still in the role. A contact map without dates goes stale the same way the old one did.

Do not let a single sponsor become your only source of information. Even a cooperative chair will miss details about procurement or technical support that fall outside their daily work. Confirm names with the people who actually hold those functions once you have them.

Do not ask every question in one sitting. A sponsor managing a merger has limited patience for a vendor's internal paperwork. Ask for the roles you actually need, note what you cannot get yet, and follow up later rather than pressing for a complete answer on the spot.

How to Practice and Score This Conversation

This conversation is easy to get wrong in the room because the pressure to sound agreeable is strong, and pushing for specifics can feel like you are questioning the sponsor's judgment. Rehearsing it before the actual meeting helps you find language that gets you names and dates without sounding like you doubt the person in front of you.

DealSpeak lets you run this exact scenario against an AI counterpart playing a sponsor who wants to simplify contact by routing everything through themselves. You practice asking for specific roles, you practice separating confirmed facts from things still in flux, and you get scored on whether you extracted real information or just accepted a vague promise. A manager coaching a newer account handler can use the same scenario to check whether the rep pushes for names and dates or settles for the first answer given.

The scoring in a tool like this looks for concrete asks, correct handling of interim versus permanent roles, and a clear plan to revisit the map on a set date. Those are the same things a manager listening to a live call would check for.

You can find this scenario and others built around research institution account changes among the Biotechnology practice conversations. Two related scenarios are also worth rehearsing before you build them into habit. One covers how to Discuss a Grant Timeline Without Promising an Evaluation Outcomeand another walks through how to Separate Image Export Settings From Research Image Interpretationboth common moments where a vendor can overstep what they actually know.

A faculty merger will not stay settled for long, so build your contact map with dates, not certainty. Revisit it at every account meeting until the institution's new structure stops changing, and let the customer correct you rather than assuming you already have it right.