Give Them a Win Before Doubt Settles In

Warm cartoon of an advisor and client high-fiving beside a checklist of coloured shapes and a glowing green light

Clients do the same maths we do. They signed up, they started paying, and every week without a clear return a quiet voice starts asking questions. Was this the right call? Should we keep going? Would another provider move faster? That voice gets louder the longer the wait. I have seen good engagements lose air not because the work was wrong, but because nothing visible landed early enough to quiet the doubt.

When I bring Microsoft 365 Copilot into an MSP or SMB engagement, I do not open with a tour of every feature. I look for one concrete win the client can point at in the first fortnight — something their team feels in the tools they already open each morning.

Pick one snag and make it disappear

Most offices I walk into share a familiar tangle. Status lives in Teams. The brief lives in SharePoint. Tasks sit half-updated in Planner. Follow-ups hide in Outlook. Someone still chases the lot by hand. That chase is perfect early territory for Copilot, because the win is obvious: less hunting, clearer next steps, something finished instead of something promised.

Here is a pattern I like. We take a live project the client already cares about — not a demo tenant, the real one. In Teams, Copilot summarises the channel noise into what actually changed this week. That summary lands in SharePoint beside the project brief so nobody is guessing. From there we ask Copilot to draft Planner tasks that match the open items, with owners the client already named. Outlook gets a short update the account lead can send without rewriting from scratch. Power Automate closes the loop: when a Planner task flips to done, a note hits the Teams channel and a copy files into SharePoint. None of that is theatre. It is one pathway from noise to a checklist that moves.

The client does not need a strategy deck to understand it. They see a messy channel become a usable brief, a task list that matches reality, and an email that went out without another late night. That win makes the monthly fee feel like progress.

Make the win theirs, not yours

I am careful about who owns the story. If I am the only one who can run the Copilot prompts or touch the flow, I have built a dependency, not a win. So I sit with their people in Teams, walk the SharePoint library they already use, and let them trigger the Planner draft and the Outlook reply. Power Automate stays simple enough that their admin can explain it next week without calling me. When the green light moment happens — the first completed loop that did not need a chase email — they should be the ones celebrating it.

That shift matters more than any slide about AI maturity. Doubt fades when the client can say, “we got that done faster this week.” They stop staring at the invoice line and start asking what else we can tidy the same way.

Belief compounds faster than features

I still care about the deeper work — governance, licensing, the longer Copilot roadmap. That work only sticks when early belief is already in place. A visible win across Teams, SharePoint, Planner, Outlook, and a small Power Automate nudge does more for retention than another workshop that ends with “we’ll circle back.”

So my rule is simple. Find the snag they already complain about. Use Copilot on the surfaces they live in. Deliver something they can tick off before the quiet voice gets loud. Do that, and the engagement stops feeling like a bet and starts feeling like a partnership already paying its way.

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.

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.

Three Power Automate flows every MSP should productise

image

Every MSP I talk to has the same Power Automate problem.

Not a tech problem. A consistency problem.

Client A has a leave-request flow built by some intern in 2022. Client B has an onboarding flow that emails three people, one of whom left last year. Client C runs approvals through someone’s personal Outlook because it was “quicker that way”.

That’s not automation. That’s tribal knowledge held together by hope.

The fix isn’t more flows. The fix is three flows, built once, exported, and dropped into every client tenant you touch.

What is a Power Automate solution, really?

A flow on its own is a personal toy. It lives in someone’s default environment, it’s owned by one person, and the day they leave the tenant the flow dies with them.

A solution is that same flow, packaged with connection references and environment variables, exported as a file, and imported into any other tenant. Same flow. Different SharePoint site, different approvers, different mailbox — wired up at import time, not hardcoded.

That’s the move. Stop building per-client. Start building once and deploying everywhere.

If you’re charging your clients for automation as a service, this is what productisation actually looks like.

The three worth standardising

There are hundreds of templates in the Power Automate gallery. Most MSPs don’t need hundreds. They need three:

  • Approvals — anything that needs a yes/no with an audit trail

  • Joiner (onboarding) — new staff member, day one

  • Leaver (offboarding) — staff member out, access gone, evidence kept

Build those three properly as a managed solution and you’ve covered eighty percent of the automation requests you’ll get from an SMB client this year.

Step-by-Step: stand up the Approvals flow first
Open Power Automate inside a dedicated solution

Sign in to Power Automate, pick Solutions on the left, and create a new one. Give it a publisher name like YourMSP_Automation. Don’t skip this. Flows created outside a solution can’t be exported cleanly later.

Pick the right approval type

Open the Start and wait for an approval action and look at the dropdown. There are four real options — Approve/Reject – Everyone must approve, Approve/Reject – First to respond, Custom Responses – Wait for all responses, Custom Responses – Wait for one response — plus sequential. Most SMB approvals are First to respond. Document sign-offs are usually Everyone must approve. Pick deliberately. The full approvals reference is on Microsoft Learn.

Use environment variables for the approvers, not hardcoded emails

This is the bit MSPs skip and then regret. Don’t type finance@clientco.com into the Assigned To box. Create an environment variable called ApproverEmail, reference it in the action, and set the value at import time.

Here’s what the assignment looks like in the action:

@{parameters('ApproverEmail (yourmsp_approveremail)')}

Notice what’s missing? A client name. That’s the point. Same flow, twelve tenants, twelve different approver emails — none of them baked into the export.

