Creating Custom Copilot Cowork Skills That Actually Matter for SMBs

If you’re still using Copilot like a fancy chatbot, you’re missing the point.

Copilot Cowork is Microsoft’s quiet shift from AI that answers questions to AI that actually does work. And the real power move for SMBs isn’t the built‑in skills—it’s custom Cowork skills that encode how your business actually runs. [learn.microsoft.com]

This is where Copilot stops being impressive and starts being profitable.

What a Custom Cowork Skill Really Is

A custom Cowork skill is not code, not an agent, and not a Power Automate flow. It’s a structured set of instructions written in a simple SKILL.md file and stored in the user’s OneDrive under:

/Documents/Cowork/Skills/<skill-name>/SKILL.md

Copilot Cowork automatically discovers up to 20 custom skills per user at the start of every conversation and loads them when relevant. No prompting gymnastics required. [learn.microsoft.com]

Think of a custom skill as:

“Every time I do this type of work, follow these rules, pull this data, and produce that output.”

For SMBs, that’s gold.

Example 1: Client Meeting Prep for a 10‑Person Consultancy

The problem:
SMB consultants spend 15–30 minutes before every client meeting digging through emails, Teams chats, and old documents. It’s repetitive, error‑prone, and always rushed.

The custom Cowork skill:
Client Meeting Brief

What the skill does:

Pulls calendar context for the upcoming meeting
Finds recent emails and Teams messages with that client
Identifies open actions from last meeting notes in OneDrive
Produces a 1‑page Word briefing with:
- Client objective
- Outstanding issues
- Risks and next steps

Why it works for SMBs:
It saves time without introducing new tools. Everything stays inside Microsoft 365, using data they already trust. No CRM integration required. [learn.microsoft.com]

Example 2: Weekly Operations Report for an Owner‑Managed Business

The problem:
Business owners hate status reporting, but flying blind is worse. Most weekly reports are inconsistent, late, or ignored.

The custom Cowork skill:
Weekly Ops Summary

What the skill does:

Reviews sent emails and calendar activity from the past 7 days
Pulls key numbers from a defined Excel file in OneDrive
Generates a consistent Word report using the owner’s template
Flags anything that looks overdue or hasn’t progressed

Why it works for SMBs:
Custom skills enforce discipline without admin overhead. The report looks the same every week, uses the same data sources, and takes seconds—not hours—to produce.

Example 3: Standardised Client Follow‑Ups for Professional Services

The problem:
Follow‑up emails are inconsistent. Some are overly casual, others too formal, and key details get missed.

The custom Cowork skill:
Client Follow‑Up Drafter

What the skill does:

Detects completed meetings
Creates a draft email using the company’s approved structure:
- Summary
- Decisions made
- Actions and owners
Saves the draft for approval before sending

Copilot Cowork always asks for confirmation before external communication, which is critical for SMB risk management.

What Doesn’t Work Well as a Custom Skill

Not everything should be a skill.

Avoid:

One‑off tasks (“Summarise this document”)
Highly variable creative work
Anything that relies on local files (Cowork only accesses OneDrive and SharePoint)

The sweet spot is repeatable, boring, but important work.

Why MSPs Should Care (Even More Than SMBs)

For MSPs, custom Cowork skills become:

A standardised service delivery layer
A way to encode best practice for L1–L3 staff
A differentiator that isn’t just “we sell Copilot licences”

You don’t deploy Copilot.
You operationalise it.

Custom Cowork skills are how you turn AI from a novelty into a system—especially in SMB environments where consistency matters more than scale.

If you’re not teaching your customers how to do this, someone else will.

Further reading:
Microsoft Learn – Create custom Copilot Cowork skills
https://learn.microsoft.com/en-us/microsoft-365/copilot/cowork/use-cowork#create-custom-skills

Stop Prompting. Start Delegating: How to Use Copilot Cowork Skills Step by Step

