Map Campus Procurement Authority Before Proposing Consolidation Across Sites

A large university medical center reaches out wanting one agreement to cover every lab across five campuses. It sounds like a win. One contract, one point of contact, less friction for everyone involved. But that university almost never runs purchasing through a single office. Each campus likely has its own approval threshold, its own preferred vendor list, and its own reasons for buying the way it already buys. As a strategic account manager, your job before that meeting is to find out who actually holds the authority to say yes. Do not accept the invitation to consolidate at face value.

Why this conversation goes wrong

The request for a single agreement usually comes from one enthusiastic contact, often a purchasing director or a lab director who wants less administrative work. That person speaks with confidence, and their confidence can fool you into thinking the deal is closer than it is. You quote terms across every site, and a satellite campus buyer who was never consulted objects two weeks later because their approval threshold is different, their fiscal year runs on a different cycle, or their department reports through a separate dean's office.

At that point the deal stalls, and worse, the contact who invited you into the conversation now looks like they overstepped their own authority. You created that problem by treating one person's enthusiasm as institutional agreement. Universities are not single companies with one finance department. They are federations of departments, campuses, and sometimes even separate legal entities that share a name and little else. Assuming otherwise is the single most common way this conversation goes sideways.

How to prepare before the meeting

Before you propose anything, build a picture of who buys what and who has to sign off. Ask your primary contact directly which laboratories and campuses are actually in scope for this conversation. Ask who approves purchases at each site, what dollar threshold triggers a higher level of review, and which agreements each location currently uses. Some campuses may already have contracts running that will not expire for another year, and folding those into a new agreement early creates conflict rather than savings.

Find out what the customer actually wants before you assume it is a single contract. Sometimes the real goal is shared visibility into spending across campuses. Sometimes it is a common review cycle so renewals line up. Full contract consolidation is one possible outcome, not the default one. Build a simple map with one entry per site, listing the purchasing owner, the approval threshold, the current contracting route, and any dependency that has not been resolved yet. That map is what turns a vague request into something you can actually act on.

If this account is newer to your book, treat the mapping exercise the way you would treat a new site's intake process, the same way you would want to know a lab's ordering patterns before assuming its purchasing habits. Our guide on how to Qualify a New Laboratory Account Application Before the Lab Opens covers a similar problem, confirming who actually controls a decision before you build a plan around someone who does not.

What to say in the meeting

Once you have a rough map, you can have the conversation without overpromising. The purchasing director might open with something direct. She says, "We would like one agreement that covers every campus starting this quarter. Can you put that together for us."

You do not want to say yes, and you do not want to say no either. Instead you say, "I want to get you a workable structure, and I am not going to offer full terms across every site until I understand how approval works at each one. Can we map the approval path for each campus first, then use a joint session to see where a shared approach actually fits."

She responds, "Our satellite campus in the north has its own threshold, and its buyer has not been part of any of these conversations." You say, "That is exactly the kind of thing I want to catch now instead of after we sign something. Can you get that buyer into a joint session with your central procurement team so we can map both the local requirements and the campus wide governance in the same room."

She agrees to set up that session and names the two people who need to attend. That is a real outcome. You did not hand over a proposal that would have fallen apart under review, and you did not walk away empty handed either. You have a concrete next step and the names of the people who can actually move it forward.

Mistakes to avoid

The most common mistake is quoting a single set of terms across every site because one enthusiastic contact asked for it. Do that once and you will spend the next month unwinding it with campuses that never agreed to anything. A close second is treating the mapping conversation as a formality you can skip because the contact seems senior. Seniority at one campus does not always carry authority over another, especially in university systems where departments guard their own budgets closely.

Another mistake is proposing consolidation before you understand what problem the customer is actually trying to solve. If they want shared visibility into spending, offering a single locked contract does not solve that and may create resistance from campuses that value their independence. Say plainly when a consolidated agreement is not realistic given what you know, rather than promising something you cannot deliver just to keep the meeting positive.

Finally, do not let the mapping process become an excuse to stall indefinitely. Some account managers turn caution into inaction, and the customer's initial interest cools while you keep asking questions instead of scheduling the joint session that actually moves things along. The point of the map is to get to a real next step quickly, not to delay a decision.

How to practice and score this conversation

This is a conversation worth rehearsing before you walk into it live, because the failure mode, quoting terms too early, is easy to fall into under pressure from an eager customer. Run through the exchange with an AI counterpart that plays the enthusiastic purchasing director and pushes you toward a fast yes. Notice whether you hold the line on needing an authority map, and notice whether you still land on a concrete next step instead of a vague promise to follow up later.

Score yourself on three things. First, did you avoid committing to terms before understanding who approves what at each site. Second, did you ask specific questions about approval thresholds, current agreements, and desired outcomes rather than general ones. Third, did you end the conversation with a named next step and named people, not just an agreement to talk again. A manager reviewing this practice session should look for that third point especially, since a plan without decision makers attached rarely turns into an actual deal.

If you want more scenarios built around biotechnology accounts specifically, the Biotechnology practice conversations hub has a full set to work through, including situations closer to adoption problems than procurement ones, like the one covered in Find Out Why New Users Avoid a Lab Workflow.

The close

A university asking for one agreement across campuses is not lying to you, but it is usually speaking from one seat at a much larger table. Map the authority before you propose the structure, and you turn a request that could collapse under its own weight into a review that people with real authority can actually approve. That is a slower path than saying yes on the spot, and it is the only one that holds up once the contract is actually signed.