Cloud infrastructure sales objections, questions and competitors

When they push back.

The objections cloud infrastructure buyers raise most, what to say in the next ten seconds, and what not to promise.

"That costs more than we expected."

Compared to what: your current spend, another quote, or the cost of building it yourselves?

Do not discount before you understand the comparison. Do not run down the provider's native tools.

"Migrating would be too much work."

What worries you most: the workloads, the data, downtime, or retraining the team?

Do not say migration is simple. Do not promise zero downtime.

"We built our own platform."

That's a big investment. How much of your team's time goes to maintaining it versus building new things?

Do not imply their platform is poor. The people who built it are in the room.

"This isn't a priority this quarter."

Got it. What is the team focused on now, and when does that wrap up?

Do not invent urgency.

"Security needs to review anything with access to our cloud accounts."

Makes sense. What access model does security prefer, and can we start their review now?

Do not answer security questions from memory. Do not ask for broader permissions than needed.

"AWS (or Azure, or Google Cloud) already has a native service for this."

It might. Have you tried the native option, and what did your team think?

Do not attack the cloud provider. They are usually a partner in the deal too.

Every one of these is a deal that slips a quarter if you fumble it. Ghost puts the answer on your screen while the buyer is still talking.

Download for Windows Download for Mac

When they name a competitor.

Give them credit, then ask whether that vendor's strength matters to this buyer.

Oracle Cloud Infrastructure

OCI is a strong choice for Oracle database workloads. How much of your stack runs on Oracle today?

IBM Cloud

IBM Cloud is often chosen for regulated and hybrid workloads. How important are mainframe ties or industry controls for you?

Alibaba Cloud

Alibaba Cloud is a leader in China and parts of Asia. How much of your growth plan depends on those regions?

DigitalOcean

DigitalOcean is known for simplicity and developer friendliness. How complex do you expect your infrastructure to get?

Akamai Cloud

Akamai combines a large edge network with Linode compute. How much does running close to users matter for you?

Cloudflare

Cloudflare is known for its global edge network. Which parts of your app could run at the edge instead of in a region?

Questions that qualify the deal.

Ask these on the first call. Then dig into the pain when they say it out loud.

Qualify

Where do your workloads run today, which clouds or data centers, and how do teams get new environments?
Do you know which teams and services drive the bill, and what's changed most recently?
What did the last outage or slow release cost you, with customers or with your roadmap?
Is something driving the timeline, like a data center exit, a commitment renewal, an audit, or a launch?
Besides your team, who needs to agree, like security, finance, app teams or your cloud provider's account team?
Would this come from new budget, your existing cloud commitment, or savings somewhere else?

Dig into the pain

"Every team builds infrastructure differently." If I asked three teams how they create a new environment, would I get three answers?
"The platform team is a bottleneck." How long does a developer wait today for a new environment or an infrastructure change?
"Keeping everything patched and up to date is a constant fight." How do you track what's out of date today, and who does the upgrades?
"Security and compliance slow everything down." Where do security reviews add the most wait time, and what do auditors keep asking for?

Know who is in the room.

Cloud infrastructure and platforms are the services companies run their software on. IaaS covers compute, storage and networking rented on demand. PaaS adds managed databases, containers, serverless functions and app runtimes, so teams spend less time running servers. Buyers also purchase the tools around them for provisioning, cost management, security and operations.

Who buys and who signs

Economic buyer: The CTO or CIO, often with the CFO on large or multi-year commitments.
Champion: A head of platform engineering, cloud architect, or infrastructure director who owns reliability and the roadmap.
Users: Platform and DevOps engineers, SREs, application developers, data engineers, and FinOps analysts.
Blockers: Security and compliance (identity, network isolation, data residency, regulated workloads), finance and procurement (spend commitments, cost overruns), legal (data processing terms), and application teams who do not want to change how they deploy.

Signs the deal isn't real

