You Don’t Have a Business Problem. You Have an Owner Problem.

I’ve watched a lot of MSP owners over the years, and the pattern is almost always the same. They tell me their business runs on hard work. Long days, early starts, the willingness to do whatever it takes. And for a while, that’s exactly what built the thing.

But here’s the uncomfortable bit. All that effort didn’t make them an owner. It made them the best technician in the building — the one person who can’t leave the room.

The tell-tale signs aren’t technical

You know the feeling. The phone buzzes and your stomach tightens before you’ve even looked at it. You’re “on holiday”, but you’re really just answering tickets from a nicer chair. The people at home get whatever’s left after the business has taken the good hours.

I used to think those were signs of a busy business. They’re not. They’re signs of an owner who has wired the whole operation around themselves. Every approval, every escalation, every “let me just check that” runs through one person. That’s not a scaling problem. That’s an identity problem.

A business is a mirror. It reflects whoever built it — their habits, their fears, their inability to let go. If you can’t step away, it’s usually because, somewhere along the line, you decided being needed was the same as being valuable.

Hard work hides the real bottleneck

The reason this is so hard to see is that effort feels like progress. You’re busy, so you must be building. But more hours rarely fix a business that depends on your hours.

What actually moves the needle is taking the knowledge living in your head and putting it somewhere the team can reach without you. This is where the tools earn their keep. When a senior tech finishes a tricky onboarding, Copilot in Teams can pull a clean summary of what was decided and who owns what, so the next person isn’t starting from your memory. Ask Copilot in Word to turn that into a repeatable runbook, drop it into a SharePoint site, and suddenly the process belongs to the business, not to you.

Same with the inbox that owns your attention. Instead of being the human router for every client question, let Copilot in Outlook draft the first reply and surface what genuinely needs your judgement. The goal isn’t to answer faster. It’s to stop being the only one who can answer at all.

Build the owner first

This is the shift I keep coming back to. You don’t escape the trap by working less or hiring more. You escape it by changing who you are inside the business — from the person who does the work to the person who builds the thing that does the work.

That means writing down how decisions get made, not just making them. It means letting Planner and Loop hold the to-do list so it isn’t all in your head at 11pm. It means being okay with the team doing it 80% your way instead of 100% your way and the work never getting done without you.

I’ve seen owners break through a ceiling they’d been stuck under for years, and it almost never starts with the business. It starts with them deciding to stop being indispensable.

Your business will only ever grow to the size of the owner behind it. So the real question isn’t how to work harder. It’s who you’d need to become for the business to run beautifully on a day you don’t show up.

Stop Collecting Tactics. Fix the Three Things That Actually Matter.

I had a coffee recently with an MSP owner who pulled out his phone and showed me his “growth list.” Forty-three items. Webinars, a TikTok plan, a referral scheme, a rebrand, three new service bundles, a partnership he’d been chasing for a year. He was exhausted just reading it to me. And his revenue had barely moved in eighteen months.

I told him I’d happily help him cross off forty of those. Because in my experience, almost every stuck MSP is stuck on the same three things, and the rest is just noise dressed up as activity.

You’re Easy to Overlook

The first problem is that nobody can quickly say what you do or why they’d pick you. Walk into most MSP websites and you’ll find “managed IT solutions for growing businesses.” That sentence could belong to ten thousand others. If a prospect can’t repeat your offer back to a colleague in one breath, you don’t have an offer — you have a category.

This is the part I’d fix first, and it’s the part owners avoid because it forces a decision. Open a blank document and ask Copilot in Word to help you rewrite your core offer five different ways for a specific type of client — say, a 30-seat accounting firm worried about email fraud. Then read each one out loud. The version that sounds like a real person warning a real business is the one you keep. Specific beats clever every single time.

You’re Invisible Because You’re Inconsistent

The second problem isn’t that your marketing is bad. It’s that it shows up once a quarter, when you remember, when things are quiet. Then a big project lands, you go heads-down, and the market forgets you exist. Invisibility isn’t a talent problem. It’s a rhythm problem.

The MSPs who get noticed aren’t louder — they’re just regular. One short, useful thing a week beats a brilliant campaign you run twice a year and abandon. Build the rhythm into the tools you already live in. Draft a month of client-facing tips in a SharePoint document, drop the publishing dates into Planner, and let a scheduled Outlook reminder nudge you every Monday morning. The point isn’t sophistication. It’s that the thing keeps happening whether you feel inspired or not.

