Turn an Automation Idea Into a Pilot Decision

An automation pitch almost always starts with a number nobody has earned yet. A plant director wants a payback figure for the board. A board wants one slide. Your job as the account executive is to slow that request down without sounding like you are stalling, and turn a vague ask into a specific pilot that someone can actually approve. The conversation only works if you replace the question "what will this save us" with concrete questions about the cell, the parts, the people running it, and the safety review a pilot will require.

Why this conversation goes wrong

Most reps handle this badly in one of two directions. The first is caving to the pressure for a number. A director asks for payback on one slide, and the rep quotes a range pulled from a similar plant, hoping it reads as helpful. That number gets written into a board deck, gets treated as a commitment, and gets used against you the moment the pilot reveals a part family that needs custom tooling or a cycle time nobody measured. You lose credibility the day reality shows up.

The second failure is the opposite problem. The rep refuses to engage with the payback question at all and starts listing requirements, sounding like a consultant stalling for time. The director hears "I don't know" instead of "here is how we find out," and the meeting stalls. Neither approach gets you to a pilot. The fix is to answer the payback question honestly, by explaining that a real number requires specific inputs, and then naming exactly what those inputs are. You are not dodging the question. You are answering it correctly.

How to prepare before the meeting

Before you sit down with a plant director, find out what you can about the cell in question. Ask your internal team or the account history what part families typically run through similar cells, what cycle time ranges look normal, and what safety reviews plants in this industry usually require before adding automated equipment. You want enough background to ask sharp questions in the room, not to guess at answers.

Identify who actually holds the facts you need. The cell supervisor knows the part mix and the cycle records. The EHS manager knows what safety review applies and how long it takes. An automation engineer, yours or theirs, can describe what interfaces the cell would need. If none of those people are in the room for your first conversation, your first goal is getting them there, not producing a number without them.

Write down the four things a pilot decision actually depends on before the meeting starts. The parts running through the cell. The current work and how people do it today. The safety review the change would trigger. The decision itself, meaning who signs off and what evidence they need. If you walk in with those four categories already framed, you will recognize which one the director is skipping when he pushes for a shortcut.

What to say in the room

Say the plant director opens by telling you the board wants one slide with the payback number, and asks whether your system can run every part they make.

You answer that the number depends on the parts and how the cell runs today, and you ask which resin grades pass through that cell and what changed after the operator team revised the packing process.

The director says three grades have different handling needs and admits the new packing process is still settling in.

You respond that the cell supervisor should bring part mix and cycle records to the next conversation, the EHS manager should identify what safety review applies, and your automation engineer should describe what interfaces the cell would need. You add that once those three people bring those inputs, everyone in the room can decide together whether a limited pilot is worth designing.

That answer gives the director something better than a slide. It gives him a path he can defend to the board, one that names the exact people and facts needed to make the next decision, instead of a payback claim built on a cell nobody has actually studied yet.

Mistakes that sink the pilot decision

A few patterns kill this conversation even when the rep means well.

1. Quoting a payback range before anyone has looked at the part mix. A range still gets treated as a promise.
2. Treating every part on the line as equivalent, when different resin grades, tolerances, or packaging steps change what the cell can actually handle.
3. Skipping the safety review until late in the process, which forces a redesign after the plant has already committed time to the idea.
4. Leaving the room without naming who owns the next step. A pilot proposal with no named decision maker sits on a desk indefinitely.
5. Letting the conversation stay abstract. If nobody agrees on what evidence would make the director comfortable approving the next technical step, you have had a nice conversation and made no progress.

Watch for the moment a director tries to compress the conversation into a single number. That instinct comes from real pressure, usually a board meeting or a budget cycle, and you should acknowledge it directly rather than treating it as an unreasonable request. Say plainly that you understand why he wants one figure, and then explain why a defensible figure requires the inputs you are asking for.

How to practice and score it

This conversation rewards rehearsal more than most, because the pressure to hand over a premature number is strong and immediate. Have a manager or colleague play the director and push hard for a quick payback figure, including pushing back once or twice after you ask your first clarifying question. Your job is to hold the line without sounding evasive.

Score the practice run against a simple standard. Draw four columns labeled parts, current work, safety, and decision. Every question you ask in the roleplay should be collecting a fact for one of those four columns. If a question does not map to one of them, it is probably filler or, worse, a stall. End the practice by checking whether you landed on a clear pilot decision question, meaning you asked what evidence would let the director feel comfortable approving the next technical step, and whether you named specific people to supply that evidence.

DealSpeak is built for exactly this kind of rehearsal, since a scripted roleplay partner can push on the payback question the way a real director would, and score whether your questions actually filled in the four columns. For more scenarios built around this kind of technical qualifying conversation, look at the Manufacturing practice conversations at /industries/manufacturing. Two related situations are worth rehearsing alongside this one. If your pilot involves scanning or tracking parts, read Plan a Barcode Read Rate Study With Representative Production Samples at /industries/manufacturing/blog/manufacturing barcode read rate study for how to gather representative samples before making claims about read rates. If the automation idea touches a mixing or batching process, Assess a Batch Mixer Controls Update Without Disturbing Recipes at /industries/manufacturing/blog/manufacturing batch mixer controls assessment covers a similar discipline around not disturbing a process you have not fully mapped yet.

A payback number without a studied cell is a guess wearing a suit. Your value in this conversation is refusing to dress up a guess and instead building the short list of facts that turns a promising idea into a pilot someone can defend. Get the four columns filled, name the people who fill them, and the number will take care of itself once it has something real behind it.

You can rehearse this exact conversation in the Manufacturing practice conversations library before it happens for real. When you have this one down, read Plan a Barcode Read Rate Study With Representative Production Samples next.