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.

Do an Audit of Who’s Actually In Your Corner

A few weeks ago I was on a long drive home from a client meeting and I started running through the names of people I’d actually spent real time with over the past year — not the LinkedIn list, the actual list. The ones who’d had my ear, my weekends, my energy and, in some cases, my best thinking. By the time I got home I realised something a bit uncomfortable. A handful of those names didn’t really belong on it anymore. Not because they’re bad people. Because they’re not pulling in the same direction I am.

That’s the part nobody likes to say out loud.

The question worth sitting with

There’s one question I think every business owner should ask themselves once a year, and it’s blunt: is the time I spend with this person making me sharper, or just making me comfortable?

Comfortable is the trap. Comfortable feels like loyalty, like history, like the easy lunch where nothing hard ever gets said. Growth tends to live somewhere else.

I’ve started using Copilot in Outlook to actually look at the data. I’ll ask it to pull together who I’ve met with most over the last three months and the answer is sometimes a surprise. The people I think I’m investing in and the people my calendar shows I’m investing in are not always the same list. Calendars don’t lie. They quietly show you where your time really goes, and once you’ve seen it laid out on a page you can’t unsee it.

Three filters I run people through

When I’m doing this stocktake, I look at three things, and I try not to overthink any of them.

The first is how I feel walking away from the conversation. If I leave a coffee buzzing with ideas and a list of things to try, that’s a signal. If I leave flat and quietly wanting a nap, that’s also a signal. The body keeps a fairly honest scoreboard, even when the head is trying to be polite about it.

The second is whether they’re actually moving. Movement doesn’t have to be loud — I know plenty of quiet operators who are building something serious. But if someone has been telling me the same story about the same plan for three years running, that stagnation will start to drag on you whether you notice it or not.

The third is whether they’ll tell me I’m wrong. The people who only ever agree with me have very little to offer me. The ones who push back, who ask the awkward question, who say “are you sure about that?” — those are the ones I keep close. Anyone who’s only ever told me what I wanted to hear has never once helped me improve.

The hardest cuts are the kindest people

The brutal part of this exercise isn’t the obvious ones. It’s the genuinely lovely humans who just don’t fit where you’re heading next. Lovely doesn’t equal useful. You can wish someone well, mean it completely, and still recognise that the season of regularly being in each other’s diaries has run its course. That’s not betrayal. That’s adulthood.

I keep a private Loop page with my thinking on this — a few names, a few notes, no judgement attached. Copilot helps me draft the reflection prompts when I’m not quite sure what I’m trying to articulate. It’s not a kill list. It’s a way of being deliberate about where my hours go next year, because nobody else is going to be deliberate about it for me.

If you’ve never done a Friendventory, do one this month. Block an hour in your calendar, pour something decent, and walk through the names honestly. The people in your corner shape the business you build next. Pick them on purpose, because by default you’ll just keep whoever was around when you started.

The Clients You Need to Let Go

Last Saturday morning I sat down with a coffee and went through my client list properly. Not the polished version on a spreadsheet — the honest one. The list where you stop and ask yourself which names make your shoulders drop when they appear in your inbox.

Out of every hundred clients, maybe twenty fit that description. They weren’t bad people. But they were the ones who turned a thirty-minute call into ninety. The ones who treated every standard you set as optional. The ones who had a complaint queued up before they’d even tried what you suggested.

And here’s the part most MSP owners don’t want to admit out loud: those clients aren’t just slightly more work. They quietly run the place.

The Maths You’ve Been Avoiding

Sit down and add up the hours. Not the billable ones. The total ones. The Friday afternoon you spent re-explaining MFA for the fifth time. The Sunday email you answered because they wrote at 9pm and you didn’t want them to think you’d ignored them. The team meeting that ran twenty minutes long because someone needed to vent about a client who refuses to follow the playbook.

If you log it honestly for a fortnight, the pattern is uncomfortable. A small handful of clients eat a disproportionate slice of your week, your team’s morale, and your own headspace. The rest of your book — the ones who pay on time, listen to your advice, and treat your team with respect — get whatever scraps of attention are left over.

Copilot Can Show You What You Already Suspect

Here is where Microsoft 365 quietly earns its keep. Ask Copilot in Outlook to summarise the volume and tone of messages you’ve exchanged with a particular client over the last quarter. Open your Teams channels and let Copilot in Teams surface the recurring complaints by topic. Pull up the recap from your last quarterly review with that client and read it back without the emotion of being in the room.

You will see it plainly. The same three issues raised four quarters in a row. The same standards politely ignored. The same tone in every second message. Copilot isn’t telling you anything new. It’s just laying out the evidence you’ve been too busy or too loyal to read properly.

I have started doing this every quarter. It takes about twenty minutes per client, and it removes the wishful thinking. You stop asking “are they really that bad?” and start asking the more useful question: “Why am I still putting up with this?”

The Conversation Itself

When you do decide to end the relationship, do it cleanly. Refund what is fair. Offer to hand over their data in a tidy package via OneDrive. Recommend a provider who is genuinely a better fit for them — not a punishment, just a different match.

I draft the offboarding email in Word with Copilot’s help, sit on it overnight, then read it again in the morning. If it still says what needs saying, I send it. No long justification. No door left ajar. A short, professional close.

What You Get Back

The first time I did this properly, three things shifted within a month. My team felt lighter. Monday mornings stopped starting with dread. And the clients I genuinely respect — the ones who do the work, follow the advice, ask good questions — got noticeably more of me.

That last shift is the one that matters. The people paying for your best work deserve your best attention, and you simply cannot offer it while a small group is quietly running off with the fuel.

