AI Is Coming for Your Business — Will It Be Your Best Hire or Your Biggest Risk?

Last week I watched a business owner ask Copilot to summarise a forty-message email thread, draft a reply, and pull the three action items into a list — all before his coffee had cooled. He looked up and said, half-joking, “That’s better than the temp I hired last summer.” Then his face changed. “Wait. Is this thing safe? Where did all that just go?”

That single moment is the whole argument. The same tool that feels like your sharpest new employee can, in the wrong setup, feel like your most exposed liability. Both reactions are correct. The question isn’t whether AI is coming for your business — it already walked in the door the day you switched on Microsoft 365 Copilot. The question is which version of it you’ve actually hired.

The best hire you’ve ever made

Let me be honest about why people fall in love with this stuff. A good hire doesn’t need everything spelled out. They pick up context, remember what happened last quarter, and get on with it. That’s exactly what Copilot does when it’s grounded in your own data.

Ask it in Outlook to catch you up on a client you haven’t spoken to in a month, and it reads the thread history, the meeting notes in Teams, and the proposal sitting in SharePoint — then hands you a briefing. Drop a messy spreadsheet of sales numbers into Excel and ask which region slipped, and it tells you, with the reasoning, in seconds. Walk into a meeting late and Copilot in Teams gives you what you missed and what you’re expected to say.

This isn’t a chatbot answering trivia. It’s a capable assistant working across your inbox, your documents, your calendar — the same surfaces your team already lives in. For a small business that can’t afford a chief of staff, that’s genuinely levelling. I’ve seen one-person operations punch well above their size simply because the admin grind stopped eating their day.

The biggest risk you haven’t priced in

Here’s where I get less comfortable. The thing that makes Copilot powerful — it can see your data — is exactly the thing that should make you cautious. A new hire who can read every file in the building is only safe if the building has locks on the right doors.

Most small businesses don’t. Permissions sprawl over years. That old SharePoint site “everyone” can access. The shared mailbox nobody cleaned up. The folder of contracts a departing staff member could still open. For years that mess was survivable because nobody had the time to go digging through it. Copilot has all the time in the world, and it digs instantly. Ask it the wrong question and it might cheerfully surface salary figures, a confidential deal, or a client’s private details to someone who was never meant to see them.

That’s not Copilot misbehaving. That’s Copilot doing precisely what you asked, on top of a foundation you never tidied. The tool didn’t create the risk — it just made your existing mess searchable at the speed of conversation. Tools like Microsoft Purview and proper access reviews in Entra exist for this reason, but most businesses I talk to haven’t touched them.

So which one did you hire?

The uncomfortable truth is that you don’t get to choose between “best hire” and “biggest risk” as two different products. They’re the same product. The difference is entirely in the preparation you did before turning it loose.

A great new employee with no onboarding, no boundaries, and access to everything is a liability waiting to happen — that’s true of people and it’s true of AI. The businesses getting real value from Copilot are the ones that did the boring work first: cleaned up who can see what, set sensitivity labels on the documents that matter, and decided deliberately what the tool should and shouldn’t reach.

The ones treating it as a magic switch are the ones who’ll have a very bad day, probably one they won’t even notice until a client mentions seeing something they shouldn’t have.

I’m not in the camp that says slow down and wait. The advantage is real and the businesses that move now will pull ahead. But I am firmly in the camp that says you wouldn’t hand a new starter the keys to the entire business on day one without a single conversation about boundaries. Give your AI the same respect.

Hire it well, and it’s the best decision you’ll make this year. Hire it carelessly, and it’s the breach you’ll spend next year explaining.

The Gap Is The Point

Someone asked me last week what my goals were for the next twelve months. I gave the usual answer — bigger speaking calendar, more clients, a couple of certifications I’ve been putting off. Standard stuff. Then I drove home and realised the answer I’d just given was the version of me that exists today talking. Not the version I’m trying to become. There’s a difference, and most of us never sit with it long enough to feel it.

I’ve started thinking about my future self as a separate person. Not a fantasy figure, but the version of me five years from now who reads what I’m reading now, sits in the rooms I’m sitting in now, eats what I’m eating, wakes up with the habits I’m building today. That person already exists in outline. Every choice I’m making is voting for who they turn out to be.

The inputs are the outputs

