NewActiValet is here. Introductory offer: 25% off your first 12 months when you sign up by December 31, 2026.See it →

The Backup Billing Shift MSPs Can't Ignore

Rodney Hall, COO

A reservoir wall showing an old high-water stain far above the current, lower water level.

The biggest operational trend in MSP backup and BCDR right now is not a new threat. It is billing. Vendors are moving away from usage-peak pricing toward committed-minimum contracts, which turns backup capacity planning into a budgeting discipline your operations team has to own, not a technical setting support staff adjust later.

What changed in backup billing, and why now?

Vendors are retiring high-water-mark billing for backup and RMM platforms and moving to committed-minimum-quantity contracts instead of charging for whatever peak you ever touched. Kaseya has moved Datto RMM, SaaS Protection, and Autotask off the high-water-mark model and onto a committed-minimum-quantity (CMQ) structure, saying the change is designed to support how MSPs actually use its solutions rather than just their peak usage.

Autotask's own FAQ confirms the change applies starting with the December 1, 2025 invoice, and that the per-unit rate itself does not change under CMQ. For backup specifically, SaaS Protection locks each subscription's committed minimum at the usage level calculated in November 2025, and that floor stays static from that point forward. The floor is not a soft guideline, either: Datto RMM's billing FAQ states that reductions to your committed minimum can only happen at contract renewal, and that the previous 10% overage buffer no longer applies. That same FAQ scopes the policy to Datto RMM, Advanced Software Management, and Ransomware Detection licenses, while leaving Kaseya 365 Endpoint licenses out of the new model for now.

Billing modelHow usage above the floor is billedHow reductions are applied
High-water-mark (retired)Invoice reflected the highest usage point ever reached during the termA usage drop did not lower the bill until the term ended
Committed-minimum-quantity (current)Invoice reflects usage above the committed floor, with no overage bufferThe floor can only be lowered when the contract renews

What this means if you resell backup under your own contracts

If you quote backup or BCDR to clients as a flat per-seat or per-device fee, a fixed committed-minimum floor sitting underneath that pricing changes your own math. You are no longer paying your vendor in rough proportion to what you bill your client that month. You are paying a fixed floor regardless, and your client-facing price has to cover that floor even in a slow month, not just an average month. Pricing a managed backup service without accounting for that floor is one of the easier ways a profitable-looking contract quietly stops being profitable.

How does committed-minimum billing change BCDR operations?

It moves the risk of a sizing mistake from the vendor to you. Under the old model, a seasonal spike in onboarded devices or a short-term integration project cost you for the rest of the term, which was frustrating but at least tracked real usage. Under a committed-minimum model, you can end up holding a floor sized for growth that never showed up, and you cannot shrink it until renewal.

Hypothetical example: say an MSP commits to a floor of 400 protected seats when it signs a two-year renewal, expecting steady growth from new client wins. Six months later, the MSP loses a 60-seat client to an acquisition and never backfills that volume elsewhere. Usage drops to 340 seats, but the bill stays pinned to the 400-seat floor for the remaining eighteen months of the term, since the commitment cannot be adjusted until renewal. Those 60 unused seats are pure margin loss on a service the MSP is still trying to price competitively against other bidders.

That dynamic turns backup and BCDR capacity planning into a recurring finance-and-operations exercise rather than a one-time setup task. Your team needs a standing process for tracking protected-seat counts against committed minimums, flagging when an offboarding client or a tech refresh will leave you overcommitted, and timing renewal conversations around realistic growth instead of whatever number a vendor rep first proposes. Treat the renewal date itself as your one real control point, since it is the only moment the floor can move.

Building and running that kind of capacity discipline is an operational skill, not a technical one, and it belongs with whoever owns vendor contracts and service delivery, working alongside whoever owns the technical backup console rather than instead of them. Forge University trains MSP staff to run exactly this kind of operational discipline, rather than leaving a team to improvise it after a surprise invoice.

Why is BCDR carrying more of MSP revenue now?

Backup and BCDR are no longer a bundled afterthought inside a support contract. The 2026 Kaseya State of the MSP Report found that 79% of MSPs now offer backup and recovery as a managed service, which means most of the market already treats it as a standalone, billable practice. That finding comes from a report built on feedback from more than 1,000 managed service providers, which gives it more weight than a single vendor's informal read on the channel.

As BCDR becomes a bigger, more visible line of business, the billing model underneath it stops being a back-office detail. A committed-minimum contract sized wrong does not just inflate a vendor invoice, it quietly erodes the margin on the service you are actually selling clients. Pricing your BCDR offering without first understanding your own committed-minimum exposure is how a growing practice turns into a thin-margin one without anyone deciding that on purpose.

The same report frames BCDR growth and billing exposure as moving together. Kaseya's own summary of the 2026 State of the MSP Report lists how security and BCDR continue to drive consistent revenue growth as one of its central findings. That growth is happening in the same practice area now running on a less forgiving billing floor, and treating growth and billing exposure as separate conversations is how the billing side gets ignored until it shows up in a margin review.

What belongs in your operational playbook for this shift?

A practical response does not require dropping any vendor. It requires a short, recurring checklist your operations team actually runs instead of a policy that lives in a folder:

  • Pull current protected-seat and license counts for every backup and BCDR contract at least once a quarter, not only at renewal time.
  • Compare actual usage against your committed minimum before you negotiate the next term, so the floor reflects your real book of business rather than a growth forecast.
  • Flag any client offboarding or consolidation right away, since a dropped seat lowers your usage but not your commitment until renewal.
  • Keep every backup and BCDR renewal date on a calendar your service-delivery lead owns, not buried inside a vendor billing portal only accounting checks.

None of this requires new backup technology. It requires treating your vendor stack like any other recurring cost center, with visibility and a review cadence attached to it. Put one person's name next to each backup and BCDR contract as the owner who signs off before any renewal, instead of letting the renewal auto-process because nobody flagged it in time. Auditing what is actually running in your stack against what you are committed to paying for is the starting point, and it is worth doing before your next renewal notice arrives rather than after an invoice surprises you.

If backup, BCDR, and the rest of your tool stack have been accumulating without that kind of review, the full white-label catalog is a reasonable place to see what else in your stack could use the same scrutiny.

Backup and BCDR are not getting simpler to run. They are getting more consequential, operationally and financially, at the same time. Treat committed-minimum billing as a planning input alongside your SLAs and recovery targets, not paperwork you handle when the renewal notice shows up.

See the full stack