Sales Feels Awkward, So You Undercharge

The third one is the quiet killer. Plenty of capable owners walk into a sales conversation, sense the tension when price comes up, and instinctively shave the number to make the discomfort go away. Then they wonder why they’re working flat out and still underpaid.

Awkwardness usually comes from walking in unprepared and hoping to wing it. Before your next prospect call, ask Copilot to pull together what you already know — recent emails with that contact, notes from earlier meetings, the brief from your discovery call — into a one-page summary of what they actually care about. When you walk in knowing their world, you’re not selling. You’re advising. And advisors don’t apologise for their price.

The Real Work Is Subtraction

What struck me about that coffee was how relieved the owner looked when I told him to bin most of the list. We’re trained to believe progress means adding more. With this stuff, it’s almost always the opposite.

Get your offer clear, show up consistently, and stop flinching on price. Do those three, and you can ignore nearly everything else. The forty-three-item list was never the path forward. It was just a very busy way of avoiding the three things that mattered.

Stop Holding People Accountable. Start Building Momentum.

There’s a conversation I’ve watched play out a hundred times, and it always goes the same way. Someone agreed last week to get a thing done. This week, they didn’t. So the check-in begins. Did you finish it? No. Why not? And then comes the explanation — the kids were sick, a client blew up, the week got away from them. By the end they feel small, the task gets shuffled forward, and everyone agrees to try again next time.

Then we run it back. Same script, same shrinking feeling. And here’s the part nobody admits out loud: the simplest way to make that bad feeling stop is to walk away from the whole arrangement entirely. People don’t quit because they’ve failed. They quit because the relationship has quietly become a source of guilt.

I see this with MSP owners constantly. They build accountability structures for their teams, their clients, even themselves — weekly stand-ups, status trackers, a long list of overdue commitments staring back at them. And the structure, the thing meant to drive progress, becomes the thing people learn to dread.

Accountability is a low ceiling

The uncomfortable truth is that accountability only works on people who don’t really need it — and even then, only for a while. It’s a tool built around the assumption that someone has to be watched or they’ll drift. Chase the high performers in your business with that energy and watch how fast they disengage. The good ones already hold themselves to a higher standard than you ever could. They don’t want a minder checking their homework. They want to get somewhere, faster.

So I stopped asking whether things got done. When I sit down with someone now — whether it’s a one-week review or a full six-week stretch — I ask two questions only. What went well? And what did this teach you? That’s it. Everything else from the past is noise. The misses, the excuses, the guilt — none of it moves you an inch forward. The wins tell you what to repeat. The lessons tell you what to change. The rest is dead weight you’re dragging into next week for no reason.

From rear-view to road ahead

Once those two things are on the table, the conversation flips direction. We’re no longer auditing the past — we’re using it. We find the one obstacle actually slowing the person down, we clear it out of the path, and we decide the very next move. Look back only long enough to learn, then point everything forward.

This is where the tooling matters more than people expect, because most of the friction that kills momentum is small, dumb, and repeatable. Someone “forgot” to follow up because the note lived in their head instead of anywhere useful. A commitment vanished because it was never written down where the team could see it. That’s not a discipline problem. That’s a system problem, and systems are fixable.

Inside Microsoft 365, this gets a lot easier. When I close out a planning session in Teams, I’ll ask Copilot to pull the wins and the agreed next moves straight out of the meeting transcript, so nobody’s relying on memory by Friday. The actual commitments go into Planner as real tasks with owners and dates — visible, shared, alive — not buried in someone’s inbox. A Loop component pinned in the channel becomes the running scoreboard the whole team can glance at. And first thing in the morning, Copilot in Outlook surfaces what’s drifted and what’s due, so the next move is obvious before the day even starts. None of that is about catching people out. It’s about removing the friction that quietly steals forward motion.

Speed, not surveillance

This is the shift I’d put to any MSP leader still running their team on guilt. The higher someone performs, the less they need policing and the more they crave progress. So give them progress. Clear the road, name the next step, and get out of the way. Momentum compounds — one clean win makes the next one easier, and before long the person isn’t being pushed at all. They’re pulling.