The honest truth is that almost nobody wakes up in five years and accidentally becomes someone better. The reading you do, the people you stay close to, what you put on your plate at lunch, the routines you let calcify — those are the materials. There is no secret fifth ingredient. If you don’t like where you’re heading, change one of the four. That’s the whole lever.

The trap is thinking the future version of you is waiting for some big reinvention moment. A course, a milestone, a quiet six months. That moment never arrives. The future you is being built right now, in the tiny decisions you barely notice — the email you snap off in two seconds versus the one you take three minutes to write properly, the meeting you let drift versus the one you tighten with an agenda before walking in.

What would the better version do right now

This is the question I keep coming back to. Not what would I do — what would the sharper, calmer, more focused version of me do with this hour? The one I’m trying to become. It reframes everything. The reply I was about to send, the meeting I was about to accept, the rabbit hole I was about to fall into. Most of the time the answer is obvious; I just don’t want to hear it.

This is also where Copilot has quietly changed how I work. When I open Outlook in the morning and ask Copilot to summarise overnight threads, the better version of me actually has time to think instead of reacting to a triage queue. When I sit down to a Teams meeting and let Copilot handle the recap, I’m fully present in the conversation rather than half-scribbling notes. The point isn’t the feature — it’s that the friction keeping me stuck in version-of-me-today gets quietly removed. The future me has more room to show up.

Direction, not failure

Most people read the gap between who they are and who they want to be as evidence they’re falling short. I read it the other way. The gap is the only signal that tells you which way to walk. If there’s no gap, you’ve stopped growing. If the gap is huge, that’s not a problem — that’s a map.

So this week I’m watching what I read, who I sit with, what I put on my plate, and which habits I’m letting form by accident. Five years sounds like a long time. It isn’t. It’s about 1,800 versions of today, stacked on top of each other. The future me is being built in the next hour. So is yours.

Copilot audit logs in Purview

Most people ask the wrong question about Copilot.

They ask “is it safe?” What they mean is “can it leak our stuff?” Fair worry. But it’s the wrong place to start.

The real question a client should be asking is “can you show me what Copilot has been doing?” Because if the answer is no, safe or not doesn’t matter. You’re flying blind.

Here’s the thing nobody tells you in the licensing pitch. Every Copilot interaction is already being recorded. You don’t have to buy anything. You don’t have to flip a switch. It’s been sitting in the unified audit log the whole time, waiting for someone to go look.

Most MSPs never do.

What is Copilot audit logging, really?

It’s the receipt for every conversation your users have with Copilot.

When someone asks Copilot in Word to summarise a document, or asks Copilot in Teams what they missed, that interaction writes a record into Microsoft Purview. Who did it. When. Which Copilot app. And — this is the part that matters — which files and resources Copilot reached into to answer.

This happens automatically as part of Audit (Standard), which is on by default for business tenants. If auditing is running, Copilot logging is running. Microsoft spells it out in the audit logs for Copilot and AI applications docs: no extra steps, no separate config.

That’s not a feature you enable. That’s a feature you’ve been ignoring.

Step-by-Step: finding Copilot activity in Purview

Open the Audit solution

Go to the Microsoft Purview portal at purview.microsoft.com, sign in, and pick Audit from the Solutions list on the left. If you’ve got the Audit Logs or View-Only Audit Logs role, you’ll land on the search page. If you don’t, that’s your first job — sort the permissions, per the search the audit log guidance.

Set your date range and activity

Pick a start and end date. Then in the activities filter, search for the Copilot record type.

RecordType: CopilotInteraction
Activity:   Interacted with Copilot

Notice what’s missing? No prompt text in that filter. The audit row tells you that a conversation happened and what files it touched — it doesn’t hand you the back-and-forth wording. That content lives elsewhere, retained for eDiscovery and Communication Compliance, not in the row you’re reading. Knowing that distinction is what separates someone who’s read the docs from someone who’s guessing.

Run the search and read the resources

Start the job. It keeps running even if you close the browser, and finished searches stick around for 30 days. Open a result and look at the AccessedResources field. That’s the gold. It shows the actual files Copilot pulled in to ground its answer.

This is where oversharing shows up. If Copilot is referencing a payroll spreadsheet for someone in the warehouse, you didn’t find a Copilot problem. You found a permissions problem Copilot just made visible.

