Why most MSPs sell you the wrong thing

There are roughly 40,000 to 50,000 managed service providers operating in the United States (Source: ChannelE2E / MSP Resources industry estimates, 2024). Most of them are honest. Most of them want their clients to do well. The problem is not character; it is structure.

The structure is this: a typical MSP earns the majority of its margin not from the labor it sells you, but from the products it resells to you and the vendor incentives it earns when you say yes. The recommendation you get from your MSP is not a recommendation about what is best for your environment. It is the intersection of what is plausible for your environment and what pays the MSP best. Sometimes those overlap. Often they do not.

This piece is not an attack on the MSP industry. It is a buyer’s guide to its economics, written for the CEO or CFO who has been getting “vendor-neutral” pitches that do not feel vendor-neutral. By the end you should be able to read any MSP proposal and see where the money is moving, why specific products keep showing up in specific recommendations, and what an IT provider whose incentives actually align with yours would look like.

We are one of those providers. We will get to that at the end. But first the structure, because once you can see it you do not need us to tell you.

When all three forces overlap, you get an honest recommendation. When they diverge, you get the proposal — assembled from whatever sits in the intersection of MSP profits and vendor incentives, even if 'what you need' lives somewhere else entirely.

How MSP economics actually work

When an MSP quotes you a managed-service contract, the visible price is for labor: monitoring, support, patching, the helpdesk. That number is the part you negotiate over. It is also, for most MSPs, not the part that determines whether they make money on you.

The hidden economics live in four places.

1. Hardware and software resale margins

MSPs typically mark up hardware they resell to clients in the range of 20 to 28 percent (Source: Wireguided LLC industry analysis, 2023). On a $40,000 server-and-network refresh that is $8,000 to $11,200 of pure margin, none of which appears as a line item on your invoice — it is baked into the unit price.

Software is similar. Microsoft 365 licenses sold through the Cloud Solution Provider (CSP) program carry partner margins typically in the range of 12 to 18 percent, with higher margins available on bundled or value-added offerings (Source: Cloudmore, Microsoft CSP Margin Benchmarks; Microsoft Partner Center documentation). When your MSP sells you 30 seats of Microsoft 365 Business Premium at $22 per seat per month, somewhere between $2.64 and $3.96 of that monthly seat price is the MSP’s margin on the license itself — separate from any management fee they charge on top.

Across an SMB book of business those numbers compound. A 50-employee customer running a typical stack — Microsoft 365 Business Premium, an EDR product, a backup product, a couple of point-solution SaaS tools — represents roughly $35,000 to $55,000 a year in licensed software pass-through. At a 15 percent blended margin, that is $5,250 to $8,250 per year of pure license-resale profit per customer, with zero incremental labor. Multiply by a hundred customers and the resale book is paying the rent.

2. Vendor incentive programs (rebates and tier bonuses)

On top of resale margin, vendors pay MSPs back-end rebates based on volume. Hit a sales threshold for a particular vendor across the partner’s book of business and the partner gets a percentage rebate, typically 1 to 8 percent of total volume, paid quarterly or annually (Source: Cisco Provider MDF documentation; HP Partner First and Dell PartnerDirect program structures).

The mechanics matter. A rebate triggered at, say, $500,000 of vendor volume becomes a strong incentive to push that vendor’s products to the next ten customers regardless of whether those products are the best fit, because the rebate effectively re-prices everything sold beneath it. Volume thresholds also create end-of-quarter pressure — the same dynamic that produces the “we have to close this by Friday” pitches in software sales, applied to the MSP’s recommendation engine.

3. Market Development Funds (MDF) and co-op funds

Vendors fund the marketing of partners who sell their products. Cisco’s Provider MDF, HP’s Partner First MDF, Dell’s PartnerDirect MDF, and Microsoft’s various co-op programs collectively put hundreds of millions of dollars per year into the channel (Source: vendor partner-program documentation; TechTarget, MDF funds: How MSPs can get their cut). One published case study described a single MSP accessing $255,000 in Cisco MDF (Source: Vendasta case study).

MDF dollars pay for the events, webinars, content marketing, sales-development reps, and sometimes the trips and dinners that the MSP uses to acquire and retain customers. Those dollars are not free. They are conditional on selling the funder’s products. An MSP whose marketing function is funded by Vendor X has, on the marketing side, become an extension of Vendor X’s sales channel.