If what you want is someone standing over your shoulder reminding you of everything you haven’t done yet, I’m honestly not the right person for that. But if you want the obstacles gone, the path clear, and the next move obvious so you can win quicker — that’s the whole job. Stop counting what’s overdue. Start building what’s next.

AI Doesn’t Care About Your MSP Business Model

I’ve been thinking about a question that might make some MSPs uncomfortable.

Should the next technology revolution be guided by the same people who have spent the last twenty years building businesses that depend on things staying exactly the way they are?

That sounds harsh, but hear me out.

Every major technology shift creates winners and losers. Cloud changed the value of servers. Microsoft 365 changed the value of maintaining Exchange on-premises. Remote monitoring and management changed the need for technicians driving between customer sites. AI is now doing the same thing to knowledge work.

Yet when I talk to some MSPs about AI, I often hear the same response.

“It’s not ready.”

“Our clients aren’t asking for it.”

“We’ll wait and see.”

“They still need us to do the basics.”

Maybe. But that’s exactly what people said about cloud computing.

The Incentive Problem

The challenge isn’t that MSPs don’t understand technology. Most understand it very well.

The challenge is incentives.

If you’ve built a successful business around selling licences, managing devices, responding to support tickets and charging for technical expertise, then AI creates a problem. The more capable AI becomes, the more it starts consuming activities that have traditionally generated revenue.

If a Microsoft 365 Copilot prompt can analyse a meeting, draft a proposal and create an action plan in minutes, what happens to the hours previously spent doing that work?

If an AI agent can resolve basic support requests, summarise conversations and retrieve information from SharePoint or Teams, what happens to the service model built around handling those requests?

It’s understandable that some MSPs look at this and feel uncomfortable.

But technology has never cared about existing business models.

History Doesn’t Reward Defenders

I’ve seen this pattern before.

Businesses often spend more energy trying to protect the old revenue stream than understanding the new opportunity. They look at disruption as something to resist rather than something to harness.

The problem is that customers rarely share that loyalty to the old model.

Business owners don’t wake up in the morning hoping to buy more support hours. They want outcomes. They want faster decisions. They want less administration. They want their staff spending more time serving customers and less time managing information.

Today, a growing number of those outcomes can be delivered through AI.

Whether MSPs like it or not.

The Risk of Becoming the Blocker

One of the dangers for traditional MSPs is becoming the organisation that says no.

No, you shouldn’t use AI yet.

No, you shouldn’t change your process.

No, your existing approach is good enough.

Meanwhile, another adviser walks in and shows the client how Microsoft 365 Copilot can reduce the time spent preparing for meetings in Teams, drafting emails in Outlook and analysing information in Excel.

Guess which adviser the client sees as helping them move forward?

I’ve always believed that our role as technology professionals is not to preserve the status quo. It’s to help customers navigate change safely and effectively.

That doesn’t mean blindly embracing every new feature that appears. Governance still matters. Security still matters. Data quality still matters. AI without preparation can create as many problems as it solves.

But that’s very different from pretending the change isn’t happening.

The MSP Opportunity

Ironically, AI may create one of the biggest opportunities MSPs have seen in years.

Most businesses have no idea how to prepare their data, secure their environment or establish the governance needed to use AI safely. They need guidance. They need strategy. They need trusted advisers.

That’s where MSPs can create enormous value.

But only if they’re willing to evolve.

The conversation can’t stay focused on devices, licences and tickets. It needs to move towards business processes, information management, knowledge discovery and AI readiness.

That’s where the real opportunity sits.

Final Thoughts

I don’t think AI should be entrusted solely to old-school MSPs who want everything to stay the same. Equally, I don’t think businesses should rush headlong into AI without experienced technology advisers.

The answer lies somewhere in the middle.

The MSPs that thrive over the next decade won’t be the ones defending the past. They’ll be the ones helping clients prepare for the future.

Because AI isn’t interested in protecting anyone’s business model.

It’s simply moving forward.

And the question every MSP needs to answer is whether they’ll be leading that change or explaining to clients why they missed it.

The MSP Skills Gap Nobody Is Talking About Yet