Export when you need a paper trail

Push the results to CSV. Now you’ve got evidence, not anecdotes.

Why this actually changes the client conversation

Walk into a renewal with “Copilot is secure, trust me” and you sound like every other reseller.

Walk in with “here’s a report of every file Copilot accessed last quarter, and here are the three oversharing issues we caught and fixed” — that’s a different meeting. That’s you doing governance, not selling a licence.

“Wait, so I can actually prove Copilot isn’t quietly reading files it shouldn’t?”

Yes. And that single sentence is worth more to a nervous business owner than any feature slide.

One caveat worth knowing. Retention isn’t infinite and it isn’t equal. On most Business Premium tenants you’re looking at 180 days. On E5, key workloads stretch to a year, and you can build longer audit log retention policies if compliance demands it. If a client needs to answer “what happened nine months ago,” check the retention before you promise the answer exists.

This is the stuff cyber insurance forms ask about. It’s what SMB1001 and Essential Eight assessors want to see. Not “do you have Copilot.” But “can you account for what it did.”

Copilot doesn’t forget. Make sure you can read what it remembers.

If you’ve rolled Copilot out to a client and you can’t pull this report, you haven’t finished the rollout. You’ve just started the part nobody bothered to do.

Copilot in Outlook

Most people meet Copilot in Outlook through the Draft button. They click it, type “write a reply saying yes”, watch it produce three paragraphs of corporate waffle, and quietly decide the whole thing is overrated.

I get why. That’s the demo everyone shows. It’s also the least interesting thing Copilot does in your inbox.

The real value isn’t writing email faster. It’s reading it faster.

Think about where your time actually goes. It’s not composing. It’s the forty-message thread you got CC’d on at 4pm — the one you have to scroll to the bottom of and reconstruct before you can say anything useful. That’s the tax.

So before you write a single prompt, flip the question. Don’t ask “what can Copilot write for me?” Ask “what am I wasting time reading?”

What is Copilot in Outlook, really?

It’s two jobs wearing one badge.

The first job is Summarize. Open a long thread and there’s a “Summary by Copilot” card sitting at the top. One click boils the thread down to who said what and what’s still outstanding — with little numbered references back to the actual messages, so you can check it didn’t invent anything.

The second job is Draft. You give it an instruction, it writes the email, you fix the bits it got wrong. Tone and length are dials, not destiny.

Notice the order I put those in. Summarize first. For most people that’s eighty percent of the value — and nobody demos it.

Step-by-Step: getting actual value out of it

Summarise before you read

Open any thread more than a few replies deep. Click Summary by Copilot at the top of the message. Read the summary, then jump straight to the messages it references. You’ve just skipped the scroll.

Draft by pointing, not pleading

Here’s the prompt pattern that works:

Reply to the client agreeing to the Tuesday 2pm slot,
confirm I'll send the agenda by Friday, keep it short and warm.

Notice what’s missing? No “please write a professional email that…”. No throat-clearing. You point at the decision and the facts, and Copilot handles the wording. Vague in, vague out — every time.

Set the tone, then get out of the way

Before you generate, open the tone and length options. Pick direct and short for internal mail. Save formal for the email going to a client’s lawyer. Microsoft’s own walkthrough covers drafting an email with Copilot if you want the full button tour.

Always read it before you send

Copilot will confidently add a detail you never gave it. The draft is a starting point, not an outbox.

The shared mailbox trap that catches everyone

Here’s the one that generates support tickets.

Your client runs everything out of info@ or accounts@. They turn on Copilot, open the shared mailbox, hit Summarize… and nothing. The button’s missing, or it tells them it has no knowledge of that mailbox.

For a long time, Copilot in Outlook only worked on your primary mailbox. Shared and delegate mailboxes were off-limits — the single most common “is this thing broken?” question I get.

That’s finally changing. Microsoft now supports Copilot in shared and delegate mailboxes, but the fine print matters: the person using it needs the right level of access, the mailbox has to live in Exchange Online, and encrypted messages still can’t be read. So when a client says “it doesn’t work in our support inbox”, you can tell them why — and what to check — instead of shrugging.

That’s the difference between an MSP who resold Copilot and one who understands it.

Why this actually changes behaviour

“I’ll get to my inbox after lunch.”

