Skip to content
Menu

Move From Break Fix to Managed Services at a Fair Price

Move from break fix to managed services with a costed offer, then check actual delivery margin before widening your conversion campaign.

MSP owner and client review a proposal to move from break fix to managed services at a meeting desk

Before, the client calls when something breaks and pays for the repair. After, you own an agreed service for a monthly fee. Moving from break fix to managed services means pricing that new work, then checking what it actually costs. A signed proposal is a sales result. It isn't a margin report.

Say you're quoting the model's 20-seat US client at its $225 seat-price goal. That produces $4,500 a month. The model sets a $2,000 monthly client minimum and favors a $3,000 to $7,000 band. Those figures help you shortlist clients; they don't prove you can serve one profitably.

Choose Clients You Can Serve on Your Standard Stack

Start with the clients you already know, then check what you don't know. Read the work history and ask your technicians what the environment needs. Check whether the client pays as agreed and will accept your standard stack.

Don't infer a cheap managed account from a quiet repair history. The client might have put work off or sent it elsewhere. Ask what they've been doing between your visits before estimating the service you're about to take on.

Here is what I'd cut: the generic conversion email sent to every break-fix account. Build the shortlist first. For each client, record why the offer fits and what you'd need to change before your team could support it properly.

If you can't establish the work, keep discovery as the next step. Marketing can't make an unknown environment cheap to manage. A friendlier proposal won't supply the missing estimate either.

Compare the New Work With the Old Invoice

For the hypothetical client, the old invoice pays for requested repairs. The new agreement puts your MSP in charge of a continuing service. Show the buyer what they'll get and how they'll ask for help, rather than expecting the phrase managed services to explain the difference.

Write what the flat fee includes. Keep separately priced work visible so the client can compare the offer with what they need. Use the proposal to settle the difference before a technician has to explain it during a ticket.

The model includes baseline security in every plan, with advanced tools as add-ons. Show the baseline plainly in the proposal:

  • Endpoint protection is included.
  • MFA is included.
  • Awareness training is included.
  • Email protection is included.

Explain what each part means for the service the client buys. They shouldn't have to decipher a product list to understand the monthly fee.

Price the Commitment Before Pitching the Saving

Last year's repair bill shows what the client bought last year. It doesn't price everything you'll do under the new agreement. Estimate the labor and tools for the actual managed work, including the account work outside the help desk.

Use burdened pay for labor. Include technical work you do yourself instead of making the account look cheaper because the owner handled it. Then compare the fee with the cost on the same monthly basis.

The model's managed-service target is 50% gross margin, fully loaded with burdened labor and tools. Divide the relevant delivery cost by 0.50 to calculate the revenue needed at that target. The gross profit still has to pay for overhead and sales, with a fair-market owner salary counted before you claim profit.

Check your all-in seat price as well: recurring revenue divided by seats. The model counts the larger of users or devices as seats and sets a US floor of $150. That's a danger line, not a price to aim for. Use the $225 goal as the pricing reference, then test your actual costs.

The example's $4,500 clears the minimum and sits in the preferred band. You still need the cost calculation. If the proposed work misses the margin target at that fee, a place inside the band won't pay for the gap.

Budget the Transition Without Discounting the Monthly Fee

Here is what I'd cut next: the introductory recurring discount used to get a hesitant client over the line. The model keeps the monthly fee intact. If you offer the usual onboarding concession, quote that fee and include it free when the client signs.

The work hasn't become free to you. The model budgets 60 project-engineer hours for a new client's onboarding, outside the desk's capacity. Use that as a planning reference and scope the actual conversion. Knowing the client already doesn't establish how much work the move will take.

Keep a remediation project separate where the environment needs one. Agree what must change to meet your standard stack and price that work. If an existing account already has a weak margin, check whether fixing the environment can reduce its hours before relying on a price rise.

Have the project scheduler check the work before you promise a start date. Have finance check when the actual project payments and managed fees arrive. Waiving onboarding leaves the labor to fund even though you won't collect an onboarding fee.

Put the Ongoing Terms Beside the Price

A flat monthly fee needs a plain account of what it buys. Put these points in the proposal and agreement so the client and your team can use them:

  • State the included services and exclusions, with the price or quoting process for extra work.
  • Explain the user and device counts used for seats and how changes affect the bill.
  • Name the required standard stack and agree any remediation before managed support starts.
  • Show the baseline security included in the plan and the separately priced advanced options.
  • Write in the fixed annual price step and explain how you’ll notify the client ahead of it.

The model uses a fixed 5% annual increase written into the agreement and communicated in advance. It doesn't repair an inaccurate starting scope or seat count. Your technicians and your contract should promise the same service.

Confirm the handoff before the managed start date. Give the desk the agreed scope and the route for questions about it. Don't make the first support call the moment your team learns what sales promised.

Count Delivered Margin Alongside Conversions

Record offers and decisions in the CRM, with the scope and price attached. Ask why a suitable client declined. A higher acceptance rate could mean you've improved the offer, or it could mean you've quietly made it cheaper.

After service starts, have the service lead compare the actual labor and tools with your estimate. Then have finance check what you billed against what it cost and whether the client paid. No time logged doesn't mean no work done. Chase the entries.

Grade margin and fit quarterly, as the model recommends. I'd pause a wider conversion campaign if delivered managed-service margin misses the 50% target, then investigate the work and estimate. Record that check with the agreement in your PSA and financial review so the decision rests on the account you actually delivered.

The model's recurring-revenue goal is 70%, counting managed services and recurring product. Read that mix beside profit and the work your team can handle. Choose a suitable client, price the service, and inspect the result before sending the same offer to the rest of your shortlist.

Written ByOwen Gallagher

Staff Writer, Marketing and Growth. Owen Gallagher covers marketing and growth for MSP Outpost. He is mostly interested in what can be measured and what should be cut.

More by Owen

mspoutpost.com/articles/move-from-break-fix-to-managed-services-at-a-fair-price

Written by Owen Gallagher
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.

Welcome Back

Sign in to your MSP Outpost account.