ITSM and IT operations sales objections, questions and competitors

When they push back.

The objections ITSM and IT operations buyers raise most, what to say in the next ten seconds, and what not to promise.

"Your price is higher than we expected."

Higher compared to what: the current renewal, another quote, or the budget you set?

Do not discount before you know the anchor. Do not trade away scope you will need later.

"Migrating off our current platform would be a nightmare."

What worries you most about moving: the data, the integrations, or retraining people?

Do not say migration is easy. Do not commit to moving all historical data without scoping it.

"We built our own tooling for this."

What made you build it, and who keeps it running today?

Do not belittle what they built. Do not assume they want to throw it away.

"Now is not a good time."

Fair enough. What would need to change for this to move up the list?

Do not push a fake deadline. Do not keep calling without a reason tied to their calendar.

"Security will never approve a cloud tool with access to our systems."

What does security usually need to see before they approve something like this?

Do not claim certifications or controls you have not confirmed. Do not try to route around security.

"We already have ServiceNow, so why would we look at anything else?"

Makes sense. Is there a part of it your team works around today, or is it working well everywhere?

Do not claim you replace everything the incumbent does. Do not trash a platform the buyer chose.

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.

ServiceNow

ServiceNow is the platform a lot of large enterprises standardize on. Are you using it across many teams, or mostly for the IT service desk?

Jira Service Management

Jira Service Management is popular when engineering already lives in Jira. How much of your IT work needs to connect to developer workflows?

BMC Helix

BMC has a long history in enterprise IT operations. Is your team on Helix in the cloud, or still on Remedy on-prem?

Ivanti

Ivanti covers service management alongside endpoint and security tools. Is the appeal one vendor for both, or the service desk itself?

Freshservice

Freshservice is often picked for how fast teams get going. How complex are the processes you need to run?

ManageEngine

ManageEngine offers a wide set of IT tools at a practical cost. Is breadth across tools what matters most to you?

SolarWinds

Many IT teams know SolarWinds from monitoring. Are you looking at it for observability, the service desk, or both?

TOPdesk

TOPdesk is well liked in Europe, especially in education and public sector. How much do you value simplicity over deep customization?

PagerDuty

PagerDuty is the name many engineers think of for on-call. Is your pain in getting the right person paged, or in what happens after?

Splunk

Splunk is strong at searching machine data at scale. Is your need log and event analysis, or service workflows?

Questions that qualify the deal.

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

Qualify

Take a ticket from this week. Where did it come in, who touched it, and how long until the person who filed it was back to work?
If you could take one thing off your team's plate tomorrow, what would it be?
Think about your last major incident. Who noticed first, and what did the business lose while it was open?
What happens on the date you are working toward, and what happens if you miss it?
Besides you, who has to say yes, and who could say no?
Is this coming from an existing line, like the current tool's renewal, or would it need new money?

Dig into the pain

"Our CMDB is a mess and nobody trusts it." When the CMDB is wrong, what breaks first: change approvals, incident routing, or audits?
"We are drowning in alerts." Of the alerts your team got last week, how many actually needed a human?
"Changes keep causing outages." For the last outage caused by a change, did the change go through your approval process or around it?
"Our agents spend all day on password resets and access requests." What share of your ticket queue could be handled without a person, if the employee could just do it themselves?
"It costs too much to run the tool we have." When you say it costs too much, is it the license, the admins it takes to keep it running, or the consultants for every change?

Know who is in the room.

IT service management (ITSM) is how an IT team takes in requests, fixes what breaks, and changes systems without causing new outages. The software covers the service desk, incident, problem, change, request and asset management, usually built around ITIL practices. IT operations tools sit next to it: monitoring, alerting, on-call, event correlation (often called AIOps) and runbook automation.

Who buys and who signs

Economic buyer: The CIO or VP of IT Operations. In larger companies, a head of enterprise service management may own the budget across IT, HR and facilities.
Champion: The service desk manager, ITSM process owner, or an SRE or platform lead who is tired of noisy alerts and manual tickets.
Users: Service desk agents, resolver groups, change managers, asset managers, on-call engineers and every employee who files a ticket.
Blockers: Security (access to production data, SSO, audit logs), procurement, enterprise architecture (the "one platform" rule), and the admins who built the current tool and its customizations.

Signs the deal isn't real

No renewal date, outage or audit driving the project; "just looking at options"
The champion cannot name who owns the current platform or its budget
Requirements copied from an analyst template with no real workflows behind them
The incumbent admin team is not in the room and has not been asked
They want a full feature comparison but will not share ticket volumes or pain examples
Enterprise architecture has a standing "single platform" mandate and no one has challenged it

15 words ITSM and IT operations buyers use

ITIL: The common framework of IT service practices
Incident: An unplanned interruption or degradation of a service
Problem: The underlying cause behind one or more incidents
Change / RFC: A request to modify a system, often reviewed by a CAB
CAB: Change advisory board that approves risky changes
CMDB: Configuration management database, the map of systems and their dependencies
CI: Configuration item, one record in the CMDB
SLA / OLA: Agreed service targets with the business or between internal teams
MTTR: Mean time to resolve or restore
Major incident: A high-impact outage with its own response process
Service catalog: The menu of requests employees can make
Shift left: Moving resolution toward self-service or the first line
AIOps: Using event correlation and machine learning to cut alert noise
Runbook: Documented or automated steps to handle a known issue
ESM: Enterprise service management, ITSM practices applied to HR, facilities and others

Selling ITSM and IT operations: questions

What objections come up when selling ITSM and IT operations?

The most common are: "Your price is higher than we expected", "Migrating off our current platform would be a nightmare", "We built our own tooling for this", "Now is not a good time", "Security will never approve a cloud tool with access to our systems" and "We already have ServiceNow, so why would we look at anything else?". Each one above has a line to say back and what to avoid.

What discovery questions should I ask a ITSM and IT operations buyer?

Start with: Take a ticket from this week. Where did it come in, who touched it, and how long until the person who filed it was back to work? If you could take one thing off your team's plate tomorrow, what would it be? Think about your last major incident. Who noticed first, and what did the business lose while it was open? What happens on the date you are working toward, and what happens if you miss it?

Who are the main competitors in ITSM and IT operations?

Buyers most often compare ServiceNow, Jira Service Management, BMC Helix, Ivanti, Freshservice, ManageEngine, SolarWinds, TOPdesk, PagerDuty and Splunk.

Who buys ITSM and IT operations?

Economic buyer: the CIO or VP of IT Operations. In larger companies, a head of enterprise service management may own the budget across IT, HR and facilities.

How does Ghost help on ITSM and IT operations calls?

Pick the ITSM and IT operations 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 Cloud infrastructure Data and databases DevOps and developer tools Observability ERP Collaboration HCM and payroll Analytics and BI Supply chain Marketing automation Contact center and CX Finance and spend Ecommerce PLM and CAD Healthcare EHR Payments and POS Applicant tracking

ITSM and IT operations: what buyers say on the call, and what to say back.