AI Fluency Isn’t Optional Anymore – and Microsoft 365 Copilot Is Where It Starts

image

There’s a quiet shift happening in workplaces right now.

It’s not about who knows the most tools.
It’s not about who can write the cleverest prompt.
And it’s definitely not about chasing the latest shiny AI platform every second week.

It’s about AI fluency.

More and more, I’m seeing decisions being made – hiring, promotion, even redundancy – based on one simple question:

Can this person actually work effectively with AI?

And here’s the part many people miss:
AI fluency isn’t about learning “AI”. It’s about embedding AI into the way you already work.

That’s why, for most businesses, Microsoft 365 Copilot should be the default starting point.


Phase 1: Foundations – Make Copilot the First Place You Go

The biggest mistake I see people make with AI is treating it like a special activity.

You “go and do AI”, then you go back to your real work.

That’s backwards.

The foundation of AI fluency is simple:
use AI everywhere you would normally think, search, write, or plan.

With Microsoft 365 Copilot, that means:

  • Drafting and refining emails directly in Outlook

  • Summarising meetings and actions in Teams

  • Turning rough ideas into structured documents in Word

  • Analysing data and trends inside Excel

  • Asking Copilot questions against your own tenant data, not the public internet

The habit you want to build is this:
If you’re already in Microsoft 365, Copilot is already there – use it.

No extra tabs.
No copy‑paste gymnastics.
No context switching.

That alone puts Copilot ahead of generic AI tools for day‑to‑day business use.


Phase 2: Copilot as a Coach, Not a Crutch

Early on, AI shouldn’t be doing your job for you.
It should be helping you think better about the job you’re already doing.

This is where Copilot shines inside Teams, Word, and OneNote.

Examples I see working well:

  • “Summarise this meeting and highlight risks I might have missed”

  • “Review this proposal and challenge my assumptions”

  • “What questions should I be asking before I send this to a client?”

  • “Turn these messy notes into a clear executive summary”

You’re still in control.
You’re still accountable.
Copilot is acting like a thinking partner that never gets tired.

That’s real productivity uplift – not AI theatre.


Phase 3: Copilot as a Worker (With You Still in the Loop)

Once the thinking habits are in place, then you let Copilot do more of the heavy lifting.

But not 100%.

The rule I use is simple:

  • You do the first 10% (direction and intent)

  • Copilot does the middle 80% (drafting, structuring, expanding)

  • You do the final 10% (judgement, tone, accuracy)

This works brilliantly for:

  • Reports and proposals in Word

  • Policy drafts and SOPs

  • Client updates

  • Internal documentation

  • Slide outlines for presentations

Copilot already understands your documents, your language, and your context because it’s working inside Microsoft 365 – not guessing from a blank prompt window.


Phase 4: Systems Beat Prompts

Prompt obsession is a trap.

What actually scales is repeatable systems.

Copilot naturally encourages this because it’s embedded in workflows:

  • Meeting → transcript → summary → action list

  • Email thread → summary → response draft

  • Document → critique → rewrite → final version

You’re not reinventing prompts every time.
You’re refining how you work.

That’s a massive difference, especially for teams.


Phase 5: Copilot as Infrastructure

This is where things get interesting.

When AI is built into the platform your business already runs on, it stops being a tool and starts becoming infrastructure.

Copilot connects across:

  • Outlook

  • Teams

  • SharePoint

  • OneDrive

  • Word, Excel, PowerPoint

All governed by your existing security, identity, and compliance controls.

That matters – especially for SMBs, regulated industries, and MSP-managed environments.

You don’t need ten different AI subscriptions.
You need one AI that understands your business context and respects your data boundaries.


The Bottom Line

AI fluency isn’t about knowing which AI is smartest this week.

It’s about choosing an AI that:

  • Fits naturally into how people already work

  • Reduces friction instead of adding it

  • Scales across teams, not just individuals

  • Works securely with business data

For most organisations, that AI is Microsoft 365 Copilot.


What’s Actually Happening to MSPs

image

Every few months the same take does the rounds:

“MSPs are dying.” “AI will wipe out MSPs.” “The MSP model is broken.”

None of that is quite right.

MSPs aren’t dying.
They’re polarising.

What we’re watching isn’t a collapse — it’s a hard split into three very different realities. And if you don’t understand which one you’re talking to (or operating in), everything else you do — marketing, content, AI strategy, pricing — is noise.

