Simplifying and Maintaining an MSP Pricing Plan
- Pricing gets complicated one exception at a time: a custom add-on, a discount that stays, a mix of per-user and per-device.
- A workable plan is readable by the client, priced with a known margin, and able to grow when the client adds staff.
- Three tiers, bundles for what belongs together, and client-specific prices kept in one pricing book with an end date.
- Review prices when vendor costs change, and move existing clients onto a new plan at renewal.
Table of contents
A pricing plan works when a rep can quote it without asking anyone and a client can read it without a call.
Price lists that grew deal by deal tend to fail both tests. One client got a custom backup add-on, another a discount that was never removed, a third pays per device while everyone else pays per user. After a few years, only the owner knows what a service really costs. Here is how to simplify the plan and keep it simple.
Where the Complexity Comes From
Complex pricing rarely starts as a strategy. It builds up from one-off exceptions: special terms to win a deal, add-ons created for a single client, old vendor prices nobody updated. Each exception makes the next quote slower to build, harder for the client to compare, and more likely to contain a pricing error that eats your margin.
Principles of Effective MSP Pricing
Transparent: The client can see what is included per user or per device, and what is billed on top, such as onsite visits or out-of-hours work. Hidden fees surface eventually, usually at the first invoice.
Priced on value, with known margins: Price what the service is worth to the client, and know your cost and margin behind every line.
Built to grow with the client: When a client adds staff, the price should follow without a new contract structure. Per-user pricing usually does this better than per-device.
See tiers and bundles on a quote
Bring one service you sell three ways. We will show it as clear options on a proposal.
Simplification Strategies
Standardise on three tiers. Define a fixed set of services and a clear price for each tier. Three options give clients a real choice without a long menu.
Bundle what belongs together. A new-starter bundle can hold the laptop, the Microsoft 365 licence and the managed endpoint service at one price. In Salesbuildr, a bundle sits on the quote as one line while each component syncs to your PSA for billing and delivery.
Consider all-inclusive packages. A package that combines hardware, software, services and support for one monthly price gives the client predictable costs. Some MSPs go further and tie part of the price to an outcome, such as an agreed uptime level. Only do that when you can measure the outcome and control what drives it.
Limit add-ons. Offer the handful of add-ons clients actually ask for. Handle anything else case by case.
Keeping the Plan Up to Date
Review prices when costs change. A vendor price rise, such as Microsoft's, should trigger a price review straight away. Schedule a full review at least twice a year.
Watch margin per service. A service with low margin quarter after quarter needs a new price or a cheaper way to deliver it.
Keep client-specific prices in one place. Agreed prices for one client belong in a pricing book with an end date, where every rep can find them. In Salesbuildr, pricing books hold fixed prices per client, take priority over catalog prices, and are checked for expiry when a quote is sent.
Let cost prices update themselves. Salesbuildr pulls cost prices from your distributors into the catalog and syncs with Autotask, ConnectWise or Halo, so reps don't quote from last month's prices.
Put agreed prices in one place
We will show a pricing book that overrides the catalog for one client, with an end date.
Rolling Out a New Plan
Train your sales team on the new structure before the first client sees it. Start with new clients, then move existing clients over at renewal, and tell them in writing what changes, from when, and why.
Measuring Success
Compare sales cycle length, win rate, average deal size and margin per service before and after the change. Also count how many quotes needed a price exception. If that number doesn't go down, the plan is still too complicated.
Want to go further? Download our free guide, The MSP Productisation Guide.
Related reading: Pricing, Bundles, and Portfolio Management.