Who Is the Software For Now?

Cartoon of a person relaxing with coffee while app windows around them work on their own

Picture asking Copilot in Teams for a status report on a client project. It goes through the project files in SharePoint, pulls numbers from an Excel workbook, checks which Planner tasks are overdue and drafts a summary to send from Outlook. You never open a single one of those apps.

That gets me thinking. If we don’t need to open the apps, who exactly are they for now?

Is software going headless?

“Headless” usually describes a system with the engine but no front end. You talk to it through an API rather than a screen. What I’m seeing with Microsoft 365 Copilot, agents and Copilot connectors looks like the same idea applied to everyday work. You give the AI a goal, and it goes off and talks to the tools directly.

Take it a step further. Bring in a line-of-business system through a connector or an agent built in Copilot Studio, and that report could include CRM or ticketing data too, without logging in to anything. The tools are still doing the work. Nobody is looking at them.

So is the SaaS product we pay for every month slowly becoming a tool for AI rather than for people? For a growing slice of routine work, I think yes. I’m not convinced it’s the whole story, though.

What it means for the people using the tools

If you’re a creator or knowledge worker, the skill shifts from knowing where every button lives to knowing what to ask for. And knowing what good looks like when the answer comes back.

That sounds liberating, and it is. But it means people may understand their own systems less. When the report is wrong, someone still has to know which spreadsheet fed it and why. If nobody ever opens the tool, who notices when the data inside it has rotted?

And humans aren’t leaving the screen entirely. We still need interfaces to review, approve, handle the exceptions and make the creative calls that don’t fit a prompt. I don’t want an agent sending a client proposal without me looking at it first. The UI doesn’t disappear. It shrinks down to the moments where judgement and trust matter.

What it means for the people building the tools

This is where I think the bigger shake-up sits. Plenty of SaaS companies have built their business on a polished interface, per-seat pricing and the stickiness that comes from people living in the app all day. If an agent is the main user, what’s a seat? And how much is a beautiful dashboard worth if nobody looks at it?

My guess is differentiation moves underneath the interface. It shifts to the quality of the data, how good and open the APIs are, reliability, and how well permissions and security are handled. When AI is acting on my behalf, I care a lot about whether the tool respects who is allowed to see what. Trust becomes the product.

Vendors that treat their API as an afterthought could find themselves invisible. The tool might work perfectly but never get picked by the agent.

So, where does that leave us?

I don’t think the apps vanish. I do think the people who build them need to work out who their real customer is. Maybe it’s the human, maybe the agent, and most likely both. For the rest of us, the job is learning to direct the work rather than do every click ourselves, while staying close enough to the detail to spot when it goes wrong.

So I’ll put the question to you. How much of your working day already happens without opening the app? And will the tools you rely on still matter if you never see them?

Same Licence, Different Results

Cartoon of an experienced person in a casual wizard hat guiding a colleague who holds a plain stick, with a laptop on the desk

Picture two people in the same team asking Microsoft 365 Copilot to do the same job. Same licence, same tenant, same Monday morning. One ends up with something she can send to a customer. The other ends up with something he quietly deletes.

The tool is identical. Everything around it is not.

Where the difference shows up

The task is simple: a customer has sent a long Outlook thread about a delayed project, and the team needs a recovery update for a Teams meeting that afternoon.

The first person starts by thinking. She knows what the customer is worried about, and which commitments are real and which are wishful. She asks Copilot to summarise the thread, then to separate the decisions from the complaints. She opens the project plan in Planner, checks the dates against what Copilot said, and spots a milestone stated with far too much confidence. She corrects it, then asks for a draft in Word, matching the tone of an earlier update stored in SharePoint.

The second person types “write an update about the delay” and pastes the answer into a document. It reads fluently, is polite, and is wrong in two places. He doesn’t notice, because he never decided what a good answer looked like.

Same wand. The difference was framing the problem, checking the result, and knowing where the real data lives.

It goes beyond prompts

I’m wary of the idea that this is all about prompt wording. Prompts matter, but they’re the visible tip. Underneath sits judgement: knowing which Excel workbook is the trusted one and which is last year’s copy with a different name. Knowing that a SharePoint site full of duplicates gives Copilot a confused view of your business. Knowing when a sensible-sounding answer should make you suspicious rather than relaxed.

None of that arrives with a licence. It comes from experience, a healthy scepticism, and someone being willing to say “that doesn’t look right” out loud.