That sentence is a productivity confession. Inbox triage gets deferred because it’s expensive — every thread is a small act of reconstruction before you can act.

Summarize makes that cost almost nothing. When reading a forty-message thread takes ten seconds instead of ten minutes, you stop quarantining email into a dreaded afternoon block and start clearing it in the gaps between meetings.

That’s not a feature. That’s a different relationship with your inbox.

Your inbox doesn’t pay you to read. It pays you to decide.

My recommendation? Teach clients Summarize first, Draft second. Draft is the headline. Summarize is the reason they’ll keep the licence.

If you’re not showing them both — and the shared mailbox gotcha — you’re leaving the best part of what they’re already paying for sitting in the box.

Consistency Doesn’t Show Up When Things Are Comfortable

A good month in an MSP can hide a lot. The pipeline is healthy, the techs are humming, the client tickets are getting closed, and Friday afternoon feels almost calm. In those weeks, every business looks disciplined. Every process looks tight. Every standard looks honoured.

That’s not consistency. That’s just a quiet stretch.

The real test arrives when something breaks — a bad migration, a difficult client, a tech walking out, a month where revenue doesn’t land. That’s when you find out whether your standards live in your head or live in the way your business actually behaves.

The discipline you don’t see in a good month

I’ve watched MSPs run beautifully for a quarter and then quietly drop the things that made them beautiful the moment work got heavy. The monthly client reviews stop. The patching cadence slips. The onboarding checklist becomes “we’ll get to that next week.” Nobody decides to lower the bar. It just happens, one small omission at a time, until what was a standard is now just a story you tell prospects.

What I’ve come to respect is the unglamorous stuff that keeps going regardless of mood. The same Monday standup at the same time every week. The same security baseline applied to every new tenant. The same call to a client at the same point in their lifecycle, even when there’s nothing wrong. Those rhythms only feel valuable when things get bumpy — and by then it’s too late to start them.

Build the rhythm, then defend it

This is where I think a lot of MSPs underuse what’s already sitting in their stack. A weekly cadence in Microsoft Planner with the same recurring tasks, surfaced through a Teams channel everyone actually opens, is more useful than a polished playbook nobody reads. A standing client review template in Word, kept in the same Teams tab month after month, builds a record that shows whether you actually turned up.

Copilot helps here in a way I didn’t fully appreciate until recently. Asking Copilot in Outlook to summarise a client’s last quarter of email before a review meeting takes ninety seconds and means the conversation starts with something real. Asking Copilot in Teams to recap the last three internal stand-ups before a leadership meeting means decisions don’t get re-litigated. Asking it to pull the highlights from a SharePoint site of project notes before a Monday catch-up turns ten minutes of digging into one minute of reading. The point isn’t the time saved — it’s that the rhythm becomes easier to maintain on the day you’d rather skip it.

Tools don’t create consistency. But the right ones lower the friction enough that you keep showing up on the days you don’t feel like it.

When nobody’s watching

The reason consistency is hard isn’t intelligence or capability. It’s that nobody claps for it. Doing the same review the same way for the eighteenth time in a row produces no dopamine. No client thanks you for the patches that didn’t cause an outage. No prospect signs because your internal documentation happens to be current.

But the MSPs I see growing steadily — not in spikes, but year after year — are almost always the ones doing the boring things on the bad days as well as the good ones. That’s the only kind of consistency that actually compounds, and it’s almost never visible from the outside until much later.

So the question I keep asking myself, and the one I’d put to anyone running an MSP right now, is simple. What did you still do well last month, when nothing was easy? That’s the answer that tells you who you actually are as a business.

Why "I Don’t Have a Good Idea" Is Almost Never the Real Problem

I have a conversation almost every week that goes the same way. Someone tells me they want to start their own thing. They want a bit more control over their time, a bit more income, a path that doesn’t rely on a payslip landing every fortnight. Then they sigh and say the same line: “I just don’t have a good idea.”

I used to nod along. Now I push back. Because in nearly every case, that’s not what’s actually going on.

The skills are already there

Sit with someone for half an hour and ask them what they’ve done in the last decade of work. You’ll hear about budgets they’ve cleaned up, teams they’ve coached, customers they’ve calmed down, processes they’ve quietly fixed without ever being asked. They’ve negotiated with suppliers, written training material on the fly, run projects with no formal authority, and kept things moving when the org chart said they shouldn’t have been able to.

