Energy / Utilities · Pricing Negotiation Call
The Energy / Utilities Pricing Negotiation Script: Holding Your Number After the Technical Win
You've won this one on the engineering. The Chief Engineer ran your ranked list blind against his own view of the worst feeders, it matched on the top twelve and flagged sixty-odd pole-mounted units nobody was watching, and the Manager Network Performance & Reliability has already told her GM this is the direction. Nobody on the call wants a different vendor. They want your vendor, cheaper.
What makes this negotiation different from every other industry is the shape of the levers they'll pull. It won't be "can you do better on price." It'll be "we're mid-determination, the allowance is locked, there is genuinely no capex line until the 2027 reset." It'll be "the OEM will bundle monitoring into the next transformer supply contract, effectively free." It'll be "our panel process needs three comparable quotes and you're the highest." It'll be "we can't raise the PO until the OT security review closes, so let's just look at this next financial year." Every one of those is a real constraint and a negotiating position at the same time, and the skill is telling which is which without calling anyone a liar.
The trap is how pleasant it is. Asset managers negotiate the way they run a works program — calmly, over long timeframes, with the patience of people who plan in five-year blocks. They'll be warm, they'll be reasonable, they'll go quiet after they name a figure, and unless you've written your floor down before you dial you will concede thirty points across forty minutes and get nothing but goodwill for it. Below is the script: the frame, the five tactics they'll run, the trade list that works specifically on a distribution business, and a full dialogue you can rehearse out loud in DrillCall before the real one.
The pricing negotiation call script
Say it in your own words. The structure is the part that matters.
- 1
Before you dial: three numbers and a utility-specific trade list
Write these down. If your floor isn't on paper before the call, the floor becomes wherever the Head of Asset Management stops pushing. **Ask:** $340K/year on the quote — fleet-wide transformer risk model across 42,000 distribution units, vegetation risk module across 11,000 line km, ADMS/OMS integration, plus $45K implementation. **Target:** ~$320K on a 36-month term with a capped uplift. **Floor:** $300K platform with prepay. Below that needs your VP. Below $285K you walk and come back at their reset. **What you can give (in order of cheapness to you):** - Implementation fee waived — protects your platform baseline for renewal - Year-one ramp: veg module activates at month 7, full rate from year two - Deferred first invoice to align with their financial year - Additional read-only seats for the control room and the works planners - Renewal uplift cap at 4% **What you must ask for in return:** - 36-month term (matches the back half of their determination period) - Annual prepay, up front - Signature by a named date - Named case study: their logo, a quote from the Chief Engineer, a presentation slot at the industry asset management conference - Warm intro to the sister DNSP / the other business unit in the group - Removal of the uncapped-liability redline their legal team put in **Rule:** nothing leaves the left column without something specific from the right. Not "I'll see what I can do." A named counter-item, every single time. Also know: who actually signs (usually the GM Operations or the Head of Asset Management up to a delegation limit, then the exec committee), whether the category manager in procurement has to run the panel process, and when their financial year rolls.
- 2
Opening 90 seconds: make them re-state the yes
Get in before the anchor lands. > "Before we get into commercials — last week you said Ken's comfortable after the blind ranking test and you'd told your GM this is the pick. Just so I'm building the right paper: is that still where the team is?" Let them say yes out loud. It is much harder to threaten to walk twenty minutes after confirming you've already won. If they hedge — "well, procurement still has a view" — that's a process fact, not a decision reversal. Note it and keep going: "Understood, we'll deal with the panel process separately. On the technical side, you're settled?"
- 3
Restate the case in their numbers, not yours
You are not justifying the price. You're setting the ratio the discount will be measured against — and in a distribution business, the ratio is regulated dollars. > "When we scoped this with Priya, three things came out. You're running an unplanned distribution transformer failure rate of 4.1 per thousand units and about 70% of those failures are on the rural feeders where the response time is worst. Those failures were carrying roughly 18 SAIDI minutes a year between them, before you count the GSL payments to the worst-served customers on the two long spurs. And Priya's STPIS position for this period is sitting on the wrong side of the target. > The proposal on the table is $340K. If it moves the needle on even a third of those minutes over the term, the STPIS arithmetic alone makes this a rounding error. That's the shape of the deal — so let's talk about what needs to happen to get it signed." Then stop. Don't add "and of course there's some flexibility." That single sentence is the most expensive thing reps say on this call.
- 4
Tactic 1 — the low anchor: "We budgeted about half that"
Do not counter. Do not react to the number at all. Get curious about how it was built. > "Help me understand how you got to $175K. Is that an approved line in the maintenance budget this year, or is it what's left after the condition monitoring spend you've already committed?" In utilities the answer usually reveals the whole deal. "$175K" often means: *$175K of opex is available this financial year, and the real money sits in the reliability program business case going into the next submission.* That's not a price problem, it's a timing and structure problem — and timing and structure you can solve for free. Follow up: > "And which line is it coming from — maintenance opex, or is Regulatory Affairs trying to get it into the reset submission as part of the reliability program?" > "When does drafting on that submission actually start, and who owns the reliability business case?"
- 5
Tactic 1b — when they push price, you move scope
This is the single most important move on the call, and in this industry scope is beautifully divisible: number of transformers modelled, number of feeders, whether the vegetation module is in, whether you're integrated into the ADMS/OMS or delivering a ranked list into the works program. > "I can absolutely build you something at $175K. It won't be this. It'd be the 12,000 units on your forty worst-performing feeders — the ones already at the top of the criticality ranking — no vegetation module, and a quarterly ranked list into the asset register rather than a live feed into the ADMS. Do you want me to price that properly, or do we work together on getting the full-fleet scope funded?" Nine times out of ten they don't want the small version, because the Chief Engineer's whole objection to their last condition monitoring platform was that it only covered part of the fleet and nobody trusted a partial picture. Let them talk themselves back up. What you must never do is deliver the full scope at the reduced number.
- 6
Tactic 2 — the competitor quote (usually an OEM bundle or a big-consultancy CBRM study)
Assume it's real. Assume it is also not the same thing. > "That's a real number and I believe you. Can you send me the quote? Not to match it — I want to see what's actually in it. Every time we've seen an OEM bundle monitoring into a transformer supply agreement, it's nameplate, age and DGA on the units they supplied. It doesn't model the 30,000 pole-mounts already on your network that nobody has condition data for, which is the fleet that's actually failing on day three of a heatwave." Then the question that decides the rest of the call: > "If their model were free — genuinely zero — would you still be buying it?" When the Chief Engineer says "no, honestly, we'd still want yours," that answer is your leverage for the next thirty minutes. Never say the competitor is worse. Say precisely what isn't in the quote and what it costs them when it turns up as a variation in month four.
- 7
Tactic 3 — the regulatory cycle as a discount lever
"We're mid-determination, the allowance is locked" is true and it is also being used on you. Separate the two. > "I'm not going to argue with the determination — you can't spend an allowance you don't have. So let's split it. Is the constraint that there's no money at all this period, or that there's no *capex* this period?" Then offer structure instead of discount: > "If it's capex, this doesn't have to be capex. It's a subscription, it's operating expenditure, and it sits against the same maintenance line that's currently funding the emergency callouts and truck rolls for unplanned transformer faults. If it defers even fifteen run-to-failure replacements a year and takes a chunk out of the after-hours callout count, it may be net-neutral inside maintenance before it ever gets near the capex allowance. > And separately — the submission. You told me drafting starts in nine months. A reliability business case with two years of your own data behind it, showing which units the model called and how the failures actually landed, is a fundamentally stronger paper than one with a vendor's brochure attached. Signing now is what makes the reset submission credible." That reframes the locked period from a reason to wait into a reason to start.
- 8
Tactic 4 — the case study and reference trade
In this industry the currency is real and specific: they all know each other, they all sit on the same working groups, and a named DNSP reference is worth more than a logo on your website. So price it properly and put a date on it. > "I'd genuinely value that, so let's make it a real trade rather than a handshake. What I need is: your logo, a named quote from Ken as Chief Engineer, a twenty-minute joint presentation at the asset management conference in November, and one intro to your counterpart at the sister network. Written into the order form with dates. If you can commit to that, I can move on the implementation fee. Does corporate affairs need to sign off on the external presentation?" Most buyers who dangle a case study go quiet the moment you ask for an approval path and a date. If they can't commit, the concession comes off the table — warmly. "No problem at all, let's park that one and find something else to trade."
- 9
Tactic 5 — the delay threat: "Let's push the PO to next financial year"
Do not panic and do not buy the quarter with margin. Make them do their own cost-of-delay arithmetic out loud. > "That's your call and I'll still be here in July. Practically though — the model needs a full summer of loading and temperature data before it's calling anything useful. If we start in July, the first real fire season it can speak to is the one after next. Is Priya comfortable going into the next STPIS year with the same transformer failure rate and no new lever?" Then solve the actual problem, which is almost always cash timing, not decision: > "If it's the financial year rather than the decision, I can structure around it. Sign this month at this number, first invoice dated 1 July, data onboarding starts now so we're not burning the summer. You get the price on the table and the spend lands in the year you've got room in." Zero cost to you. Solves their entire stated problem. Removes the lever.
- 10
Tactic 6 — the silence
They name a number and stop talking. This is where deals leak margin, and asset managers are unusually good at it because they spend their working lives in long meetings where nobody rushes. **The rule: you may not improve your own offer twice in a row.** After they go quiet you have exactly two legal moves — say nothing back, or ask a question. > [count to seven] "...What's your reaction?" If you have to speak, speak about process, never about price: > "What's the approval path once we've agreed the number — does this go through the panel, or straight to your delegation?" What you must not say: "...I could probably get that approved." The pause was the tactic. Don't pay for it.
- 11
The concession ladder — and what to discount
Every concession must be (a) smaller than the last, (b) traded, and (c) explained. And in a business that will renew this against a regulated cost line for the next ten years, **protect the platform number and give away fees and timing instead.** A discounted platform baseline is a permanently discounted baseline, and the uplift conversation at renewal is brutal. **Move 1 — term:** "36-month term, aligned to the back half of your determination period, and I'll hold the platform at $322K with a 4% uplift cap. That's the shape I can defend internally." **Move 2 — prepay:** "Annual prepay up front, and I'll waive the $45K implementation entirely. That's a real dollar give and it doesn't move your recurring number, which matters when Regulatory Affairs is justifying the line at the reset." **Move 3 — date, and final:** "Signature by the 24th and I'll ramp year one — vegetation module activates month seven, so your year-one cash is $282K, full rate from year two. That's it. That's the end of what I have." Bad ladder: 15% → 20% → 25%. You've just taught them each ask is worth five points. Good ladder: decreasing increments, each one bought.
- 12
Using approval authority as a trade, not a stall
"Let me check with my manager" is a genuine tool, used once, to buy something. > "That number's outside my delegation, I can't sign it. I can take it to our VP, but I can't walk in and just ask — I need an argument. If it's 36 months and prepaid, I've got one. Give me that and I'll go and fight for it properly." Two things this does: it makes the concession conditional, and it makes the no somebody else's decision, which is what lets you hold firm without being the person holding firm. Come back once, with a number that is visibly final, and say why it's final.
- 13
Landing it — the signature path in a regulated business
Confirm verbally, then in writing within the hour. In a DNSP the signature path has more gates than most, so name every one. > "So let me read it back. Platform $322K a year, 36-month term, 4% uplift cap. Implementation waived. Vegetation module ramps in at month seven so year-one cash is $282K. Annual prepay. Case study with Ken's quote and the conference slot in November, written into the order form. Signature by the 24th. > On the path: OT security review — that's with your architecture team and the sign-off is data feeds only, no device on an energised asset, no connection into the control system. Where's that up to? Legal has the MSA, the uncapped liability clause is coming out as part of this. Does this go to the panel process or does it sit inside your delegation? And who raises the PO?" Then the line that protects the whole thing: > "And to be straight with you — this number is tied to those terms and that date. If the 24th moves, I have to re-approve it, and I'd rather tell you that now than surprise you in three weeks." Book a fifteen-minute hold for the day after the security review closes. Don't leave with "end of the month."
- 14
Staying warm the whole way through
You are sitting on their side of the table arguing with your own company on their behalf. Signal it constantly: "I want this done." "Let me see what I can build." "I'll go and fight for that." A firm no delivered warmly gets respected. A soft yes delivered nervously gets pushed again. Asset managers are patient, professional negotiators who deal with contractors and OEMs every week — they enjoy negotiating with someone who's also good at it. Losing your nerve is what invites the fourth ask.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Before we get into the number — last week you said Ken had run our ranked list blind against his own view of the worst feeders, and you'd told your GM this was the direction. Is that still where the team is?
Buyer
It is. Ken's happy. It matched him on eleven of his top fifteen feeders and it flagged about sixty pole-mounts on the western spurs he wasn't watching, which he found interesting. That's not the problem. The problem is $340,000. We budgeted about half that.
Rep
Help me understand how you got to $175K. Is that an approved line finance has already signed off, or is it what's left in the condition monitoring budget after this year's commitments?
Buyer
It's what's in the maintenance line. And I'll be honest with you, we're three years into a five-year determination. The capex allowance is locked. There is no allowance for this — anything new has to come out of someone else's project or wait for the 2027 reset.
Rep
I'm not going to argue with the determination. But let's split it, because I think there are two different constraints in there. Is it that there's no money this period, or that there's no capex this period? Because this is a subscription. It's opex, and it sits against the same maintenance line that's currently paying for the emergency callouts when a pad-mount lets go on the fourth day of a heatwave.
Buyer
Sure, but $340K of opex is still $340K of opex. And I should tell you — our transformer OEM has offered to bundle monitoring into the next supply agreement. Effectively free. Procurement is going to ask me why I'm paying you three hundred and forty thousand dollars for something we're being offered at zero.
Rep
That's a real offer and I believe it. Send me the quote — not to match it, I want to see what's in it. Every OEM bundle we've come up against covers the units they supply, on nameplate, age and DGA. It doesn't touch the thirty-odd thousand pole-mounts already on your network with no condition data at all, and that's the fleet that's driving your 4.1 unplanned failures per thousand units. Let me ask you the honest question, though: if their model were genuinely free, would you still be buying ours?
Buyer
...No. Ken wouldn't wear it. Their thing is an age curve with a logo on it. But that doesn't change my budget. Look — I can get to $210,000. And we'd be happy to be a reference for you. We're on two working groups, everyone in this sector talks to everyone.
Rep
[pause] What's driving the $210 specifically — is that the delegation limit, or is that where the line runs out?
Buyer
That's where the line runs out this financial year. [silence]
Rep
Okay. Two things, then. First, on the reference — I'd genuinely value that, so let's make it a real trade instead of a handshake. Your logo, a named quote from Ken as Chief Engineer, a joint twenty-minute session at the conference in November, and one intro to your counterpart at the sister network. Dated, written into the order form. Can you commit to that, and does corporate affairs need to approve the external piece?
Buyer
Corporate affairs would need to see the wording, but yes, I can commit to that. November's fine. What's it worth?
Rep
It's worth the $45K implementation fee — I'll waive it entirely, in exchange for that plus annual prepay up front. What I'm not going to do is move the platform number down to $210, and here's why that's actually in your interest: that recurring figure is what Regulatory Affairs has to justify in the reset submission and what your renewal uplift gets calculated off. Cutting it now means you're defending a discount you can never rebuild from. I'd rather give you real dollars off the fees and the timing.
Buyer
I hear you. But I still can't raise a PO this year. The OT security review hasn't closed — architecture want to see the data feed design before anything touches the historian — and honestly, we might just push this into next financial year and pick it up then.
Rep
That's your call and I'll still be here in July. Practically though — the model needs a full summer of loading and temperature data before it calls anything useful. Start in July and the first fire season it can genuinely speak to is the one after next. Is Priya comfortable going into another STPIS year with the same failure rate and nothing new in her plan? Because if the constraint is the financial year rather than the decision, I can just solve that: sign this month, first invoice dated 1 July, data onboarding starts now so we don't lose the summer.
Buyer
...That actually helps. If the invoice lands in the new year, I can get this through my delegation without going near the exec committee.
Rep
Then here's where I can land it, and this is the end of what I've got. Platform at $322K, 36-month term, 4% uplift cap. Implementation waived. Vegetation module activates month seven, so your first-year cash is $282K, full rate from year two. Annual prepay, invoice dated 1 July. Case study and the November session in the order form. Signature by the 24th.
Buyer
Take the vegetation module out entirely and give me $290 and I'll sign Monday.
Rep
I can't sign that one — and I'd push back on the logic anyway, because vegetation is still your biggest single cause of unplanned outage minutes on the rural feeders and it's the line the regulator asks about every year. Pulling it out saves you $40K and leaves your veg spend per line kilometre exactly where it is. What I'll do instead: keep everything as I described, and if you can get me signature by the 24th rather than the 27th, I'll add read-only seats for the control room and the works planners at no charge. That's it. Do we have a deal?
Buyer
Send me the revised order form today and I'll walk it into Ken and legal tomorrow. The 24th should be achievable if architecture close out this week.
Rep
It'll be with you within the hour. I'll put a fifteen-minute hold on Thursday to confirm the security review's clear and legal's happy with the liability clause coming out. And to be straight with you — this number is tied to those terms and the 24th. If the date moves I have to re-approve it, and I'd rather say that now than surprise you in three weeks.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “"We're mid-determination. The capex allowance is locked and there's no line for this until the 2027 reset — so the number has to be half."” | Agree with the constraint, then separate money from capex. "You can't spend an allowance you don't have, I get that. Is the constraint no money this period, or no *capex* this period?" A subscription is opex and it competes with the emergency callout and truck-roll spend already sitting in maintenance — if it defers fifteen run-to-failure replacements and cuts after-hours responses, it can be argued as net-neutral inside the maintenance line without touching the allowance. Then use the reset as a reason to start now, not later: "Your reliability business case for the submission is drafted in nine months. That paper is far stronger with two years of your own data showing which units the model called and how the failures actually landed, than with a vendor's brochure attached." |
| “"Our procurement panel needs three comparable quotes and yours is the highest of the three."” | Don't discount to the middle of a list you didn't build. Attack comparability instead. "Happy to go through the panel — can I see the scope statement the other two quoted against? Because if one of them is a one-off CBRM desktop study and the other is nameplate-and-age on the OEM's own units, those aren't comparable to a live model across all 42,000 units feeding your works program." Then offer procurement something they actually want: a scope-comparison table, written by you, that the category manager can attach to the recommendation. You're helping them justify the choice they've already made rather than bidding against a list. |
| “"The transformer OEM will bundle condition monitoring into our next supply agreement — effectively free."” | Assume it's real, then be specific about what's not in it. "Send me the terms. Every bundle we've seen covers the units they supply, on nameplate, age and DGA — it doesn't model the pole-mount fleet already on the network that has no condition data at all, and that's where your unplanned failure rate per thousand units is actually coming from." Then the closing question: "If it were genuinely free, would you still be buying ours?" When the Chief Engineer says no, that's your leverage for the rest of the call. Never say the OEM is bad — say precisely which part of the fleet their model can't see. |
| “"We'll be a reference for you. We sit on two working groups — that should be worth twenty percent."” | Treat it as real currency and price it properly, with a date and an approval path. "I'd genuinely value that. So let's make it concrete: your logo, a named quote from your Chief Engineer, a joint session at the conference in November, and one intro to your counterpart at the sister network — written into the order form with dates. Does corporate affairs need to approve the external piece?" If they commit, pay for it with the implementation fee, not the platform line. If they go quiet on dates and approvals, take the concession back warmly: "No problem, let's park that and find something else to trade." |
| “"We can't raise a PO until the OT security review closes and the Chief Engineer signs off. Let's just pick this up next financial year."” | Don't buy the quarter with margin — that's the most expensive mistake on this call. First test it: "That's your call and I'll still be here. Practically though, the model needs a full summer of loading and temperature data before it calls anything useful — start in July and the first fire season it speaks to is the one after next." Then solve the real problem, which is almost always invoice timing: sign now, first invoice dated to the new financial year, data onboarding starts immediately. Also shrink the gate: your review is data feeds from the historian and outage records, not a device on an energised asset — no type approval, no permit-to-work path, nothing on a live pole. Say that explicitly, because it's usually why the review is sitting in a queue. |
| “"Legal won't sign your MSA — we need uncapped liability for anything touching network data."” | This is a trade, not a wall. "I can't get uncapped liability signed, that's a board-level position at our end, not mine. What I can do is take a specific increased cap to our VP if you'll tell me what the actual exposure concern is — is it data security, or is it a decision the model makes that leads to an asset failure?" Then be clear about what you're not: you produce a ranked risk list into their works program; the switching decision, the permit-to-work and the asset intervention are all theirs and always will be. Once that's on the table the clause usually narrows. And when it comes out, count it as their concession in the ladder — because it is one. |
| “"Give us the rural feeders free for twelve months as a proof, and we'll do the full fleet at the reset."” | You've already done the technical win — a second free period is buying the same yes twice. Name that gently and convert it into scope. "You've already run the eval and Ken's already validated the ranked list against his own, so I don't think another proof tells you anything new. What I can do is scope down honestly: price the forty worst-performing feeders as a paid year one, full fleet from year two at a pre-agreed rate, all inside one 36-month order form signed now. You get the smaller cash number this year and I get the term — and you don't have to re-run this whole procurement in twelve months." |
Questions reps ask about this call
- How do I keep a utility from using the regulatory determination period as a permanent discount lever?
Separate the two things inside the objection. "No allowance" almost always means no capex allowance — it rarely means no money at all. A subscription is opex and competes against the maintenance line that's already funding emergency callouts and unplanned truck rolls, so ask which constraint is actually binding. Then flip the reset from a reason to wait into a reason to start: the reliability program business case going into the next submission is dramatically stronger with two years of the utility's own data behind it. Ask when submission drafting begins and who owns that business case — that's the real deal timeline, and it's usually earlier than the reset date they quoted you.
- What can I trade instead of price when selling to a DNSP?
The things a distribution business can give that cost them nothing and are worth a lot to you: a 36-month term aligned to the back half of the determination period, annual prepay, a named case study with a quote from the Chief Engineer, a joint session at an asset management conference, an intro to the sister network or another business unit in the group, and removal of the uncapped-liability redline their legal team added. What you give back should be implementation fees, year-one ramps, deferred invoice dates and extra read-only seats for the control room — not the recurring platform number.
- Should I discount the platform line or the implementation fee?
The fee, almost always. The recurring platform number is what Regulatory Affairs justifies in the submission and what your renewal uplift is calculated from, so a cut there is permanent in a way a one-off fee waiver is not. Waiving a $45K implementation fee often feels bigger to the buyer than five points off the subscription while doing far less damage to your baseline. You can even say this out loud — "I'd rather give you real dollars off the fees than cut the recurring figure you'll have to defend at the reset" — because it's true and it sounds like you're on their side of the table.
- They've told me an OEM will bundle condition monitoring for free. How do I respond without trashing the competitor?
Ask for the quote, then be specific about scope rather than quality. OEM bundles typically cover the units the OEM supplies, on nameplate data, age and DGA — they don't model the existing pole-mount fleet that has no condition data and that drives most of the unplanned failure rate per thousand units. Say that, then ask the deciding question: "If it were genuinely free, would you still be buying ours?" If the Chief Engineer says no, you have your leverage. If he hesitates, you have a technical gap to close before you talk about price at all.
- What do I do when the buyer names a number and then goes completely silent?
Nothing, for seven seconds. Then ask a question — never improve your own offer. Acceptable follow-ups: "What's driving that figure specifically — is it a delegation limit or where the line runs out?" or "What's the approval path once we've agreed the number?" The silence is a deliberate tactic and asset managers are unusually good at it because they spend their lives in unhurried meetings. The rule that saves the deal: you may not improve your own offer twice in a row.
- They want to push the PO into the next financial year until the OT security review closes. Do I discount to hold the quarter?
No. Test it, then solve the structure. Test it by making the cost of delay concrete — a condition model needs a full summer of loading and temperature data before it's calling anything useful, so a delay costs them a fire season, not just a quarter. Then solve the actual issue, which is usually invoice timing: sign this month at this number, first invoice dated to the new financial year, onboarding starts now. Also shrink the security gate by being precise about what you are — data feeds from the historian and outage records, no device on an energised asset, no type approval and no permit-to-work path required. That's often why the review is sitting untouched in a queue.