It changes how I think about buying decisions, too. A business that rolls Copilot out to everyone and calls it done has bought wands. A business that invests in tidy data, clear ownership and shared habits for checking AI output has started building wizards. I’d take the second approach with half the licences over the first with all of them. A skilled person with a plain tool beats a novice with a fancy one most days.

What I’d do on Monday

Pick one real task, such as a weekly report or a customer reply, and have your most careful person and your most enthusiastic person both do it with Copilot. Then compare more than the output. How did each of them get there? What did they ask first? What did they check? What did they ignore?

That comparison tells you more than any vendor demo ever will. It shows you what to teach, what to document and where your data needs attention.

If you buy services from an MSP or adviser, apply the same test to them. Ask less about which products they resell and more about which problems they’ve solved that look like yours. Ask who will actually work with you, and what they did the last time it went sideways.

Tools will keep changing every few months. Framing a problem, questioning an answer and understanding your own information will still be worth having when the next one arrives. That’s what I’d invest in first, and I suspect it quietly decides whether any of this pays off.

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.

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.

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.

The task app you already bought four times

Open most small businesses and you’ll find the same thing. Someone’s running their personal to-dos in To Do. The team’s tracking a project on a Planner board. A manager’s got a Trello tab open. And somebody just expensed a Monday.com seat.

Four tools. One job. Nobody can see the whole picture.

Here’s what most people missed. Microsoft quietly folded To Do, the old Planner, Tasks in Teams and Project for the web into a single app — and just called it Planner. One place. No new licence.

That’s not a rebrand. That’s four subscriptions your clients can stop paying for.

And if they’re on a Microsoft 365 Business plan, they already own it.

What is the new Planner, really?

Think of it as one task list that finally spans the messy middle between “remind me to call the accountant” and “ship the office move by March”.

At the bottom sits your personal stuff — the same tasks that used to live in To Do, now showing up under My Tasks and My Day. In the middle are shared plans your team works from together. At the top, if you ever need it, full project scheduling with timelines and dependencies.

Same app. You just go as deep as the job needs.

Here’s the real win for an SMB. The thing you were about to buy Asana for? It’s the middle tier, and it’s already switched on.

Step-by-Step: putting tasks where the work happens

The mistake is opening Planner as its own app and treating it like another silo. Don’t. Put it where the team already talks.

Find the app

In Microsoft Teams, click Apps on the left rail, search for Planner, and add it. Until April 2024 this was the clunkily-named “Tasks by Planner and To Do” — same app, now just Planner. You’ll also find it on the web at planner.cloud.microsoft if you want it in its own tab.

Pin it to a channel

This is the step that changes everything. Open the channel where the team already works — say your client’s Marketing channel — click the + at the top, and add a Planner tab.

Now the plan lives inside the conversation. No app-switching. No “where’s that board again”. The tasks sit right next to the chat about them.

Build the plan

Create a plan, add a few buckets — To Do, Doing, Done works fine — and start dropping in tasks. Assign people, set due dates, done.

Know which tier you’re on

This is where people get nervous about cost. They shouldn’t. Here’s the line:

Included with Microsoft 365:  Grid, Board, Schedule, Charts
Needs a paid Planner plan:    Timeline, People, Goals, dependencies, sprints

Notice what’s missing? There’s no licence to buy for the everyday stuff. Boards, grids, a schedule view and basic charts are all in the box. You only pay if a client genuinely needs Gantt charts and dependencies — and most never will. The admin documentation spells out exactly what sits where.

Why this actually changes behaviour

“Which app has the project in it again?”

When that question disappears, something shifts.

Tasks stop being scattered across four tools and start living in one place the team already opens fifty times a day. Your personal to-dos, your team’s plans, even your old Project schedules — one pane.

For an MSP, this is a quietly brilliant client conversation. You’re not selling anything new. You’re showing them they’ve been paying a third party for something Microsoft already bundles. That builds trust faster than any upsell ever will.

And the migration worry? There isn’t much of one. Your old Planner boards are already there. To Do items flow in on their own. Project for the web has been retired straight into Planner. You’re not moving anything — it already moved.

If you’re rolling out Microsoft 365 and you’re not showing clients this, you’re leaving them to pay for Trello out of habit.

The new Planner isn’t there to give your clients another task app. It’s there to let them close the other three.

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.