Let’s frame this cleanly.


1. Legacy MSPs: The Majority (and the Dead End)

This is still most of the market.

Legacy MSPs compete on:

  • Seat price

  • RMM stacks

  • “We manage your IT” as a generic promise

Their business looks fine from the outside. In reality:

  • Margins are crushed

  • Staff are burnt out

  • Owners are trapped inside delivery

  • Every new tool adds complexity, not leverage

These businesses have no spare capacity — financially or cognitively — for:

  • AI adoption

  • Transformation projects

  • Training

  • Strategic change

They are running just fast enough not to fall over.

Here’s the uncomfortable truth:
These MSPs cannot be your target market.

Not for AI. Not for Copilot. Not for advisory. Not for transformation.

It doesn’t matter how good your content is. They don’t have the oxygen to act on it. Their problem isn’t awareness — it’s structural exhaustion.

Trying to “educate” this segment is a waste of time and energy.


2. Survival MSPs: The Loud Middle (and the False Signal)

This is the group most people think is “the market” — because they’re the ones talking.

You see them in communities. You see them in comments. You see them consuming content.

They are:

  • Intellectually aware they’re in trouble

  • Personally curious about AI

  • Smart, engaged, thoughtful individuals

But the business reality looks like this:

  • No discretionary budget

  • No mandate to change pricing or offers

  • No execution runway

They consume content as individuals, not as businesses.

That’s the trap.

They feel like a market.
They sound like a market.
They engage like a market.

But they don’t convert.

Not because they don’t want to — but because they can’t.

This group is where the “MSPs are dying” narrative comes from. And in a very real sense, it’s true — this segment is dying. Slowly. Quietly. Frustratingly.

They will tell you they’re “exploring AI”. They will attend webinars. They will save posts. They will nod along.

And then… nothing changes.

If your strategy relies on this group, you’re building on sand.


3. Post‑MSP Firms: The Quiet Minority That Already Moved

This is the group almost no one markets to properly — because they don’t self‑identify as MSPs anymore.

These firms have already started moving away from:

  • Per‑seat pricing

  • Pure support contracts

  • Tool‑centric value propositions

They sell:

  • Advisory

  • Governance

  • Compliance

  • Outcomes

They invest in:

  • Training

  • Capability

  • AI

  • Systems that reduce labour, not increase it

They don’t ask:

“How do we add Copilot to our stack?”

They ask:

“How do we redesign the business now that Copilot exists?”

Here’s the key insight most people miss:

These firms do not think of themselves as MSPs.

And that’s why traditional MSP messaging doesn’t land with them.

They’re not trying to save the MSP model.
They’ve already accepted it’s over.

They’re building something else.


The Real Shift (That No One Wants to Say Out Loud)

The market hasn’t disappeared.
The money hasn’t disappeared.
Demand hasn’t disappeared.

What’s disappeared is tolerance for undifferentiated IT support.

AI didn’t create this shift — it exposed it.

If your value is labour, AI compresses you.
If your value is outcomes, AI amplifies you.

This is why:

  • Content engagement is high but conversion is low

  • “AI curiosity” doesn’t turn into projects

  • MSPs feel stuck despite knowing the right answers

The industry isn’t waiting for better tools.

It’s waiting for fewer MSPs — and more firms willing to stop being one.


The Bottom Line

MSPs aren’t dying. They’re sorting themselves.

  • Legacy MSPs will grind until exit or burnout

  • Survival MSPs will talk, but not move

  • Post‑MSP firms will quietly compound advantage

If you’re building content, products, services, or communities, the question isn’t:

“How do we help MSPs survive?”

It’s:

“Who is already leaving — and how do we help them go faster?”

That’s where the future actually is.

Why Running Your MSP on “Hard Mode” Is Slowly Killing It

image

Let’s get something uncomfortable out of the way.

If your MSP feels hard…
If growth feels heavy…
If the thought of “scaling” makes you tired rather than excited…

The problem probably isn’t your tools, your stack, or your tactics.

It’s that your business is out of alignment with you.

For years, MSPs have been fed the same lie:
If it’s not hard, you’re not doing it properly.

Long hours.
Always-on availability.
Endless meetings.
Constant pressure to sell, hire, scale, document, standardise, repeat.

Congratulations — you’ve built yourself a prison. And you’re the warden.

The MSP “Pain Line”

