Who Is Actually Good?

Cartoon of a small business owner sitting with a practitioner who is showing papers and a whiteboard of abstract shapes.

I get asked this a lot. An MSP owner, or a small-business leader, wants a coach, an advisor, or a specialist, and they cannot tell who is any good. There is no certificate that settles it. It is easy to look competent on Instagram. A tidy grid and a confident caption will get you a meeting. They will not get the business where you want it.

The test I use is plainer than the marketing. Has this person solved the problem you actually have? Did they get the result you want? Have they helped a fair number of people like you get there, rather than telling a polished story about one lucky result?

Write the problem down before you shop

Most owners start with a feeling. The week is full. Margin is thin. The team is tired of the same snag. A feeling is not a brief, and a vague brief attracts someone who is good at a problem you do not have.

Before I talk to anyone, I sit in Microsoft 365 and ask Copilot to draft the problem from what is already in the tenant. Recent Teams threads where the same argument keeps returning. SharePoint documents that were meant to be the process and clearly are not. Planner boards crowded with tasks that never quite close. Copilot earns its place because it can pull those threads onto one page: what keeps breaking, who it lands on, and what better would look like in the numbers you already track.

I read that page and I edit it. If Copilot has smoothed over a sore point, I put the sore point back in. I hand it to a candidate and say, this is the job. If they have not done that job, you hear it quickly. They talk about their method. They do not talk about your board, your clients, or the result.

Ask for the work, not the pose

A person worth hiring will show you work. Not a slide of logos. How they read a business that looked like yours. What they changed. What moved, and what did not. Papers on the table. A whiteboard. A walk through a real engagement. If the only evidence is a photo and a promise, I keep looking.

I want someone who has done it more than once. One success can be luck, or a very patient client. A run of similar businesses, under similar constraints, reaching similar results, is a pattern. That pattern is what you are paying for.

Watch what they do with your brief. Do they push back where it is wrong? Do they ask what you have already tried? Or do they skip straight to a package with their name on it? The person who stays with the problem is usually the one who has been in the room when it was hard.

What changes when they are on the team

Get this choice right and the business feels different. The work is more enjoyable, because you are not grinding the same stuck point every week. You help more of the people you set out to help. And you make more money, because time stops leaking into work that does not pay.

None of that shows up because someone posted well. It shows up because a person who has already walked the path is now walking it with you, against the problem you wrote down, not the problem they prefer to sell.

I still do not know a certificate that replaces that test. I do know that if you write the real problem first, and you only sit down with people who have solved it for others like you, the choice gets a lot less foggy.

Your Clients Aren’t Asking for More. They’re Asking Where To.

Cartoon of a small group of people hiking a trail, one slightly ahead pointing the way

I keep hearing the same two complaints from MSP owners. Clients feel restless. Prospects who used to answer have gone quiet. The reflex is to add a service, cut the price, or send a longer newsletter. That rarely fixes it. You are asking the market to follow you, and the market is still asking where to.

More product does not create loyalty. A destination does.

Name the ridge, then start up it

Most MSPs I speak with have a catalogue, not a heading. Security, backup, licensing, a Copilot chat if someone asks. None of that is wrong. None of it answers the question an owner actually has: where are you taking my organisation over the next eighteen months?

Pick one serious goal. Not a homepage slogan. Something you can point at on a Tuesday. Every client we look after will have a written path from the tenant they have today to a Microsoft 365 setup their staff actually use, with Copilot where it earns its keep and nowhere else. That is a ridge worth climbing. You can say, out loud, that you have started.

I am not talking about a vision deck. I mean a SharePoint page the client can open without calling you, and a Planner board with the next three moves, names and dates included. The goal is the ridge. The agreed work is the track. If you cannot show both, you do not have a direction. You have a brochure.

Report where you are, not only what you sold

A quiet pipeline is often just confusion. They liked the first meeting. Months later the only message was a renewal or a ticket number. Nobody said whether the journey had moved.

This is ordinary Microsoft 365 work, done on purpose. Keep the roadmap on a SharePoint site they already use. Break the quarter into Planner tasks, not a slide that dies in an inbox. Once a month, post a short note in the shared Teams channel. What moved. What stalled. What is next. Ask them to reply. That is an invitation onto the track, not a speech.

Copilot earns a place here as a drafter, not a mascot. I open the month’s tickets and the Planner board, then ask Copilot in Word, or in Teams, to draft the client note in plain language. I still edit it. I still own the judgement. What I stop doing is staring at a blank page until the update never leaves the building. The owner who ignores Teams should get the same story in Outlook. Same heading, two doors.

