The margin conversation is the same in nearly every MSP sales meeting. "We charge $X per endpoint" or "Our all-in-one package costs $Y per user, per month." The logic is straightforward: calculate your total delivery cost, apply a markup, and that's your price. It works—until the market floods with competitors willing to work thinner margins.
Cost-plus pricing is a race to the bottom. When everyone in your market knows roughly how much it costs to deliver managed services, pricing becomes commoditized. Your only differentiation is the margin you're willing to lose. That's not a business model—that's a commodity trap.
The cost-plus pricing problem
Race to the bottom. Cost-plus pricing makes it easy for competitors to undercut you. If your costs are roughly similar to theirs, the only lever they have is margin. They drop their price. You drop yours. Eventually nobody makes money on the services that were supposed to anchor the relationship.
Commoditization. When pricing is based purely on costs, customers have no reason to prefer you over anyone else. They shop based on price alone. This kills your ability to build lasting relationships, upsell, or expand within an account.
Hidden cost blindness. Most MSPs underestimate the true cost of service delivery. Escalations, support tickets outside the SLA, scope creep from "quick fixes," and knowledge workers troubleshooting edge cases—these costs don't appear in your initial cost-plus calculation. They erode margins silently until you're working below cost.
Three pricing models: pros and cons
Cost-plus pricing is the easiest to calculate and explain to customers. You know your costs, you apply a standard margin, done. The downside is everything above—race to the bottom, commoditization, and hidden cost leakage. Cost-plus works if your market has no competition. If it does, you're in trouble.
Competitive pricing means you research what competitors are charging and price near that market rate. This prevents you from being undercut, and it feels "fair" to customers because it matches market expectations. But it also means you're locked into a pricing band you don't control. If your costs are higher than competitors', you'll struggle. If they're lower, you're leaving money on the table.
Value-based pricing starts with a question: "What is the customer's problem worth solving?" You price based on the value your solution delivers—not the cost to deliver it. If your managed services save a customer $500K per year in avoided downtime and IT staff overhead, pricing at $50K-$75K annually is a steal for them. This model requires understanding your customer's economics and selling the value, not the features.
Calculating your true cost of service delivery
Before you can price strategically, you need accurate cost data. Most MSPs don't have it. They estimate labor at an hourly rate and call it done. That's incomplete.
Direct labor. How much time does each service category actually require? Not the SLA promise—the real average from your last 100 tickets. Include the tool time (RMM, helpdesk, documentation), not just hands-on troubleshooting.
Escalation costs. Some issues go to your senior engineer. Some require vendor escalations and conference calls. What's the average escalation cost per service per customer? This is often 10-20% of your base ticket cost and is routinely ignored.
Infrastructure and tooling. Allocate your licensing costs (RMM, PSA, backup, security) across your customer base proportionally. A 500-user environment costs you more in tooling than a 50-user one.
Support overhead. Not every ticket is preventive maintenance. Some customers generate support volume that exceeds their SLA allocation. You absorb that cost when you can't track it. Build in a support volatility buffer—typically 15-20% of your base labor cost.
Knowledge work. Troubleshooting novel problems, architecture design, and implementation projects take time that's often bundled into the service. If you're not measuring this separately, you're giving away value for free.
Building value-based pricing tiers
Value-based pricing doesn't mean custom pricing for every customer. It means creating tiers that align with customer outcomes, not endpoints.
Define outcomes, not features. Don't sell "24/7 monitoring and alerting." Sell "guaranteed 4-hour incident response with a 99.5% uptime SLA." The customer cares about the outcome (uptime) and the response promise (4 hours), not the monitoring technology. Price accordingly.
Stack the value proposition. Create 3-4 tiers with increasing outcomes and value. Bronze tier: basic monitoring and patching, 8-hour response. Silver: comprehensive monitoring, vulnerability management, and reporting, 4-hour response. Gold: everything in Silver plus proactive security assessments, quarterly business reviews, and 1-hour response. Each tier costs more because it delivers more value to the customer.
Tie price to customer economics, not your costs. If your service prevents one ransomware incident that would cost a customer $100K, the service is worth $15K-$25K to them, regardless of whether it costs you $8K or $12K to deliver. Price based on the value at stake, not your cost structure.
Data-driven pricing: the role of profitability analytics
Strategic pricing requires real numbers—not assumptions. You need to know: Which services are profitable? Which customers are profitable? What utilization rates do different service tiers actually require?
Service profitability. Not all managed services are created equal. A fully automated, preventive-focused service (like patch management) might have 65% gross margin. A troubleshooting-heavy service (like technical support) might have 35% margin because of escalation costs and low utilization. You need visibility into each service's actual profitability.
Utilization rates. You price a service at a certain labor cost, but if utilization is only 70%, your actual cost is higher. Track utilization by service, by customer, and by team. Use that data to adjust pricing or improve delivery efficiency.
Margin analysis by customer. Your highest-revenue customer might be your least profitable. They might be driving support volume that exceeds their SLA, or they might be demanding lower price concessions. Know which customers fund your business and which ones tax it.
Price optimization over time. As you automate and improve service delivery, your costs drop. Value-based pricing lets you keep some of that efficiency gain as margin improvement—you're not locked into cost-plus, where cost reductions immediately become pressure to lower prices.
How Voyager helps MSPs win with pricing strategy
Strategic pricing requires connecting three data sources: your PSA (service delivery and labor cost), your billing system (pricing and revenue), and your CRM (customer value and industry context). Most MSPs keep these systems separate, which means pricing decisions are made blind.
See true service profitability. Voyager connects your PSA data with billing data to show you gross margin by service, by customer, and by time period. You can answer instantly: "Are we profitable on HaloPSA implementations?" or "What's our margin on Xero support?" This visibility is the foundation for strategic pricing.
Track utilization and cost trends. Voyager pulls labor cost from your PSA and billable hours from your billing system. You see utilization rates, cost drift, and margin trends in real time. If support costs are climbing for a customer, you see it before they've exhausted their SLA—you can adjust pricing or improve efficiency before margins collapse.
Align pricing with customer value. By connecting your CRM and financial data, you can see which customers are most valuable (highest revenue, lowest support cost, best expansion potential). You can price new tiers strategically, knowing which customer profiles will benefit most and which can support premium pricing.
Pricing strategy isn't guesswork. It's data-driven. The MSPs winning in 2026 aren't competing on cost—they're competing on profitability and customer value. They know their true cost of delivery. They price based on value, not costs. And they have the data to back it up.