Most people are still using Copilot like a very expensive chatbot. Ask a question, get an answer, move on. Copilot Cowork changes that model completely. Instead of responding once, it takes ownership of work, executes it step by step, and stays with the task until it’s finished—or you tell it to stop. Microsoft calls this a coworker, not an assistant, for a reason.

At the heart of this shift are Cowork skills. These aren’t prompts or templates; they’re defined capabilities Cowork loads dynamically to get real work done across Microsoft 365.

Let’s break down what this actually means and how to start using it properly.

What Are Copilot Cowork Skills (and Why You Should Care)

Copilot Cowork ships with a set of built‑in skills covering common Microsoft 365 workloads—things like documents, email, meetings, research, and scheduling. When you give Cowork a task, it plans the work, selects the relevant skills, and executes them in sequence, showing its progress as it goes.

The key difference from normal Copilot usage is this:

You give one outcome‑based instruction
Cowork figures out the steps
It asks for approval before irreversible actions (like sending an email)
Output is saved directly to OneDrive or SharePoint, ready for use.

This is procedural AI, not conversational AI—and that matters for anyone serious about productivity or governance.

Step 1: Open Copilot Cowork

Start in Microsoft 365 Copilot:

Open the Microsoft 365 Copilot app
Select Cowork from the available agents
You’ll land on the Cowork home page, with suggested starter tasks like:
- Catch me up
- Organise my inbox
- Prepare for a meeting
- Research a company

These aren’t marketing examples—they’re fully functional task starters designed to load the right skills automatically.

Step 2: Enter a Task, Not a Prompt

In the chat input box:

Type what you want done, not how to do it
- e.g. “Prepare me for my meeting with the sales team tomorrow”
Press Enter or select Send
Cowork immediately starts planning and executing the task

Behind the scenes, Cowork decides which skills to use—email, calendar, meetings, documents—based on your request. You don’t need to micromanage this.

Step 3: Add Context with Files (This Is Critical)

Cowork is good by default, but it’s far better with context.

To attach files:

Drag and drop files directly into the chat, or
Select Add attachments and choose:
- Work files from OneDrive, SharePoint, or Teams
- Upload files from your device
- Reference meetings or people from your tenant
Wait for file uploads to complete, then send your task

This is how you stop Copilot guessing and start getting outputs that match how you work.

Step 4: Follow Along While Cowork Works

Once the task starts, you’ll see:

A thinking/processing indicator
Step‑by‑step progress as Cowork executes each phase
Pauses when approval is required for higher‑risk actions

This is deliberate. Microsoft designed Cowork so you stay in control—even when you’re delegating complex, multi‑step work.

Step 5: Resume or Extend the Task

Cowork treats work as ongoing, not single‑use:

Recent tasks appear on the home page
You can resume any task without starting from scratch
You can add new instructions while Cowork is still working

This is especially powerful for research, reporting, and meeting prep workflows.

The Bigger Picture

If you’re still judging Copilot by how clever its answers sound, you’re missing the point. Cowork is about execution, traceability, and control inside your M365 boundary. That’s the real shift—and it’s why skills matter more than prompts.

Used properly, Copilot Cowork isn’t faster typing. It’s labour delegation.

And that’s the mindset change most people haven’t caught up with yet.

Cowork skills – https://learn.microsoft.com/en-us/microsoft-365/copilot/cowork/use-cowork#cowork-skills

Stop Checking. Start Scheduling. How to Use Scheduled Prompts in Microsoft 365 Copilot

One of the biggest mistakes I see with AI adoption is treating Copilot like a fancy search engine.

You jump in, ask a question, get an answer… then disappear for a week and repeat the process.

That’s not transformation. That’s dabbling.

If you want real value from Microsoft 365 Copilot, you need to stop reacting and start automating your intent. One of the easiest ways to do that is by creating a scheduled prompt.

In plain English: instead of remembering to ask Copilot the same question every week, you tell Copilot once to do it for you — on a schedule — and deliver the result where you already work.

