I see a lot of MSP owners get into trouble at the point where the business starts to feel slow.
The pipeline is not moving the way it used to. The team meeting feels a bit flat. The same service issues keep coming around again. Nothing is broken enough to panic, but nothing is improving enough to create energy either.
That is a dangerous place to sit, because a quiet business rarely stays quiet for long.
Borrowing from the wrong playbook
When progress gets hard, the temptation is to look sideways. You see another MSP posting about a new offer, a new pricing model, a new automation stack, or a new AI service, and the instinct is to copy it.
I understand why. Doing something feels better than sitting with the problem. A fresh tactic gives you the sense that movement has returned.
The issue is that another provider may not be playing the same game as you.
A fifty-person MSP with dedicated account managers, mature project delivery, and a bench of engineers can make moves that will punish a ten-person business still trying to standardise its support desk. A one-person consultant can make promises that a larger team cannot deliver consistently. A cybersecurity-focused provider can price and position differently from a generalist MSP still carrying legacy client expectations.
The tactic may be sound. It just may not belong at your stage.
Progress needs context
This is where I think Microsoft 365 Copilot becomes useful, not as some magic answer, but as a way to get clearer about the current state of the business.
Before chasing the next idea, I would rather see an MSP owner ask Copilot in Teams to summarise recurring themes from recent leadership meetings, or use Copilot in Outlook to pull together the common patterns in customer escalations. If the team keeps discussing noisy clients, delayed projects, margin pressure, or weak documentation, that is a signal.
Then take that signal into Excel. Look at ticket trends, project slippage, licence margin, and client profitability. The goal is not to produce a beautiful report. The goal is to work out what level of the game you are really in.
Are you trying to win new business when delivery is already stretched? Are you selling AI readiness while your own SharePoint permissions are messy? Are you chasing strategic advisory revenue while your QBR process is still a slide deck built the night before?
That is not failure. That is feedback.
The next move should fit the level
Good strategy is not about copying the smartest-looking move in the market. It is about choosing the move your organisation can actually absorb.
For one MSP, that might mean tightening onboarding before launching a new managed Copilot service. For another, it might mean cleaning up agreement profitability before hiring another technical resource. For another, it might mean using Planner and Teams to create a simple weekly operating rhythm, so the leadership group can see what is stuck before it becomes expensive.
None of that sounds glamorous. That is partly the point.
A business usually regains energy when it can see progress again. Not noise. Not theatre. Real progress. A decision made. A blocker removed. A client segment clarified. A service standard improved.
The MSPs I see do well are not always the ones with the cleverest tactic. They are the ones with enough discipline to ask, “What game are we actually playing right now?” and enough honesty to answer it.
That is where momentum comes back.
Not from copying someone else’s move, but from making the next right move for your own business.
CIAOPS 