Map Sample Intake Before Proposing a Platform Evaluation

A core facility director opens the call by asking you to prove that your platform will clear a sample backlog nobody has mapped yet. Say yes to that framing and you end up proposing an evaluation for a problem that has never been described in detail. The better move is to slow the conversation down, learn how samples actually travel through the lab, and let the facility's own observations set the agenda for whatever gets tested later.

Why This Conversation Goes Wrong

A director under pressure wants relief, not a process. They see a queue building up, they hear that a platform exists, and they ask you to confirm it will fix things before anyone has traced where the delay actually starts. If you answer with confidence at that point, you are guessing, and the guess usually points at the wrong stage of the workflow. Samples move through receipt, labeling checks, assignment, and processing, and each of those steps can involve a different person or a different team. A weekend receiving team might report to someone the director never mentions. An incomplete submission might sit for a day before anyone notices it is incomplete. None of that shows up if you accept the director's framing and jump straight to a platform pitch. You end up promising an outcome for a cause you have not identified, and when the fix does not land, the credibility damage falls on you, not on the workflow.

How To Prepare Before You Ask For A Meeting

Ask the core director to walk you through a recent busy day, from the moment a sample arrives to the moment it gets assigned for processing. Get specific about weekend coverage, since many facilities run a thinner team on Saturday and Sunday and that gap often explains part of the backlog on its own. Ask about incomplete submissions, how labeling gets checked, and who has the authority to say a sample can move to the next stage. Each of those points is a potential handoff, and handoffs are where delay and rework tend to hide.

Once you have the outline of a busy day, ask the director what measure would actually make an evaluation worth their time. Some directors care about elapsed time from receipt to assignment. Others care about rework, meaning how often a sample gets sent back because something was missing or mislabeled. Others care about visibility, meaning whether staff can see where a sample sits without walking over and asking. Write down what the director tells you as fact, and write down anything you infer or guess in a separate column. That separation matters later, because assumptions dressed up as facts are what make an evaluation plan fall apart under scrutiny. If you want a fuller framework for turning this kind of discovery into measures a facility will actually stand behind, the post on Define Core Facility Success Measures Before Setting Adoption Milestones at /industries/biotechnology/blog/biotechnology core facility success measures walks through that step in detail.

What To Say When The Director Pushes For A Platform Pitch

The director opens with, "Prove your platform can eliminate our backlog and I will bring my team in for a demo."

You answer, "I do not have enough information yet to make that claim honestly. Before we talk about any platform, can we map one weekday sample path and one weekend sample path together, with your intake lead and your operations manager in the room. Once we can see where samples actually stall, we will know what an evaluation needs to measure."

The director mentions that weekend receiving is handled by an entirely separate team that reports through a different manager, someone who has not been part of any conversation about this backlog so far. That one detail changes who needs to be in the room and probably changes your timeline too.

You respond, "Good, let's bring that manager in as well. One more question before we schedule anything. Do you already track how long a sample sits before it gets checked in, or would we be building that measurement for the first time."

The director admits nobody has tracked that number before. That answer alone tells you the evaluation cannot start with product demonstrations. It has to start with a small measurement exercise the facility runs on its own samples, using people who already work there.

Mistakes That Undercut A Good Discovery Call

The most common mistake is answering the director's opening question directly instead of naming what you do not yet know. A close second is scheduling the big evaluation meeting before you know who owns each part of the intake process, which means you end up rescheduling once the weekend team turns out to matter. Treating the director's frustration as if it were a finished specification is another one, since frustration tells you something is wrong but not where or why. Skipping the people who actually touch samples during off hours is a mistake that shows up later as a schedule slip nobody warned you about. Mixing what the director told you with what you assumed is a subtler mistake, but it is the one that causes the most damage, because a plan built on an unmarked assumption looks solid right up until someone in the room corrects it in front of everyone else.

This same instinct, treating an unverified guess as settled fact, causes trouble in other parts of a biotechnology sales conversation too. A rep who assumes which budget an order should be billed against, without asking, runs into a similar problem, and the post on Clarify a Cost Center Question Before an Order Is Submitted at /industries/biotechnology/blog/biotechnology cost center order clarification covers that case directly.

How To Practice And Score This Conversation

Reconstruct one sample's path on a whiteboard or a shared document before you ever get on the call. Mark every owner, every decision point, and every fact you still do not have. Then look at the meeting you are proposing and check whether it has a stated purpose and whether the people who can actually supply the missing facts are the ones you invited. If the weekend manager is missing from your invite list, you already know the meeting is incomplete.

A manager coaching you through this should listen for premature performance language, meaning any sentence where you promise an outcome before the workflow has been mapped. The correction is not to soften the promise. It is to replace the promise with a precise discovery question, the kind that gets you a fact you did not have thirty seconds earlier. You can rehearse this exact exchange, including the moment the director pushes back and the moment a new team gets mentioned, through DealSpeak's biotechnology scenarios, and a manager can score how quickly you catch the weekend team detail and adjust your invite list in response.

Mapping intake before proposing anything keeps the conversation grounded in what the facility actually experiences, not in what a platform can theoretically do. For more scenarios built around this kind of research sales conversation, the biotechnology hub at /industries/biotechnology has additional practice material worth working through.

You can rehearse this exact conversation in the Biotechnology practice conversations library before it happens for real. When you have this one down, read Define Core Facility Success Measures Before Setting Adoption Milestones next.