From IT supplier to business enabler: why most MSPs get stuck

The step from IT supplier to business enabler is on every MSP strategy slide, usually as an arrow to the right with a bit of colour around it. And still the average account manager walks in at a client on a Tuesday morning with exactly the same story as three years ago: a price, an SLA, a ticket status. The board talks about transformation, the client notices nothing.

What you see happening everywhere: owners and boards have had the internal discussion, concluded that they have to support the client more broadly, and put the word “enabler” in the pitch. In daily practice the MSP is still a supplier of products and incidents. The pride sits in the product you deliver, not in what the client does with it.

That works as long as the client does not notice what is missing. But the mid-sized business owner on the other side is running into NIS2, into AI questions they cannot oversee, into data that is in order nowhere. They call their accountant. Not their MSP. While the MSP has a far better picture of what happens in their company. That is not the client fault. That is a positioning problem that you keep alive yourself by continuing to talk in technology.

From IT supplier to business enabler starts with language, not with a service

What works in practice is less spectacular than most transition decks suggest. No new proposition, no rebranding, no extra vertical. It starts with the question of whether the seller with their boot in the mud speaks the language of the client. Not “we deliver product X with 99.9% uptime”, but “how do you currently rent out your boats, and where does that process get stuck”.

That sounds banal, and it is. Except: most MSPs do not do it. They send round an account manager who thinks in quarterly cycles, with a pipeline that has to close somewhere, and who therefore works towards a quote in two conversations. In that time you do not get to know the client. You get to know their IT budget. That is something else. The difference sits in whether you are willing to go three or four conversations without naming a product.

A complete menu, or the orchestration in your hands

There is a second layer that sits deeper. An MSP of five or ten people can no longer oversee the whole security field, let alone AI governance, data classification and sector-specific legislation on top. That is not a weakness, that is simply the reality of the market in 2025. Anyone who acts as if they can do it all themselves loses the client within two years to a party that is more honest about what they can and cannot do.

The choice is then simple but hard: either you make sure your menu is complete by becoming part of a larger whole, or you explicitly choose a niche and arrange the rest through partners. What does not work is the halfway house. The MSP with fifteen services on its website, eight of which in practice are passed on to an external party with no orchestration, no governance, no ownership of the outcome. That is not a business enabler. That is a letterbox with an invoice attached.

That halfway house is not a stupid choice, by the way, it usually grew historically. A client once asked for something, you brought in a partner, it worked, and it has been on the site ever since. But what three years ago was a nice extra is now a risk. Because if the client calls once with an incident in that area and you have to put them through to someone who does not know them, you lose your orchestrating role in a single conversation. The question owners ask themselves too rarely: of which of my current services do I really hold the orchestration, and which do I actually leave to a supplier whose client I am myself?

What an orchestrating role means in practice

The role that structurally gets added is that of orchestrator. You used to keep an overview of a client install base: which servers, which licences, which contract. Before long you keep an overview of that same client agentic workforce: which bots are running, which data they see, which decisions they may take independently, where the governance sits. That is a completely different craft from managing endpoints, and it is hardly doable without scale at the back end.

In concrete terms that means: the modern workplace, the security baseline, patching, monitoring, the back office of your own company, all of it has to be automated to the point where it is invisible to the client. The time that frees up goes into the conversation that really matters. Going through roadmaps with the owner. Translating legislation into what it means for their continuity. Looking together at how data from their ERP and their CRM could be used for something they do by hand now. That is business enabling. Not switching on more AI, but helping to put it to work.

Why most transitions run aground on the organisation itself

What rarely comes up in strategy sessions: the brake is usually not the client, but your own team. An engineer who has been measured on tickets for fifteen years is not going to be rebuilt in a quarter into someone who sits next to a business owner on a Thursday afternoon to talk about how they run their company. That is a different kind of person, and sometimes a different job. Anyone taking the transition seriously splits those roles. One keeps doing technology, and does it excellently. The other sits at the front, digs into the client sector, reads the trade press the client reads, and knows the names of the client competitors better than the client does.

That is also where the commercial problem sits. Someone like that is expensive, and produces no demonstrable revenue in the first year. They build trust whose outcome only becomes visible in year two or three in cross-sell, renewals and referrals. That asks for an owner who understands that and is willing to give up margin temporarily for position. In the MSP market, where EBITDA multiples hang on acquisitions, that is a difficult choice. Yet it is exactly that patience which separates the parties still independent in five years from the parties that get swallowed or bought out.

The MSPs that win this transition over the coming years are not the most technical and not the smoothest talkers. They are the parties who have set up the back end so tightly that time is left for the front end, and who at the front have the nerve to talk about the client business instead of about the technology. Anyone who calls their clients back on time, keeps their agreements and digs into the sector they work in still earns an excellent living. Anyone who keeps leaning on the product as an anchor will be acquired or passed over within three years.