Discover Seasonal Overtime Cost Before Framing an Operations Project

Seasonal overtime numbers get thrown around a lot on manufacturing calls, and they almost always mean less than they sound like they mean. A plant manager says the holiday run cost too much in extra labor, and the instinct is to jump straight to a piece of equipment that promises to make the number go away. That instinct skips the real question. Overtime can point to demand growth, a staffing gap, a changeover that eats too much time, or a bottleneck somewhere else entirely. An industrial account executive who frames a project around one dollar figure before knowing which of those it is will build a proposal nobody can defend in a budget meeting.

Why This Conversation Goes Wrong

Overtime is an emotional number for plant managers and controllers alike. It shows up on a report, someone gets asked about it, and the fastest answer is often the wrong one. A manager under pressure will describe the problem in terms of the fix they already have in mind, not the cause. That is not dishonesty. It is how people talk when they want a problem to be over.

The account executive's job is to slow that down without dismissing the pressure. If you accept the framing at face value, you end up scoping a project around a symptom. Maybe packaging worked sixty extra hours a week during the holiday run, and the plant buys automation to cut that labor. But if the real cause was a scheduling decision that packed three product changeovers into one week, the automation does not fix anything. The overtime comes back next season, and now there is a capital purchase sitting next to it that did not solve the problem it was bought for.

The other failure mode is treating overtime as one uniform category. Finance often splits planned seasonal labor from unplanned overtime differently than operations does. A department can carry extra hours every year during a known peak, and that is not the same problem as a shift that runs long because a changeover took twice as long as scheduled. Until you know which one you are looking at, you do not know what kind of project makes sense, if any.

How to Prepare Before the Call

Before you get on the phone, figure out what you do not know yet, not what you plan to sell. You want three things out of the conversation, the departments and time periods involved, the work that was still incomplete when the extra hours ended, and the person on the finance side who can explain how the company defines and tracks overtime versus planned labor.

Look at whatever account history you have first. If a plant has flagged overtime before, in prior calls or notes from other reps, check whether it was the same departments each time. A repeat pattern in packaging or sanitation points toward a structural issue with staffing or scheduling. A one time spike tied to a specific order points toward demand, not equipment. Either finding changes what you ask next, so do this before the call, not during it.

Also decide in advance who else needs to be in the room before a project gets scoped. Plant managers know the operational pain. They rarely have the full financial picture, and they are not always the ones who own the production schedule. Go into the call planning to name the controller and the scheduling manager as people the review needs, rather than waiting to see if the plant manager offers them.

What to Say

In a practice version of this call, plant manager Rosa opens with the number. She says the plant spent far too much on overtime during the holiday production run and wants a piece of equipment that fixes it going forward.

Account executive Devin does not argue with the number or agree to look at equipment yet. Devin asks which departments worked the extra hours and what work was still waiting when those shifts ended. Rosa says packaging and sanitation absorbed most of it, and that finished product sat waiting for sanitation to clear a line before the next run could start.

Devin follows with a second question instead of moving to solutions. Devin asks how finance separates planned seasonal labor from unplanned overtime, and who owns the production schedule that determines when changeovers happen. Rosa says the controller tracks that distinction and the scheduling manager sets the run order.

Devin closes the exchange by proposing a specific next step rather than a project. Devin says the group should review last season's shift records together with the controller and the scheduling manager, and use that review to identify what decisions an operations project would actually need to support.

Notice what Devin did not do. Devin did not dismiss Rosa's frustration or tell her the equipment idea was wrong. Devin also did not agree to scope anything yet. The questions stayed specific, departments, timing, ownership, and the ask at the end named real records and real people instead of asking for a vague follow up call.

Mistakes to Avoid

The most common mistake is accepting the first explanation and moving straight into solution mode. If a plant manager says overtime is the problem, and you start describing what your equipment does within the first two minutes, you have skipped the diagnosis entirely. You will find out you were wrong at the worst possible time, in front of a budget committee.

A second mistake is asking for a dollar figure and treating that as sufficient. A total overtime cost tells you almost nothing about cause. Two plants can spend the same amount on overtime for completely different reasons, one because of a genuine capacity shortfall and one because of a scheduling decision that could be fixed for free. Chasing the total number instead of the pattern behind it wastes everyone's time.

A third mistake is leaving the call without naming the people who own the financial and scheduling data. If you end the conversation with a vague plan to check in later, you leave the door open for the plant manager to go find a competitor who will just say yes to the equipment request. Naming the controller and the scheduling manager, and setting up the records review, keeps the process moving on your terms.

Do not treat this pattern as unique to overtime either. The same discipline applies whenever a plant leads with a cost or downtime number and a specific fix already attached. The approach used in Prepare a Servo Drive Obsolescence Service Plan With Current Asset Facts works the same way, get the current facts about the asset before agreeing to a service plan built around someone's assumption of what broke it.

How to Practice and Score This Conversation

This conversation is hard to get right on the first live call, because the pressure to agree with the customer's framing is real and immediate. Practice it with a colleague who plays the plant manager and pushes for an immediate return estimate or a quick yes on equipment. Your job in the practice run is to hold the line on questions, not conclusions.

Score yourself, or have your manager score you, on three things. Did you ask about the specific departments and time periods affected. Did you ask how the company defines overtime versus planned labor, and who owns that definition. Did you end the call with a concrete next step that names records and people, instead of a general promise to follow up.

DealSpeak is built for exactly this kind of rehearsal, letting you run the seasonal overtime scenario against an AI counterpart that pushes back the way a real plant manager would, and scoring how well you held the diagnosis open before moving toward a project. If you manage a team of account executives, running this scenario across the group surfaces who jumps to solutions too fast and who asks the right questions under pressure.

Closing Thought

Overtime numbers are a starting point, not a diagnosis. Ask about the departments, the work left waiting, and who owns the schedule and the numbers, and you turn a vague complaint into a real project scope that finance and operations will both back. For more scenarios built around this kind of discovery, look at Manufacturing practice conversations.