Here’s the truth: most Managed Service Providers (MSPs) set prices by guessing what competitors charge. That’s why they struggle with thin profits and unpredictable income.
The better way? Know your actual costs, understand your value, make buying decisions simple, and raise prices regularly. Think of pricing as a system you build once, then maintain—not just a number you pick and hope works.
Step 1: Know What Things Actually Cost You
You can’t price well if you don’t know what it costs to deliver your service.
The math seems simple but most people get it wrong.
Here’s the wrong way: Take a technician’s $50,000 salary, divide by 2,080 hours (a full work year), and mark it up a bit. Seems logical, right?
The problem is this ignores health insurance, payroll taxes, software tools, training time, vacation days, and the fact that nobody bills 100% of their hours. When a technician is in team meetings, doing paperwork, or waiting for a customer to respond, those are hours you’re paying for but not billing for.
The right way involves understanding the full picture.
Successful MSPs aim to bring in at least $2.50 in revenue for every $1 they pay in wages. So if you pay someone $50,000, you need them generating at least $125,000 in revenue.
This 2.5× rule accounts for all those hidden costs and ensures healthy profit margins. When you hit this target consistently, you’ll have enough left over to cover your office rent, your own salary, marketing costs, insurance, and still have money left for growth and savings.
Think about it this way: if you’re paying your technicians but barely breaking even at the end of the month, something is fundamentally wrong with your pricing.
You’re essentially running a charity, not a business.
The 2.5× rule gives you a clear target to aim for.
Here are some questions you need honest answers to. At your current prices, can you afford to pay your team well? This matters because good technicians don’t stay at companies that underpay them.
How many billable hours can you realistically expect per technician?
Hint: It’s not 40 hours a week. Factor in training, administrative work, team meetings, and downtime between projects. Most healthy MSPs plan for around 30 or more billable hours per technician per week, not 40.
If you need to hire senior, expensive experts, will customers pay rates high enough to cover them? This is a crucial question. If you can’t afford expensive senior people at your current prices, you need a different team structure.
You need more junior technicians doing most of the work, with just a few experts supervising and handling the complex problems. This pyramid structure is how most successful service companies operate.
The expensive experts aren’t in the trenches all day—they’re guiding the team and solving the hardest problems.
The trap many business owners fall into is being too optimistic about utilization. They imagine their technicians will be busy every minute, but the reality includes gaps between appointments, time spent documenting work, internal meetings, and training on new technologies.
When you factor in vacation time, sick days, and holidays, a technician working a full year might only have 1,800 truly available hours, not 2,080.
And of those 1,800 hours, maybe only 1,400 are actually billable to customers. This is why the simple salary-divided-by-hours math fails so badly.
Step 2: Price for the Value You Deliver, Not Just Your Costs
Once you know your minimum viable price (your “floor”), you can charge more based on the value you provide. This is where many MSPs leave massive amounts of money on the table.
Great MSPs don’t just “match what others charge.” They price based on what they’re worth to the customer. Think about what you’re really delivering. You’re providing risk transfer, meaning you’re taking on the stress and liability of their technology. When their email server crashes at 2 AM, that’s your problem, not theirs. That peace of mind has real value.
You’re also delivering productivity gains because their team works better when systems actually work reliably. Nobody can work effectively when they’re fighting with their computer all day. And you’re providing scalability, meaning they can grow their business without technology disasters derailing everything.
Here’s something most MSPs learn the hard way: when you launch a new service offering, you’ll always underestimate the real cost.
Most companies discover a pattern. Their initial estimate is “This will cost us X to deliver.” Then after 20-30 customers, reality hits: “Oh, this actually costs us twice what we thought—2X.” Finally, at maturity, when they’re doing it really well and consistently, they realize “To do this properly takes three times our original estimate—3X.”
Smart companies learn from others’ mistakes. They price at 3X from day one and save themselves years of losing money while “learning.”
Yes, this might mean your prices are higher than some competitors when you launch something new, but you’ll actually make money while they’re bleeding cash and wondering why their “profitable” new service is bankrupting them.
Here’s another counterintuitive truth: don’t discount for bigger customers.
It seems logical at first. A company with 200 employees should pay less per person than a company with 20 employees, right? Wrong. It’s actually backwards, and here’s why.
Bigger customers usually need more sophisticated tools, more experienced technicians, more account management time, and more careful coordination. Your cost per user goes up with bigger accounts, so your price should too.
Think about the difference between supporting a 10-person startup where everyone uses the same basic setup versus a 200-person company with multiple departments, remote workers, compliance requirements, and a CFO who wants detailed reporting.
The 200-person company is dramatically more complex to support. You might need dedicated account management, formal quarterly business reviews, more sophisticated monitoring tools, and technicians who can handle enterprise-level challenges.
All of that costs more, not less.
Step 3: Make Buying Simple
Don’t give customers a menu of 47 service options.
It paralyzes them and leads to bad choices that hurt your margins. When you present too many options, customers focus on finding the cheapest possible combination rather than thinking about what they actually need.
A better approach is to offer one comprehensive service package with clear scope. Let customers think in simple terms: $X per employee per month for complete IT support, or $Y per month for their whole company.
The detailed breakdown lives in the contract (so you can adjust when they add people), but the buying decision is simple: “Do you want your technology managed well? Here’s the price.”
This simplicity benefits everyone. Customers can make faster decisions because they’re not trying to figure out whether they need the silver plan with extra backup or the gold plan with faster response time.
They’re just deciding whether they want comprehensive IT support or not. Your sales process gets faster too. Instead of spending hours customizing quotes and going back and forth on which services to include, you’re having a straightforward conversation about whether you’re the right fit for their needs.
The detailed units still matter, but they belong in the contract, not the sales pitch.
The contract specifies things like “includes up to 50 users, 50 computers, 5 servers” so you can cleanly handle adds and removals. But during the sales conversation, you’re focused on outcomes: “Your team will have reliable technology, fast support when things break, proactive monitoring to prevent problems, and the security protection your business needs.”
When it comes to hourly pricing, avoid it when possible. “Call us and we’ll bill you by the hour” creates unpredictable income for you and scary surprise bills for customers. Neither party benefits from this arrangement.
You can’t forecast your revenue, and customers are afraid to call you for help because they don’t know what it will cost.
If you must do hourly work, sell prepaid blocks like “20 hours for $3,000” that expire if unused and auto-renew monthly. This gives you predictable recurring revenue and gives customers predictable expenses.
But recognize that this is still less stable than managed services where customers pay the same amount every month regardless of how much support they need. Managed services is where you want most of your revenue to come from.
Step 4: Raise Prices Every Year (Yes, Really)
If your prices don’t go up annually, your service quality will quietly decline. This isn’t optional, it’s mathematical reality.
Here’s why it matters: Your team expects raises, and they should get them. If you want to keep good technicians, you need to pay them more this year than last year. Health insurance costs rise, recently by 5% to 10% or more annually. Software tools get more expensive.
Microsoft, your monitoring tools, your security stack—they all increase prices regularly. And everything costs more due to inflation. Your office rent, your internet connection, even your coffee for the break room costs more this year than last year.
If your revenue per customer stays flat while all your costs increase, the math only works one way: your profit margin shrinks.
Eventually you reach a breaking point where you either have to cut corners (hurting service quality), underpay your team (losing good people), or work twice as hard just to stay in the same place financially.
What great companies do is build automatic annual price increases into 90% of their contracts, typically 2% to 5% per year. This isn’t sneaky or aggressive. It’s just keeping pace with the reality that costs increase over time.
Every other vendor your customers use does this. Their office lease goes up, their insurance premiums increase, their suppliers raise prices. It’s normal business.
Here’s what you’re probably thinking right now: “We’ll lose customers if we raise prices!” This fear is so common and so overblown.
Here’s what actually happens: almost everyone accepts reasonable increases without complaint. The few who push back can usually be retained with a conversation about the value you provide. And the very rare customers who actually leave are usually your most difficult, least profitable customers anyway.
Your team will actually be relieved to see them go.
One IT company owner told me he lost sleep for weeks before announcing a 5% price increase to existing customers. He drafted careful emails explaining the increase, prepared detailed justifications, and braced for an onslaught of complaints and cancellations.
Out of 40 customers, 38 didn’t even respond to the email—they just accepted it. One called to say “that’s fine, thanks for letting us know.” And one complained but ultimately stayed anyway.
All that anxiety for nothing.
The key is making it normal, not dramatic. Put the escalator in the contract from day one so new customers know it’s coming. Treat it as routine business, not a big negotiation.
Send a simple notification 60 days before it takes effect: “As outlined in our agreement, your monthly rate will increase by 3% starting in March, from $5,000 to $5,150. This helps us continue delivering excellent service as our costs for tools, insurance, and talent continue to rise.”
Step 5: Run Pricing Like a Business System
Great pricing isn’t a one-time decision.
It’s an ongoing process that you build into how your company operates.
Start by giving pricing authority to the right people. Your service delivery team, not your sales team, should own pricing. Why? Because they actually deliver the work, they know the real costs, and they care about profitability, not just closing deals. Salespeople are optimists.
Their job is to see the possibility in every deal and find ways to yes.
That’s valuable, but it makes them terrible at pricing discipline.
Service managers, on the other hand, are the ones who have to deliver on the promises, so they’re naturally more realistic about what things actually cost.
Make discounts rare and require approval from service management. When salespeople can discount freely, they will, because it makes their job easier. But each discount comes out of your profit margin.
Over time, if you require approval for every discount and make the approval process slightly uncomfortable, your team will stop expecting to discount at all.
Discounting stops being “normal” and becomes the rare exception for truly strategic situations.
You also need to track what matters.
Know your profit per customer, not just your revenue.
A $10,000 per month customer who requires constant hand-holding and generates only $1,500 in profit is worse than a $5,000 per month customer who runs smoothly and generates $2,500 in profit.
Revenue is a vanity metric, profit is what actually matters.
Forecast six months ahead. Plan for hiring and spending based on expected profit, not guesses. If you know you’re adding $50,000 in monthly recurring revenue over the next quarter, and you know your target profit margins, you can calculate exactly how much you can afford to spend on hiring another technician or investing in better tools.
Review your numbers monthly.
Are you hitting your profit targets? If not, adjust quickly. Don’t wait until the end of the year to discover you’ve been unprofitable for months. Monthly reviews let you catch problems early when they’re small and fixable.
Maybe you need to tighten up your processes to work more efficiently. Maybe you need to have tough conversations with customers who are consuming way more time than expected.
Maybe you need to pause hiring until revenue catches up.
When presenting prices to potential customers, talk about outcomes, not itemized lists. Don’t say “3 server check-ins per month, 47 desktop monitors, 2 on-site visits, unlimited phone support.” That invites customers to question each line item and try to negotiate removing pieces to save money. Instead say “Your technology will be reliable, secure, and supported.
Your team can focus on their work instead of fighting with their computers. When something breaks, we fix it fast. And we proactively prevent problems before they impact your business.”
Save the detailed units for the contract itself, where they help manage adds and removals smoothly.
The contract might specify “50 users, 50 workstations, 5 servers” so everyone’s clear about what’s included and you can easily adjust when they hire more people or add servers.
A Real-World Example
Let’s make this concrete. A 25-person company signs up for your standard IT support plan. Your calculations show you’ll spend about 1 hour per employee per month on support, plus device management and quarterly business reviews.
With all your costs factored in—technician wages, benefits, software tools, your overhead—you charge $150 per person per month. That’s $3,750 monthly or $45,000 annually from this client.
At that price, you’re hitting your target margins. After paying your technicians, covering software costs, and accounting for management time, you have healthy profit left over.
Three months in, their CFO asks for a detailed breakdown of exactly what they’re paying for. This is a test of your positioning.
You politely but firmly explain: “We sell outcomes and results, not itemized tasks. You’re paying for reliable technology, fast support, and the peace of mind that comes from having experts managing your systems. But your contract does show per-person pricing so we can smoothly add or remove people as you grow.”
Most CFOs accept this because it’s actually reasonable.
They don’t itemize their payments to their lawyer or accountant either.
They pay for expertise and results.
At renewal time, your automatic 2.5% increase applies. The price goes from $150 to $153.75 per person. You send a brief notification, and they accept it without discussion. No drama, no negotiation, no stress.
Six months in, you notice two customers are taking more time than expected. Maybe they’re less organized, maybe their previous IT setup was worse than you realized, or maybe they’re just higher-maintenance personalities. You have two levers to pull. First, you tighten up your processes to get more efficient.
Maybe you implement better documentation so tickets get resolved faster, or you do some training with their team to reduce repetitive questions. Second, for work that falls outside the normal scope—like a network redesign or a migration project—you propose a small project add-on at additional cost.
The system works because it’s a system. You’re not guessing and hoping each month. You have a process.
The Payoff
When you run pricing as a system—knowing costs, charging for value, keeping it simple, raising prices regularly, and managing it tightly—you get more predictable income, better profits without working harder, less stress and volatility, the ability to pay your team well, and customers who value what you do.
The difference between companies that struggle and companies that thrive often isn’t dramatic. It’s not about working twice as hard or being twice as smart.
It’s about doing these basics consistently, measuring what matters, and making small improvements that compound over time.
You don’t need to be perfect.
You just need to treat pricing like the business system it is, rather than a number you guessed and hoped would work.
Build the system once, maintain it monthly, and let it compound. That’s how ordinary MSPs become quietly, sustainably profitable.