This is not nefarious. It is how the channel has worked for thirty years. It is also why, when you ask an MDF-funded MSP “should we use Product X or Product Y,” you are asking a question whose answer has already been pre-paid.

4. Spiff and SPIF programs

The fourth lever is short-term sales incentives — Sales Performance Incentive Funds, paid directly to individual MSP salespeople for closing specific products in specific windows. A vendor running a quarterly SPIF might pay the MSP’s account executive $200 to $1,500 per closed seat or per closed deal, on top of the MSP’s own commission, for selling that vendor’s product instead of a competitor’s.

The customer almost never sees the SPIF disclosed. The customer sees an account executive who is unusually enthusiastic about a specific product this quarter.

Putting the four together

Sum the four levers and a typical MSP earns:

• 20–28% margin on resold hardware
• 10–18% margin on resold licenses (software, SaaS, security tooling)
• 1–8% back-end rebates on vendor volume
• A meaningful share of marketing and sales operations subsidized by MDF
• Short-term SPIFs flowing directly to the salesperson on specific products

The labor bill you negotiate over is the visible 30 to 40 percent of the relationship’s economics. The hidden 60 to 70 percent is structured to prefer specific vendors. Which vendors? The ones with the most generous partner programs. Which is to say: the largest vendors, on their highest-priced SKUs.

This is why, across the SMB market, you see the same five or six product names in almost every MSP proposal regardless of customer size, customer industry, or customer fit. It is not because those are always the best products. It is because those are the products that pay.

The vendor-lock cost to the customer

The rough rule of thumb across multiple industry analyses is that customers buying licenses and hardware through an MSP pay 15 to 30 percent more than they would pay sourcing directly from the vendor or through a cost-plus arrangement, after accounting for any volume discounts the MSP claims to pass through. That gap is the resale margin plus the rebate, expressed as overpayment.

There are also hard costs to switching once you are entangled. Industry analysis from Flamingo found switching costs in the $50,000 to $325,000 range for organizations changing managed-services vendors, with five-figure data-migration costs alone for mid-sized engagements (Source: Flamingo, MSP Vendor Lock-In, 2024). Some of that is unavoidable; some of it is engineered into the contract.

The contractual mechanics that lock customers in are predictable:

• 36-month minimum terms with auto-renewal at 90-day notice windows. Miss the window, sign up for another year.
• Per-seat true-ups that bill for adds throughout the year but do not credit subtractions until renewal.
• License entanglement — your Microsoft 365 tenant, your EDR licenses, your backup tenant, all purchased on the MSP’s account, do not transfer cleanly when you leave.
• “Data-portability” or “exit assistance” fees that are not disclosed until termination.
• IP ownership of runbooks — clauses asserting that the operational documentation built during the engagement belongs to the MSP, not the customer.

None of these are illegal. All of them are predictable. All of them favor the structure that makes resale margin the primary profit lever.

The five questions an MSP cannot answer honestly

If you want to test the alignment of an MSP candidate (or your current MSP) in a single 30-minute meeting, ask these five questions and listen for the wriggle. The questions are not gotchas. They are the questions an aligned provider answers in plain English and an unaligned provider redirects.

1. “What is your gross margin on the licenses you are reselling to me, and will you pass through the vendor’s actual cost?”

A provider whose business model is labor will tell you the number. A provider whose business model is resale will tell you that the question is more complicated than it looks. Both answers are real. Only one of them lets you make a clean decision.

2. “Do you receive rebates, MDF, co-op funds, or SPIFs from the vendors whose products you are recommending? If so, please disclose them.”

The honest answer is almost always yes. The interesting answer is whether the disclosure happens before or after you ask.

3. “If I want to buy these licenses directly from the vendor and have you manage them, will you do that, and at what fee?”

This is the cleanest test of whether the provider is a labor business or a resale business. A labor business has a quote ready. A resale business has a story about why direct procurement does not work — usually framed as “we cannot guarantee SLAs on licenses we do not own.” That story is sometimes true and usually not.

4. “Who owns the configurations, runbooks, and documentation that get built during our engagement?”

