Assess Automation Workcell Readiness Before Discussing a Connection

A field application scientist walks into a lab, sees an open bench beside a liquid handling robot, and the customer says the new instrument can just plug in. That moment feels like progress. It usually is not. Before you talk about connecting an automation workcell to anything, you need real facts about the lab, not a hopeful glance at floor space. This piece walks through why that pressure builds, what to learn before you say the word connection out loud, and how to run the conversation so the customer trusts your process instead of your optimism.

Why This Conversation Goes Wrong

The customer wants speed. You want the sale to move. Both of you look at a robot and an instrument sitting a few feet apart and treat that as evidence the connection will work. Proximity is not readiness. A workcell has real owners, real network segments, real safety reviews, and real material flows that a walk through the lab will never reveal on its own. When you agree that a connection sounds straightforward, you set an expectation you cannot back up, and the customer holds you to it later when engineering finds a problem you should have flagged first.

The failure mode is subtle. Nobody lies in this conversation. The customer genuinely believes the layout supports the plan, and you genuinely want to help. But agreement without facts creates a promise neither of you can keep. When the safety review or the network team pushes back weeks later, the customer remembers that you said yes, not that you meant maybe.

What Readiness Actually Requires

A workcell connection is not one conversation, it is several, spread across different people who each control one piece of the puzzle. Before you describe anything as available, learn how material enters and exits the workcell, who owns the automation equipment itself, and which team controls changes to the network or the facility. You also need any acceptance question the customer's own process requires answered before a new connection goes live. Some labs run these questions through a formal change control process, others through an informal conversation with a facilities lead. Either way, you need to know which one you are dealing with before you promise anything.

Ask for a simple layout or process description if the customer can share one through an approved channel. You are not trying to design the integration. You are trying to build a map that tells you and the customer which technical questions still need an answer from a specialist, and which people need to be in the room when those questions get asked.

How to Prepare Before the Call

Build a blank readiness map before you get on a call or walk the floor. Leave space for four things. First, the physical location of the workcell and the space around it. Second, how material moves in and out, including any manual steps. Third, who owns each piece of equipment and each system, the robot, the network, the facility controls. Fourth, the open questions that have to go to a specialist before anyone commits to a timeline.

Bring this map into every automation conversation, filled in as far as you can from what the customer already told you, with the rest left open. Treat the blanks as your agenda. A customer who sees you asking specific, grounded questions trusts you more than one who hears a quick yes followed by a slower, more painful no from engineering weeks later.

What to Say

Here is how that exchange actually sounds in a real conversation.

Carlos, the customer, says, "We can just set the instrument next to our robot, so hooking them together should be simple."

You say, "That layout gives us a good starting point. Can we walk through how material moves between the two systems, who owns the robot and the network on your side, and what your team needs signed off before a new connection goes live."

Carlos thinks about it and says, "Engineering owns the robot, actually, and I think a safety review has to happen before anything new touches that network."

You say, "Then let's get engineering into a short readiness session with us, so we can map this out with the people who actually control those pieces, instead of guessing based on how close the two systems sit."

Notice what happened. You did not argue with Carlos, and you did not shut the idea down. You redirected the certainty in his statement toward the facts that actually determine feasibility, and you named the people who need to be part of that decision.

Mistakes to Avoid

A few habits sink this conversation more than any other. Do not treat physical proximity as a stand in for technical compatibility, the two have nothing to do with each other. Do not answer technical feasibility questions yourself when you are not the engineer who owns that system, hand those off to the right specialist every time. Do not let a customer's confidence substitute for your own documentation, if the customer sounds sure but cannot point to an approved layout or process description, that confidence is not evidence. Do not skip naming the acceptance question or the safety review just because the customer did not bring it up first, ask directly, because customers often do not know which reviews their own organization requires until you ask.

Also resist the urge to fill silence with reassurance. A pause while the customer thinks through who owns what is a good sign, not a problem to smooth over.

How to Practice and Score This Conversation

Run this scenario before you rely on it in front of a real customer. Use the blank readiness map as your script and have a manager or peer play a customer who assumes proximity means readiness. Score the call on whether you asked about material handoffs, named the actual owners of the equipment and network, and proposed a readiness session instead of accepting the premise that the connection is already possible. A manager listening in should watch for questions that pull real facts out of the customer, not questions that lead the customer toward the answer you want.

DealSpeak gives you a place to run this exact scenario against an AI counterpart and get scored on those behaviors before you try it live. You can find more Biotechnology practice conversations covering related situations, including how to Discuss a Backorder Against a Research Timeline With Accurate Ownership and how to Handle a Budget Freeze During a Quote Follow Up.

A finished readiness map is worth more than a fast yes. It gives the specialists who review the connection a clear starting point, and it gives the customer a reason to trust the next thing you tell them.