Let’s walk through exactly how to do that, using a simple but powerful example:
a regular update on what’s new in Microsoft 365.

What Is a Scheduled Prompt in Copilot?

A scheduled prompt allows you to:

Define what you want Copilot to do
Specify how often it should run
Choose where the results are delivered

Think of it as turning Copilot from a chatbot into a digital analyst that checks things for you while you’re busy doing real work.

For MSPs and IT pros, this is gold. Updates, changes, alerts, summaries — all on autopilot.

Step-by-Step: Creating a Scheduled Prompt in Microsoft 365 Copilot

Step 1: Open Microsoft 365 Copilot

Start in either:

Microsoft Teams (Copilot app), or
copilot.microsoft.com while signed in with your Microsoft 365 account

You want the full Microsoft 365 Copilot, not consumer Copilot.

Step 2: Go to Prompt Management / Scheduled Prompts

Inside Copilot:

Select Prompts or Create a prompt
Choose Scheduled prompt (or “Run on a schedule”, depending on your tenant wording)

This is where you switch from ask once to ask repeatedly.

Step 3: Write Your Prompt (This Matters More Than You Think)

Here’s an example prompt you can copy and adapt:

Each week, provide a clear summary of what is new or changed in Microsoft 365.

Include:
- New features released
- Upcoming changes that are rolling out
- Any features that are being retired or deprecated
- Items that may impact security, compliance, or end users

Summarise the information in plain English.
Highlight what matters most for SMBs and IT administrators.
Include links to official Microsoft documentation where available.

Notice what’s missing?

No hype. No vague “tell me about”.
You’re setting expectations, scope, and audience.

That’s how you get useful output.

Step 4: Set the Schedule

Now tell Copilot when to run it:

Frequency: Weekly
Day: Pick something predictable (Monday or Friday work well)
Time: During business hours so it’s there when you are

Copilot doesn’t get tired. Use that.

Step 5: Choose the Delivery Location

This is where Copilot shines compared to standalone AI tools.

You can send the output to:

A Teams chat with yourself
A Teams channel (great for internal IT updates)
Your email
A OneNote page for long-term knowledge capture

My recommendation?
A private Teams chat or a dedicated “Microsoft 365 Updates” channel.

Meet people where they already are.

Why This Actually Changes Behaviour

Here’s the real win.

Once Copilot delivers the information without you asking, you:

Stop missing updates
Stop reacting late to changes
Start scanning trends instead of chasing announcements

That’s how Copilot moves from interesting tool to operational advantage.

And once people see this working, the conversation shifts from:

“What can Copilot do?”

to:

“What should we automate next?”

That’s when adoption sticks.

If you’re rolling Copilot out to an SMB or MSP client and you haven’t shown them scheduled prompts, you’re leaving value (and credibility) on the table.

Copilot isn’t there to answer questions.

It’s there to remove them completely.

You’re Using Copilot Backwards (And It’s Costing You Time)

Most people say Copilot “isn’t very good”.

What they really mean is they’re doing all the hard work themselves and then tossing Copilot a half‑finished task at the end, hoping it magically improves things.

It won’t.

If you’re spending 80% of the effort thinking, drafting, structuring, and deciding — and then asking Copilot to “clean it up” — you’ve already missed the point. At that stage, Copilot isn’t an assistant. It’s just a fancy spell‑checker.

And I see this constantly with business users and MSPs rolling out Microsoft 365 Copilot.

The Common Copilot Anti‑Pattern

Here’s what usually happens:

Someone writes most of an email, proposal, policy, or presentation themselves
They paste it into Copilot
They ask: “Can you make this better?”

Copilot shrugs (digitally), rewrites what you already decided, and gives you something that feels… underwhelming.

So the conclusion becomes: “Copilot isn’t worth it.”

Wrong diagnosis.

The real issue is how Copilot is being used.

Copilot Isn’t Meant to Finish Your Thinking

Copilot shines when it’s allowed to do the thinking with you, not after you’ve already locked everything in.

