This opens Part 3 of the course — winning the deal, once it’s qualified and the right stakeholders are mapped. Objections in platform deals cluster around a small set of recurring themes, almost all traceable to the connectivity-to-platform shift covered in Module 1 and Module 2. This module is a working script library for the five most common ones, not a list of abstract principles.
An objection is rarely a true no. It’s usually a question the pitch hasn’t answered yet.
Five objections, and response scripts
“We’ll just use AWS/Azure directly”
When it comes up: A technical stakeholder has an existing hyperscaler relationship and sees no reason to route the platform service through the telco.
Script:
“That makes sense for the compute itself — and we’re not trying to replace that relationship. What we’d handle is the in-region compliance, the latency-sensitive connectivity between your sites and that cloud region, and a single point of accountability when something breaks across the stack. [Name a specific GCC-region detail relevant to the account] is the part a direct hyperscaler relationship doesn’t solve on its own.”
Why it works: Concedes the true part of the objection (the hyperscaler is good at compute) and redirects to where the telco genuinely adds value, per Module 4’s hyperscaler response strategy — rather than arguing against a point that’s actually correct.
“Your price is higher than [competitor]”
When it comes up: A procurement-driven comparison, often against a connectivity-style flat quote from a competing telco, or a bare infrastructure quote from a hyperscaler.
Script:
“Can I ask what that quote includes? — [listen] — Ours is structured differently: [explain the consumption/outcome model from Module 2]. For a workload like yours, that usually lands lower in practice than the flat number, and it scales with you instead of locking in peak-capacity pricing you won’t always need.”
Why it works: Reframes a price comparison as a pricing-model comparison, which is usually an apples-to-oranges situation once surfaced — directly applying Module 2’s framework.
“We’ve always bought connectivity from you, this is different”
When it comes up: An existing connectivity-relationship stakeholder is uncertain whether the telco is credible for the platform layer.
Script:
“Fair — and that’s worth being direct about. Here’s specifically what we’ve built for this: [name one concrete technical proof point or case detail]. We’re not asking you to take it on faith; we’d suggest a limited proof-of-concept scoped narrowly enough to test exactly that.”
Why it works: Doesn’t oversell; offers a low-risk way to verify the claim, which sets up Module 10’s proof-of-concept design directly.
“We need to see other vendors before deciding”
When it comes up: A procurement-driven requirement for competitive comparison, sometimes genuine, sometimes a stalling tactic.
Script:
“Of course — what would make a comparison most useful for you? If it’s price, we can walk through how our model compares directly. If it’s technical risk, we’d rather show you than have you take a competitor’s claims at face value.”
Why it works: Doesn’t resist the comparison — shapes what gets compared, steering toward technical credibility rather than a pure price shootout.
“This needs executive approval we don’t have yet”
When it comes up: Often surfaces late, revealing a stakeholder-mapping gap from Module 8 — the real Economic Buyer was never engaged.
Script:
“Understood — would it help if we put together a short, outcome-framed summary specifically for that approval, rather than the full technical material? What does that person care most about on a decision like this?”
Why it works: Treats this as a signal to go back to Module 8’s stakeholder map, not just a scheduling obstacle — and offers to help close the Authority gap directly rather than waiting passively.
What comes next
Module 10 covers how to design a proof-of-concept that actually closes the deal it supports, rather than becoming a long, inconclusive technical exercise — directly following from the “prove it” objection above.
Which of these five objections comes up most in your own deals, and does your current response match the script above, or default to defending price?