I had a conversation with an MSP owner last week that has been rattling around in my head ever since. He was telling me, proudly, about how his team had just finished a big project hardening a client’s endpoint stack. Patching, EDR, conditional access, the lot. Then almost as an afterthought he mentioned the same client had quietly turned on Copilot for sixty users and was already building their first agent in Copilot Studio. He had no plan for any of it. No policy, no review process, no clear idea who in his team would actually own it. And here is the uncomfortable part. He is not unusual. He is the rule.

The growth in AI agents inside SMB environments is going to be the steepest curve we have seen in years, and most MSPs are walking into it carrying the wrong toolkit. The skills that built a successful managed services business over the last decade are not the skills that will keep customers safe and productive over the next one. That gap is widening every week, and very few MSP owners I speak to have noticed.

Agents are not endpoints

For twenty years MSPs have been organised around things. Devices, servers, mailboxes, firewalls. You patch them, monitor them, back them up, replace them. The whole MSP operating model — RMM, PSA, ticketing, SLAs — assumes a world of static assets that misbehave in fairly predictable ways.

An AI agent is none of those things. It is not an endpoint. It does not sit still. It reads documents in SharePoint, drafts replies in Outlook, pulls data from line-of-business systems, and acts on behalf of a user across surfaces the MSP has never had to think about as a single connected thing. When a Copilot agent fetches the wrong document and pastes confidential numbers into an external chat, no RMM alert is going to fire. The questions are different too. Not “is it patched?” but “what did it do today, and why?” That is a governance and behaviour problem, not an infrastructure one.

The new skill set is governance, data and prompts

Managing agents well leans on a set of muscles most MSPs have never had to build. Understanding identity scope in Entra so an agent cannot reach data it has no business touching. Configuring sensitivity labels and DLP in Purview so a chatty agent does not quietly become a leak. Reviewing prompt design and grounding sources in Copilot Studio before an agent is let near real users. Watching audit logs in the Microsoft 365 admin centre for patterns of agent behaviour that look off.

This is closer to the work of a data steward or a security analyst than a traditional systems engineer. It is slower, more interpretive, and more about judgement than ticket throughput. It rewards curiosity and writing skills as much as PowerShell. The MSP business model has not been built for that kind of work, and the hiring pipeline certainly has not.

The retraining window is now

Here is the bit that worries me. Customers are going to assume their MSP has this covered. They will turn on Copilot, build agents in Copilot Studio, plug them into their CRM, and look across the table expecting the same calm competence they get for backups. When something goes wrong — a leaked document, an agent that quietly emails the wrong list, a workflow that has drifted off purpose — they will ring their MSP. And most will not be able to help.

The MSPs that get ahead of this will start small and start now. Pick one client, one agent, and learn it end to end. Read the audit logs. Write the policy. Build the review cadence. The technical hardening skills will still matter. They are just no longer enough on their own.

Opportunity Is the Enemy

The most dangerous moment for an MSP isn’t a slow quarter. It’s a good one.

When the calendar is full, leads are landing, and a former client pings you about “a quick idea” — that’s when the trouble starts. Suddenly you’re half-thinking about a new managed service line, a side venture with a vendor friend, a property deal someone mentioned at lunch. None of it is bad. That’s the whole problem.

I’ve watched too many capable owners chip themselves into pieces this way. The wins keep arriving, just not in the lane they originally chose. The actual business — the one paying the bills and the team — quietly slows down while they chase the next shiny thing. A year later they wonder how the work they actually built ended up running on autopilot, or not running at all.

Every shiny thing has a real cost

When someone pitches you an opportunity, the cost looks small. A meeting. A few emails. A weekend reading through a deck. Easy.

But every hour spent on something that isn’t your main game is an hour you didn’t spend on the clients, the people, and the systems that pay your mortgage. That trade is rarely visible in the moment. It shows up six months later when renewals slip, your senior tech is restless, and you can’t remember the last proper sit-down with your number one client.

The discipline isn’t in saying yes to the right work. It’s in saying no to the wrong opportunities — especially the flattering ones.

Build a filter, not a willpower contest

Relying on raw willpower to turn things down is a losing strategy. By Friday afternoon you’re tired, someone’s been charming, and the calendar fills back up.