If you treat Copilot like a junior admin who only gets the task once the design is finished, don’t be surprised when the output adds little value.

Microsoft 365 Copilot works best when you reverse the flow:

You define where you want to end up
Copilot helps work out how to get there

That’s a fundamental mindset shift — especially for technical people who are used to solving everything themselves.

Outcome First. Steps Later.

Instead of feeding Copilot instructions, templates, or half‑baked drafts, start with the result you want.

For example:

“I need a customer‑friendly explanation of why MFA is non‑negotiable”
“I need a repeatable onboarding sequence for new Microsoft 365 customers”
“I need internal guidance for staff on safe Copilot usage with client data”

Notice what’s missing?
No steps. No structure. No micromanaging.

Just the destination.

Copilot is very good at mapping routes — if you stop insisting on driving the whole way yourself.

Make Copilot Do the Heavy Lifting

Here’s the part most people skip: context discovery.

Instead of guessing what Copilot needs and dumping everything into one massive prompt, tell Copilot to interrogate you.

Ask it to identify the missing context.

For example:

Ask Copilot to identify the key assumptions it needs
Let it surface the constraints, tone, audience, or risks you haven’t considered
Answer those questions clearly — then step back

This is where Copilot becomes genuinely useful. You’re no longer wrestling with a blank page or reworking mediocre drafts. You’re guiding a system that can reason across your Microsoft 365 data, your documents, your emails, and your environment.

That’s the real power MSPs should be showing customers.

Why This Matters for SMB Copilot Adoption

SMBs don’t need another tool. They need leverage.

Copilot isn’t about typing faster. It’s about:

Better decisions
More consistent communication
Less mental load on key staff
Fewer bottlenecks around “the one person who knows”

But only if it’s introduced correctly.

If your Copilot rollout training is just “click here and type this”, you’re setting everyone up for disappointment. Copilot adoption succeeds when users understand how to think with it, not just how to prompt it.

The Simple Rule to Remember

You provide the destination.

Copilot helps chart the course.

If you’re doing most of the thinking before Copilot ever gets involved, you’re paying for a Ferrari and pushing it uphill.

Use Copilot earlier. Trust it more. And stop asking it to finish work you should never have started alone in the first place.

That’s when Microsoft 365 Copilot stops being a novelty — and starts being a competitive advantage.

The Real Challenge with AI Isn’t Accuracy — It’s That It’s Probabilistic, Not Deterministic

One of the hardest mindset shifts people are struggling with in the age of AI isn’t learning how to use the tools.

It’s unlearning how we expect technology to behave.

For decades, IT has trained us to think in deterministic terms. Same input, same output. Every time. If it doesn’t work that way, it’s broken and we fix it.

AI doesn’t work like that. And pretending it does is where most of the frustration, fear, and failed deployments come from.

We Built Our Businesses on Determinism

Traditional IT systems are deterministic by design. Firewalls either block traffic or they don’t. Conditional Access policies either allow sign-in or they don’t. Accounting software produces the same report today as it did yesterday, assuming the data hasn’t changed.

That determinism is comforting. It’s auditable. It’s predictable. It’s what allows MSPs to scale, standardise, document, and support environments consistently.

AI blows a hole straight through that expectation.

Large language models don’t know things in the way traditional systems do. They predict. They generate the most statistically likely next word based on context, patterns, and probability. That means two identical prompts can produce slightly different outputs — both valid, both reasonable, neither “wrong”.

For IT people, that feels deeply uncomfortable.

“Why Did It Give Me a Different Answer?”

This is the number one complaint I hear from business owners and technicians alike.

“I asked Copilot yesterday and it gave me a better answer.” “It worked last time — why is this one different?” “How can I trust something that changes its mind?”

Here’s the blunt truth: AI isn’t changing its mind. It never had one.

It’s doing exactly what it was designed to do — generate a probabilistic response, not execute a fixed rule.

