MRR tells you what a client pays. It does not tell you what they cost to support.

One P&L can hide several different businesses

Managed services, projects, licences, security products, hardware, consulting and ad-hoc support do not behave the same way.

A dollar of managed-service revenue can carry technician labour and stack costs. Project revenue depends on how efficiently the work is scoped and delivered. Hardware may carry a much thinner margin, while licensing can hide vendor commitments inside a blended number.

Which part of the business is actually making the money?

Two equal-MRR clients can have very different economics

The invoice can say the same thing about both clients while the operating data tells a very different story. Recurring revenue and recurring profit are not the same metric.

To understand client economics properly, the financial data may need to be combined with reliable PSA, time or service information.

Growing MRR can still hide margin pressure

An MSP can add customers while the cost base grows faster underneath it: engineers may be added ahead of utilisation, support load can rise faster than contract value, and vendor costs can move without pricing changing.

• Senior staff pulled into low-value support work
• Project work using capacity assumed for managed clients
• Customer environments becoming more complex
• Software and vendor commitments rising faster than revenue

Is the recurring revenue becoming more or less profitable to service?

Project work and managed services should not automatically be judged the same way

Project revenue can be excellent, but it can also hide poor utilisation, weak scoping or expensive senior delivery. Managed-service revenue can be predictable while hiding clients whose support burden has drifted beyond what the agreement was priced to support.

At the deeper service level, Kurrent can analyse recurring services, projects and other material revenue streams separately where the data supports it.