Frame a Plant Water Use Review With Process and Meter Facts

A facilities director calls you with a water bill that jumped and a directive from leadership to bring it down. That is the entire brief, and it is not enough to act on. Before you talk about any project, you need to know what changed, on which meter, over which months, and why. This post walks through how to run that first conversation as an industrial account executive, using process and meter facts instead of guesses.

Why This Conversation Goes Wrong

Water use in a plant moves for a lot of reasons that have nothing to do with waste. Production volume goes up, a new wash station comes online, a cooling tower runs longer in warm months, or a valve starts leaking somewhere nobody has checked yet. A rising bill on its own tells you almost nothing about the cause.

The trouble starts when an account executive treats a vague complaint as a request for a reduction number. Leadership wants a plan, the facilities director is under pressure to produce one, and the easiest path is to name a percentage and move toward a proposal. That number gets written down, repeated in a meeting, and eventually held against you when the plant cannot hit it. You end up defending a figure nobody derived from real data, and the relationship absorbs the damage.

The fix is not complicated, but it takes discipline. You separate the billing pattern from the process condition before you talk about solutions. That means finding out which meter changed, what else changed in the same window, and who holds the records that can confirm or rule out each explanation.

How to Prepare Before the Call

Walk into this conversation with a short list of things you need to learn, not a list of things you plan to say.

1. Ask for a meter map. Plants often have one main meter and several submeters on wash stations, cooling loops, or process lines. You need to know which meter actually moved before you can talk about a cause.
2. Request twelve months of utility invoices and meter readings if the plant has them. A jump that lines up with a season or a production run tells a different story than a jump that appears suddenly and stays high.
3. Find out what changed operationally in the same period. New equipment, an added shift, a revised cleaning schedule, or a change in product mix can all move a water bill without any leak or waste involved.
4. Identify who owns each piece of information. Sanitation staff usually know the wash schedule. An energy analyst or facilities engineer usually holds the invoices and meter logs. You want both in the room or on the call, not just the director who raised the concern.

This preparation does the same job as the groundwork described in Prepare a PLC Network Segmentation Workshop With the Right Ownerswhere the right people in the room matter as much as the right questions. A water review is no different. You are not the expert on the plant's process. The people who run it are, and your job is to get their facts organized around a clear question.

What to Say in the Room

Picture a call with Karen, the facilities director. She opens with the same brief most account executives hear. "Our water costs jumped and leadership wants a reduction plan."

You do not answer with a number or a project idea. You answer with a question. "Which meters show the increase, and did production volume or cleaning schedules change during those same months."

Karen thinks about it and says the main meter rose after a new wash station started running. That is a real lead, but it is not proof of waste. It could simply reflect added process volume that leadership already expected when they approved the wash station.

You keep going. "Who can walk us through the wash schedule, and who keeps the invoices and meter readings so we can look at the numbers together."

Karen names her sanitation manager and her energy analyst. You close the call with a plan instead of a promise. "Let's set up a working session with both of them, pull three months of records, and figure out what process questions an assessment needs to answer before anyone talks about a target."

That last line matters. You have not refused to help, and you have not stalled. You have given Karen a concrete next step that produces real answers instead of a guess dressed up as a plan.

Mistakes to Avoid

The biggest mistake is naming a savings percentage before you have seen a single meter reading. It feels helpful in the moment and it costs you credibility the moment the real numbers come back different.

A second mistake is assuming a meter increase means a leak. Leaks happen, but so do added equipment, longer shifts, and seasonal cooling loads. Ruling those out is part of the job, not a formality you skip because a leak makes a better story.

A third mistake is talking only to the person who raised the concern. The facilities director may not track wash cycles or read meter logs personally. Skipping the sanitation manager or the energy analyst means you build a plan on secondhand information, and secondhand information is where bad assumptions hide.

A fourth mistake is treating this like a one call problem. A working session with records on the table takes more time than a phone call, but it is the only way to tell a billing pattern from a process condition. Rushing past it to get to a proposal just moves the guesswork later, where it costs more to fix.

How to Practice and Score This

This kind of call rewards a specific skill, asking good questions under pressure to produce a number right away. That skill is hard to build by reading about it. You build it by running the conversation enough times that the discipline becomes automatic, even when the person across from you is pushing for a quick answer.

DealSpeak lets you rehearse exactly this scenario against an AI counterpart that plays a facilities director under pressure from leadership. You can practice holding off on a figure, naming the meters and records you need, and closing with a plan instead of a promise. The scoring shows you where you gave in too early or missed a data owner you should have named.

If you work manufacturing accounts regularly, browse Manufacturing practice conversations for more scenarios built around the same kind of discovery work, including situations like checking parts availability before committing to a repair window, covered in Check Pneumatic Fitting Availability Before Moving a Repair Window. The pattern repeats across manufacturing conversations. Get the facts and the right people lined up before you commit to a number.

A rising water bill is a starting point, not a conclusion. Your job in that first call is to turn a vague worry into a specific set of questions the plant's own records can answer. Get the meters, the months, and the data owners right, and the reduction plan that follows will actually hold up.