Most MSPs eventually hit what I call the pain line.

That point where:

  • You’re busy, but not growing

  • You’re profitable, but not happy

  • You know what to do tactically… but still feel stuck

You don’t quit, because the business “works”.
You don’t change, because change feels risky.
So you push harder.

That’s when MSP owners burn out — not because they’re weak, but because they’re misaligned.

And here’s the key insight most MSPs miss:

You will never deliberately grow into pain.

If growth feels like more stress, more chaos, more pressure… you’ll subconsciously cap your own business. You’ll stall, plateau, or self‑sabotage — and then blame the market.

What Works vs What Works For You

There’s a massive difference between:

  • What works
  • And what works for you

Just because:

  • Quarterly sales pushes work for other MSPs

  • Big teams work for other MSPs

  • Back‑to‑back meetings work for other MSPs

…doesn’t mean they should work for you.

MSPs are notorious for copying business models without asking a basic question:

“Would I still want to run this business in 10 or 20 years?”

If the answer is “not like this”… then something needs to change.

Your MSP Is the Product You Forgot to Design

Most MSPs obsess over:

  • The services they sell

  • The technology they deliver

  • The experience their clients have

Almost none spend serious time designing the business they work in every day.

That’s the real product.

Your MSP should fit you like a glove — your personality, your strengths, your energy, your season of life.

If you’re an introvert forced into constant sales calls, that’s friction.
If you hate meetings but built a meeting‑heavy culture, that’s friction.
If you love deep technical work but spend all day managing people, that’s friction.

Friction is expensive. Not just financially — emotionally.

MSPs Aren’t Broken — They’re Misaligned

Here’s the good news:
There’s probably nothing wrong with your MSP.

It’s just built for a version of you that no longer exists.

Your life changes.
Your energy changes.
Your priorities change.

But most MSPs never update the business model — they just keep tolerating it.

And tolerance is dangerous. It turns into resentment. Then burnout.

The Alignment Test

Try this brutally honest exercise:

Make two lists.

List 1: The parts of your MSP you genuinely love
The work that energises you
The days where work feels like play

List 2: The parts you hate
The things you tolerate
The work that drains you but “has to be done”

Now ask yourself:

Why does my calendar still contain so much of List 2?

This isn’t about doing less work.
It’s about doing the right work.

Easy Mode Isn’t Lazy Mode

Let’s be clear: “easy” doesn’t mean small, lazy, or unambitious.

It means:

  • Work that suits how you’re wired

  • A delivery model that energises you

  • A sales model you don’t dread

  • A team structure that doesn’t suffocate you

When your MSP is aligned, effort feels lighter — not because you’re doing less, but because you’re not fighting yourself.

That’s when growth accelerates. That’s when creativity returns. That’s when clients feel the difference.

People follow energy. They buy from clarity. They trust alignment.

The Real Challenge for MSPs

So here’s the uncomfortable challenge:

Stop asking, “How do I scale this?”
Start asking, “Do I even want to scale it this way?”

Because building an MSP that fits everyone else’s idea of success — but not yours — is the fastest way to hate the thing you worked so hard to build.

You don’t need another framework.
You don’t need another tool.
You don’t need to push harder.

You need alignment.

And once you have that, growth stops feeling like punishment — and starts feeling inevitable.

AI Guilt Is the Wrong Question (But the Right Wake‑Up Call)

image

I watched a video this week that stuck with me far longer than it probably should have. It wasn’t flashy. It wasn’t hyped. It wasn’t trying to sell me the “AI will save us all” story.

Instead, it focused on something far more uncomfortable: the guilt felt by people who build AI systems that lead to job losses.

And honestly? That discomfort is exactly what we should be leaning into right now.

The AI conversation is broken because it’s usually framed at the extremes. Either AI is an unstoppable monster coming for everyone’s job, or it’s a magical productivity fairy that somehow improves everything without consequence. Both positions are lazy. Both avoid responsibility.

The truth — as usual — is messier.

AI Doesn’t Lay People Off. People Do.

Let’s get one thing clear early: AI does not make decisions. Humans do.

AI doesn’t walk into a boardroom and announce redundancies. AI doesn’t restructure teams. AI doesn’t decide that headcount is the fastest way to protect margins.

Executives do that.

Business owners do that.

Leaders do that.

Blaming “the technology” is a convenient way to outsource accountability. It allows people to say, “We had no choice”, when what they really mean is, “We chose efficiency over people, and we don’t want to own that.”

