MSP 2.0 Trends: Part One

    Written by HarmonyPSA on 2017-04-24 Last updated 2018-06-27 - 2 minute read

As managed services providers (MSPs) move from break/fix to service contract (whether pre-pay or not), they have a clear decision to make regarding their billing models. Do they stay with incident-based billing or move up to the more recent all-inclusive device-based billing model, sometimes referred to as AYCE (All You Can Eat).

As increasing automation in remote monitoring and management (RMM) tooling drives more advanced MSPs towards the latter, this blog discusses the pros and cons of both models and (naturally enough) the professional services automation (PSA) functionality needed to support them.

Incident-based billing is not quite the same as break/fix (B/F). The latter relied on a reaction to a failure somewhere in order to intervene, basically someone working a ticket and booking their time.

RMM tooling, designed specifically to help MSPs avoid such failures, presented a problem as the better they got at proactive avoidance, the less revenue B/F organisations made, in fact the less benefit their customers saw in their services as systems became increasingly reliable (some of this being a natural trend in technology, some due to increasingly more powerful and sophisticated RMM tools preventing the break in the first place). The result was break/fix moved to true incident-based where an RMM alert auto-closure can trigger a billing event directly before the failure and without a tech touching anything.

Now the problem is that most PSA tools don’t support direct auto-closure as a billing event as they were built in a time when ticket time bookings drove support billing. In many cases this limitation is currently being solved with fake t/s bookings, though direct incident (i.e. ticket) closure auto-debiting a fund is now available in the latest PSAs.

This automation trend, as RMMs get better, causes a logical shift to device-based AYCE billing. As the RMMs are licensed by device, this model makes perfect sense because then revenue scales directly with direct cost, not via a tech’s timesheet.

The challenge for the PSA tool here is three-fold:

  • To be able to automatically generate a periodic invoice broken down by device price group and customer and to have this either debit a prepayment fund or raise an invoice line automatically, together with full device listing back-up sheets.
  • To understand the cost of goods per device by modelling the volume contract on the buy-side simultaneously.
  • To understand whether the model, for different asset mixes, is returning the right margin. For this latter point, all tech time on that fund and the device monitoring costs need to be bootstrapped in real-time, once again automatically.

However, PSA tools are now emerging that can handle these situations without manual intervention so the time is coming when RMM tools will become a direct money earner via more advanced integration allowing MSPs to scale their profitability without increasing staff.

Read the other posts in this series:

MSP 2.0 Trends: Part Two

MSP 2.0 Trends: Part Three


About the Author: Harmony Business Systems Ltd (HBS) is the company behind HarmonyPSA, the most complete cloud PSA software on the market. Developed with functionality to cater for even the most complex needs of MSPs, VARs, ISVs and Professional Services organisations, HarmonyPSA truly is the next generation of PSA systems. Follow HarmonyPSA on , LinkedIn or Website

Tags: All You Can Eat contracts, Business, device-based billing, MSP billing trends, MSP Business, msp future trends


Recent posts

Subscribe to our blog