Guide

MSP pricing models, and what each one does to your marketing

For MSPs and IT services companies: per-user, per-device, tiered, à la carte and value-based. The commercial mechanics of each, which buyers each attracts, and why declining to address price anywhere on your website costs deals you never hear about.

Pricing is a positioning decision

MSPs and IT services firms tend to treat pricing as a finance exercise: establish the cost to serve, apply a margin, check it against the local competition. But the model selected performs more marketing work than most marketing does. It determines which buyers select themselves in, which objections occupy the sales cycle, and whether the offer is directly comparable to the provider three miles away or deliberately not.

This is why packaging and pricing are settled during Month 1 rather than handled separately. A precise position accompanied by an opaque price structure still loses.

The models

Five structures, and how each behaves commercially

  • Most common

    Per user

    A fixed monthly rate per employee covering their devices. Straightforward for a buyer to forecast against headcount, and it does not penalise multi-device users.

    • Strengths: predictable, scales with the client, simple to quote
    • Weaknesses: unprofitable in device-dense or shift-based environments
    • Attracts: buyers requiring a budget line they can defend internally
  • Traditional

    Per device

    Priced per endpoint, server and network device. The closest approximation to actual cost to serve, which is why it persists in device-dense sectors.

    • Strengths: tracks cost honestly, equitable in mixed estates
    • Weaknesses: penalises modern multi-device users, harder to forecast
    • Attracts: manufacturing, clinical settings, device-heavy operations
  • Packaging

    Tiered

    Three levels applied above a per-user or per-device unit. The packaging layer most providers should operate and many do not.

    • Strengths: establishes an upgrade path and anchors the middle tier
    • Weaknesses: meaningless where tiers differ only in response-time commitments
    • Attracts: buyers who prefer to select rather than be quoted
  • Flexible

    À la carte

    A base agreement with separately priced services: backup, security stack, compliance, projects, advisory.

    • Strengths: allows a price-sensitive buyer to begin somewhere
    • Weaknesses: complex quotes, scope disputes, inconsistent margin
    • Attracts: buyers optimising line items, rarely the clients you want
  • Advanced

    Value-based

    Priced against outcomes — availability commitments, compliance posture, risk transfer — rather than units consumed.

    • Strengths: escapes per-seat comparison, strongest available margin
    • Weaknesses: requires genuine specialisation and evidence to defend
    • Attracts: regulated and risk-aware buyers not shopping on price
  • Alongside

    Project and co-managed work

    Operates above whichever model is selected. Co-managed is increasingly where growth sits for providers serving larger organisations with internal IT staff.

    • Strengths: opens accounts too large to outsource entirely
    • Weaknesses: scope boundaries must be explicit or margin erodes
    • Attracts: 100+ seat organisations with one overextended IT manager

What belongs on the website

The instinct is to publish nothing and route every enquiry to a discovery call. It is understandable: pricing depends on the environment, and no provider wants to be compared on a figure presented without context.

Consider what occurs in practice. A buyer with a live problem evaluates four providers on a Tuesday afternoon. Three state that pricing is available on request. The fourth explains the model, the variables that move it, and approximately where an organisation of that size lands. The fourth receives the call — not because it is cheapest, but because it was the only firm that made the process appear straightforward.

A rate card is not required. Removing the apprehension that asking initiates something is.

Pricing for IT services companies versus managed services

The models above describe recurring agreements. An IT services company selling projects, migrations or assessments prices differently: by scope, by phase or by outcome rather than per seat or per device. The commercial logic still holds — a buyer who can anticipate the structure proceeds, and one who cannot asks for the cheapest version — but the published explanation differs.

For project work the useful disclosure is the shape of an engagement rather than a rate: what a typical scope includes, what moves the figure, roughly what a firm of that size spends, and what happens when the scope changes mid-engagement. That last point closes more deals than a discount, because unmanaged scope change is the outcome buyers of project work most expect and most fear.

Firms selling both — an ongoing agreement alongside project work — need each explained separately. Combining them produces a page that reads as evasive about both.

What an effective pricing page contains

  • The model in use and the reasoning behind it
  • The variables that move the figure: seats, sites, compliance scope, after-hours cover
  • A range or starting point, however broad
  • What is always included, so tiers are not a matter of inference
  • Onboarding: cost, duration and what it involves
  • What occurs at the end of the agreement, which defuses the principal switching concern
  • A small next step: a question, not a commitment
The term this page targets.
Keyword Searches / month Google Ads CPC
msp pricing models 30 $63.40

FAQ

Frequently asked questions

Should we publish prices on the website?

A rate card is not required, but an explanation of how pricing works is. A buyer comparing three providers will favour the one that made the process feel predictable. Silence on price does not create latitude; it creates the suspicion that the figure depends on what the buyer appears able to pay.

What is the most common MSP pricing model?

Per-user is the most common for standard managed services, because headcount is easier for a buyer to forecast than device count and it does not penalise the employee carrying a laptop, a phone and a tablet. Per-device persists in device-dense environments such as manufacturing and clinical settings, and tiered packaging generally sits above whichever unit is selected.

How does pricing affect marketing?

More than most providers anticipate. The model determines which buyers you attract, on what grounds deals are lost, and how much of the sales cycle is spent explaining the structure. A model requiring a discovery call before it can be understood filters out serious buyers conducting a comparison on a Tuesday afternoon.

Should we compete on price?

Only with a genuine structural cost advantage, which few providers at this size possess. Absent that, price competition is won by becoming the firm that can no longer afford to answer the phone. The alternative is positioning — being demonstrably more suitable for a defined buyer, which is what stage 03 establishes.

How do we raise prices on existing clients?

Not strictly a marketing question, though the answer is adjacent to one: it is considerably easier when the position has changed and the service has visibly changed with it. An adjustment accompanied by a genuine expansion of scope reads as a new agreement. An adjustment with no accompanying change reads as an increase.

Packaging is half of the positioning

Determining what you sell, in what tiers, at what price is settled during Month 1 — because a precise position with an opaque price structure still loses deals.