The guilt described in this video isn’t actually about AI. It’s about power without ownership.

Productivity Has Always Displaced Work

This part isn’t new. Automation has been displacing tasks — and entire roles — for centuries. Spreadsheets replaced ledger clerks. Email replaced postal rooms. Cloud computing replaced on‑prem everything teams.

What is new is the speed and scope.

AI doesn’t just replace manual labour. It replaces cognitive effort. Drafting, analysing, summarising, responding, triaging — the very tasks many knowledge workers believed were “safe”.

That’s confronting. It should be.

But pretending we can stop it is fantasy. The real question is: what do we do with the leverage it gives us?

MSPs Are at the Front Line of This Shift

For MSPs, this conversation isn’t theoretical. You’re already living it.

Every Copilot deployment, every automation script, every agent you roll out reduces friction — and often reduces billable effort. That’s not a bug. That’s the future.

The mistake is thinking the win is “doing the same work with fewer people”.

The real win is doing better work with the same people.

More proactive security.
More strategic advice.
More business insight.
More human judgment where it actually matters.

If your only AI strategy is cost‑cutting, then yes — guilt is probably appropriate.

The Ethical Line Is Leadership, Not Technology

The developers in this video are asking themselves the wrong question: “Should we build this?”

The better question is: “How will this be used?”

AI is a multiplier. It amplifies intent. Good leaders will use it to elevate teams. Bad leaders will use it to extract value and discard people.

The technology doesn’t decide which path you’re on. You do.

And for MSPs advising clients? This is where your role becomes critical. You’re no longer just implementing tools — you’re shaping outcomes. You’re influencing how businesses adopt AI, what they automate, and what they preserve.

That’s not a technical responsibility. It’s a moral one.

Feeling Uncomfortable Is a Sign You’re Paying Attention

If AI makes you uneasy, good. That means you’re thinking beyond features and licences.

Progress without reflection is how we end up with systems that optimise everything except humanity.

AI isn’t the enemy. But unexamined efficiency absolutely is.

So instead of asking whether AI will replace jobs, maybe we should be asking something harder:

What kind of organisations are we choosing to build with it?

Because that answer won’t be written by algorithms.
It’ll be written by leaders.

And MSPs will be right there with them, whether they like it or not.

AI Isn’t Replacing MSPs. It’s Exposing the Ones Who Never Built Real Value

image

If you’ve been paying attention to the headlines, you’d be forgiven for thinking AI is about to wipe out half the knowledge economy. Faster answers. Instant content. Automation everywhere.

And yet, when you look closely, something else is happening.

AI isn’t eliminating value.
It’s making shallow value painfully obvious.

For MSPs, this matters more than most people realise.

Because the MSP model has always sat at the intersection of technology and judgement. Tools have never been the differentiator. Thinking has.

There are six very human capabilities that still outperform machines. Not technical skills. Not certifications. But ways of thinking and behaving. And when you translate those into an MSP context, they become a pretty blunt warning:

If your business is built on “doing tasks”, AI will hollow it out.
If it’s built on judgement, taste, and responsibility, AI will amplify it.

Let’s break that down.

1. Questioning beats knowing

AI is incredible at answers. That’s the point.

But MSPs don’t win by having answers. They win by asking better questions than their clients know to ask.

“What’s the cheapest backup?” is an answer problem.
“What are we actually trying to protect, and why?” is a question problem.

The uncomfortable truth is that many MSPs trained themselves to be answer vending machines. Ticket in, solution out. AI will do that faster, cheaper, and without burnout.

The MSPs who survive are the ones who can slow the conversation down, challenge assumptions, and reframe the problem entirely. That’s not automation-resistant. That’s automation-proof.

2. Taste is becoming a commercial advantage

AI can generate endless options: architectures, policies, scripts, proposals, documentation.

What it can’t do is decide what’s good.

Good enough for this client.
Appropriate for this risk profile.
Aligned with this business reality.

That’s taste. And in a world drowning in AI‑generated mediocrity, taste becomes a filter clients are willing to pay for.

MSPs who develop strong opinions, clear standards, and consistent design thinking will stand out. The ones who proudly say “we don’t do it that way” will win more trust than those who say “yes” to everything.

3. Iteration beats perfection

AI encourages speed. MSPs have historically rewarded caution.

