iSectra — Believe IT
IT Department

Why Your MSP Recommends What It Recommends

Most IT providers earn margin on what they sell you. Here's how that shapes your proposal — and the questions to ask before you sign.

Damian Colarte Jul 21, 2026 8 min read
Why Your MSP Recommends What It Recommends

Most managed service providers earn a meaningful share of their revenue reselling vendor products — licenses, appliances, security tools, and backup platforms — at a markup, often on top of volume rebates and partner-tier incentives. That is a legitimate business model, and it is not hidden.

It does, however, shape what lands in your proposal, and most buyers have never thought about it. This article lays out the economics plainly, so you can ask better questions — not because providers are dishonest, but because incentives deserve to be seen.

Free IT Risk Assessment

See how your IT actually stacks up.

Twelve questions, about four minutes, and your score appears on screen immediately — no sales call required.

Take the assessment

How do MSPs actually make money?

A managed service provider typically runs several revenue lines alongside each other. The first is the monthly management fee — the fixed retainer for monitoring, help desk, and upkeep. The second is hardware and license resale: the provider buys products from a vendor or distributor and bills them to you at a markup. The third is project work — migrations, rollouts, one-time builds — billed separately or as an add-on. The fourth, less visible, is vendor rebates and partner-tier incentives: when a provider sells enough of a vendor's product to reach a tier, the vendor pays back a percentage or extends pricing advantages.

The markup is straightforward. A license that costs the provider $22 per seat might be billed to you at $30; the difference is margin. The rebate is more interesting, because it rewards volume rather than the single transaction. A provider who keeps a vendor's product across most of its client base earns a quarterly or annual rebate on that volume, and that rebate can be a material number. I'm not going to quote specific rates — they vary by vendor and by tier, and invented figures wouldn't help you. The structure is what matters, and the structure is consistent across the industry.

Why does this shape what you're recommended?

When a provider's margin depends partly on which product you buy, the tool that fits and the tool that pays are not always the same one. Most of the time they are close enough that nobody notices. The problem is the drift: over years, a provider's stack leans toward the vendors that reward it, and that stack becomes the default answer to almost any question. You can see how a flat-retainer managed IT model changes that default — but the point here is structural, not promotional.

This often happens without anyone acting in bad faith. The engineer writing your proposal is not calculating a kickback; they are recommending the tool their shop is certified on, the one their team knows, the one their supplier rewards them for stocking. Those are real, practical reasons to prefer a tool. But the incentive decided which tools the shop got certified on in the first place, and that decision was made years before your proposal landed on the table.

Where the model works fine

It is worth saying plainly where resale earns its place. A small business buying through its provider gets purchasing power it would not have on its own: the provider's volume pricing is usually better than a single-seat retail rate, and the provider becomes one point of accountability when something breaks. That is a genuine service, not a gimmick. For a company without a procurement function, having someone else own the vendor relationship is worth paying for.

Volume relationships can also lower real cost. A provider that buys a product at scale and passes some of the savings through is often cheaper than you buying direct, even after the provider's markup. The model is not broken. It is a structure with a built-in bias, and the bias is toward selling more of whatever the provider already sells.

Where it bites

The same structure produces predictable failures. Tool sprawl that nobody is accountable for, because each tool was a reasonable sale at the time. Renewals that auto-escalate, because the renewal is where the provider's margin compounds year over year. Security products layered on top of each other rather than consolidated, because each new product is a new line on the invoice. Migrations recommended on the vendor's timetable rather than yours, because the provider earns on the migration and on the licenses that follow. Being sold the tier above what you need, because the higher tier pays the higher rebate.

None of these requires a villain. Each is the natural output of an incentive that rewards selling. A buyer who understands the incentive can spot the pattern and ask one more question.

The CrowdStrike example

In July 2024 a faulty update from CrowdStrike took down millions of Windows machines across airlines, hospitals, and banks worldwide (the event is documented in detail on Wikipedia). It was one of the largest IT disruptions on record.

