Pavone
SIGN IN

Discovery Call Questions for IT Services Sales

IT services buyers, whether a managed service provider, a consultancy or a systems integrator, are technical people who run a people business. These discovery questions cover both halves, from ticket volume and SLAs to utilization and margin, so you can uncover a real problem and a real decision path without the buyer feeling interrogated.

Want one built around your product? Use the Discovery Call Question Generator.

What IT Services buyers care about

The buyer is usually the owner or managing director of an MSP, a service delivery manager, a head of professional services at a consultancy, or a practice lead at a systems integrator. Their world is contracts and capacity: recurring managed services agreements with service level commitments, project work delivered by engineers whose hours are the product, and a help desk that has to answer the phone. They are vendor-dependent themselves, reselling and supporting other companies' products, which shapes how they evaluate yours.

They are judged on monthly recurring revenue, gross margin on managed services, engineer utilization, ticket volume per endpoint or per client, SLA attainment, client churn and the ratio of reactive to proactive work. Project-based firms watch project margin and estimate accuracy. The owner also watches revenue per engineer and, if they plan to sell, the quality of recurring revenue. Hiring and keeping engineers is the constraint that limits everything.

They are wary of vendors who do not understand the MSP tool stack, RMM, PSA, documentation, security tooling, and of anything that adds to an already crowded console. They evaluate technically and will test you on integration specifics. They respect reps who ask about ticket trends, SLA misses and engineer burnout, and who know that a tool the technicians refuse to use is worthless regardless of what the owner thinks.

Situation questions

A managed services provider with recurring contracts, a project-based consultancy and a systems integrator reselling hardware have different economics and different tooling. Establish the revenue mix, client count, engineer headcount and the PSA and RMM stack before asking about problems.

  1. How does revenue split today between managed services, projects and product resale, and which part is growing?
  2. How many clients and roughly how many endpoints or users are under management, and how concentrated is revenue?
  3. How many engineers and technicians are on the team, and how are they split between help desk, projects and account management?
  4. What is the core stack: PSA, RMM, documentation, security, backup, and which pieces are up for renewal or review?
  5. What is driving this conversation: margin, a client loss, growth, an engineer retention problem or a vendor change?

Pain questions

MSP pain shows up in ticket queues, missed SLAs, engineers working nights on projects and clients that churn after a bad quarter. Ask about the queue, the worst client and the last engineer who left; the service delivery manager can describe each in detail.

  1. What does the ticket queue look like right now, and which clients or issue types generate the most volume?
  2. Where do you miss SLA most often, and what does the client see when it happens?
  3. How much of the engineering time goes to reactive work versus proactive or project work, and what is the target?
  4. When a client churns, how much notice do you usually get, and what was the real reason the last time it happened?
  5. Which engineers are closest to burning out, and what is driving that?

Impact questions

MSP owners know their margin per contract and their cost per engineer, so the arithmetic is quick. Tie the pain to MRR retained, margin per client and engineer capacity, and let the buyer put their own figures on it rather than quoting yours.

  1. What is an average managed services client worth in annual recurring revenue, and how many have you lost in the last year?
  2. If ticket volume per endpoint came down by a fifth, how many engineer hours does that free up per month?
  3. What does it cost you to replace an engineer who leaves, including recruiting, ramp and the clients who notice?
  4. How much project work is delivered over estimate, and what is that costing in margin over a year?
  5. If SLA attainment and margin stay where they are, what happens to the plan for the business, whether that is growth, acquisition or sale?

Decision process questions

The owner decides, but the service delivery manager and the senior engineers decide whether it is adopted, and the PSA integration is a hard gate. Some MSPs belong to peer groups or vendor programs that influence choices. Map the people and the technical gates now.

  1. Who makes this decision, and who on the technical side would need to validate the integration with your PSA and RMM?
  2. What happened the last time you added a tool to the stack, and how long did it take from evaluation to full use?
  3. Are you part of a peer group, franchise or vendor program that influences which tools you adopt?
  4. Is this funded from the tooling budget, passed through to clients, or does it need to replace something you already pay for?
  5. What would your senior engineers say if you told them about this tomorrow, and would that decide it?

Next step questions

IT services buyers want to see it work in their environment. Propose a technical validation with the service delivery lead or a senior engineer, scoped tightly, with a date that avoids their project crunches and client onboarding waves.

  1. Would it make sense to run the next session with your service delivery manager or a senior engineer so we validate the integration early?
  2. If we piloted with one client or one engineer pod for a month, what ticket, SLA or utilization change would justify rolling it wider?
  3. Who else needs to be convinced before this becomes a decision, and can we get them on a call in the next two weeks?
  4. What is the realistic timeline given your renewal calendar and any big onboardings or projects in flight?
  5. Is there anything about your stack or your team that makes you think this would not survive the first month?

Red flags on a IT Services discovery call

  • The MSP is being acquired or is rolling up into a larger provider, and all tooling decisions will be made by the acquirer.
  • The contact is a technician who likes the product but has no budget and no path to the owner.
  • They are mid-migration between PSA or RMM platforms, which absorbs the whole team for a year.
  • They cannot tell you ticket volume, SLA attainment or utilization, which means nobody is managing the operation to those numbers.
  • They are evaluating you only because a vendor program or peer group recommended it, and nobody internally owns the problem.

Tips for running the call

  • Know the stack vocabulary: PSA, RMM, endpoints, SLA, MRR, reactive versus proactive, tickets per endpoint. Technical buyers will test you.
  • Establish the revenue mix first. Managed services, projects and resale have different margins and different pain.
  • Ask about the ticket queue and SLA misses directly. Service delivery managers live in those numbers and will open up.
  • Validate technically early. Involve a senior engineer in the second meeting; if the integration does not work, nothing else matters.
  • Frame impact as MRR retained, margin per client and engineer hours freed, in their numbers.
  • Watch the calendar. Big client onboardings, migrations and quarter-end projects consume every spare hour, so time the next step around them.

Frequently asked questions

What questions should I ask an MSP on a discovery call?

Ask how revenue splits between managed services, projects and resale, how many endpoints are under management, which PSA and RMM they run, what the ticket queue and SLA attainment look like and how many clients they lost last year. Then ask what a client is worth in ARR and who would validate the integration.

How do I sell to IT service providers?

Lead with operational outcomes, tickets, SLAs, utilization, margin, not with features. Involve a senior engineer early for technical validation, because adoption and integration decide the deal. Expect skepticism; these buyers are vendors themselves and know every trick.

What metrics do MSPs care about?

Monthly recurring revenue, gross margin on managed services, engineer utilization, tickets per endpoint, SLA attainment, client churn and the reactive-to-proactive ratio. Project-based firms add project margin and estimate accuracy. Owners also watch revenue per engineer and the quality of recurring revenue.

How long is the sales cycle when selling to MSPs?

A few weeks to a quarter if the owner is the buyer and the integration is proven. Longer if a pilot is needed or the tool competes with an incumbent renewal. PSA or RMM migrations, acquisitions and large onboardings can stall everything, so ask about them on the first call.

What is the biggest mistake reps make selling into IT services?

Underestimating the technical evaluation and overestimating the owner's ability to force adoption. Engineers will reject a tool that adds clicks or breaks the PSA workflow, regardless of what the owner signed. Validate with a senior engineer before you forecast the deal.

More discovery call questions by industry

Start practicing in minutes

AI Roleplays for any scenario

  • Build a roleplay from your scenario
  • Practice with AI, voice to voice
  • Get instant, structured feedback after practice
  • Free to start — no credit card required