What works better is a written filter. One short paragraph. What you do, who you serve, the size of client you take on, and the kind of work you flat-out refuse. I keep mine in a Loop component pinned at the top of my main planning page in Teams. When a new pitch arrives, I open it, re-read the filter, and the answer is usually obvious before I’ve finished the second sentence.

The tiny ritual takes the emotion out of the decision. The filter said no. Not me.

Let Copilot guard the door

The other shift for me has been using Copilot in Outlook as a first-pass screener. When a long, friendly email arrives proposing something tangential, I ask Copilot to summarise what’s actually being requested, how much time it would cost, and how it fits against my current priorities, which I keep in a short document in OneDrive.

Most of the time, the reply writes itself. Copilot drafts a polite decline and suggests someone better placed to help. I read it, tweak a sentence, send. A minute, instead of an afternoon of overthinking.

I do the same with meeting requests. Before I accept anything outside current client work, I ask Copilot to pull recent threads on the topic and tell me whether I’ve already had this conversation. Half the time, I have. That’s the meeting that quietly doesn’t get booked.

The quieter calendar

The strange part is that turning things down doesn’t make the business shrink. It makes it sharper. The clients I keep get more of me. The team gets more of me. And the work I actually built finally has room to grow into something worth defending.

Opportunity will keep knocking. That’s its job. Mine is to stop answering every time.

The SMB MSP As We Know It Won’t See 2030

I had a conversation recently with an MSP owner who’s been running the same shape of business for nearly twenty years. Same monthly recurring revenue model, same per-seat pricing, same mix of patching, monitoring, helpdesk, and the occasional project. He asked me what I thought the next five years looked like for him. I told him honestly. The business he runs today won’t exist by 2030. Not because he’ll do anything wrong, but because the market won’t need it anymore.

I’ve been saying versions of this quietly for a while. I think it’s time to say it out loud. The SMB MSP businesses of today — the ones built on managing endpoints, watching dashboards, resetting passwords, and pushing patches — are walking into a wall. The wall is closer than most of them realise.

The work that paid the bills is being automated away

Pick any traditional MSP price book and look at where the labour hours actually go. Patching. Monitoring. Tier 1 helpdesk. Onboarding and offboarding. Backup checks. Mailbox issues. OneDrive sync problems. Printer queues. The same dozen tickets, repeated across hundreds of clients, every week.

Almost none of that work needs a human anymore. Intune does the patching. Microsoft 365 does the self-healing. Defender does the watching. Entra automates the onboarding once it’s wired up properly. And Copilot — sitting inside Outlook, Teams, and the admin centres — answers the questions that used to be a phone call to the helpdesk. A user asking “why can’t I see this shared mailbox?” used to be a fifteen-minute ticket. Now it’s a Copilot prompt and a self-service result.

The MSP owner who thinks AI is “still a few years away” is the same one who told me cloud was a fad in 2014. The labour arbitrage that built the MSP industry — paying a junior tech in one city to fix something for a client in another — only works when the labour is needed. It mostly isn’t.

Microsoft is quietly eating the stack

The other story most MSPs aren’t telling themselves honestly is what’s happening to their tool chain. The classic SMB MSP stitched together five or six separate products to deliver a managed service — RMM, PSA, backup, antivirus, email security, password manager, MFA. The margin was in the stitching, not in any individual product.

Microsoft 365, with Defender, Intune, Entra, Purview, and Copilot layered on top, now covers most of that surface natively. It’s not perfect and it’s not cheaper, but it’s good enough for the SMB segment — and it’s getting better every quarter. When the platform a client already pays for can deliver eighty per cent of what the MSP used to charge for, the conversation about the other twenty per cent gets uncomfortable fast.

I watched an SMB owner last month ask Copilot in the Microsoft 365 admin centre to summarise her security posture, suggest fixes, and draft a message to her staff about a new MFA requirement. Three things her MSP would have charged her for, done in under a minute, without leaving the browser. She didn’t call her MSP afterwards. She just got on with her day. That’s the shift.

Buyers stopped wanting “managed IT”

There’s a generational change in SMB buyers that the industry is underestimating. The people running small businesses now grew up on consumer software that just works. They don’t want a relationship with a company that “manages their IT”. They want outcomes — their email working, their files safe, their staff productive — and they expect those outcomes to be invisible.