That’s not a person without a good idea. That’s a person sitting on a stack of skills they’ve never priced.

The gap isn’t capability. The gap is translation — taking what they already do well and shaping it into something a stranger would happily pay for.

Why people freeze at the start

The freeze happens because “find an idea” is the wrong instruction. It sends people hunting for a thunderbolt — some clever niche nobody else has noticed, some product the world has never seen. So they wait. They scroll. They tell themselves they need to read another book or finish another course before they’re ready.

Meanwhile, the offer they could already build is sitting in plain sight: the thing colleagues keep asking them for help with, the problem they solved twice at their last job, the work they actually enjoy that most people genuinely struggle with.

The question isn’t “what’s a brilliant new idea?” The question is “what do I already do well that someone, somewhere, has a real problem paying to get done?”

Use the tools to pull the offer out of your head

This is where I think modern tooling — and Copilot in particular — earns its place for first-time business owners. Not because it hands you an idea, but because it pulls one out of you far faster than you could working alone with a blank notebook.

Open a fresh document in Word, switch on Copilot, and have it interview you. Ask it to walk you through your last five roles and pull out the recurring problems you solved. Ask it to draft three different one-page offers from those skills, each aimed at a different type of customer. Drop your LinkedIn profile into a Loop page and ask Copilot to suggest who would benefit most from the work you’ve already done. Then take the strongest lines into a Teams chat with someone whose judgement you trust and pressure-test them.

In an afternoon you can move from “I don’t have an idea” to three rough offers on a page. None of them have to be perfect. They just have to be concrete enough to test in a real conversation with a real person.

The shift that matters

Financial freedom rarely begins with a perfect idea. It begins with a good-enough offer, said out loud to the right person, then reshaped based on what they actually said back.

If you’ve been waiting for the lightning bolt, give yourself permission to stop. The idea you’re looking for is almost certainly already inside the experience you’ve already had. The job now is to get it out of your head, onto a page, and in front of someone who might say yes.

That’s a much smaller first step than most people think.

The Conversation I Keep Having About Copilot

Last week a manager asked me how to write the perfect prompt. She had a sticky note on her monitor with about thirty bracketed placeholders and a warning to always start with role, then context, then task. I asked her how often she actually used it. She laughed and said almost never — it felt like homework before the real work could start.

That moment captured something I’ve been thinking about for a while. The industry has spent two years training people to be better prompters, when the real productivity gains sit one layer up. With Copilot Cowork, the unit of leverage isn’t the prompt — it’s the skill.

Prompts Are Disposable. Skills Compound.

A prompt is a single instruction. You type it, you get something back, and then it’s gone. Tomorrow morning you start again. Even a brilliantly worded prompt only helps the person who wrote it, on the day they wrote it, for the task in front of them.

A Copilot Cowork skill is different. It’s a packaged way of working — a brief, a checklist, a structure, a tone — that anyone in your organisation can invoke by name. Once it exists, it doesn’t degrade. It doesn’t get lost in someone’s chat history. It runs the same way on a Tuesday morning as it does on a Friday afternoon, and it carries the thinking of whoever built it forward into every future use.

That is leverage. Prompt engineering is a craft. Skills are an asset.

Where the Productivity Actually Lives

The real productivity question in any business isn’t how do I get a better answer from Copilot today — it’s how do we stop solving the same problem from scratch every time. Skills are the answer to that question.

Think about what happens in a typical week. Someone needs to write a board update. Someone else has to brief a meeting. A third person is drafting a proposal that looks suspiciously like the last three proposals. In a prompt-engineering world, each of those people opens Copilot in Word or Outlook and tries to remember the magic incantation. In a skills world, they invoke a Board Update skill or a Meeting Brief skill and Copilot already knows the structure, the voice, the sources to pull from in SharePoint, and the people in Teams who usually need looping in.

The hours saved aren’t in the typing. They’re in not having to think the problem through again, hunt for the right template, or remember which version of the prompt actually worked last time.

The Shift Business Leaders Need to Make

If you’re leading a team, the question worth asking isn’t are my people good at prompts? It’s what work do we do over and over that should be a skill by now? The recurring report. The standard reply. The new-client onboarding sequence. The monthly review pack assembled from Excel, Outlook and a SharePoint folder no one can quite remember the path to.

