Shared P&L in an MSP partnership: the number that decides

A shared P&L MSP partnership sounds like pure logic on paper. In practice we see something else: two partners at the same table, drinking the same coffee, while quietly fighting each other out of the building because every quarter only their own column counts.

You probably recognise the pattern. Two or three owners, each with their own branch: one runs the service desk, another does projects, the third sits on cloud or security. The management agenda says "grow together". In reality everyone has their own P&L, their own bonus, their own people who are not lent out when the neighbour starts complaining.

The moment something goes wrong, at a client, on a deal, on a migration that overruns, nothing gets shared. Fingers get pointed. The project side says service is not picking it up. Service says the project was half delivered. And the client? Stuck between two invoices and one problem. This is the point where a partnership stops being a partnership and becomes a tenancy agreement with shared coffee.

What a real shared P&L does inside an MSP

What works in practice is not another offsite about standing together. It is one number at the top that everyone is judged on, before the individual columns. If the recurring margin of the whole business drops below the line, every partner feels it in their own pocket. If it does not drop, everyone shares in it. No separate pots, no "my team hit its figures".

That sounds hard, and it is hard. But it is the only mechanism that changes behaviour. The moment the service partner is financially better off when a project colleague lands a deal, he picks up the phone himself to help scope it. Not out of collegiality, out of self interest that happens to line up with the interest of the business. That is the difference between collaborating on paper and feeling the pain and the success together.

The same applies to your largest clients

The partnership idea does not stop with the owners. At your top ten clients exactly the same dynamic plays out. As long as you send an SLA invoice and they send back a purchase order number, there is no partnership. There is a supplier contract with a QBR glued onto it. As soon as something goes wrong, and something always goes wrong, the question becomes "who pays for this" instead of "how do we solve this".

When a client relationship tips into partnership

The clients where it does work have one thing in common: there is a joint number both sides steer on. Uptime tied to their revenue. Ticket volume tied to their productivity. Migration speed tied to their own deadline towards their customer. The moment your performance has a measurable effect on something the client already steers on, something resembling a partnership appears. Without that number it stays procurement.

A partnership without a shared interest is a signature, not a relationship. That holds inside your board, and it holds between you and your client. If everyone has their own success and their own P&L, collaboration does not happen by itself. It only happens by itself the moment one of you can no longer win unless the other wins too. That is not a culture programme that runs for a year. It is a choice in how you build up the figures, and who gets which bonus.

Most MSPs that get stuck on partner conflict or client erosion do not have a communication problem. They have a structural problem in how success is measured and divided. Fix that number at the top and the behaviour underneath follows within a quarter. Leave it alone and no offsite is going to sort it out.