When the outcome can be delivered by a platform plus an AI assistant, the MSP isn’t a partner anymore. It’s a middleman. And middlemen who can’t articulate the unique value they add get squeezed out, every single time, in every industry where this pattern has played out before. Travel agents. Stockbrokers. Bookkeepers doing data entry. The MSP delivering commodity managed services is next.

The margins are already gone

Talk to any honest MSP owner about their margins over the last three years and you’ll hear the same story. Costs up. Prices flat or barely moving. Clients pushing back on increases. Staff harder to find, more expensive to keep, and asking for the kind of work that doesn’t exist in a commodity managed service anymore.

The economics don’t recover. They get worse. Because the AI tooling that’s eating the work is also reducing the cost of delivery for the few players who lean into it — meaning the price floor keeps dropping. An MSP charging eighty dollars a seat for traditional managed services is competing against a competitor charging forty, who has automated most of the same work, who is competing against a Microsoft partner bundling Copilot at a price point that makes the conversation moot.

What survives

I’m not saying every MSP is gone by 2030. I’m saying the shape most of them have today is gone. What survives is something different. Advisory businesses that help SMBs use Copilot well. Specialists who can wire up Power Automate flows that actually move the needle for a client. Security-led practices that go deep instead of wide. Firms that have stopped selling time and started selling outcomes.

Those businesses look almost nothing like the typical SMB MSP of 2025. Different revenue model, different staff mix, different conversations with clients. The ones quietly making that turn now will be fine. The ones still arguing about whether AI is overhyped will not.

I’d rather have the uncomfortable conversation in 2026 than the unavoidable one in 2029. If you run an MSP, the next eighteen months are when the work gets done — or doesn’t.

The Difference Between a Direction and a Walk

I’ve been watching people coach lately. Mine and other people’s. Inside teams, on calls, in coaching sessions, in the small handovers that happen between desks. And the same pattern keeps surfacing, in versions large and small.

We give directions. We rarely take the walk.

A direction is the polite, efficient gesture — the link in chat, the screenshot with an arrow, the “have a look at this, it explains it well”. It assumes the person on the other end has the time, the focus, and the confidence to follow the trail to the end. Most of the time, they don’t. Most of the time, they were asking because the trail is exactly what they’ve been struggling with.

Taking the walk is different. It means putting down what you were doing, getting up out of your chair (literally or in the digital equivalent of it), and going with them. It is slower, it is less elegant, and it is the thing that almost always works.

Why this hits hardest with Copilot right now

The reason this is sitting on top of my mind is what I’m seeing inside Microsoft 365 rollouts. Copilot is now embedded across Outlook, Word, Excel, Teams, OneNote, Loop — every surface a knowledge worker touches. The interface is right there. The documentation is right there. The training videos are right there.

And the gap is still enormous.

That gap isn’t a documentation problem. It’s a companionship problem. People know Copilot is in their email. What they don’t know is what to type when they actually have to reply to a customer who is upset, or summarise a three-week Teams thread, or pull the relevant lines out of a contract sitting in SharePoint. They need a person beside them the first time. Not afterwards. Not in a wiki. The first time.

When you sit next to somebody — sharing a screen in Teams works just as well as sitting at the same desk — and you open Copilot in their inbox, in front of their actual unread emails, two things happen. First, the prompt becomes specific. Generic prompt libraries are useless; their prompt for their email at this moment is electric. Second, they see you make a mistake, refine it, try again, and get somewhere usable. That’s the part documentation never teaches.

The handover is part of the coaching

The other thing I’ve come to value is the handover. Coaching isn’t finished the moment somebody can do the thing once. It’s finished when they have somewhere to go the second time.

In Microsoft 365 that means leaving a trail the next person — or the same person on a different morning — can pick up. Pin the prompt you just shaped together into a Loop component the team can see. Drop a note in their Teams channel calling out what worked. Connect them with the colleague who is already three months ahead. The point is that the next time they reach for help, the path ahead is already lit.

What I’m trying to do less of

I’m catching myself in the act of pointing more often than I’d like to admit. The instinct to send the link is strong; it costs me nothing, it looks like I helped, and it gets the conversation off my plate.

But the version of me that other people actually need isn’t the one with the curated bookmarks. It’s the one prepared to push the chair back and say, fine, let’s go and look at it together.

That’s the coaching that compounds. Everything else is signage.