If you approach AI expecting it to behave like a script, a policy, or a PowerShell command, you will be disappointed every single time.

Probabilistic Systems Are Not Broken — They’re Different

Probabilistic systems excel in areas deterministic systems are terrible at:

Interpreting vague human language
Summarising messy, unstructured data
Generating ideas, drafts, options, and variations
Adapting to context rather than rigid rules

But they are fundamentally unsuitable for tasks that require absolute consistency, precision, or compliance on their own.

This is where many AI projects go off the rails. Organisations try to replace deterministic processes with probabilistic tools instead of augmenting them.

AI shouldn’t decide whether a user gets admin rights. AI shouldn’t be the sole source of truth for compliance decisions. AI shouldn’t replace controls that require repeatability and audit trails.

That’s not a failure of AI — it’s a failure of design.

The MSP Problem: Clients Expect Certainty

As MSPs, we’re in a tough spot.

Our clients expect answers, not probabilities. They want confidence, not “it depends”. They want systems that behave the same way every day.

When we introduce AI into that environment without resetting expectations, we inherit the blame for its uncertainty.

This is why AI needs guardrails:

Defined use cases
Clear boundaries
Human-in-the-loop review
Deterministic systems underneath probabilistic ones

AI is brilliant at drafting the email. It’s terrible at deciding whether it should be sent.

Prompting Is an Attempt to Add Determinism

A lot of what we call “prompt engineering” is really just us trying to force probabilistic systems to behave more deterministically.

We add structure. We add constraints. We add role instructions. We add examples.

And it works — to a point.

But it never becomes fully deterministic, and that’s the trap. The moment you treat AI output as authoritative instead of assistive, you create risk.

The Opportunity Is in Hybrid Thinking

The organisations that will win with AI aren’t the ones chasing perfect answers.

They’re the ones designing hybrid systems:

Deterministic workflows for control and compliance
Probabilistic AI for insight, acceleration, and creativity

AI doesn’t replace judgment — it amplifies it. It doesn’t remove responsibility — it redistributes it. And it absolutely doesn’t eliminate the need for human oversight.

The Mindset Shift That Matters

The real challenge with AI isn’t hallucinations. It isn’t accuracy. It isn’t even security.

It’s accepting that we’ve invited a non-deterministic system into a world built on certainty.

Once you stop trying to make AI behave like traditional software, and start designing around what it actually is, everything gets easier.

And far more powerful.

Watching Copilot Videos Isn’t the Same as Using Copilot

There’s a mistake I see constantly when it comes to Microsoft 365 Copilot adoption.

People think they’re “learning” Copilot because they’re consuming content about it.

Videos. Webinars. Tutorials. Prompt lists. Social posts. Endless demos showing what might be possible one day.

It feels productive. It looks productive. But it’s mostly theatre.

You can easily spend hours watching Copilot content and still be no better at using it in your actual work. I see it all the time with MSPs and business users who say, “I’ve watched heaps of Copilot videos, but I don’t really use it yet.”

That’s not a Copilot problem. That’s a learning problem.

Copilot isn’t something you understand by observing. It’s something you understand by friction — by using it badly, getting average results, refining your approach, and slowly integrating it into what you already do every day.

Until Copilot is touching real work, it’s just entertainment.

The Gap Between Knowing and Doing

Here’s the uncomfortable truth:
Most people don’t fail at Copilot because it’s too complex. They fail because they never move it into their workflow.

They treat Copilot like a separate activity. Something to “play with” when they have time. Something they’ll roll out properly later. Something they’ll get serious about once they’ve watched enough tutorials.

That moment never comes.

Meanwhile, the people getting real value from Copilot aren’t the ones with the biggest prompt libraries. They’re the ones who picked one boring, repeatable task and handed it to Copilot without overthinking it.

Not tomorrow. Not next quarter. Today.

The Only Fix That Actually Works

If you want Copilot to stick, stop thinking about everything it could do and focus on one thing you already do.

Every single day.

