MSP Service Tiers: How to Package Good-Better-Best Managed Services

MSP service tiers work when each tier is priced from what it costs you to serve and the risk you carry, and when each tier has one clear job on the quote.

Most MSPs end up with tiers by accident. A bundle gets built for the first big client, a cheaper version gets made for the next one who pushes back, and a third appears when someone wants compliance help. Two years later there are three names on the pricing sheet, a dozen custom exceptions in the agreements, and nobody can say which tier makes money.

This guide is for the vCIO or account lead who builds renewals, and for the owner who signs off the prices. It covers why both common approaches leak margin, the job each tier does, a worksheet for pricing a tier from cost, what to keep out of tiers, how to present them, and how to move existing clients at renewal. The tier template is near the end.

Why a la carte and one-size bundles both leak margin

A la carte pricing looks flexible. In practice the client picks the cheapest combination, skips the security pieces, and calls you when something breaks that you were never paid to prevent. You end up doing the work anyway, because the client sees you as the IT department either way.

A single bundle has the opposite problem. One price for everyone means your lightest clients overpay and your heaviest clients get a discount they never asked for. The heavy ones stay, the light ones shop around, and your average account drifts toward the expensive end.

Tiers sit between the two. Each tier is a fixed package with a known cost, and the client chooses a level of coverage instead of a list of parts. That only holds up if the tiers are built from your costs. If they are built by copying a competitor's feature grid, you inherit their margin problems along with their column headings.

If you haven't checked your floor price yet, start with the MSP pricing math guide. Every tier has to clear that floor.

Give each tier one job

Three tiers, the familiar Good-Better-Best shape, is a sensible default because it gives you three distinct jobs. You can run two or four, but each extra tier needs a job of its own or it just adds a decision the client has to make.

Two rules keep the jobs clean.

Essentials still has a floor. Decide which controls you won't support a client without, such as MFA, endpoint protection, patching, and backup for critical data. Those go in every tier. If a client won't pay for them, the right answer is usually a polite no.

The step between tiers should be easy to explain. "Standard adds security awareness training, after-hours response for critical issues, and a quarterly review" is a sentence a client can repeat to their partner. A list of fourteen line items is not.

Price each tier from cost to serve

Price a tier per user or per device, whichever unit matches how your work actually grows. The per-user vs per-device pricing guide covers that choice. Then build the price from three inputs:

1. Stack cost. What the tools in the tier cost you per unit each month, including security, backup, and management tools.
2. Labor. Expected support hours per unit per month, multiplied by your loaded hourly cost. Use your own ticket history by tier where you have it.
3. Risk and compliance load. The extra time for reviews, documentation, evidence, and the higher stakes of clients with regulatory obligations.

Add the three for cost to serve, then divide by one minus your target gross margin to get the price.

The numbers below are a labeled scenario. They show how the worksheet works and are not benchmarks. Use your own stack costs, ticket history, and labor rate.

In this scenario, a 25-user client pays $2,000 a month on Essentials, $3,275 on Standard, and $5,100 on Premium.

Notice that the target margin rises with the tier. Premium clients usually carry more risk and more senior time, so the margin has to absorb the surprises. If your Premium margin comes out lower than Standard, the tier is underpriced or overloaded.

For more on where quoting loses margin after the price is set, see the MSP pricing and quoting margin guide.

Decide what stays out of every tier

The fastest way to break a tier is to let project work and one-off requests leak into it. Keep these as add-ons or separate quotes, whatever tier the client is on:

• Projects. Migrations, office moves, refreshes, and new deployments get their own scope and price. The MSP scope of work template covers how to write them.
• Compliance evidence. HIPAA, CMMC, and cyber insurance work involves documentation and audit support that varies by client. Price it on its own. The MSP compliance pricing guide walks through how.
• Hardware and licensing. Pass these through at their own lines so a vendor price change doesn't eat your tier margin.
• On-site visits beyond an agreed allowance. Set the allowance in the tier, and bill what goes over it.
• After-hours work for non-critical requests. Critical response can live in a tier. "Can you set up my new laptop Saturday morning?" should not.

Write the exclusions into the agreement in plain words. A tier is only as clear as the list of what it doesn't cover.

Present the recommended tier first

Lead with the tier you recommend, and show why it fits this client. Then show the other two as context. If you lead with the cheapest tier, every step up reads as an upsell. If you lead with your recommendation, Essentials reads as what the client gives up to save money.

A few habits help:

• Tie the recommendation to something from discovery, such as "you handle patient records" or "you lost two days of work in the last outage."
• Keep tier names plain. Essentials, Standard, and Premium are boring, and that is fine. Clients should spend their attention on what's inside.
• Show the upgrades as options the client can add, so the client can grow coverage without changing tiers.

Before a tiered quote goes out, run it through the MSP quote approval checklist, especially any discount on the recommended tier. For the document that wraps the quote, use the MSP service proposal template.

Move existing clients between tiers at renewal

New tiers are easy for new clients. The hard part is your existing book, where clients are on old bundles, custom deals, and prices set years ago.

1. Map every client to the nearest new tier. Compare what they get today with each tier, and note the gaps.
2. Sort them into three groups. Clients who already fit a tier, clients who are underpaying for what they get, and clients who are missing controls you now require.
3. Time each move to the renewal date. The MSP renewal calendar template shows who renews when, so each change lands on a date the agreement allows.
4. Make the case in a review. Bring the gap list to the client's next business review. The vCIO account management guide covers how to run that conversation as part of the account plan.
5. Send the change in writing. If the move raises the price, the MSP price increase letter template gives you a letter that separates the re-scope from any rate change.

Some clients will stay on a legacy plan for a while. That's acceptable if you set an end date and the legacy price still clears your floor. A legacy plan with no end date becomes a fourth tier you never meant to offer.

MSP service tier template

Copy this table into your pricing sheet, then fill in your own components, costs, and prices. Mark each cell as included, limited (with the limit), or add-on.

Review the table every year with real numbers. If one tier's actual labor hours run well over the estimate, either the price moves or something comes out of that tier.

Quote tiers the same way every time

A tier only protects margin if the quote matches it. When reps rebuild each tier from a blank spreadsheet, components get dropped, prices drift, and the agreement stops matching what was sold.

Scopable's quoting workflow keeps that consistent. You start from the client and opportunity, put the tier on the quote as a bundle, and choose whether the client sees the components inside it. Upgrades can sit on the public quote as optional add-ons, so the client ticks the ones they want and sees the one-time, monthly, annual, and term totals update before they sign. Scopable records which add-ons they took and preserves the sent version.

To build your tiers as bundles and quote the next renewal from them, start Scopable for free.