The best operators are learning to combine both.

They ship at 80%.
They test with real clients.
They refine relentlessly.

Whether it’s service offerings, internal processes, or security baselines, iteration matters more than ever. AI accelerates drafts. Humans improve outcomes.

MSPs who wait until something is perfect will be outpaced by those willing to learn in public.

4. Composition is where strategy lives

AI is excellent at producing parts.
Humans are better at assembling wholes.

MSPs don’t add value by listing tools. They add value by composing solutions that make sense together: security, compliance, user experience, business constraints, and human behaviour.

Anyone can deploy products. Few can design systems that actually work in the messiness of real organisations.

That synthesis – pulling threads together into something coherent – is not a technical skill. It’s a strategic one.

5. Allocation is the new leverage

The old hero MSP was the one who could do everything themselves.

The modern MSP wins by knowing what should be done by AI, what should be done by people, and what should never be automated at all.

That’s allocation.

Time, attention, tools, staff, AI systems – all aimed deliberately. Not reactively.

MSPs who treat AI as “just another tool” will underuse it. MSPs who treat it as an intelligence multiplier will restructure their businesses around it.

6. Integrity is the real differentiator

AI has no conscience.
No accountability.
No stake in the outcome.

That burden falls squarely on the MSP.

Privacy decisions. Security trade‑offs. Risk acceptance. Truthful advice when the easy path is more profitable.

As AI amplifies impact, integrity stops being a soft value and becomes a leadership skill.

Clients don’t just need faster answers. They need someone willing to say “no”, push back, and protect them from bad decisions – even when AI confidently suggests otherwise.

The bottom line

AI isn’t coming for MSPs.

It’s coming for undifferentiated thinking.

The future belongs to MSPs who lean harder into what makes them human: judgement, taste, curiosity, responsibility, and the courage to think rather than just respond.

When the world gets more artificial, the smartest move an MSP can make is to get more human.

And that’s not a threat.
That’s an opportunity.

The Real Problem Isn’t the Tool. It’s What You Do With It.

image

There’s a pattern I keep seeing in this industry.

A new idea, tool, or capability appears. Everyone rushes to talk about it. Vendors race to slap it on a slide. MSPs add it to a stack diagram. And almost immediately, the conversation gets stuck at the shallow end.

Access is not advantage. Capability is not leverage. And owning the tool is not the same as changing the outcome.

That distinction matters more now than it ever has.

Most MSPs Don’t Have a Technology Problem

They have a thinking problem.

Microsoft Copilot, AI tooling, automation platforms, security frameworks—none of these are scarce anymore. They’re being bundled, discounted, or handed out as “included value” at an alarming rate.

Which means the old MSP reflex kicks in:

“Great, we’ll add this to what we already do.”

And that’s exactly where things break.

Because if you use new tools to reinforce old behaviour, you don’t move forward. You just get louder, busier, and more replaceable.

The Gap Is Not Knowledge. It’s Intent

The uncomfortable truth is this:

Most MSPs already know what the tools can do.

They’ve watched the demos. They’ve read the blogs. They’ve played with the prompts.

What they haven’t done is decide what they’re trying to change.

Tools amplify intent. They don’t create it.

If your intent is:

  • More tickets

  • Faster responses

  • Slightly better utilisation

  • Another feature bullet on your website

Then AI just helps you do those things faster.

But if your intent is:

  • Reducing decision friction

  • Eliminating low‑value work

  • Raising the quality of client conversations

  • Making outcomes visible instead of promised

Then the same tools produce very different results.

Why “We’re Using AI” Means Nothing to Clients

From a client’s perspective, AI is already invisible.

They don’t care that you use Copilot. They care whether:

  • Meetings produce clearer actions

  • Security advice is simpler to act on

  • Reports tell them something they didn’t already know

  • Their staff waste less time chasing information

This is where many MSPs still get it wrong.

They position AI as a feature.

Clients experience it as a by‑product.

And by the time you’re explaining the feature, you’re already late.

Leverage Comes From Redesign, Not Adoption

The biggest mistake MSPs make with modern tooling is trying to bolt it on instead of re‑architecting the workflow.

They ask:

“How do we use Copilot in what we already do?”

Instead of:

“What should no longer exist because Copilot exists?”

That second question is where leverage lives.

  • What reports should disappear?

  • What meetings should stop happening?

  • What decisions should no longer require a human bottleneck?

  • What documentation should auto‑maintain itself?