Something mundane. Something slightly annoying. Something that consumes mental energy but doesn’t really need to.

For most people, that’s one of these:

Summarising meeting notes
Drafting emails or client updates
Turning rough ideas into a first draft
Rewriting content to sound clearer or more professional
Pulling key points out of documents or threads
Preparing agendas, reports, or handover notes

Pick one. Just one.

Then deliberately route that task through Copilot every time you do it.

Not as an experiment. Not as a test. As the default.

Where Copilot Actually Shines for SMBs

This is where Microsoft 365 Copilot quietly outperforms standalone AI tools, especially for SMBs.

Copilot already lives where the work lives.

Your emails are in Outlook.
Your documents are in Word and SharePoint.
Your notes are in OneNote.
Your conversations are in Teams.

Copilot doesn’t need you to copy and paste everything into a separate interface. It works in context, with the data you already have permission to access.

That’s not a “nice to have”. That’s the difference between novelty and adoption.

When Copilot becomes part of an existing workflow — instead of another tool to manage — usage stops being optional. It becomes habitual.

Habits Beat Tutorials Every Time

Here’s what real Copilot learning looks like:

You use it.
The output isn’t great.
You adjust how you ask.
You try again tomorrow.
It gets slightly better.
You trust it with more work.
You stop thinking about “using AI” and just get work done faster.

That cycle never starts by watching another video.

It starts when Copilot saves you five minutes on something you do every day. Then ten. Then thirty.

And once that happens, you don’t need motivation to keep using it. You feel the absence when you don’t.

Start Smaller Than You Think

If you’re advising clients — or trying to get your own team using Copilot — stop leading with features and demos.

Lead with behaviour change.

One task. One workflow. One daily habit.

That’s how Copilot stops being interesting and starts being indispensable.

And that’s the difference between “we’ve enabled Copilot” and “we actually get value from Copilot.”

Why Most People Fail at AI (and How Copilot Fixes That)

I see the same pattern play out with AI adoption over and over again.

People collect tools.

ChatGPT for writing.
Another AI for images.
Something else for meetings.
Yet another for data analysis.

Before long, they’re juggling half a dozen interfaces, prompts, logins, and workflows. The result isn’t leverage. It’s fragmentation. Lots of motion, very little progress.

Learning AI this way is like trying to learn three musical instruments at the same time. You might make some noise, but you won’t make music. Depth never comes from constant switching.

That’s why most AI initiatives stall.

The problem isn’t capability.
It’s focus.

Depth Beats Breadth Every Time

Real skill—whether it’s music, sport, or technology—comes from going deep before going wide. You don’t become competent by tasting everything. You get there by committing to one thing long enough to understand how it really works.

AI is no different.

If you want genuine productivity gains, you need to stop asking “Which AI tool should I try next?” and start asking “Which AI fits how I already work?”

For most SMBs and MSPs, the answer is obvious: Microsoft 365 Copilot.

Not because it’s flashy. Not because it’s perfect. But because it lives inside the tools you already use every day.

Copilot Wins Because It’s Embedded, Not Exotic

Copilot isn’t another destination you have to remember to visit. It’s not a separate browser tab or a disconnected chatbot. It sits inside Outlook, Word, Excel, Teams, SharePoint, and OneNote—the places where work actually happens.

That matters more than people realise.

When AI is embedded into your existing workflows, learning accelerates naturally. You don’t have to rethink how you work. You just augment it.

Drafting emails becomes faster.
Meeting notes stop being an afterthought.
Documents evolve instead of restarting from scratch.
Data gets explained, not just displayed.

This is where Copilot shines for SMBs: incremental improvement at scale, without cultural whiplash.

The 30‑Day Commitment Most People Avoid

Here’s the uncomfortable truth: most people never master Copilot because they never commit to it.

They test it once or twice, get a mediocre result, and move on. That’s not evaluation. That’s impatience.

If you want Copilot to deliver value, treat it like a skill, not a shortcut.