Power Automate can nudge you when a Planner date slips, so the note is not an act of memory. This is not a product tour. It is how an MSP shows it has a heading and is still on the track.

Point, then let them choose

People follow someone who names the destination and reports the distance covered. They do not follow a vendor stuffing the pack. There is a plain gap between “we also do Copilot readiness” and “here is the ridge, here is where we stood this month, and you are welcome to walk it with us.”

If clients are fidgeting and prospects have gone quiet, do not add another offer. Stand a little ahead. Point. Say where you are going and where you intend to take them. Keep saying it, inside their tenant, in language they can read before the first coffee.

The ones who want a leader will come. The ones who only wanted a cheaper licence will not. That silence, once you can tell the difference, is useful.

Scout, Now Autopilot: How Microsoft’s Always-On Agent Really Works

Cartoon of a woman standing on a stack of documents looking through binoculars and guiding her colleagues forward

Most workplace AI I use still sits there politely, waiting for me to type something. Microsoft Scout is different, and that’s exactly why I think MSPs and SMBs need to understand how it works before someone in the business goes looking for the download link.

Quick housekeeping first. Microsoft introduced Scout at Build in June 2026 as its first “Autopilot” agent. On 25 September it renamed the product itself to Autopilot, describing it as “previously called Scout”. Yes, same name as Windows Autopilot, the device provisioning service, which is entirely unrelated. The docs still say Scout, so I will too.

So what is it, really?

Scout is an agent that works on your behalf without being prompted every time. The current Frontier release is a desktop app for Windows 11 and macOS. You describe a task in a chat, Scout picks the tools it needs, works through the steps visibly, pauses for your approval on sensitive actions, then hands back the result or saves files to your workspace.

The tools are the interesting bit. Scout can read and write files in an approved workspace folder, run shell commands, drive a browser to fill in forms, and connect to Microsoft 365. That covers Outlook mail and calendar, Teams chats, meetings and transcripts, SharePoint Lists, and files in OneDrive, SharePoint and Teams. It creates Word, Excel and PowerPoint files, remembers your preferences and can spin up parallel sub-agents.

What makes it “always-on” are two background modes. Heartbeat runs check-in prompts every 15 to 120 minutes while you’re away, and Automations run on schedules or triggers you define. The September announcement goes further: Autopilot becomes cloud-hosted, with its own identity, memory and workspace inside your tenant, and you @mention it in Teams, Outlook and documents like a colleague.

Under the hood it’s built on open-source OpenClaw, with Microsoft adding Entra identity and access controls on top.

The permissions story is where you need to pay attention

Scout operates with the user’s existing Microsoft 365 permissions. It can’t see anything the user can’t. That sounds reassuring until you remember how many SMB tenants I see with broad sharing links scattered across SharePoint. An agent that tirelessly works through everything a user can reach will find your oversharing faster than any auditor.

There’s a finer detail buried in Microsoft’s own Responsible AI FAQ. In the Frontier desktop app, model interactions are processed through GitHub Copilot, under separate terms. When that happens, some Microsoft 365 protections, such as data residency, retention, sensitivity label enforcement and eDiscovery, don’t apply to that processing. That’s why admins must complete an attestation before anyone can use it. Read that page before you tick the box.

Getting access is deliberately fiddly. You need Frontier turned on in the Microsoft 365 admin centre, an Intune policy on devices, the attestation form, and a GitHub Copilot Business or Enterprise seat for each user. Miss any one of those and sign-in fails without a clear message, which will make for entertaining helpdesk tickets.

How I’d approach it

Treat this as a pilot for a handful of technically capable people, not a rollout. Clean up permissions and sharing first. Keep the approval prompts on and resist the temptation to click “Always allow”. Lock down heartbeat and automation permissions tightly, because those run when nobody is watching. And budget carefully: Microsoft says Autopilot runs on usage-based billing, not the fixed Copilot licence.

I genuinely think agents that follow through are where this is heading. But an assistant that acts is a very different beast from one that answers. The organisations that do well here will be the ones that realised their governance needed to be ready before the agent arrived, not after.

Sources: Microsoft Scout overview (Microsoft Learn), Responsible AI FAQ, Admin access overview, Introducing the new Copilot with Home, Code and Autopilot

Personal AI Speed Isn’t Company Freedom

Cartoon of a founder stepping back while a small team calmly handles office work

Most business owners I speak with already use AI every day. They write faster, research faster, publish more content, and stitch together a few small automations. That is genuinely useful. It is also where a lot of people quietly stop — and that is the problem.

Personal speed feels like progress because your inbox clears and your notes look sharper. The business, though, still waits on the same bottlenecks it waited on last month. The opportunity is not another trick for your own desk. It is building AI into the company so the organisation gains capacity and you get room to breathe.