If nothing gets removed, nothing meaningful has changed.

The MSPs Pulling Ahead Aren’t Louder. They’re Quieter.

The most effective MSPs I see right now aren’t shouting about AI.

They’re:

  • Spending less time explaining

  • Sending fewer emails

  • Running shorter meetings

  • Producing cleaner outputs

  • Making decisions earlier

From the outside, it looks like calm. From the inside, it’s ruthless focus.

That’s the real signal clients notice:

“Things just feel easier when we work with you.”

Not:

“Wow, you use a lot of tools.”

This Is Not a Skills Gap. It’s a Courage Gap.

Let’s be honest.

Redesigning how you work is uncomfortable. Letting go of billable‑looking activities feels risky. Removing process feels like loss before it feels like gain.

So most MSPs compromise. They adopt the tool… …but protect the old model.

And then they wonder why nothing really changes.

Progress doesn’t come from better inputs. It comes from better choices about what no longer deserves your time.

The Question That Actually Matters

If you’re an MSP reading this, here’s the only question worth asking:

What would we stop doing if we truly trusted these tools?

Not next year. Not after more training. Not once “the market is ready”.

Now.

Because the MSPs who answer that question honestly aren’t waiting for permission. They’re quietly building distance.

And by the time everyone else catches up,
the gap won’t be technical.

It’ll be structural.

The Point Isn’t the Tool. It’s What You Do With It.

image

There’s a short video doing the rounds at the moment that a lot of people are nodding along to.

Not because it’s packed with new information.
Not because it introduces some breakthrough idea.

But because it quietly exposes something most MSPs would rather not look at too closely.

We’re very good at having things.
We’re not nearly as good at using them properly.

And no, this isn’t another “AI will change everything” post. It’s about something more uncomfortable than that.

It’s about intent.

Most MSPs Don’t Have a Capability Problem

Talk to almost any MSP today and you’ll hear a familiar list:

  • Microsoft 365

  • Copilot (or at least a licence or two)

  • Security tooling

  • Automation platforms

  • Documentation systems

  • PSA, RMM, scripts, templates, frameworks

On paper, the stack looks impressive.

In reality?
Most of it is sitting there like gym equipment in January.

Owned.
Rarely used properly.
Almost never used deliberately.

The video’s real value isn’t what it shows — it’s what it implies: tools don’t create leverage. Decisions do.

Using Something Isn’t the Same as Leveraging It

Here’s the trap MSPs fall into:

“We’ve deployed it, so we’re using it.”

No, you’re not.

You’re exposed to it.

Leverage only happens when a tool meaningfully changes one of three things:

  1. Speed – you move faster with less friction

  2. Quality – the output is materially better

  3. Capacity – you can do more without more people

If none of those shift, the tool is just decoration.

Copilot that drafts emails you’d write anyway?
Nice. Not leverage.

Automation that still needs babysitting?
Helpful. Not leverage.

Security tooling that generates alerts nobody reads?
Expensive. Definitely not leverage.

The Real Gap Isn’t Technical. It’s Cognitive.

What the video quietly highlights is this:
Most people don’t struggle with access to capability. They struggle with changing how they think.

MSPs love new products because products don’t demand introspection.

But leverage does.

Leverage forces uncomfortable questions:

  • What should we stop doing because the machine can now do it better?

  • What human work actually matters here?

  • What outcome are we optimising for — speed, margin, quality, or control?

  • Are we designing workflows, or just reacting to features?

That’s the part most MSPs skip.

Why This Matters for MSP Business Models

Here’s the uncomfortable truth.

If two MSPs have access to the same tools, the one that wins isn’t the one with the better stack.

It’s the one with the clearer intent.

One MSP uses Copilot to “help staff write faster”. Another redesigns service delivery so first‑pass responses, documentation, and reporting are largely machine‑assisted — and humans step in where judgement matters.

Same licence.
Very different business.

One MSP adds another security platform. Another uses the platforms they already own to reduce noise, tighten scope, and clearly articulate risk to the client.

Same technology.
Different outcomes.

This Is Why So Many MSPs Feel Stuck

They’re busy. They’re licensed. They’re “doing AI”.

And yet… nothing really changes.

Margins don’t improve. Staff are still stretched. Clients don’t magically become easier.

Because activity has replaced design.