No named owner for the migration or platform.
The cloud provider's own team is designing the solution and you have not met them.
A committed-spend agreement was just signed and fully allocated.
They cannot describe which workloads move or why.
Finance is not aware of the project.
"We're going multi-cloud" with no workload or reason attached.
The evaluation is a cost comparison to use in renewal talks.
Security has not been told about the project.

27 words cloud infrastructure buyers use

IaaS / PaaS: Renting raw infrastructure versus managed platforms.
Hyperscaler: One of the largest public cloud providers.
Landing zone: A pre-built, secure baseline of accounts, networking and guardrails.
Infrastructure as code (IaC): Defining infrastructure in version-controlled files.
Kubernetes / K8s: The common container orchestration system.
Serverless: Running code without managing servers.
Committed spend / EDP / MACC: Multi-year spend agreements with a cloud provider.
Reserved instances / savings plans: Discounts for committing to usage.
FinOps: The practice of managing and allocating cloud cost.
Egress: Data leaving a cloud, often a cost concern.
Multi-cloud / hybrid cloud: Using more than one provider, or mixing cloud and on-premises.
Lift and shift: Moving workloads without redesigning them.
Platform engineering: An internal team that builds paved paths for developers.
Drift: When live infrastructure no longer matches its code.
Shared responsibility model: What the provider secures versus what the customer secures.
How do you handle Terraform state?: Terraform keeps a file that records what it built. That file is the state.
What about state locking?: A lock that stops two people changing the same infrastructure at the same time.
How do you deal with drift?: Drift means the live cloud no longer matches what the code says.
Which remote backends do you support?: The place the state file is stored, like an S3 bucket, instead of a laptop.
How do you handle a multi-account setup?: Running many separate cloud accounts, for example one per team or environment, instead of one big one.
Do you build landing zones?: The starting setup of a cloud: accounts, network, access and security rules, ready for teams to use.
Do you support OIDC?: A standard way to prove who someone (or a pipeline) is, without sharing passwords or long-lived keys.
How do you handle least privilege?: Give each person or tool only the access it needs, nothing more.
Do you support SCIM?: Automatic adding and removing of user accounts from the company directory, like Okta or Entra ID.
What is the blast radius if something goes wrong?: How much breaks if one thing fails or one mistake is made.
Do you support golden paths?: A ready-made, approved way for developers to build and ship, so they do not start from scratch.
Can we enforce policy as code?: Rules written as code that run automatically to block changes that break them.

Selling cloud infrastructure: questions

What objections come up when selling cloud infrastructure and platforms?

The most common are: "That costs more than we expected", "Migrating would be too much work", "We built our own platform", "This isn't a priority this quarter", "Security needs to review anything with access to our cloud accounts" and "AWS (or Azure, or Google Cloud) already has a native service for this". Each one above has a line to say back and what to avoid.

What discovery questions should I ask a cloud infrastructure buyer?

Start with: Where do your workloads run today, which clouds or data centers, and how do teams get new environments? Do you know which teams and services drive the bill, and what's changed most recently? What did the last outage or slow release cost you, with customers or with your roadmap? Is something driving the timeline, like a data center exit, a commitment renewal, an audit, or a launch?

Who are the main competitors in cloud infrastructure and platforms?

Buyers most often compare Oracle Cloud Infrastructure, IBM Cloud, Alibaba Cloud, DigitalOcean, Akamai Cloud and Cloudflare.

Who buys cloud infrastructure and platforms?

Economic buyer: the CTO or CIO, often with the CFO on large or multi-year commitments.

How does Ghost help on cloud infrastructure calls?

Pick the cloud infrastructure market pack in Ghost's setup and every card on this page loads into Ghost. When a buyer raises one of these objections or names one of these competitors on a live call, Ghost shows you what to say on your screen, hidden from screen shares and recordings.

Other markets

CRM Cybersecurity Data and databases DevOps and developer tools Observability ERP Collaboration HCM and payroll Analytics and BI ITSM and IT operations Supply chain Marketing automation Contact center and CX Finance and spend Ecommerce PLM and CAD Healthcare EHR Payments and POS Applicant tracking

Cloud infrastructure and platforms: what buyers say on the call, and what to say back.