Look at the whole organisation

I ask leaders to walk the company with a colder eye: Operations, Sales, Marketing, Hiring, Finance, and Leadership. Not “what tool is trendy?” but “where does work repeatedly snag?” Microsoft 365 Copilot only matters when it sits inside those snags — Word, Outlook, Teams, SharePoint, Excel, Power Automate — the surfaces people already live in.

In Operations, that might be the status update that always needs a founder rewrite. Copilot in Teams can turn a noisy channel into a clean summary so the ops lead can act without waiting for your evening catch-up. In Sales, the proposal that sits in draft for a week can start as a Word document grounded in a SharePoint brief, then get shaped in Outlook as a reply that sounds like your firm, not a blank template. Marketing can pull approved language from SharePoint instead of reinventing the story in every campaign. Hiring can turn interview notes from Teams into a structured scorecard in Word before the panel forgets what they heard. Finance can ask Copilot in Excel to surface the variance you used to hunt for on Sunday night. Leadership can stop treating every decision as a meeting when the context already lives with the work.

Where AI should earn its keep

I look for four signals. Where can AI remove a recurring bottleneck — the same chase, the same rewrite, the same “can you just…” every week? Where can it save another hire because one strong person suddenly produces far more without burning out? Where does output still wait on the founder’s typing speed rather than the team’s judgement? And which decisions still depend on you that should not — approvals, prioritisation, a first-cut plan — only because nobody else has a workable draft?

That is where Copilot and Power Automate earn their place. A Power Automate flow can move an approved Word pack into the right SharePoint library and ping the owner in Teams without another follow-up email from you. Outlook Copilot can turn a tangled thread into clear next steps so sales does not need you CC’d on everything. Excel Copilot can draft the commentary Finance would otherwise rewrite after every board pack. None of that is about looking modern. It is about taking load off people who already know the work.

The test I use is simple: if you disappeared for two days, would the company stall for vanity reasons or for structural ones? Personal AI helps you type through the vanity. Company AI attacks the structure.

Freedom is what happens when you are not the bottleneck

Freedom shows up when Operations can close the loop, Sales can send a solid first cut, and Finance can answer a straight question without your calendar. Not because you worked faster at eleven at night, but because the organisation no longer routes every sticky decision through one person.

I am not anti personal AI. Use it. Just do not confuse a faster founder with a freer company. Build AI into the workflows, the libraries, and the routines — then step back far enough to lead.

Prefer Grease Over Gloss

Cartoon of a coach leaving a cluttered workshop with stained sleeves and a sticky-note prototype, colleagues leaning in

I scroll past another perfect feed and feel that familiar sour taste. Neat theories. Spotless creators. Slide decks that look like they have never met a real tenant. I do not learn much from people who only polish. I learn from people who still have grease under their sleeves.

I want the residue of making. Campaigns that actually shipped. Workshops that ran long because someone asked a hard question. Odd little experiments with clients where half the room shrugged and the other half leaned forward. What worked. What failed in spectacular fashion. The soot, not the lab coat. If the work left a mark on your day, I want to hear about that mark.

What I actually look for

In Microsoft 365 land the polished story is endless. Another AI deck. Another thread about how Copilot will change everything if you just adopt the mindset. Fine. I still want the artefacts. Screenshots with the edges showing. Notes scribbled beside a failed run. The version of the story you tell after the meeting, not the one you rehearsed before it.

Show me the Copilot prompt you tried in Word that spat out a policy draft with three confident wrong facts, and how you fixed the grounding. Show me the Outlook draft that saved you twenty minutes on a reply chain until it politely invented a deadline that never existed. Show me the Teams meeting summary that missed the one decision that mattered, so you had to go back into the recording like a detective with a coffee that had gone cold.

I care about the imperfect Power Automate flow that emailed the wrong SharePoint library for a week before someone noticed the condition was upside down. I care about the SharePoint build with three views too many and a permissions model you had to redraw on a whiteboard while the client watched. I care about the workshop demo that half-worked on the day — Copilot Chat answering beautifully until someone asked about their own retention labels and the room went quiet while we dug through the admin centre together.

That quiet is useful. That stumble is useful. The residue of a real session is useful. Perfect creators rarely leave residue. Practitioners leave trails you can follow.

Content theatre versus leftover evidence

Plenty of content is theatre. Lights up. Script tidy. No fingerprints. I am not interested in performing usefulness. I am interested in doing useful work and then talking about it. The difference sounds small until you have sat through both kinds of session and realised which one changed how you configure a tenant the next morning.