Not one iSectra customer was affected, because we had never deployed that product to them. I want to be careful about how I say this: it is our own account of our own customer base, not an industry statistic, and I am not claiming it says anything about CrowdStrike's product in general. What it does illustrate is that not carrying a resale incentive changes what ends up in an environment. We had no reason to push that tool, so we hadn't, and so our clients were not in the blast radius. The point is structural, not a victory lap.

How iSectra is structured differently

We don't take vendor rebates or margin incentives that shape what we recommend. Hardware and third-party costs are passed through at cost. Our revenue is the monthly retainer — the invoice we receive is the invoice you receive. You can read more about how the company is set up and why.

I want to be honest about what that does and does not mean. It removes one conflict of interest — the one where the provider earns more by selling you more. It does not make us infallible, and it does not mean every recommendation we make is automatically correct. You should still ask us the same questions you'd ask any provider, and we should answer them the same way. The structure is a guardrail, not a halo.

What to ask your current provider

These questions work regardless of who you're talking to. Ask them in writing, and notice the tone of the answer as much as the content.

  1. 1.Do you mark up licenses and hardware? A good answer names the markup plainly, or says there isn't one. A deflection — "it's all bundled" — is an answer of its own kind.
  2. 2.What rebates or partner incentives do you receive from vendors you've recommended to us? A good answer acknowledges them and explains the structure. "We don't get incentives" is rarely the whole truth at any sizable provider.
  3. 3.If we bought this tool direct, what would it cost? A good answer gives you the number, or gets it for you. A refusal to compare is a signal.
  4. 4.Who owns the license — us or you? A good answer is unambiguous: you own it, it's in your name, and you can take it with you.
  5. 5.What happens to these tools if we leave? A good answer describes a clean exit: licenses transfer, data exports, no hostage clauses. A vague answer is worth pressing on.
  6. 6.Do you have a partner tier that depends on selling this vendor? A good answer is honest about whether the vendor relationship carries a sales target. The honest answer is more useful than the convenient one.

A straight answer to these is not an admission of guilt; it's the baseline of a working relationship. A provider that answers them well is usually a provider worth keeping, resale model or not.

DimensionResale-margin modelFlat-retainer model
How revenue is earnedManagement fee plus markup on products and vendor rebatesMonthly retainer; hardware and licenses passed through at cost
What gets recommendedThe provider's stocked, certified, rewarded stackWhatever fits the client, with no margin riding on the choice
Who owns the licensesOften the provider, under their partner accountThe client, in the client's name
What happens at renewalMargin compounds; renewals tend to auto-escalateCost tracks the vendor's list price, with nothing added
Incentive at tool-selection timeSell the product that pays the providerSelect the product that fits the client
Cost predictabilityLower — markup and rebate layers varyHigher — the invoice you receive is the invoice we receive
What happens if you leaveLicenses may be tied to the provider; exit can be hardLicenses are yours; exit is clean

The issue isn't the margin

The issue is that most buyers have never asked how the margin works. Providers are entitled to earn a living, and resale is one honest way to do it. But a buyer who understands the economics — who knows which lines of the invoice are margin and which are pass-through, who knows whether the recommendation carries a rebate — makes better decisions regardless of which provider they choose.

The same instinct connects elsewhere in this industry. When a vendor claims its product makes you "compliant" on its own, the same move applies: follow the incentive, then ask the next question. We made that argument in our article on 21 CFR Part 11. The structure of who pays whom is usually more informative than the brochure.

Hero photo: "Balance scale with spheres on a marble pedestal" by Myles Bloomfield on Unsplash.

Frequently asked questions

Don't see your question? Email info@isectra.com and we'll answer it directly.

Share
IT Department
DC
Founder & CEODamian Colarte

Damian Colarte is Founder & CEO at iSectra. He has spent two decades inside the managed services industry, watching how provider economics shape what businesses actually buy.

Get the next post in your inbox.

Signal, once or twice a month. No spam — just the posts worth reading.

Let's see what your IT could feel like.

A senior engineer will review your environment and respond within 24 hours. No sales script, no obligation.

(845) 563-0346
Call