Export it as a managed solution

Solutions > your solution > Export > Managed. You ship managed solutions to client tenants and keep the unmanaged copy in your build tenant. Microsoft’s import guide walks through what the receiving tenant sees — connection references prompt for new accounts, environment variables prompt for values, and your flow turns itself on when it lands.

Joiner and Leaver follow the same shape

For Joiner the trigger is usually a new Microsoft Lists item or a Forms submission. The flow creates the Entra user, assigns licences, drops them into groups, posts a welcome card to a Teams channel, and sends the manager an approval to confirm everything looks right before the password lands in the helpdesk mailbox.

For Leaver the trigger is the same list, different status. The flow disables sign-in, revokes sessions, converts the mailbox to shared, transfers OneDrive ownership to the manager, and writes a row to a SharePoint list that becomes your audit trail when the cyber insurance auditor asks “what was your offboarding process on the 14th of March?”.

Both flows reuse the same three environment variables — HelpdeskMailbox, ManagerApprovalGroup, OffboardingEvidenceList. Build once. Import twelve times. Done.

One more thing: lock the connectors down before you ship

Before you push any of this into a client tenant, set a Data Loss Prevention policy in the Power Platform admin centre. Put Office 365, Approvals, SharePoint, and Teams connectors in the Business group. Put Twitter, Dropbox, Gmail, and the rest in Non-Business or Blocked. Microsoft’s DLP guidance spells out why this matters: without it, any maker in the tenant can build a flow that pipes mailbox data into a personal Dropbox.

Before: “Can you build us a leave-request flow?”

After: “We’ll deploy our standard approvals solution to your tenant on Friday.”

That’s the shift. From bespoke build to productised deployment. From “this might take a few days” to “this is a forty-minute import”.

Why this actually changes behaviour

If you’re an MSP and you’ve built the same flow three times for three clients, you’re not running an MSP. You’re running a freelance bench with a logo.

The three-flow library — approvals, joiner, leaver — is the smallest automation product that pays back. It compresses delivery time. It standardises what “good” looks like across every client you touch. And when a client says “we’d like our offboarding to leave evidence for our cyber insurer”, you don’t quote a project. You import a solution.

Here’s the real win. Once these three are running cleanly, the conversation with the client changes. They stop asking if you can automate something. They start asking what else you’ve already got in the library.

That’s where the margin is.

Build the flow once. Sell the deployment every time.

AI Didn’t Remove Programming – It Lowered the Bar

image

One of the most dangerous misunderstandings I hear is:
“AI means we don’t need programming anymore.”

The opposite is true.

We need more programming literacy—just a different kind.

AI doesn’t replace logic, structure, or clarity. It amplifies them. When an AI tool “writes code” for you, what it’s really doing is translating your intent into something executable. If your intent is vague, messy, or logically broken, the output will be too.

MSPs already see this in practice:

  • A poorly described Power Automate flow that works once and then quietly breaks.

  • An AI-generated script that technically runs but makes unsafe assumptions.

  • A Copilot prompt that looks clever but produces useless business output.

The common issue isn’t the tool. It’s the thinking behind the instructions.

Understanding basic concepts—inputs, outputs, conditions, loops, exceptions—has never been more important. The difference now is you don’t need to memorise syntax. You need to think clearly and explain cleanly.


This Is a Business Advantage, Not a Technical Party Trick

Here’s where many MSPs miss the opportunity.

They see AI-assisted “programming” as something clever techs play with internally. In reality, it’s fast becoming a deliverable business capability.

Think about your SMB clients:

  • They know their processes are inefficient.

  • They can explain what they want, but not how to build it.

  • They don’t want a six‑month dev project for a simple workflow problem.

An MSP that can sit with a client, map a process in plain English, and turn it into an automated solution is no longer just “support”. You’re helping redesign how the business operates.

And the simplicity is the point.

A one‑page English description that becomes:

  • A ticket triage workflow

  • An onboarding checklist generator

  • A management report assembler

  • A light internal chatbot using their own documents

None of that needs hardcore development skills anymore—but all of it still needs structured thinking.


Your Team Doesn’t Need Coding Skills – They Need Programming Awareness

This is where MSP leaders need to be deliberate.

You don’t suddenly need Python experts across your service desk. What you do need is:

  • Staff who can break problems into steps

  • People who can explain outcomes unambiguously

  • A shared understanding of how logic flows

If your team can already document SOPs well, they are halfway there.

I’ve seen MSPs get real value by:

  • Treating AI prompts like mini specifications, not chat questions

  • Reviewing AI-generated automations as a team, not blindly deploying them

  • Teaching junior staff how to describe a problem, not just which tool to click

Those are capability investments, not tool training.


The MSPs Who Win Will Treat This as a Core Skill

We’ve crossed a line. Programming is no longer gated by language barriers—it’s gated by thinking quality.

That changes what “technical literacy” means for MSPs.

The firms that thrive over the next few years won’t be the ones chasing every new AI tool. They’ll be the ones that:

  • Build strong internal habits around logical thinking

  • Help clients translate business problems into clear instructions

  • Package simple automation as repeatable, billable outcomes

If English is now the language of code, the question is simple:

Are you teaching your people how to speak it clearly—or assuming the tools will do that for them?

That’s a strategic choice every MSP leader needs to make, sooner rather than later.