The best posts I have written for CIAOPS were not born as content calendars. They came from a messy Tuesday: a Copilot experiment in Word that surprised me, a flow that broke overnight, a Teams rollout where the chat etiquette mattered more than the licence SKU. I made something. Then I showed the leftovers. Colleagues remembered the leftovers longer than the slides.

When I stagger out of a workshop still holding a sticky-note laptop and a prototype that looks like it lost a fight with a highlighter, that is the signal. Not a victory lap. Just: we figured something out, and here is the board if you want to try it yourself. Bring your own stains. Ask awkward questions. Prefer the workshop mess over the feed glow.

In a world of perfect creators and AI slide decks, I would rather be the practitioner with dirty hands. Coach the work. Share the stains. Prefer makers over gloss.

Do something useful and talk about it. Make something and show it. That is enough.

Clear the Runway. Then Cross the Gap.

Warm cartoon office scene with a person at a desk facing a blank document and a colleague cheerfully narrowing a messy whiteboard of sticky notes into three simple cards

I have a habit when someone tells me they are stuck. A client, a mate, a team member staring at a half-finished brief. My first instinct is almost always the same: strip friction out of the process. Make the first step smaller. Hand them a simple framework. Cut a few steps so starting feels less heavy.

That instinct is usually right. Most creative stuckness is external. Too many options. No clear place to put the work. A blank page that asks for a masterpiece before it will accept a rough sentence. In Microsoft 365 we spend a lot of time removing exactly that kind of friction, and we should.

Tools that clear the runway

Copilot in Word is a clean example. The blank document used to be the whole problem. Now you can point Copilot at a previous proposal, a Teams thread, or a SharePoint folder and ask for a first pass. The page is no longer empty. Outlook is similar — a reply draft appears before you have argued with the empty compose window for ten minutes.

Teams and Planner do the framework job. Instead of “we should write something,” you get a channel, a few checklist cards, and an owner. Power Automate cuts the busywork between systems so the human only shows up for the judgement call. SharePoint stops the scavenger hunt for last quarter’s file. External friction falls away. People move.

I have watched this pattern work again and again. Clear the runway and most people take off.

When the gap is inside

Sometimes they don’t. They know exactly what to write. They want to write it. The brief is sitting in SharePoint, the Word outline is already there, Copilot even offered a draft — and still nothing happens. The gap is not between them and the tool. It is between wanting and starting.

That is internal friction, and no amount of Microsoft 365 polish removes it on its own. You can have Copilot ready in Outlook, a Planner board tidy enough to make a project manager smile, and a Power Automate flow that files the finished piece. The document still stays closed.

People invent odd personal tricks for this. A side quest before the real work. A particular playlist. Opening the file and typing one deliberately bad sentence so the page is no longer sacred. Rewriting the same bullet three times in Teams before pasting it into Word. From the outside it looks inefficient. From the inside it is charm and coping mechanism mixed together — a private on-ramp the process diagram never shows.

Make it worth wanting

Here is the part I used to resist. If it is not fun, or at least interesting, it often will not get done. Sometimes the answer is not to make the work easier. Sometimes you make a small part harder on purpose, because that hardness makes you want to engage.

I will pick a fancier Word template than I need. I will draft the hard paragraph by hand first and only then ask Copilot in Word to tidy the rest. I will turn a dull status update into a short story for the Teams channel, even though a bullet list would have been faster. The extra friction is the point. It pulls me over the start line.

So when someone is stuck, I still reach for the external fixes first. Copilot, Planner, Power Automate, a cleaner SharePoint path — clear the runway. Then I ask a quieter question: are they blocked by the process, or by the private gap between wanting and starting? Tools handle the first. The second needs a personal tactic, and occasionally a little deliberate difficulty, so the work feels worth beginning.

Don’t Just Automate the Process. Build the Factory.

Cartoon of people organising matching binders on a workshop line with tidy shelves behind them

I still catch myself doing the clever version of the wrong thing. Someone shows me a pain point — a weekly report, a client onboarding checklist, a pile of the same Outlook replies — and the itch is to automate that path. One Power Automate flow. One Copilot prompt saved in a notebook. One private script that only I know how to run.

It works. Once. Then the process changes, the person who owned it leaves, or a second team needs the same outcome, and you’re back to heroic effort. You didn’t build a factory. You built a one-off machine in a corner of the shed.

A process is a recipe. A factory is how you ship.

When I say factory, I don’t mean a heavy program or a six-month transformation. I mean the boring layer that lets the same kind of work repeat without you reinventing it: where the inputs live, what “good” looks like, who can trigger it, and how Copilot or automation reaches the same materials every time.