Each of those is a skill waiting to exist. And the moment it does, the productivity gain isn’t a one-off — it accrues every time anyone in the business uses it.

What I’m Watching

I think the businesses that win the next stretch with Copilot won’t be the ones with the cleverest prompters. They’ll be the ones who treat their best ways of working as something to package, name, and share. Prompt engineering helps one person, once. A well-built skill helps the whole organisation, every time. That’s where the productivity actually shows up.

Copilot in PowerPoint

Most people type “make me a presentation about cyber security” into Copilot, watch it spit out ten generic slides, and decide the whole thing is a gimmick.

I don’t blame them. That output is rubbish.

But that’s not Copilot failing. That’s Copilot doing exactly what you asked — building from nothing, with no source, no structure, no brand.

Garbage in, garbage slides out.

Here’s the shift. Copilot in PowerPoint isn’t a “write my deck” button. It’s a converter. You already have the content — a Word doc, a PDF proposal, last quarter’s report. The job isn’t inventing slides. It’s turning what you’ve already written into something you can stand up and present.

What is Copilot in PowerPoint, really?

Think of it as the worst part of your week, automated.

You know the drill. The thinking is done. The report is written. The client signed off on the wording. Now you’ve got two hours of copy-pasting into slides, fighting text boxes, and nudging the logo a pixel to the left.

Copilot eats that two hours.

You point it at a file. It reads the structure, pulls the key points, and drafts slides — text, layout, the lot. You’re not staring at a blank slide anymore. You’re editing a first draft.

That’s the whole game. Not creativity. Removal of drudgery.

Step-by-Step: building a deck that doesn’t look generic

Open your template first

This is the step everyone skips, and it’s the one that matters most.

Before you touch Copilot, open your organisation’s PowerPoint template — your branded .potx, your client’s deck, whatever carries the right fonts and colours. Microsoft is explicit about this: start from your template and Copilot keeps the theme and reuses your existing layouts.

Skip it, and you get Microsoft’s house style. Every. Single. Time.

Reference your file, don’t describe it

Open the Copilot pane, then reference a file — click the paperclip, or just type / and pick the document. Word, PDF, Excel, a Loop page. Now Copilot reads the actual content instead of guessing at it.

Write a prompt that points, not pleads

Don’t ask for a slide “about the project”. Tell it exactly where to look:

Create slides from the attached proposal.
Use the "Scope" and "Pricing" sections only.
One slide per phase. Key points, not full sentences.

Notice what’s missing? Any mention of colours, fonts, or design. You don’t ask Copilot for those — your template already decided them. Ask once, point clearly, and let the template do the rest.

Review, then refine in place

Copilot drafts. You read. Then you tell it what’s wrong — “tighten slide three”, “drop the jargon”, “add a summary slide” — in plain English, right there in the pane. No re-prompting from scratch.

A couple of traps before you sell this to clients

Two things will bite you.

First, dense slides. Copilot tends to lift whole paragraphs straight off the page. If your source doc reads like a report, your slides will too. Fix it in the prompt — “bullet points, not sentences” — or trim after.

Second, the file has to be readable. Text-based PDFs work. Scanned images and password-protected files don’t. And keep source files under 24MB, or the results get flaky.

Old thinking: “I’ll block out the afternoon to build the deck.” New thinking: “I’ll point Copilot at the doc and spend the afternoon making it good.”

That’s not a small change. That’s where your hours go back.

Why this actually changes behaviour

Here’s the real win for anyone running this in a business.

Your team already produces the content. Proposals, reports, meeting notes — the substance exists. What kills them is the packaging. The deck that has to look right for the board, the client, the pitch.

Copilot collapses the gap between “we’ve written it” and “we can present it”. The expensive part — the thinking — stays human. The tedious part disappears.

And be straight about the cost. The file-referencing piece sits behind the paid Microsoft 365 Copilot add-on, not the base subscription. For a lot of SMB clients, this is the use case that justifies the licence. Not chatbots. This.

Show a client how an afternoon of slide-building becomes ten minutes, and the conversation about value is over.

If you’re running Microsoft 365 for clients and you’re not showing them this, you’re leaving real money — theirs and yours — on the table.

Copilot in PowerPoint isn’t there to make your slides.

It’s there to delete the part of the job nobody ever wanted.