8 Questions to Ask Before You Sign With an MSP

Reports to: 
02
Location: 

8 Questions to Ask Before You Sign With an MSP

on this page

The earliest signals that you've outgrown your current IT setup don’t always land as “we need an IT solution”. New hires stumble through onboarding, leadership spends time on IT decisions instead of running the business, engineering jumps in to answer a security questionaire… moments such as these often get written off as generic growing pains. But they are avoidable with a strong IT and security partner; it’s just important to find the right partner for your business

What separates good from great? A good IT service provider answers tickets; A great provider makes them disappear. Ask the right questions during the evaluation stage, before a contract is signed, so you set yourself up with the best partner for your business – not just where you are today, but what you want to grow into in the next five years.

Eight interview questions for your potential IT service provider

  1. What percentage of a typical client's work runs on automation, and can they show it live?
  2. Who owns the long-term roadmap, and are they the same people doing the work?
  3. What's covered under one roof, and what still needs outside vendors?
  4. What does onboarding require in the first 30 days?
  5. Who ends up owning the logins and admin access to your accounts?
  6. Can they show a live demo of the cost and security dashboard you'd get as a client?
  7. How do they help you evaluate a spend request before you approve it?
  8. Can you talk to a current customer and meet the team that would work on your account?

The questions, with a double-click

What percentage of a typical client's work runs on automation?

A provider whose work still runs mostly on people is renting you their headcount. As your company grows, that appears as slower response times and rising prices. Ask the provider to walk you through their automations live, in a demo, rather than describing it in the abstract.

Automation is what lets a provider's cost structure scale sublinearly with your headcount. When something breaks at a traditional provider, they add a person. When volume grows, they add a person. This is a staffing agency model with an SLA, and that's still billable work, fixed or not.

Who owns the long-term roadmap?

The most expensive failure mode is an IT partner with no seat at the table when strategic decisions get made. You find out what that costs six months later, cleaning up a decision nobody with operational context was in the room for. Most providers force a choice between a consultant who hands over a plan and walks away, and an MSP that executes without one. A fully staffed internal team solves that split, but typically only enterprises can afford the security, compliance, and AI expertise today's environment requires. That's where an embedded provider earns its keep: one team, accountable for both the strategy and the execution behind it.

What's covered vs. not?

Day-to-day IT alone doesn't cover security, compliance, or AI advisory. Left uncovered, those responsibilities fall to vendors you have to manage yourself, which quietly turns "we outsourced IT" into "we're now coordinating across four vendors." Ask what's included end-to-end and what gaps you're still responsible for filling.

A useful way to test this: ask the provider to name their service lines instead of describing capabilities in general terms. A provider with distinct, named offerings across IT, security, compliance, and AI advisory is built for full coverage. A provider who can only answer "we can help with that" or "that's part of the retainer" probably hasn't.

What does onboarding require in the first 30 days? 

Onboarding should start with a full audit of your environment: how your people log in, what devices they use, the apps that crept in without IT's blessing, your compliance obligations, and who uses your systems most. A provider that tries to understand your environment by headcount alone is running on a cookie-cutter model that overlooks what your business truly needs.

The apps that crept in without IT's blessing deserve particular attention. This is called shadow IT: tools a team adopted on a credit card because procurement was slow, or a spreadsheet-based process that became load-bearing without anyone deciding it should be. This isn't a fringe problem. Gartner found that 41% of the technology employees bring into a company happened outside IT's visibility in 2022, and projects that number will reach 75% by 2027.

"At an early-stage startup I joined, I audited the environment and found 400+ active SaaS applications for fewer than 300 employees. Most were unowned, many redundant, and none were centrally managed."

A provider who asks these proactive questions about your environment in the first week is planning around your actual environment. A provider who doesn't is planning around an unrealistic,simplified version of it (which carries its own associated risks).

Who ends up owning your accounts?

A great provider builds everything inside your environment, under your accounts, so you can walk away cleanly if the relationship ends. Some providers deliberately structure account ownership so switching costs are high. Find out which one you're getting before you sign.

Ask directly who holds admin rights to your identity provider, your device management, and your core business systems. The answer should be: you do, with the provider operating inside that structure rather than owning it.

Can they show you the dashboard live?

Ask to see the cost and security dashboard live, in a demo environment, not as a screenshot from a sales deck. If a provider can show you the dashboard on the spot, they're running on live tooling that proactively flags issues before you even have to file a ticket. A spreadsheet, or "we'll send that over," means cost and risk are hard to track for the provider, which affects your own visibility.

"I've watched a CFO nearly cut the most-adopted tool in the company because nobody had ever shown her usage data. Visibility is the difference between decisions made with data and decisions made in the dark."

Once you're a client, you own that visibility. You shouldn't be the last to know.

How do they help you evaluate a spend request?

A good partner shows you what’s driving a spend request before asking you to approve it in a way that ties to your business priorities. You are responsible for resource allocation; you should be presented with information that serves those strategic decisions.

If IT isn't your background, a $100,000 infrastructure request is hard to evaluate on its merits. The gap between technical spend and non-technical leadership is exactly where budgets tend to grow past what's needed because nobody in the room is positioned to push back with technical grounding of their own. 

Internal technology teams get expensive fast, in ways that aren't always visible until well after the hiring decisions are made (more on that comparison in in-house vs. outsourced IT). A single hire to reduce a point of failure tends to become two, and then a small team, well before the original problem is fully solved.

Can you talk to a current customer?

Claiming stellar service costs a provider nothing. Verify what potential providers say: look at how the sales process itself is run, meet the team and systems behind the account, and ask what current customers say about the provider without a rep sitting in on the call.

Legacy IT provider vs. consultants vs. strategic partners

These three types of relationships are optimized for different results.

As you’re interviewing potential providers, you’ll run into three different types of relationships, optimized for different outcomes.

Legacy IT provider Consultant Strategic partner
Automation Minimal; runs mostly on people Not applicable, advisory only Core to the business model, freeing up a fractional executive to own your IT roadmap and strategy
Roadmap None; reacts to ticket queue Hands you a plan, then leaves Same team plans and executes, no handoff
Coverage Varies; may need multiple vendors Strategy only Built for where you are today and where you're headed in five years
When something breaks Reactive; you file a ticket, then wait for a fix Out of scope once plan is delivered Monitors proactively; you hear it from them first, and sometimes it's fixed before you feel it
When to work with this provider type You want to handle IT issues ad hoc, as they arise You have a fully staffed internal team and only need an outside perspective on the strategic roadmap You want a consistent partner who knows your business to build your roadmap and manage the execution, by either augmenting your internal team or letting them take full ownership of it

You’re now equipped to make the best decision for your business when selecting an IT service provider. If you’d like to test these questions, feel free to practice with us. Schedule time and ask every one of them.

Frequently asked questions: Additional context before you interview an MSP 

What is an MSP?

A managed service provider (MSP) is a company that runs some or all of an organization's day-to-day IT, security, and related infrastructure under an ongoing contract, instead of relying solely on internal staff or an augmented or co-managed setup. Scope varies widely between providers. See what outsourced IT support covers for a full breakdown of the models.

How much of my leadership team's time should IT be taking up?

There's no universal number, but the direction matters: if IT is consistently pulling your leadership's attention away from decisions that grow the business, that's a signal worth acting on rather than absorbing as normal overhead. Even 1% of your leadership’s time on IT is extremely costly when you think of how else that time could be spent.

What's the difference between a legacy MSP and a strategic partner?

A legacy MSP profits when problems keep happening; a strategic partner is there to prevent them in the first place, which is what lets your business grow efficiently while keeping the expertise in house.