Respond to an Energy Savings Question With a Usable Baseline Plan

A plant manager watching a rebate deadline close in wants one number, the annual savings from the energy project. You do not have that number yet, not honestly, because the plant has not finished measuring its own energy use. This is the moment the deal either gets stronger or gets built on a guess. Handle it well and you turn a pressured question into a shared plan for finding the real number together.

Why This Conversation Goes Wrong

The rebate deadline creates a false sense of urgency around the wrong task. The manager is not actually short on time to hit the deadline. The plant is short on the operating data that would make any savings number defensible. When you feel that pressure and answer with a number anyway, you have handed the plant an estimate nobody can stand behind, built on partial data and hope. If the number is wrong once the full baseline comes in, you own that gap, not the manager.

The opposite mistake is just as damaging. Some reps get nervous about giving a soft answer and refuse to engage at all, saying something like we cannot discuss savings until the audit is complete. That sounds careful, but it leaves the manager with nothing to act on and no reason to keep talking to you instead of a competitor who will just make up a number. The manager is not wrong to ask. They are trying to hit a deadline with the information they have. Your job is to give them a real next step instead of a real number you do not have yet.

How to Prepare Before You Get Asked

Know the shape of a defensible baseline before you walk into the room. That means interval meter data from the production areas that matter most, utility invoices covering a full year so seasonal swings show up, equipment nameplates for anything that changed since the last audit, and a clear picture of whether major systems, like compressed air, have expanded or been reconfigured since that audit ran. If the compressor room added capacity last year and nobody updated the baseline, any number you quote now is already stale.

Also know who inside the plant can actually approve the assumptions behind a savings estimate. That is rarely the plant manager alone. Facilities engineering usually owns the meter data and equipment specs, and finance usually has to sign off on how the calculation gets framed for a rebate application. Find out before the call whether those people are available this week, because the fastest way to stall a deal is to promise a review and then discover the right person is out until next month.

If the account is also mid expansion, treat the savings conversation as one piece of a bigger sequencing problem. Stage an Expansion Materials Review Before Quoting the Full List at /industries/manufacturing/blog/manufacturing expansion materials sourcing phases works through the same logic, get the review staged before you commit to numbers the plant cannot yet verify.

What to Say When the Question Lands

Plant manager Colin opens with the pressure point directly. He says, the rebate window closes soon, so what is our annual savings number. Account executive Aisha does not flinch and does not stall. She says, I can help you build a number the rebate reviewer will accept, and the fastest way there is figuring out what data we already have. Which production areas have interval meter data right now, and did the compressed air system change at all since your last audit.

Colin tells her only one area has interval data, and yes, the compressor system expanded after that audit ran. Aisha treats that as useful information, not a setback. She says, that tells me exactly where the gaps are, so here is what closes them. Can your facilities engineer pull utility invoices, meter exports, and nameplates for the equipment that changed. If finance can join a short scope review this week, we will walk through the assumptions together and decide what is solid enough to go into the rebate application now versus what needs another week of data.

Colin asks if that means missing the deadline. Aisha says, it means we file with numbers that hold up instead of numbers that get challenged later, and most rebate programs would rather see a documented partial baseline with a clear plan than a full number nobody can defend if they ask questions. That answer respects the deadline without pretending it overrides the math.

Notice what Aisha never does. She never invents a percentage to keep the mood positive. She never tells Colin his request is unreasonable. She gives him an action for this week, names who needs to be in the room, and turns the deadline into a scheduling constraint instead of a reason to guess.

Mistakes That Undercut the Estimate

The most common mistake is quoting a range too early just to have something to say. A rep who throws out fifteen to twenty percent before the meter data exists is setting an anchor that will not move even after the real number comes in lower. The plant remembers the first number, not the caveats you attached to it.

A second mistake is treating the facilities engineer as an afterthought. If you build the estimate with the plant manager alone and loop in engineering after the fact, you will find out too late that the compressor upgrade changed the whole baseline, and you will have to walk back a number you already put in front of the manager.

A third mistake is letting the deadline dictate the scope of the review instead of the other way around. A rebate date tells you when paperwork is due. It does not tell you which systems have changed, which meters are missing, or which assumptions are still shaky. Reps who let the calendar drive the technical review end up filing confident numbers built on old data.

A fourth mistake, more subtle, is failing to name a decision owner. If nobody in the room has authority to approve the final assumptions, the review meeting produces discussion but no output. Always ask, before you schedule anything, who signs off on this number once we have it.

How to Practice and Score This Conversation

This exchange rewards a rep who can absorb pressure and immediately redirect it toward evidence, and that skill is hard to build by reading about it once. Run it as a scenario where the AI counterpart opens with the deadline question and, on a second pass, opens by asking directly whether the deadline can even be met. Score the response on three things. Does the rep ask for specific baseline evidence instead of a general audit. Does the rep name who approves the final assumptions. Does the rep tie the next step to an actual date instead of a vague soon.

A strong practice session ends with the rep producing a short written list of what the plant needs to supply, something like interval meter data for the flagged production area, twelve months of utility invoices, nameplates for any equipment changed since the last audit, and a scheduled scope review with finance included. If the rep cannot produce that list cleanly at the end of the roleplay, they have not internalized the approach yet, no matter how smooth the conversation sounded.

Manufacturing practice conversations at /industries/manufacturing cover this scenario and others where technical uncertainty meets a customer deadline, and DealSpeak scores each attempt against the same criteria, so a manager can see whether a rep's language is actually improving over repeated runs. If the account is also evaluating new equipment alongside the savings question, Define an Extrusion Feeder Test Before Selecting Equipment at /industries/manufacturing/blog/manufacturing extrusion feeder test plan shows the same discipline applied to a hardware decision instead of a savings estimate.

A rebate deadline is real pressure, but it is not a substitute for a baseline. The rep who says so plainly, then hands the plant a concrete list of what to gather this week, keeps the deal moving without putting a number on the table that will not survive scrutiny. That is the difference between a savings estimate the plant can act on and one it will later regret trusting.