Nobody buys tickets to a concert when they haven’t heard the songs

A mate of mine said something last week that I’m still chewing on. We were talking about the slog of marketing — the endless push to fill webinar seats, chase trial sign-ups, follow up on outreach that goes nowhere. He stopped mid-sentence and said he was done with all of it. He didn’t want to spend his career flogging tickets to a show. He wanted to make a body of work so strong that the show booked itself.

That hit me, because most MSPs I speak to are stuck in the wrong half of that sentence. They’re flogging tickets to a concert when nobody has heard a single track.

The album is the persuasion

Think about what actually changes someone’s mind in this business. It isn’t a sales page. It isn’t a “book your free assessment” button at the bottom of a generic landing page. It’s the post they read on a Sunday morning that made them rethink how they saw their own business. It’s the short video that answered a question their current provider had been dodging for months. It’s the comment on someone else’s post where you said something sharp and useful, and they thought, hang on, who is that.

That body of work is the album. The offer at the end — the assessment, the migration, the security review, the Copilot rollout — that’s just the tour. If the album is good, the tour fills. If the album is thin, the tour costs you blood to fill every single time, and you’re back to the slog my mate was so tired of. It’s the same hustle dressed up in a new font.

Make the work before you sell the work

The trap is producing thin content with a CTA stapled to it. A 200-word post that took twenty minutes and ends with “DM me to book a call” is a flyer, not a song. Nobody travels to see a flyer.

A real piece takes longer. It needs a genuine opinion. It needs a story you actually lived. It needs editing — the part most people skip because it isn’t fun.

Microsoft 365 is built to take the friction out of that work without taking the soul out of it. I draft most of my posts in Word with Copilot sitting next to me, asking it to push back on my argument, sharpen the opening line, surface the point I’m circling but haven’t written yet. I’ll record a short Teams call talking an idea out loud and ask Copilot to pull a structure from the transcript. I keep a SharePoint page where every client conversation that surprised me gets dropped in as a few lines, and over a month it becomes a list of post ideas I’d never have remembered otherwise.

The point isn’t to make more. It’s to make better, more often, with less of the activation energy that usually kills the habit before the third post lands. That’s the shift that matters — not the volume, but whether you can keep showing up with something actually worth someone’s attention.

Then you stop selling tickets

When the work is genuinely good, you stop chasing. People who already trust how you think don’t need to be sold the offer — they need a way to say yes. The hustle quietly drops away, because the persuasion happened months ago, in public, while you weren’t pitching anything at all.

So before the next campaign, the next list, the next funnel — ask the harder question. Are the songs any good? Good enough that someone would forward one to a colleague without you having to ask. Because nothing on the tour can rescue an album nobody wants to hear.

Why Your Marketing Keeps Disappearing

I see the same pattern in MSP after MSP. The pipeline thins out, sales gets nervous, and suddenly there’s a flurry of activity. A newsletter goes out. A few posts appear on LinkedIn. Someone dusts off the old webinar deck. Leads start trickling in, projects get signed, and the team gets buried in delivery. Six weeks later, the marketing has gone quiet again. No newsletter. No posts. No webinar. Just heads down, tickets, and onboarding.

Then the pipeline thins out again. And the cycle starts over.

What surprises me is how few owners recognise this as the actual problem. They tell me they’re tired of marketing. That it doesn’t work. That they’ve tried it. But when I push a little, what they’ve actually tried is marketing in panic mode — a short, intense burst when sales were already down. Of course it didn’t work. It was never given enough time to.

The exhaustion is the symptom, not the cause

The story most owners tell themselves sounds reasonable. “I stopped because I was exhausted.” Sit with it for a minute and the logic flips. You weren’t exhausted because you were marketing. You were exhausted because you were doing everything in catch-up mode — chasing leads you should have already had, writing content you should have written months ago, scrambling for testimonials you should have collected at the time of delivery.

Steady marketing isn’t what wears people out. The on-again, off-again version is what wears people out. And every time you stop, you guarantee the next round will be harder than the last, because you’re always starting cold.

Make the boring part automatic

This is the part where Microsoft 365 quietly earns its keep. Most MSPs already pay for it. Few of them use it for their own business the way they sell it to clients.

Pick one rhythm and protect it. A weekly post. A fortnightly newsletter. A monthly client tip. Whatever the cadence, build it inside the tools you already live in. I’ll sit down on a Sunday morning, open Copilot in Word, and ask it to turn a few rough notes from the week into a draft post. Ten minutes later I have something to work with rather than a blank page. In Outlook, Copilot can take a long internal email — a war story from a recent project, an interesting client question — and reshape it into something appropriate for an audience.

Park the ideas as they happen. A Loop component pinned in a Teams channel called “marketing scraps” is enough. A Planner board with one column for “next post”, one for “next newsletter”, and one for “case study someday” gives you a queue instead of a panic. None of this is glamorous. It’s plumbing. But the plumbing is what keeps the tap running when you’re flat out delivering.

Steady beats clever

I’ve never met an MSP that grew because of one brilliant campaign. I’ve met plenty that grew because they kept showing up — every week, every month, regardless of how the pipeline looked that quarter. The content wasn’t always sharp. The newsletter wasn’t always polished. But it was there.

If your marketing only appears when you need sales, your prospects learn the pattern too. They see the silence and read it correctly. The fix isn’t a bigger push. It’s a smaller, steadier one — and an honest look at why the quiet stretches keep happening.

You’re not exhausted by marketing. You’re exhausted by stopping.