What Does Your Service Desk Need to Look Like for the Business You’re Becoming?

Every few years, a leadership team sits down to debate whether their service desk function should be run in-house or handed to a managed service provider. After a few weeks of debating spreadsheets, they’ll make a decision, once again overlooking an even more fundamental question: What does the service desk need to do?

Build for the business you want, not the bnusiness you have 

What does the future of your business look like? What kind of service desk will that business need? These questions should anchor every service desk strategy discussion. Focusing on the future forces the conversation off the org chart and onto strategy. It also surfaces questions that the in-house vs. MSP frame never reaches:

• Are we growing headcount? At what pace and in which geographies?
• Are we acquiring companies? Integrating teams with different tech stacks?
• Are we shifting to a hybrid or fully distributed workforce model?
• Are we operating across time zones in a way that demands 24/7 support?
• What is our tolerance for variability in service quality during leadership transitions, hiring freezes, or budget contractions?
• And, critically: how much of our ticket volume do we expect AI to deflect in the next two to three years, and who is positioned to actually deliver on that?

None of those questions appear naturally in a build-vs-buy debate. But all of them should determine the answer.

Why the wrong question feels like the right one

The in-house vs. MSP debate persists because it feels concrete. You can put FTE costs in a spreadsheet. You can model a contract. You can benchmark a rate.

What you cannot easily put in a spreadsheet is organizational readiness. The capacity to hire and retain specialized talent in a competitive market. The true cost of a service desk manager who leaves six months after you promoted them. The speed at which your current team can absorb a new collaboration platform, a new security framework, or an entire workforce after an acquisition.

Those are real costs. But because they don't show up cleanly in a cost model, they often get ignored.

There is also a political dimension. Sometimes the in-house vs. MSP debate is really about whether the current IT leadership team is adequate. A vote for managed services can seem like a vote of low confidence in the people who built and run the current function. 

A better question short-circuits both problems. When you ask "what does our service desk need to look like for the business we're becoming?" the conversation becomes future-oriented and strategic. It stops being about judging what exists and starts being about designing what should exist.

What the reframe unlocks

Organizations that ask the right question first tend to arrive at better answers, regardless of where they land on the in-house vs. MSP spectrum.

Some find that a hybrid model makes the most sense: an internal function focused on strategic IT leadership, architecture, and business relationship management, paired with a managed service partner handling the operational service desk. That split is not a compromise. For many organizations, it is genuinely the right answer.

Others find that full managed services is the right move because it provides the flexibility, geographic coverage, and AI-enabled tooling that their internal team cannot realistically build or sustain.

Others still find that bringing more capability in-house is the right answer, particularly if a service desk is a genuine strategic differentiator for their business, or if the workforce model requires a uniquely high-touch, culturally embedded support function.

A framework for the conversation

If you are in the middle of this evaluation, here are the questions worth putting on the table before you debate delivery models:

1. Growth trajectory: Where will we be in 18 months? Three years? Does our current support model scale to that, without heroic effort?
2. Geographic footprint: Are we operating or planning to operate across time zones, countries, or regulatory environments that require specialized coverage?
3. Workforce model: Has the pandemic permanently changed how our workforce operates? Does our support model reflect that, or is it still built for a pre-2020 office-centric world?
4. AI and deflection: What percentage of our current ticket volume is candidates for AI-assisted deflection? Who is building and operating those capabilities, and what does our roadmap look like?
5. Talent risk: Where are we most exposed if key people leave? What would it cost us in time, quality, and business disruption if that happened tomorrow?
6. Strategic role of IT: Is a service desk a commodity function or a competitive asset for us? The answer shapes everything about how it should be staffed and managed.

The takeaway

In-house or MSP is still a worthwhile question, but it shouldn’t be your first question. Priority one is getting clear about the business you’re building and the role you need your service desk to play. Answer that honestly, and the delivery model question becomes much easier because you have actual criteria to evaluate against.

Astreya is a global IT managed services provider specializing in end-user computing, service desk, and IT operations for high-tech, financial services and consumer-tech companies. We help organizations design service desk models that evolve with the business they are becoming.
Have thoughts on this? Or a problem that looks something like it?

[Get in touch →]