Commit to using Copilot as your primary AI for 30 days.

Not casually. Deliberately.

Use it every day.
Ask better questions.
Refine your prompts.
Push it into edge cases.
See where it breaks—and why.

That’s how understanding forms.

Copilot has quirks. It has limits. It has strengths that only become obvious once you stop dabbling and start relying on it.

Master One, Then Sequence

Once you truly understand Copilot—how it reasons, where it adds value, where it needs structure—you’re in a much stronger position to evaluate other AI tools.

At that point, adding another tool is a strategic decision, not a distraction.

This is the sequencing most organisations get wrong. They expand too early, before they’ve extracted value from what they already have.

Masters don’t rush to accumulate.
They build depth first.
Then they extend deliberately.

The Real AI Advantage for SMBs

The competitive advantage with AI isn’t having access to the most tools. Everyone has access now.

The advantage comes from consistent execution.

SMBs that win with AI won’t be the ones chasing every new model. They’ll be the ones that picked a single, integrated platform, learned it properly, and embedded it into daily work.

For most, that platform is already licensed, already deployed, and already waiting.

Microsoft 365 Copilot isn’t the loudest option.
It’s the most practical one.

And in business, practicality beats novelty every time.

Copilot Adoption: Where Your Customers Really Sit on the Curve

The image above should look familiar. It’s the classic technology adoption curve: Innovators, Pioneers (early adopters), the Majority, Late Majority, and Laggards. It’s been used for decades to explain why new technology doesn’t spread evenly. What’s interesting is how clearly Microsoft Copilot now fits into this model — and what that means for MSPs and business leaders trying to drive real adoption, not just licence sales.

Right now, most organisations experimenting with Copilot sit firmly on the left side of the curve. Innovators (roughly 2.5%) are the people who will try anything new just to see how it works. They don’t need much convincing. Give them access and they’ll start prompting, breaking things, and discovering value on their own.

Next come the Pioneers, about 13.5%. These are forward‑thinking leaders, power users, and teams who see Copilot as a competitive advantage. They’re curious, optimistic, and willing to tolerate some friction. Most early Copilot success stories live here — not because Copilot is “done”, but because these users are motivated enough to push through the learning curve.

The real challenge — and opportunity — sits in the middle.

The Majority (34%) won’t adopt Copilot because it’s exciting. They’ll adopt it because it clearly makes their work easier, faster, or better than what they’re doing today. This group doesn’t want AI theory, prompt engineering jargon, or hype. They want specific outcomes: “Will this save me time writing emails?”, “Will this help me understand documents faster?”, “Will this reduce rework?”

This is where most Copilot rollouts stall.

Too many deployments assume that once licences are assigned, value will magically appear. It won’t. The Majority needs structure: role‑based scenarios, simple starting prompts, guardrails, and reassurance that using Copilot won’t break anything or get them into trouble. Adoption here is less about technology and more about change management.

The Late Majority (another 34%) are even more cautious. They adopt only when Copilot becomes the normal way of working — when peers are already using it and the risk of not using it feels higher than the risk of trying. For this group, success stories, internal champions, and visible leadership usage matter far more than features.

Finally, the Laggards (16%) will resist until the very end. Some will never fully adopt, and that’s fine. Copilot doesn’t need 100% usage to deliver value. Forcing it here usually creates more friction than benefit.

The key takeaway from the image is this: Copilot adoption is not a technical rollout, it’s a staged journey. Each segment of the curve needs a different approach. Innovators need freedom. Pioneers need enablement. The Majority needs clarity and proof. The Late Majority needs confidence and social validation.

For MSPs, this changes the conversation. Success isn’t measured by how fast you sell Copilot licences, but by how effectively you help customers move from left to right on the curve. Those who focus on outcomes, education, and real‑world workflows will win. Those who treat Copilot like just another SKU will get stuck in the trough — wondering why “no one is using it”.

Copilot isn’t early anymore. But meaningful adoption still is.