Can my MSP provide good strategic advice?

Your MSP can provide tactical recommendations about the systems they manage, but strategic advisory requires independence from operational revenue. When the same company operates your IT and advises on strategy, they have a financial incentive to recommend solutions that expand their scope, not necessarily solutions that serve your best interest. Separate the roles for better outcomes.

Do I need all three roles at the same time?

Most mid-market businesses (25-500 employees) need an MSP and an advisor simultaneously, with consultants engaged on a project basis. The MSP handles daily operations; the advisor provides strategic direction and vendor oversight. Consultants are brought in for specific initiatives like migrations, implementations, or security assessments. You rarely need all three at full capacity at once.

How much does an IT advisor cost compared to an MSP?

An IT advisor (fractional CIO or vCISO) typically costs $5,000-$15,000 per month. An MSP typically costs $100-$250 per user per month. For a 100-person company, the MSP cost is roughly $10,000-$25,000/month while the advisor is $5,000-$15,000/month. The advisor investment typically pays for itself through cost optimization. CCK Advisors' 38% IT cost reduction far exceeded the advisory fee.

MSP vs IT Advisor vs IT Consultant Explained

What each role does

Each role serves a fundamentally different function in your IT ecosystem. Confusing them leads to misaligned expectations and wasted spend.

MSP (Managed Service Provider): Operates your day-to-day IT environment. Help desk, patching, monitoring, backups, user account management, endpoint security. The MSP keeps the lights on. Revenue model: per-user or per-device monthly fees.
IT Advisor (Fractional CIO/vCISO): Guides your technology strategy. Roadmap development, vendor evaluation, budget planning, compliance governance, security posture management. The advisor decides what to build. Revenue model: advisory retainer or project fees.
IT Consultant: Solves specific technical problems. Cloud migration, ERP implementation, network redesign, security assessment. The consultant executes a defined project. Revenue model: project-based or hourly fees.

Think of it this way: the advisor decides the destination, the consultant builds the road, and the MSP drives the bus every day.

Where they overlap and conflict

The boundaries between these roles blur in practice, and that ambiguity creates problems. The most common conflict: an MSP that also claims to provide strategic advisory.

MSP + Advisor conflict: When your MSP also advises on strategy, they have a financial incentive to recommend solutions they can manage, even if better alternatives exist. This is the most damaging overlap.
MSP + Consultant overlap: Some MSPs offer project-based work (migrations, implementations). This is generally acceptable if the project scope is clearly defined and separate from the ongoing MSP contract.
Advisor + Consultant overlap: An advisor may provide consulting on specific projects, particularly strategic ones like vendor selection or security architecture. This overlap is usually benign.
The danger zone: When one company fills all three roles, accountability disappears. Who evaluates whether the MSP is performing well? The MSP themselves.

CCK Advisors experienced this firsthand: their previous IT provider was both operator and advisor, which led to 38% in unnecessary costs that were only revealed through independent, vendor-neutral evaluation.

Why your IT advisor should not be your MSP

Separating advisory from operations is the single most impactful structural decision a business can make about IT governance. The reasons are straightforward.

Accountability: An independent advisor evaluates MSP performance without bias. When the advisor and MSP are the same company, no one is watching the watchman.
Vendor neutrality: An MSP has partnerships with specific vendors and earns margin on product sales. An independent advisor evaluates the full market.
Cost control: MSPs benefit from expanding scope and adding tools. An independent advisor benefits from optimizing spend and eliminating waste.
Chicago Jet Group example: When Chicago Jet Group's IT director left, an independent fractional CIO stabilized operations and achieved zero downtime during the transition because the advisor had no incentive to create dependency on a specific MSP.
Conflict disclosure: Ask your current IT provider: "Do you earn commissions on any products you recommend?" If yes, their advisory function is compromised.

The best configuration: an independent advisor who holds the MSP accountable, evaluates vendors neutrally, and manages the technology roadmap without operational conflicts.

How to structure the right team

Building the right IT leadership structure depends on your organization's size, complexity, and internal capabilities. Here are the most common configurations.

Under 25 employees: MSP only. At this size, a dedicated advisor is rarely cost-justified. Ensure the MSP provides basic security and compliance guidance as part of the contract.
25-100 employees: MSP + Fractional CIO or vCISO. The advisor provides strategic oversight, vendor evaluation, and compliance governance. The MSP handles operations.
100-500 employees: MSP + Advisor + occasional Consultant. The advisor manages the IT roadmap and holds the MSP accountable. Consultants are engaged for specific projects (cloud migration, ERP implementation).
500+ employees: Internal IT team + Advisor + MSP/MSSP. At this size, you likely have internal IT staff. The advisor provides executive-level strategy that the internal team executes, with MSP/MSSP support for specialized functions.

Regardless of size, the principle holds: the entity that advises on strategy should not be the same entity that profits from selling the solution.