Telecommunications · Pricing Negotiation Call
Telecommunications Pricing Negotiation Script: Holding Your Number After the Technical Win
You've won this. The NOC lead ran the six-week read-only trial off the northbound feed, the Head of Network Operations told the CTO it's the pick, and someone in Field Ops has already put your degradation flags next to last quarter's no-fault-found rate and liked what they saw. Nobody on this call is trying to talk themselves out of buying. They are trying to buy the exact same thing for less, and they will be extremely pleasant about it.
Telco buyers are good at this in a specific way. They negotiate access charges, backhaul commitments and CVC/AVC pricing for a living — the whole commercial muscle of the business is built around squeezing per-service cost. They will tell you the capex committee doesn't meet for nine weeks. They will mention that their assurance vendor is "probably going to bundle something similar" at renewal. They will point out that half the faults you'd predict sit on the access network so you should only charge for half the value. And after they name a figure, they will go quiet and let you talk yourself down twenty points.
This telecommunications pricing negotiation script is for the ten minutes before that call. The rule underneath all of it: when they push on price, you move scope, not price — and nothing leaves your side of the table without something specific and dated coming back. You are not trying to win the negotiation. You are trying to hold the number, keep them wanting to sign with you, and get off the call with a date.
The pricing negotiation call script
Say it in your own words. The structure is the part that matters.
- 1
Before you dial — write down your three numbers in their units
Ask / Target / Floor, and convert each one into cost per truck roll and cost to serve per service per month before you dial. If your ask is $240K a year across 400,000 services, that's five cents per service per month — and that's the number the CFO will actually test, not the annual figure. Know the same three things about them: - Which budget line this comes off. Field services opex? Contact centre? Network build? If it's field services, the Director of Field Operations is spending money that shows up as a saving in someone else's column, and that peer tension will surface on the call. - When their fiscal year ends and when the capex committee sits. - Who actually signs. CTO? COO? Or does it go to a procurement panel that will re-open the number after you've agreed it? Your trade list, telco-shaped: | You can give | You must ask for | |---|---| | Discount points | 24 or 36-month term | | Deferred start until after the migration cutover | Annual prepay | | Onboarding / feed-integration fees waived | Signature by a named date | | A second region or second POI footprint at no uplift | Named case study — logo, spokesperson, date | | Ramped year one (region 1 only, expand at month 6) | Two reference calls to named peer carriers | | Renewal uplift cap at 5% | Auto-renew clause intact | | Exec sponsor + monthly review with the NOC lead | Intro to the enterprise or wholesale business unit |
- 2
First 90 seconds — make them say the yes out loud before they anchor
"Before we get into commercials — last week you said the team's aligned, and that the NOC lead was comfortable with the precision threshold. Is that still where you are, or has anything moved?" [Wait. Let them confirm it.] "Good. Then this is a commercial conversation, not a technical one, and I'll stay out of re-pitching it." Do not open with flexibility. Do not say "and there's some room on price." The moment you do, the negotiation starts from your lower number and they haven't paid a cent for it.
- 3
Restate the case in their metrics — this is the ratio the discount gets measured against
"Just so we're measuring the number against the right thing. In the trial, across the Northern region, we flagged degradation ahead of the customer call on a bit under a third of the faults you dispatched on. Your team put cost per truck roll at around $180 all-in — van, tech, the two-hour window. At your current run rate that's roughly [X] avoidable dispatches a quarter in one region alone, before you count the no-fault-found rate coming down or the first-time-fix lift. "And that's the smaller half. The bigger one is that mean time to detect stops being dominated by the customer calling in — which is the thing that drives the 30-to-60-day churn after every mass service disruption. "The proposal on the table is $240K. That's the shape of the deal. So let's talk about what has to happen to get it signed." You're not justifying the price. You're putting it next to a number they gave you.
- 4
The low anchor — "honestly, we budgeted about half that"
Do not counter. Do not flinch at the figure. Get curious about how it was built. "Help me understand how you got to $120K. Is that a line finance has actually approved, or is it what you'd like it to be?" Then listen for which of three things it is: an approved line, a placeholder someone typed before scoping, or this quarter's slice of a bigger annual number. If it's real, move scope — never price alone: "I can absolutely build you something at $120K. It won't be this. It'd be one region rather than the full consumer footprint, and no dispatch-side integration — so you'd get the prediction into the NOC but not into the field workflow, which is where the truck roll saving actually lands. Do you want me to price that version, or do we work on how to fund the full scope?" Nine times out of ten they don't want the small one. They want the big one at the small price, and you've just made that visible without saying no.
- 5
The bundled-competitor lever — "our assurance vendor will probably throw this in at renewal"
Assume the quote or the hint is real. Assume it is also not the same thing. "That's a real conversation and I'd have it too. Can you send me what they've put in writing? Not to match it — I want to see whether it's correlation or prediction. Every bundled module we've seen sits downstream of the alarm: it tells you what already broke and groups it. That's not what your NOC lead was testing us on. He was testing whether we flagged degradation before the customer dialled in. "And the question I'd ask them: does the bundle change mean time to detect, or does it just tidy up the queue after?" Then the one that gives you the rest of the call: "If theirs were free, would you still be buying it?" When the answer is a version of "no, yours is the one we want" — that's your leverage. Never say the competitor is worse. Say precisely what isn't in their scope and what it costs when it lands as a change order in month four.
- 6
The logo trade — price it, date it, and put it in the order form
Carrier logos are genuine currency and they know it. Treat it like currency. "I'd genuinely value that — there aren't many RSPs of your size who'll talk publicly about truck roll numbers. So let's make it a real trade rather than a warm intention: 4% off, and in exchange I need your logo, a named quote from you or the GM Service Assurance, and one recorded session within 120 days of go-live — written into the order form. "Practical question, because I know how this works in telco: does that need corporate affairs sign-off, and does anything with outage or dispatch numbers in it need to go past legal or regulatory first?" If they can't name a person and a path, the discount comes off the table — warmly. "Totally fine. Let's leave the case study out and I'll hold at the earlier number."
- 7
The delay threat — "we'll pick this up at the next capex cycle"
Do not buy the quarter with margin. Make them do the cost-of-delay maths out loud. "That's your call and I'll still be here in April. Practically though — two things. One, the window your team held for the feed work was February; do they still have that in April, or are they on the OLT replacement programme by then? Two, the GM Consumer's retention number for this half was partly built on getting ahead of the post-MSD churn. What happens to that if the detection piece lands two cycles later?" Then solve the actual problem, which is almost always timing rather than decision: "And if it's cash timing rather than the decision itself — this shouldn't be a capex item anyway. It's opex against dispatch cost. But if the money genuinely isn't there until the new year, I can do a deferred start: sign this month, first invoice 1 April, service starts with the April billing cycle. You get today's price and the spend lands in the quarter you need it in." That costs you nothing and removes the lever.
- 8
The silence
They name a figure. Then they stop talking. This is where margin leaks. Rule: **you may not improve your own offer twice in a row.** After they go quiet you have exactly two legal moves — say nothing, or ask a question. [Count to seven.] "...What's your reaction to that?" Or, if you have to speak, speak about process, not price: "What's the approval path once we've landed on the number — does it go to the COO directly, or through a procurement panel?"
- 9
The concession ladder
Every step smaller than the last, every step traded, every step explained. Step 1: "I can do 7% on a 24-month term. Annual, and it's list." Step 2: "I can get to 10% if it's 24 months and prepaid annually rather than quarterly — that's what gives me the argument internally." Step 3: "11%, tied to signature by the 27th, and that's where I stop. Not because I'm posturing — because below that I'm discounting the platform line, and that permanently resets your renewal baseline. You don't want that either." 7 → 10 → 11 tells them there's a floor. 10 → 15 → 20 tells them to keep asking. And protect the platform line specifically. Give away the feed-integration fee, the second region, the onboarding — not the per-service rate. In two years' time the per-service rate is the number the CFO benchmarks the renewal against.
- 10
Escalation with a reason, not a request
Use this once, and use it to buy a trade — never as a stall. "15% is outside what I can sign. I can take it to my VP, but I can't walk in there with just a request; I need an argument. If it's 36 months, prepaid, and I can name you as a reference for two conversations with carriers your size, I've got something to take in. Give me that and I'll go and fight for it." When you come back, come back final, and say why it's final.
- 11
Landing it — say the whole thing back and put a date on it
"So let me say it back. $216K, 24-month term, annual prepay, feed-integration fee waived, renewal uplift capped at 5%, case study with corporate affairs sign-off inside 120 days of go-live, and you're signing by the 27th. Have I got that right? "Who signs — is that you or does it go to the COO? Is legal engaged yet, and is the security review closed or still open? Is there a PO to raise before the 27th, and how long does that normally take you? "I'll have the revised order form to you within the hour. I'll hold fifteen minutes on Thursday to confirm legal's clear." Then the line that protects it: "And to be straight with you — that number is tied to those terms and that date. If the 27th moves, I have to take it back for re-approval. I'd rather tell you now than surprise you in three weeks."
- 12
Staying warm — you're on their side of the table
Signal it constantly, because a firm no delivered warmly gets respected and a nervous yes gets pushed again. "I want to get this done before your cycle closes." "Let me see what I can build." "Give me the argument and I'll go and fight for it." "That's your call and I'll still be here." This buyer negotiates access pricing for a living. They will enjoy negotiating with someone who is also good at it. Losing your nerve loses their respect — and their respect is what stops 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 the NOC lead was comfortable and that you'd told the CTO this was the pick. Is that still where you're at?
Buyer
It is. He liked it. Genuinely — the flags on the Northern POI two days before the ticket volume spiked were the thing that convinced him. That's not the issue. The issue is the number. I took $240K to our CFO and he did the thing where he doesn't say anything for a while. He's got cost to serve per service per month written on a whiteboard in his office. Your fee adds about five cents to it and he can see that immediately.
Rep
He would. So what did he say the five cents needs to come back as?
Buyer
He didn't. He said we'd budgeted around $120K for anything in this space this year. That's the number I've got.
Rep
Help me understand how $120K got built. Is that an approved line finance has already carved out, or is it what someone put in the plan before we'd scoped this?
Buyer
Bit of both, honestly. It was in the assurance tooling line from the annual plan, before we'd run your trial. But it's the line that exists.
Rep
Okay. Then two options and you tell me which one's more useful. I can price you a $120K version — one region, prediction into the NOC, no dispatch-side integration. You'd see mean time to detect move, but you wouldn't see truck rolls per thousand services move, because the flag never reaches the field workflow. Or we work on funding the full scope from the dispatch line, where the saving actually lands. Which conversation do you want?
Buyer
See, that's the bit that annoys me. You're asking me to take money off Field Ops to pay for something in my budget. Steve's already been told to lift first-time-fix and cut dispatch volume with the same headcount. He's not going to hand me $120K out of his van budget so I can buy a prediction engine.
Rep
Understood — and that's a real internal problem, not a fake one. But run it the other way for a second. In the trial we flagged ahead of the customer call on close to a third of the faults you dispatched on in one region. At $180 a truck roll, that's Steve's line getting cheaper, not more expensive. If the business case is written as dispatch avoidance rather than assurance tooling, is it still Steve handing you money, or is it Steve funding his own target?
Buyer
Maybe. Look, I'll be straight with you — our assurance vendor's renewal is in May and they've hinted they'll bundle a predictive module. Might be nothing. But if I can get eighty percent of this for free in six months, $240K looks silly.
Rep
Fair. Can you send me what they've put in writing? Not to match it — I want to see whether it's prediction or correlation, because everything we've seen from them sits downstream of the alarm. It groups events after the fault. Your NOC lead wasn't testing us on grouping, he was testing whether we saw degradation before the customer dialled in. Different product. But let me ask you the honest version: if theirs were free tomorrow, would you still be buying ours?
Buyer
...Probably, yes. Yours worked. Theirs is a slide.
Rep
Then let's price the one that worked. Here's what I can do. 7% off on a 24-month term. If you can make it annual prepay rather than quarterly, I can get to 10% — that's the piece that gives me an argument with my VP.
Buyer
Get me to 15% and I'll give you a case study. We're a recognisable name in this market. Nobody in your logo wall is our size.
Rep
I'd genuinely value that, and you're right about the size. So let's make it a real trade instead of a warm intention. 11% — 10 for the prepay, one more for the case study — with your logo, a named quote from you or the GM Service Assurance, recorded inside 120 days of go-live, written into the order form. Practically: does that need corporate affairs sign-off, and does anything with outage minutes or dispatch numbers in it need legal or regulatory eyes first?
Buyer
[pause] Corporate affairs, yes. Regulatory if we quote anything on unplanned outage minutes. That's... probably a six-week process on our side.
Rep
That's fine — six weeks inside 120 days works. What I can't do is take the point off and then find in April that nobody can name a spokesperson. So: who owns it on your side?
Buyer
I'll do it myself. Alright. But 11% still doesn't clear the CFO. And honestly, we could just park this until the capex committee sits in April and go again with the full-year plan.
Rep
That's your call and I'll still be here in April. Two practical things though. One — this shouldn't be a capex item at all; it sits in opex against dispatch, which is why it doesn't need that committee. Two — the feed work your team scoped for February, do they still have that window once the OLT replacement programme starts? And if the answer's cash timing rather than the decision, I can do a deferred start: you sign this month at this price, first invoice 1 April, service starts with the April cycle. Your spend lands in the quarter you want it in and you don't re-run the eval.
Buyer
...Say that again? Sign now, pay in April?
Rep
Sign by the 27th, first invoice 1 April, 24-month term, annual prepay from that date, 11%, case study inside 120 days with you as spokesperson, renewal uplift capped at 5%. And I'll waive the feed-integration fee, which is where the CFO's five cents gets a lot less interesting in year one. Does that get through him?
Buyer
That's a much easier conversation. He'll still push. But that I can walk in with.
Rep
Good. Then last bit — who actually signs, is legal engaged yet, and how long does a PO take you? And to be straight with you: that number's tied to the 27th. If the date moves I have to take it back for re-approval, and I'd rather tell you now than in three weeks.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Our CFO looks at cost to serve per service per month. Your fee adds five cents and he can see that instantly.” | He should — he knows the per-service numbers better than anyone in the building. So let's put it next to the line it comes off. Five cents a service a month against your cost per truck roll and your no-fault-found rate: in the trial region we flagged ahead of the customer call on close to a third of dispatched faults. That's a dispatch line getting smaller, not an assurance line getting bigger. Write the business case against cost per truck roll and NFF rate, not against tooling spend, and the five cents stops being the headline. And if it helps, I'll waive the feed-integration fee so year one lands lighter — but I need the 24-month term for that. |
| “Our assurance vendor is bundling a predictive module into the May renewal, so we shouldn't pay full price for yours.” | Send me what they've written down — not to match it, but because I want to know if it's prediction or correlation. Everything we've seen from them sits downstream of the alarm: it groups events after the fault has happened. Your NOC lead wasn't testing us on grouping, he was testing mean time to detect before the customer dials in. If their module genuinely moves MTTD, you should take it. If it's a slide with a roadmap date, you're discounting a working product against a promise. And here's the honest question — if theirs were free tomorrow, would you still be buying ours? |
| “Half our faults sit on the access network. We don't own the fix, so we only get half the value — price it at half.” | Actually that's the half where the money is. The dispatch you shouldn't have sent is the one where the degradation was upstream and the tech found nothing — that's your no-fault-found rate, and it's the same $180 van as a real fault plus a complaint from a customer you sent someone to for nothing. If you can tell before dispatch that the pattern is upstream, you raise the wholesale fault, you tell the customer the truth, and the technician stays in the van. I'm not discounting for the access-side faults. I'd argue they're the strongest line in the case. |
| “We'll push the PO into the next capex cycle — the committee doesn't sit until April.” | That's your call and I'll still be here. Two things though. This isn't a capex item — it's opex against dispatch cost, which is exactly why it doesn't have to wait for that room. And if the real constraint is cash timing rather than the decision, I can solve that without touching the price: sign by the 27th, first invoice 1 April, service starts on the April cycle. You get this number, the spend lands in the quarter you want, and your team keeps the February feed window before the OLT programme eats it. |
| “Our closure codes are rubbish and the inventory doesn't match the ground, so the ramp will be slow. We shouldn't pay full year one.” | The prediction runs off performance and alarm telemetry, not closure codes — that's why it worked in the trial on the same messy data. Bad inventory affects where you route the dispatch, not whether we spot the degradation, and one of the first outputs is a list of records where the telemetry disagrees with the inventory. So I won't discount for data quality. What I will do is ramp the footprint: region one for the first six months at a reduced rate, full consumer book from month seven at the agreed rate. You pay for what's live. I'd need the 36-month term for that shape. |
| “We're mid-migration and my engineering team has zero cycles, so we can't start until Q3 — hold the price until then.” | I'll hold the price, but it has to be attached to a signature date, not an open window. Sign by the 27th with a deferred start and the number is locked; leave it unsigned and I'm re-approving it in Q3 at whatever list is then. And on cycles — the ask is two hours from whoever can point us at the northbound feed and your NOC lead looking at output weekly. Read-only, out-of-band, no change window, nothing that touches the migration. If it needs an integration sprint before you see value, we've designed it wrong. |
Questions reps ask about this call
- How do I stop a telco buyer anchoring the whole negotiation on cost to serve per service per month?
You don't stop them — you reframe which line it comes off. Cost to serve is the right metric, but your fee shouldn't be measured against tooling spend. Put it next to cost per truck roll, truck rolls per 1,000 services and no-fault-found rate, using the numbers from their own trial region. Then offer to waive the feed-integration or onboarding fee so year one lands lighter, and charge for that concession with term length. Never discount the per-service platform rate itself — that's the number the CFO will benchmark your renewal against in two years.
- What do I do when they say the capex committee doesn't meet for another quarter?
Take it out of capex. Most predictive assurance and dispatch-avoidance spend belongs in opex against the field services or contact centre line, which is a different approval path and usually a lower threshold. Then solve the cash timing structurally rather than with margin: sign this month, defer the first invoice to the start of their next quarter, start the service with that billing cycle. That gives them today's price in the budget period they need. Paying 10% to buy the quarter is the classic mistake — it solves nothing they actually asked for.
- They're hinting their existing assurance vendor will bundle a similar module free at renewal. How should I respond?
Ask for it in writing and interrogate what it actually is. Bundled modules from correlation platforms almost always sit downstream of the alarm — they group and de-duplicate events after the fault. That is a different product from a lead indicator that moves mean time to detect before the customer calls in. Ask what the bundle does to MTTD specifically. Then ask the leverage question: 'If theirs were free, would you still be buying ours?' If they've run a six-week trial and told their CTO it's you, the answer is usually yes, and it reframes the rest of the call.
- A carrier logo is genuinely valuable to us. How much should I trade for a case study?
Treat it as currency and price it explicitly — a few points, not double digits. But make it enforceable or it's free: named logo, a named spokesperson (the Head of Network Operations or GM Service Assurance carries more weight than a marketing contact), a specific deliverable, a deadline of 120 days from go-live, and a clause in the order form. In telecommunications, always ask up front whether corporate affairs signs off and whether anything quoting unplanned outage minutes or dispatch volumes needs legal or regulatory review. If they can't name the owner and the path, withdraw the discount warmly.
- Which telco buyer titles should actually be on the pricing call, and does it change the script?
The Head of Network Operations or GM Service Assurance usually owns the technical win but rarely owns the money. The Director of Field Operations owns the budget line the savings land in. The COO or CTO signs, and a procurement panel may re-open the number afterwards. Before you concede anything, ask directly who signs and whether procurement gets a second bite — if they do, hold a point back so you have something to give in that round instead of arriving at your floor twice.
- They named a number and then went silent. What's the right move?
Say nothing, or ask a question. Those are your only two options. The rule is that you may not improve your own offer twice in a row — the pause is the tactic, and the rep who fills it pays for it. Count to seven, then either 'What's your reaction?' or move to process: 'What's the approval path once we've agreed the number — does it go to the COO or through a procurement panel?' Talking about signature mechanics during their silence is comfortable for you and useful for the deal.