The video doesn’t give you a roadmap — and that’s the point. It’s not about copying what someone else is doing. It’s about recognising that leverage is intentional, not accidental.

The Question MSPs Should Be Asking

Not:

“What tool should we add next?”

But:

“What outcome do we want this tool to fundamentally change?”

If you can’t answer that clearly, the tool won’t save you. It’ll just make you busier.

The gap between MSPs who thrive and MSPs who stall is getting wider. Not because of access to technology — but because of how deliberately they use it.

The video is just a mirror.

What you see in it depends entirely on how honestly you’re willing to look.

Staying Up to Date Isn’t a Nice-to-Have for MSPs. It’s the Job

image

Every MSP says they want to “stay up to date”.

Most even believe they are.

But in reality, a lot of MSPs are running today’s clients on yesterday’s knowledge — and hoping no one notices.

The uncomfortable truth is this:
staying current isn’t something you do on the side of your job as an MSP. It is the job.

And the gap between MSPs who understand that and those who don’t is widening fast.

The pace has changed (whether you like it or not)

There was a time when “keeping up” meant:

  • Doing a certification every few years

  • Skimming a release note once a quarter

  • Learning a product properly before it changed again

That world is gone.

Microsoft 365 doesn’t evolve annually. It evolves weekly.
Security threats don’t wait for your next training day.
AI capabilities don’t roll out neatly in versions you can plan for.

And pretending otherwise doesn’t slow any of it down — it just leaves you reacting instead of leading.

The real risk isn’t being behind — it’s thinking you’re not

Most MSPs aren’t failing because they don’t care.

They’re failing because they assume:

  • “We’ve always done it this way”

  • “That feature probably isn’t relevant for SMB”

  • “We’ll look at that later once it’s stable”

Meanwhile, the platform moves on.
Licensing changes.
Security defaults shift.
New expectations appear — often without warning.

Clients don’t see this as “Microsoft changing things again”.

They see it as you not knowing.

Staying up to date isn’t about consuming more content

This is where many MSPs get it wrong.

They try to solve the problem by:

  • Subscribing to more blogs

  • Following more people on LinkedIn

  • Sitting through more webinars

  • Saving more tabs “to read later”

That doesn’t create currency.
It creates noise.

Staying up to date is not about volume.
It’s about signal.

The question isn’t “what’s new?”
It’s “what actually matters for my clients and my service model?”

The difference between awareness and application

Knowing that something exists is not the same as knowing what to do with it.

An MSP who is genuinely up to date can answer questions like:

  • Does this change affect Business Premium customers today?

  • Is this a security uplift, a licensing trap, or a distraction?

  • Does this replace an existing tool or sit alongside it?

  • Is this worth operationalising, or just watching for now?

That’s the difference between reading updates and understanding impact.

And impact is what clients pay for.

Systems beat motivation — every time

No MSP stays current by “trying harder”.

They stay current because they build systems that make it unavoidable.

That usually means:

  • Scheduled time that is protected, not leftover

  • Repeatable review processes (not random learning)

  • Peer discussion, not solo interpretation

  • Turning learning into standards, checklists, and runbooks

If staying up to date relies on motivation, it will fail the moment things get busy — which is always.

If it’s baked into how you operate, it compounds.

Why this matters more now than ever

AI, security, compliance, identity, device management — all of it is converging.

What used to be “advanced” is quickly becoming expected.

Clients won’t ask you if you’ve kept up.
They’ll assume you have.

And when something goes wrong — a breach, a compliance issue, a missed capability — the question won’t be “why didn’t Microsoft tell us?”

It will be “why didn’t our MSP know?”

Staying current is how you stop competing on price

Here’s the part most MSPs miss.

Staying up to date isn’t just about risk reduction.
It’s how you move out of commodity territory.

When you understand what’s changing and why it matters:

  • You stop selling “support” and start selling guidance

  • You stop reacting to tickets and start shaping decisions

  • You stop being compared on hourly rates

Currency creates confidence.
Confidence creates trust.
Trust creates margin.

The uncomfortable but honest conclusion

You don’t get to opt out of staying current anymore.

You can only choose how intentionally you do it.

Because in today’s Microsoft ecosystem, falling behind doesn’t look dramatic.
It looks subtle.
Gradual.
Quiet.

Until one day, you realise you’re no longer leading your clients —
you’re just trying to keep up with them.

And by then, the gap is much harder to close.