Navigate Institutional Vendor Intake Before Scheduling Technical Work
Keep a research platform evaluation moving when the institution requires an initial vendor intake.
A research account executive can plan a technical evaluation perfectly and still watch it stall the moment procurement, security, or a research compliance office steps in with its own intake process. That is not a sign the deal is falling apart. It is a normal part of selling into an academic or institutional biotech lab, and the executive who treats it as a separate coordination track, rather than an obstacle to argue around, keeps the relationship and the timeline intact.
Why This Conversation Goes Wrong
Most sales training prepares an account executive to handle objections about price, timeline, or technical fit. Institutional intake is different. It is not an objection. It is a process the institution runs regardless of how strong the technical case is, and it often has nothing to do with the research lead's enthusiasm for the platform. The executive who does not know this can misread a delay as hesitation and push harder on the science, which annoys the lab and does nothing to move the paperwork.
The bigger problem is that intake usually sits outside the research lead's authority. A principal investigator can be fully committed to running a workshop or a technical evaluation and still have zero control over when purchasing clears a new vendor. When the executive does not separate those two tracks, the research lead becomes an unwilling go between, relaying questions from procurement or legal that the lead cannot answer and did not ask for. That is how a promising technical relationship turns into friction over something the scientist never wanted to own in the first place.
How to Prepare Before You Raise It
Before the call where intake comes up, or as soon as it does, find out three things. First, which office actually manages vendor intake at this institution, since it might be central purchasing, a research security group, or a departmental administrator, and the answer changes who you talk to next. Second, whether the process runs through a form, a portal, or a person, because that determines what you can hand over and how fast. Third, what stage of intake has to close before technical sessions can proceed, since some institutions allow parallel work while others require a name in the vendor system first.
Ask the research lead directly who the intake contact is, so questions from procurement or legal have somewhere to go besides the lab. Get that name and title in writing if you can, even if it is just a line in a follow up email. This single step prevents the most common failure mode, which is the lab passing along vague requests from an office the executive has never spoken with.
Have your standard vendor documentation ready before the request comes, including your company overview, insurance certificates, security questionnaires, and any references your operations team keeps on file. You are not trying to guess what a specific institution wants. You are trying to respond within a day instead of a week when someone finally tells you.
What to Say When Intake Interrupts the Plan
In a realistic version of this call, the research lead, Dr. Patel, opens with the problem directly. "My lab is ready to schedule the workshop, but our purchasing office told me your company has to be entered in their vendor system first."
The executive does not argue the point or try to route around it. "That makes sense, and I want to keep both pieces moving instead of waiting on one before starting the other. Can you tell me who in purchasing owns that request, so I can send our standard vendor documentation directly instead of asking your team to relay it?"
Dr. Patel connects the executive with an analyst named Jordan, who explains the registration review typically takes two weeks and confirms that the lab is free to continue planning the technical agenda in parallel. The executive replies, "That works well. I will send our company documentation to you today, and I will check back in ten days if I have not heard anything. In the meantime, Dr. Patel and I can keep working through the session agenda so we are ready to schedule the moment registration clears."
Notice what the executive does not say. There is no promise that registration will be approved, no guess at how long it will actually take beyond what Jordan stated, and no attempt to get Dr. Patel to pressure purchasing. The executive documents both tracks, names an owner for each, and sets a specific date to check back, which keeps the deal moving without speaking for an office that does not report to sales.
Mistakes to Avoid
A few habits turn a manageable intake step into a real delay.
- Treating the research lead as the intake contact and sending vendor forms or security questionnaires to a scientist who has no way to complete them.
- Promising a timeline for approval that procurement never gave you, which sets an expectation you cannot control and damages trust when it slips.
- Letting the technical evaluation stop entirely while intake runs, when in most cases the two can proceed side by side once you confirm that with the institution.
- Failing to get a named contact in the intake office, which leaves you unable to follow up without going back through the lab every time.
- Skipping the check in date, so the request sits with no one accountable for the next step.
Each of these mistakes comes from collapsing two separate processes, the science relationship and the institutional review, into one conversation. Keeping them apart is most of the work.
How to Practice and Score This Conversation
This conversation rewards preparation more than charisma, which makes it a good one to rehearse before it happens for real. Run it with a colleague playing the research lead, and then again with someone playing a procurement analyst who is less familiar with the technical side and more focused on process and documentation. After each run, check whether you walked away with the name of the intake process, the specific requester, the exact materials needed, and a real date for your next check in. If any of those four are missing, the conversation was not actually finished, even if it felt productive.
Score the notes you took during the roleplay for one thing in particular, whether you made any statement that sounds like a promise about approval or timing that was not directly confirmed by the institution. That single habit causes more damage than any other mistake in this scenario, because it puts you on record for something outside your control.
DealSpeak's Biotechnology practice conversations include this exact scenario along with others specific to research account executives, so you can rehearse the intake handoff before you are doing it live with a purchasing office you have never worked with. If you want to build out related skills, look at how to Plan an Instrument Retirement Conversation Around Active Study Impact and how to Set Integration Acceptance Criteria With Both Technical and Lab Ownersboth of which involve the same core skill of keeping institutional and scientific decisions on separate, clearly owned tracks.
Institutional intake will keep showing up at exactly the moment a deal feels ready to move, and no amount of scientific enthusiasm from the lab changes who controls that process. Handle it as a coordination task with a named owner and a real date, and the evaluation keeps moving instead of stalling on a misunderstanding about whose job it was to push it forward.
Practice these next
Connect an operational demonstration request to the customer’s actual decision process.
Help a research account executive turn a broad committee request into a bounded platform evaluation.
Guide a concern about computing capacity toward a technical discovery session that assesses whether the platform fits the laboratory’s computing environment.
Keep an exploratory consortium conversation separate from pricing or commitments while member institutions retain their own approvals.
Help a core facility define its real intake workflow and decision criteria before discussing a research platform evaluation.
Use customer dates and owners to plan a research evaluation without guessing at approval timing.