.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
How to Price Managed IT Infrastructure Services a Comprehensive Guide for MSPs
Managed service providers do not usually lose an account because their rate card lacks another monitoring tool or security add-on. They lose margin because the price measures the wrong thing. A client adds employees, brings new identities into Microsoft 365, creates more help-desk demand, and raises the security burden, while the MSP still bills the same number of endpoints.
That gap matters more as the standard technology stack grows. On September 8, 2026, Microsoft listed Microsoft 365 Business Basic at $6 per user per month on an annual commitment, while Cloudflare listed its pay-as-you-go Zero Trust plan at $7 per user per month. Both vendors price around the person who uses and needs protection from the service, not simply the device in front of them.
Monetizely’s position is clear: for mainstream knowledge-worker clients, MSPs should make the managed user the primary recurring pricing meter. Servers, shared endpoints, backup capacity, network sites, and one-time projects should sit in separate, visible charges. A flat per-device rate should not stand in for a service relationship driven by people, identity, support, and security.
A five-step sequence prevents rate cards from becoming a list of tools
Pricing works when each decision follows the one before it. Monetizely’s 5-Step Pricing Framework begins with Goals and Segmentation, then moves through Packaging - Designing Offers That Fit, Choosing the Right Pricing Metric, Finding the Right Price Points, and Operationalizing Pricing. The sequence matters because a price is only the final expression of a deeper set of choices: which customers the MSP intends to serve, what each group needs, what unit reflects delivered value, and whether the business can bill and govern that unit without constant disputes. As described in Monetizing Agentic AI, the metric is rarely an isolated financial choice; it is the hinge between the offer a customer buys and the operating model the provider must support.
Many MSPs reverse that order. They start with a familiar market rate, such as $125 per endpoint, and then try to force every client, technology stack, and service promise into it. That approach produces a neat proposal and an unstable business.
Our view is that an MSP should first decide whether it is optimizing for rapid logo growth, expansion within existing accounts, gross-margin protection, or a move into a more demanding segment. Each goal calls for different packaging and discount rules. A provider moving from break-fix work into standardized managed services needs a price that rewards standardization; a provider pursuing regulated clients needs a price that funds documentation, reporting, incident response, and senior technical oversight.
The ideal customer profile should determine what the MSP refuses to bundle
A 25-person accounting firm with standardized laptops, Microsoft 365, a cloud line-of-business application, and one office can support a clear managed-user offer. A manufacturing plant with shared terminals, scanners, operational technology, and a round-the-clock floor should not be forced into the same model. The first environment centers on named workers; the second contains material equipment and site obligations that do not rise neatly with headcount.
Segmentation therefore requires more than employee count. MSP leaders should define segments using the conditions that change cost, risk, and value:
A managed-user offer should be built for the segment where the MSP can enforce standards. If every prospect demands different endpoint tools, backup rules, response commitments, and hardware exceptions, the problem is not simply a pricing problem. It is a customer-fit problem.
Packages work when they match recognizable client needs. They fail when they merely sort features into bronze, silver, and gold columns. A client does not wake up wanting “advanced tier reporting.” It wants fewer disruptions, faster employee support, credible security controls, or a documented recovery plan.
Public software pricing shows why the unit must follow the service delivered. As of September 8, 2026, Atera charged MSPs per technician with unlimited endpoints, while Datadog listed Infrastructure Pro at $15 per infrastructure host per month on annual billing. Those meters fit the vendors’ own economics: Atera sells a technician workbench, while Datadog monitors infrastructure objects. Neither meter should automatically become an MSP’s customer-facing price.
The package design below separates the managed workplace relationship from infrastructure that needs its own economics.
| Offer | Best-fit client | Included in the managed-user rate | Charged separately |
|---|---|---|---|
| Workplace Core | Standard office with a common cloud stack | Help desk, endpoint management for one primary computer, identity administration, patching, baseline security, vendor coordination | Servers, shared kiosks, network sites, projects, backup storage |
| Secure Workplace | Firms with higher security and reporting needs | Everything in Workplace Core, plus stronger security operations, executive reporting, and documented review cadence | Servers, specialist compliance work, extended-hours coverage, backup storage |
| Complex Workplace | Multi-site or infrastructure-heavy knowledge-worker firms | Managed-user workplace service plus deeper coordination across approved platforms | Network sites, production servers, line-of-business application support, major changes |
The point is simple: every package should describe a client segment and an operating promise, while material infrastructure remains visible rather than quietly absorbed.
Several design rules follow from that distinction:
The pricing metric should make sense to the buyer before it makes sense in a spreadsheet. A managing partner can understand why a new employee increases the cost of support, identity protection, onboarding, offboarding, Microsoft 365 administration, security awareness, and incident exposure. The same leader will struggle to understand why adding a second monitor, replacing a laptop, or enrolling a phone changes the basic managed-services bill.
That does not mean every device is free. It means the recurring service should be anchored to the unit that creates the continuing relationship. A named employee is the person receiving support and gaining access to business systems. The server, shared kiosk, firewall, and backup repository are different objects with different demand patterns.
The following assessment compares common meters for a standard knowledge-worker MSP account. Scores reflect Monetizely’s view on a five-point scale, where 5 is strongest.
| Decision criterion | Per managed user | Per endpoint | Per technician |
|---|---|---|---|
| Tracks employee support and identity demand | 5 | 2 | 1 |
| Handles employees with multiple devices | 5 | 1 | 3 |
| Gives the client a forecastable budget | 4 | 3 | 5 |
| Captures growth when the client hires | 5 | 2 | 1 |
| Aligns with common workplace software meters | 4 | 2 | 1 |
| Total | 23 | 10 | 11 |
For mainstream workplace management, the managed-user meter wins because it follows both the client’s growth and the MSP’s continuing obligation.
External vendor models reinforce the need for secondary meters, not for a single all-inclusive rate. Microsoft and Cloudflare use user-based pricing for workplace and access services. Veeam meters its Data Platform by protected workload and lists Veeam Data Cloud options by user or terabyte. Backblaze B2 lists storage at $6.95 per TB per month, with additional egress charges beyond included allowances. Those differences are a reminder that servers, workloads, and capacity should not disappear inside a generic endpoint price.
A pricing architecture can have one primary meter without pretending every cost behaves the same way. The managed-user rate should be the commercial center of the contract. Secondary meters should apply only where the managed object has a distinct and observable support burden.
This structure protects the client from surprise complexity while protecting the MSP from giving away server management, backup capacity, and site support.
A useful contract test is direct: if a client adds ten employees next month, can the account manager explain why the monthly bill rises? If the answer is “because the devices increased,” the model is weak. If the answer is “because ten more people now receive managed support, protected identities, licensed administration, and security coverage,” the pricing logic is visible.
Price points must recover the service model before discounts begin
Setting the rate comes after deciding the package and meter. Pricing teams often begin with a competitor’s advertised number and work backward. Competitor references are useful, but they cannot reveal an MSP’s own service cost, client fit, or willingness to enforce standards.
A defensible managed-user price starts with the support model required to deliver the promise. Estimate the technical labor, service-desk capacity, security tooling, vendor administration, account management, and target gross margin for the client segment. Then test the rate against the client’s alternatives: internal hiring, fragmented vendors, downtime exposure, and the executive time spent coordinating technology issues.
Consider a 60-user professional-services client that needs two production servers, two supported sites, and 3 TB of protected data. The rate card below makes the recurring relationship and the infrastructure charges explicit.
| Charge | Quantity | Monthly rate | Monthly revenue |
|---|---|---|---|
| Workplace Core | 60 managed users | $185 | $11,100 |
| Production server management | 2 servers | $400 | $800 |
| Protected backup capacity | 3 TB | $25 | $75 |
| Network site support | 2 sites | $350 | $700 |
| Monthly recurring revenue | $12,675 | ||
| Annual recurring revenue | $152,100 | ||
| Onboarding and standardization project | One-time | $9,000 | $9,000 |
The account produces a price the client can audit and a revenue base the MSP can manage, rather than a single endpoint rate that hides growing obligations.
Discounting should reduce scope, term risk, or service intensity before it reduces price. A three-year commitment may justify a lower unit rate because it improves demand visibility. A client that insists on nonstandard tools, unlimited after-hours access, or unsupported legacy systems should not receive the same rate as a client that adopts the MSP’s standards.
Pricing is not complete when the proposal is signed. The operating work begins when a client hires, offboards, opens a new site, adds a server, or expands backup retention. Monetizely’s research on pricing operations emphasizes that implementation often requires more work than the design itself because the meter must connect to entitlement, billing, customer communication, and internal accountability.
A clean operating cadence prevents the account team from discovering unpaid scope at renewal.
| Charge type | System of record | Review cadence | Billing action |
|---|---|---|---|
| Managed users | Identity provider and PSA | Monthly | Add or remove users under the contract’s change rule |
| Servers and shared endpoints | RMM and CMDB | Monthly | Reconcile against contracted quantities |
| Backup capacity | Backup console | Monthly | Apply committed capacity and overage rules |
| Network sites | Service inventory | Quarterly and upon change | Add site charge when service begins |
| Projects | Signed statement of work | At milestone completion | Invoice against agreed milestones |
A customer should be able to trace each change from an operating event to an invoice line, which reduces both leakage and avoidable billing disputes.
Accountability also changes sales behavior. Sales representatives will resist a rate card that requires constant exceptions, while service leaders will resist a contract that promises unlimited work without a clear meter. The managed-user architecture aligns both groups: sales can explain it, technicians can inventory it, finance can bill it, and clients can forecast it.
Per-device pricing persists because it feels concrete. Devices can be counted, and many MSP tools are licensed that way. Yet a client does not buy managed IT to own a collection of monitored objects. It buys continuity for the people who use technology to run the business.
Monetizely’s position is not that MSPs should eliminate device, server, or capacity charges. Quite the opposite. Those charges should become more explicit precisely so that the managed-user rate can remain clean, credible, and profitable. The result is a defined architecture: managed users as the primary recurring meter; infrastructure, storage, sites, and projects as secondary charges tied to their own observable units.
MSP operators should act on that position in five ways:
Choose the market you intend to standardize around. Make knowledge-worker organizations with named users the core audience for the managed-user offer, and create a separate service line for shared-device or operational-technology environments.
Replace gross endpoint count with managed-user ARR as the leading commercial metric. Track revenue per managed user, user growth, and infrastructure attach rate at every account review.
Set a non-negotiable standardization policy. Price exceptions visibly, or decline them. Margin improves when the technology stack becomes more repeatable, not when more work is hidden inside the same rate.
Make package migration a renewal strategy. Use upcoming renewals to move legacy per-device clients into a managed-user base plus explicit infrastructure charges, supported by a side-by-side invoice comparison.
Give discounts a strategic purpose. Permit lower rates only when the client gives something measurable in return, such as longer commitment, stack standardization, prepaid onboarding, or reduced support coverage.
Footnotes
- Amazon listing: https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
- Atera, “Atera for MSPs Plans and Pricing,” accessed September 8, 2026. (atera.com)
- Microsoft, “Microsoft 365 Business Basic,” and Cloudflare, “Zero Trust & SASE Plans & Pricing,” accessed September 8, 2026. (microsoft.com)
- Datadog, “Pricing Comparison,” and Veeam, “Veeam Data Platform Editions & Pricing,” accessed September 8, 2026. (datadoghq.com)
- Backblaze, “B2 Cloud Storage Pricing,” accessed September 8, 2026. (backblaze.com)