The aligned answer is “you do, jointly with us, and we will hand over editable copies on termination at no additional fee.” The unaligned answer involves the words “intellectual property.”

5. “What does your contract say about data portability and exit assistance fees?”

If the provider has to look it up, the answer is bad. If the provider laughs and says “we do not charge those,” verify it in writing.

Why “vendor-neutral” claims are usually marketing

Most MSP websites claim vendor neutrality. Almost none of them mean it.

A genuinely vendor-neutral provider has the following structural traits, all of which are verifiable:

1. Their margin model is transparent and labor-based, not resale-based. They will quote you a flat per-employee or per-endpoint monthly fee, and they will charge cost plus a small documented handling fee (or zero) on licenses, with the vendor invoice attached.
2. Their recommendations vary across customers in the same industry. A vendor-neutral provider’s tooling stack for a 30-person law firm in California will not be identical to their stack for a 30-person law firm in Massachusetts unless there is a defensible technical reason. Look for variance.
3. They are willing to recommend products they cannot resell. A truly neutral provider will sometimes tell you “the right answer here is a product we have no commercial relationship with.” If they cannot name an example, they are not neutral.
4. They publish or will share their vendor partnership tiers. A Microsoft Solutions Partner with Modern Work designation, a CrowdStrike Elite Partner, a Datto Blue Diamond Partner — those are real commercial relationships with quotas and incentives. A neutral provider will tell you which tiers they hold and what the volume targets attached to those tiers are.

If a provider claims vendor neutrality and cannot produce these traits on request, the claim is marketing. There is no fifth way to interpret it.

What “fiduciary IT” looks like in practice

The right structural answer to the misalignment we have just walked through is to invert the economics. A provider whose margin is in the labor — not in the resale, not in the rebates, not in the MDF — has incentives that move with the customer’s incentives, not against them.

Here is what that looks like in practice. Some of these are choices a provider makes; some are guarantees a customer can demand.

Pricing transparency. A flat per-employee or per-endpoint monthly fee that includes labor, the management platform, and the operational tooling. No per-incident charges, no surprise true-ups, no separate “platform fee” or “onboarding amortization.” If the customer doubles in headcount, the bill doubles cleanly. If the customer halves, the bill halves cleanly.

Cost-plus license pass-through. Licenses (Microsoft 365, Google Workspace, EDR, backup, MDM) billed at the vendor’s actual price with a documented handling fee — typically zero to five percent — to cover billing and procurement labor. Vendor invoices available on request. Customer-name-of-record on the licenses where the vendor allows it, so the customer owns the relationship and can move the licenses at any time.

No back-end rebates retained. If the provider receives rebates or MDF from vendors whose products its customers use, those dollars are credited back to the customers in proportion to their consumption, or they are not accepted in the first place. Either model is honest. Pocketing them is not.

Customer-owned vendor relationships. Microsoft tenants, Google Workspace tenants, security tooling tenants — created in the customer’s name with the customer as the global administrator. The provider has delegated administrative access. Termination of the engagement does not require migrating the tenant; it requires removing the provider’s delegated access. Five minutes, not five months.

Customer-owned documentation. Runbooks, network diagrams, identity configurations, integration maps — written into the customer’s documentation system (Notion, SharePoint, Confluence, the customer’s choice), with the provider as a contributor. On termination the customer keeps the documentation; the provider keeps the methodology that produced it. No “IP ownership” clause.

Honest tooling consolidation. A standard stack that the provider can defend on technical grounds — not because it pays the most, but because it is genuinely the right combination at the SMB scale. Where a customer-specific deviation makes sense (an industry-specific tool, an existing investment, a regulatory constraint), the deviation is welcomed, not resisted with “we only support our standard stack.”

Contract terms that do not punish leaving. Month-to-month or 12-month terms, not 36-month minimums. Notice windows of 30 to 60 days, not 90. No data-portability fees. No “exit assistance” charges. The economic relationship has to keep being earned, not contractually enforced.

This is what we mean by fiduciary IT — an IT provider whose contractual and economic structure puts them in the position of a fiduciary for the customer’s IT decisions, the same way a fee-only financial advisor is structurally a fiduciary for the customer’s financial decisions and a commission-driven broker is not. The legal term fiduciary is overloaded; we use it here in the structural sense — incentives that genuinely align with the client’s interest, not just a marketing claim of alignment.

