Per-user, per-machine and other pricing models can make sense in certain situations. It is also handy because you can price your service based on bundles (e.g., you can charge a set rate for the first 500 gigabytes of backed-up data, then another rate for the next 500-gigabyte bundle, and so on). In general, billing per storage unit (e.g., per gigabyte) of data that you back up is the simplest approach. In this case, managed backup pricing depends on your situation. In this case, it’s worth charging extra for the high-value DR you are providing.įurther reading Add DRaaS to Your MSP Offering Q: Do You Bill Per-Storage Unit, Per-Machine, Per-Employee, Per-User or Something Else? You will need to live “mirror” data infrastructure that you can use to perform a DR quickly, and you will need the right staff on hand to perform the DR whenever it is necessary. On the other hand, if your client has strict RTO and RPO needs and can tolerate very little downtime, you’ll need to spend a lot more effort ensuring that you can meet those requirements. If your client can tolerate some downtime and it is relatively easy to restore data to the client’s devices, consider offering DR as part of your general service package, at no additional charge. The answer to this question depends on which kind of DR services your client needs.

Q: Do You Include DR in Your Offering or Provide It Separately?

Msp360 managed backup pricing