In Microsoft 365 that usually looks unglamorous. A SharePoint library with a real structure instead of a dumping ground. A Teams channel where the working files and decisions actually sit. A Word or Loop template that already carries the sections you always need. Then Copilot in Word, Outlook, or Teams has something solid to work against — not a blank chat window and a hope that someone remembers the steps.

Automating a messy process just makes the mess faster. Building the factory means you fix the shape of the work first, then put Copilot and Power Automate on top of something stable.

What I watch people skip

The skip is almost always the same. They open Copilot Chat, describe the job in a long prompt, get a decent draft, and feel productive. Next week they write a slightly different long prompt. The week after, a junior asks how they did it, and the answer is a shrug and a screenshot.

Compare that to a factory move: the standard brief lives in SharePoint. The output template is a Word doc everyone can find. Power Automate drops a Planner task or a Teams message when a new request lands. Copilot is pointed at those artefacts — “draft from this template using the intake form in this library” — not at thin air.

I’ve seen MSP teams do the first version for client reporting and burn a Saturday. The ones who get time back are the ones who turned the second and third report into a product line: same intake, same store of evidence, same review checklist, Copilot filling the skeleton so humans only judge the exceptions.

Build once, run many

The test I use on myself is simple. If only I can run it, it isn’t a factory yet. If the knowledge is trapped in my chat history, it isn’t a factory yet. If swapping one person breaks the chain, we automated a habit, not a system.

So when someone asks me to “just automate this,” I try to answer with a smaller, harder question: where will the inputs live next month, and can Copilot find them without me? Until that answer is clear in SharePoint, Teams, or a shared template, I hold off on the clever flow.

Don’t just smooth one process. Build the factory for the thing — the place, the pattern, and the Copilot-ready materials — so the next ten times cost a fraction of the first.

The Quiet Value of AI as a Watchdog

Cartoon of a person at a desk with a watchdog dog watching over documents

Most of the AI talk I hear is about speed. Draft faster. Summarise faster. Clear the backlog faster. Fair enough — I use that side of it every day. What I talk about less, and what I think is underrated, is the other job AI is quietly good at: sitting beside the work and barking when something looks off.

A watchdog doesn’t write the proposal for you. It notices the clause that drifted from your standard, the share link that went wider than it should, the meeting decision that never made it into the record. In a Microsoft 365 world, that kind of attention is where a lot of real risk and rework lives.

Speed without a second set of eyes

I’ve sat with founders and MSP leads who are thrilled that Copilot in Word or Outlook gets them to a first draft in minutes. Then I ask what catches the miss — the wrong customer name left in a template, the permission that opened a SharePoint library to “everyone”, the Teams reply that promised something Finance never agreed to.

Often the answer is still “me, later, if I have time.” That’s not a process. That’s hope with a calendar invite.

Copilot can help you produce more. Without a watchdog habit, you also produce more chances to ship a quiet mistake.

What “watchdog” looks like in the flow of work

I’m not talking about a sci-fi control room. I mean small, repeatable checks inside the tools people already open.

Before a sensitive Word doc leaves the building, ask Copilot to compare it against the last approved version or the policy page you keep in SharePoint — not for prose polish, for drift. Before you hit send in Outlook, have it flag attachments, recipients, or wording that doesn’t match how your organisation usually handles that kind of mail. In Teams, use meeting recap and action capture so “we decided X” doesn’t evaporate, then spot when the follow-up never landed in Planner or the channel.

On the governance side, Microsoft Purview and the sharing reports in SharePoint and OneDrive are the boring cousins of the same idea. AI that helps you see oversharing, odd access, or content that shouldn’t sit in a public Team is doing watchdog work — even when the interface looks like a report, not a chat.

The point isn’t to automate judgment away. It’s to put a consistent second pass in front of human judgment, every time, not only on the days when someone remembers.

The value shows up as fewer ugly surprises

The payoff is rarely a dramatic dashboard. It’s the near-miss you never have to explain to a client. It’s the junior who doesn’t learn the hard way because the check caught the loose link. It’s the founder who stops being the only person who “just knows” something felt wrong in a draft.

I’ve started treating Copilot less like a typist and more like a colleague whose job is to ask, “Are you sure about this bit?” That shift changes what I ask it to do. Fewer “write me a long email.” More “what in this draft conflicts with our standard terms?” More “summarise what we committed to in that Teams meeting and what still has no owner.”

If your AI stack only makes you faster, you’re using half of it. The quieter half — the watchdog — is what keeps the extra speed from multiplying the mess. Build that habit into Outlook, Word, Teams, and SharePoint, and you get something rarer than another productivity tip: confidence that someone, or something, is actually watching the work while it moves.