The point of the analogy is that the question is not “is your provider a good person.” The question is “is your provider’s compensation structured so that the right answer for the customer is also the right answer for the provider.” If the answer is yes, you have an IT department. If the answer is no, you have a vendor.

How goCloudOffice is structured differently

We built goCloudOffice as the structural alternative to the resale-margin MSP. The choices were not subtle and they were not free; we accepted lower top-line revenue per customer in exchange for a model that is defensible on alignment grounds.

The specifics:

• Productized, transparent monthly pricing per employee. The same number for the same scope at the same headcount, listed on the website, with a build flow that produces a defensible quote in five minutes. Not a custom proposal; a published price.
• Cost-plus on licenses. We pass through Microsoft, Google, security, and backup licenses at the vendor’s actual cost. Where we earn partner-program credits we apply them to the customer’s bill.
• Customer-owned tenants and licenses. When we onboard you, your Microsoft 365 tenant or Google Workspace tenant is in your name. We have delegated access. You can terminate our access in minutes.
• No back-end rebates retained as profit. Where we participate in vendor incentive programs, we do so to access training and roadmap visibility, not to convert rebates into profit on the customer’s account.
• Month-to-month service, with a one-time onboarding fee. No 36-month minimums. No auto-renewal traps. The relationship has to keep earning itself.
• Customer-owned documentation. Your runbooks, your network diagrams, your identity configurations — in your documentation system. We are a contributor, not the owner.
• Disclosed partner tiers. We tell you which vendors we have commercial relationships with and at what tier. If a recommendation we make happens to coincide with a vendor we hold a tier with, we say so explicitly.

We do not claim this is the only legitimate way to run an IT services business. There are MSPs who run a resale-heavy model honestly, who disclose their incentives, and whose customers love them. The point is that the customer should be able to see the structure, ask the questions in the section above, and decide whether the answers add up.

How to evaluate any IT provider’s incentive alignment in 10 minutes

If you take nothing else from this piece, take this checklist. Ten minutes, applied to your current provider or to any provider you are evaluating, will tell you most of what you need to know.

Pricing model (2 minutes). Is there a published per-employee or per-endpoint price, or is every customer a custom proposal? Custom proposals are not always misaligned, but published pricing is structurally harder to game.

License pass-through (2 minutes). Ask: “Will you sell me my Microsoft 365 licenses at the same price the vendor would charge me directly?” The answer reveals the resale model.

Rebate disclosure (1 minute). Ask: “What rebates, MDF, or SPIFs do you receive from the vendors of the products you are recommending?” Listen for the answer, not just the words.

Contract length (1 minute). Look at the term. Three years with auto-renewal is a lock-in. One year or month-to-month is alignment.

Tenant ownership (2 minutes). Ask: “If we hire you, who is the global administrator on our Microsoft tenant?” The right answer is “you are; we have delegated access.”

Documentation ownership (1 minute). Ask: “If we leave you, what documentation do we get?” The right answer is “all of it, in editable form, at no charge.”

Recommendation variance (1 minute). Ask for two reference customers in your industry of similar size. Ask each what tools they use. If the stacks are identical, the recommendations are vendor-driven. If they vary defensibly, the recommendations are customer-driven.

Six of seven answers in the right column means a structurally aligned provider. Three of seven or fewer means the economics will work against you, eventually, regardless of how nice the people are.

What this means for the buyer

You do not have to switch providers tomorrow. What you should do today is read your current MSP’s last invoice, last proposal, and last contract through the lens of this piece, and notice what you see. The vendors that recur. The line items that compound. The clauses that quietly favor the provider over you.

If the answers add up, your provider is structurally aligned and you should keep them. If the answers do not, you have a decision to make — and you have it earlier rather than later, which is the only useful time to have it.

When you are ready to look at what an aligned model costs and covers for a company your size, the build flow will give you a defensible per-employee number in five minutes. If you would like to talk it through, a 15-minute conversation is the fastest way to get to a real answer for your specific situation. We will not push the conversion, because the math has to work for you on its own merits — that is the entire point of the model.