Copilot Credit Pre-Purchase Plans

Ok, deep breath before we start. In. Out. Let’s start.

If you want to purchase Copilot Credits for use with Cowork you’’ll need access to https://admin.microsoft.com. Then you’ll need to navigate to Copilot | Cost Management | Configuration. You’ll then need to select Buy prepaid credits. Then you need to select a Subscription, then How many credits you want from the table that displays.

Upon selection, you’ll be shown the price and then you can pay via the Checkout.

If you look closely you’ll also see this.

So, billing is measured in CCCUs. 1 x CCCU = 100 credits. CCCU means Copilot Credit Commit Unit.

Given that this PAYG style billing is applied against an existing Azure subscription, if you go into the Azure portal and locate Reservations you find another location where you can pay:

Again, here, we have Copilot Credit Pre-Purchase Plans measured in CCCUs.

At the lowest prepaid tier you get 5% discount and at the pre-paid top tier you get a 20% discount, with remaining tiers in between these two. Any overage returns to be being billed with no discount at the base rate.

If you now look at how usage is reported, you see it is reported in Copilot Credits, not CCCUs. So CCCUs appear to be a billing construct only.

Thus, if we focus on just the Copilot Credits (not CCCUs) we get the Microsoft quoted US$0.01 per Copilot Credit. Thus, the above consumption cost becomes 1,574 x US$0.01 = US$15.74 in real money.

Thus, to enable Copilot Cowork going forward you will need:

– M365 License (e.g. M365 Business Premium)

– M365 Copilot license (to enable premium Copilot capabilities like Cowork)

– An Azure subscription for Copilot Cowork to be billed against

– Cowork consumption and billing is tenant wide, not per user

That will bill Copilot Cowork at a PAYG rate of $0.01 per Copilot Credit. A simple average would be to assume each Cowork interaction will consume around 400 credits. That is, around US$4 every time ANY user uses Cowork. This is because Cowork interactions vary on how many credits they use based on their complexity of the request and actions taken.

You can pre-purchase Copilot Cowork credits at average discounted rates starting from US$0.0095 down to $0.0080 (i.e. 5 – 20% discount) for a fixed annual commitment.

Annual pre-paid Copilot Cowork credits are measured in Copilot Credit Commit Units (CCCUs) which have the ratio of 100 credits per 1 CCCU. The entry level CCCU is 3,000 which provides 300,000 credits across all users in the tenant.

These credits can be purchased from the M365 admin portal or the Azure portal (vis Reservations).

An administrator can restrict Copilot Cowork in various ways to control costs but that is the subject for additional post.

….. and we are done. Breath. In. Out.

The Sales Process That Stopped Feeling Like Selling

The best sales conversations I’ve watched in the MSP world don’t feel like sales conversations at all. They feel like someone helping someone else work out what’s actually going on. There’s a diagnosis. There’s a plan. And then, at the very end, there’s a quiet question: would you like a hand putting this in place? That’s the whole thing. No closing technique. No manufactured urgency. No script that leaves either side feeling slightly off afterwards. Just a useful hour and a natural offer at the end of it.

Help is the offer

A few of my clients have built their front door around a paid consult. Someone pays a modest fee, sits down for an hour, and walks out with a real read on what’s happening inside their tenant — security gaps, licence waste, the four Copilot use cases their team would actually adopt, the Conditional Access policy that’s been quietly broken for months. The deliverable isn’t a quote. It’s clarity.

That changes the dynamic. The buyer isn’t being sold to. They’re being helped. And by the time the hour is up, they already know whether the person across the table is worth working with, because they’ve seen them work.

This is where Copilot has quietly become a useful ally in those conversations. Rather than disappearing for a week to write up findings, the consultant pulls a draft summary together in Word with Copilot during or right after the session — referencing the discovery notes, the screenshots from the tenant review, the Secure Score export. The buyer leaves with something tangible the same day. The speed is part of the help.

The invitation writes itself

Here’s the bit most MSPs still miss. When you have genuinely helped someone — when they walk out the door clearer than they walked in — you don’t need a pitch. You need one sentence. Want us to do this for you?

That sentence works because the buyer has already done the qualifying themselves. They’ve seen your thinking. They trust the diagnosis. They want the plan executed. The proposal that follows is short, because the work has been pre-sold by the consult itself.

I’ve watched clients use Copilot in Outlook to turn the same notes into the follow-up email — the recap, the recommended next steps, the link to a SharePoint page with the proposed scope. It lands inside a few hours, while the conversation is still warm. Nothing about it feels like a chase. It feels like a continuation.

Why this beats the old playbook

Free discovery calls dressed up as consults don’t fool anyone anymore. Buyers have sat through enough of them to recognise when they’re being qualified rather than helped. The free version trains people to expect a pitch at the end. The paid version trains them to expect value — and a small amount of money on the table changes how seriously both sides show up.

For MSPs trying to move up the value chain, this is a quieter, more dignified way to do it. You stop hunting. You start advising. The right buyers — the ones who want a partner rather than a price — self-select towards it. The wrong ones fall away on their own. That filtering is worth the effort by itself.

The thing I keep coming back to is how much pressure this approach takes off both sides of the table. The buyer doesn’t have to fend off a pitch. The MSP doesn’t have to manufacture one. Helping first, then inviting, with Copilot doing the heavy lifting on the write-up, turns the sales process into something that actually resembles the work itself. Which, when I think about it, is probably the point.

Copilot in Word

Most people meet Copilot in Word the same way. New blank document, click the icon, type “write me a proposal,” hit Generate.

Out comes 400 words of beige. Technically correct. Completely generic. The kind of thing that could be about your business or anyone else’s.

So they shrug, decide Copilot “isn’t that good,” and go back to writing from scratch.

Here’s the thing. They weren’t using Copilot wrong. They were using the worst part of it and ignoring the best part.

A blank page is the one thing Copilot is genuinely bad at. Give it nothing and it gives you nothing — just confident, well-punctuated filler. The magic isn’t in asking it to invent. It’s in pointing it at what you already have.

What is Copilot in Word, really?

Forget the demos where someone conjures a document from a one-line prompt. That’s the party trick, not the job.

What Copilot in Word actually does well is take your material — a file, an email, a meeting, a folder — and reshape it into something new. The official term Microsoft uses is grounding. The button you press is Reference a file.

That’s the whole ballgame. You’re not asking a stranger to guess what your last client proposal looked like. You’re handing it the last one and saying “another like this.”

So the question stops being “can Copilot write?” and becomes “what do I already have that Copilot can stand on?” For most SMBs, the answer is a lot. Years of proposals, reports, policies, and SOWs sitting in OneDrive, doing nothing.

Step-by-Step: drafting from something you already have

This is the workflow I show every client. It takes about ninety seconds.

Open a new document

Start a blank document in Word, then click the Copilot icon. You’ll get the Draft with Copilot box. Don’t type your prompt yet.

Reference the file first

Click Reference a file (the paperclip), and start typing the filename. Pick the document you want Copilot to learn from — an old proposal, a strong report, a policy you’re proud of. You can attach more than one. Microsoft has the full walkthrough in Draft and add content with Copilot in Word, and the Welcome to Copilot in Word page confirms it only ever looks at the files you choose — nothing else.

Write your prompt

Now tell it what you want, and point it back at what it’s holding:

			
Draft a one-page proposal for Acme Pty Ltd.
Reference: /Northwind-Proposal.docx /Acme-Discovery-Notes.docx
Match the structure and tone of the Northwind proposal.
Keep it under 400 words.

Notice what’s missing? Nowhere do I explain what a proposal is. I’m not teaching Copilot to write. I’m showing it how we write and telling it to do that again.

Keep, regenerate, or bin it

Copilot drops the draft in. Keep it, Regenerate for another go, or Discard. Then you edit like a human — because you still have to.

Why this actually changes behaviour

Before: “Copilot, write me a client report.” → generic mush you rewrite anyway. After: “Copilot, write this report the way I wrote the last three.” → a first draft that already sounds like the business.

That second one is the difference between a toy and a tool.

Here’s the real win for MSPs. Grounding turns your clients’ own document history into an asset they didn’t know they had. Every good proposal becomes a template. Every solid SOP becomes a pattern. The licence they’re already paying for suddenly does something a free chatbot never can — because the free chatbot can’t see their files.

And it’s not just drafting. Flip it around and Copilot becomes a reading tool. Open a long contract, type Summarize this document, and it’ll hand back the gist with citations back to the source — chat with Copilot about your Word document covers that side. Summarize before you read. Draft from what you’ve got. Same tool, both directions.

Don’t ask Copilot to know your business. Show it.

If you’re rolling Copilot out to clients and the first thing you teach them is “type a prompt on a blank page,” you’ve handed them the weakest trick in the box and you’ll get the predictable shrug.

Teach Reference a file first. That’s where the value lives, and it’s the bit nobody stumbles onto by accident.

Reference a file isn’t there to help you write faster. It’s there to make sure what gets written already sounds like you.

The Lessons Only Show Up After You Commit

Someone said to me recently that the things you experience from actually going all in on something will change the way you think and the way you experience life. I sat with that for a few days, and I keep coming back to how true it is. The lessons I’ve learnt that actually shaped me — the ones I still use — never arrived from reading about them or watching someone else do it. They arrived after I committed. After I hit publish on the video. After I greenlit the project. After I said yes to the thing that might not work.

You can’t think your way to the lesson

For years I noticed a pattern in my own work. The plans that lived in a Word doc were always cleaner than the plans I actually shipped. The launches I’d rehearsed in my head were always smoother than the ones in the wild. But the rehearsal never taught me anything. The shipping did. You only find out what your audience actually wants once you put something in front of them. You only find out where the workflow breaks once a real client sits in it on a Tuesday morning.

This is where I think a tool like Copilot has quietly changed how I move. I used to delay things because the draft email wasn’t right, the outline wasn’t sharp enough, the slides weren’t worth showing yet. Now I’ll ask Copilot in Outlook to give me a first pass on a reply, sit with it for a minute, and send something that’s eighty per cent of where it needs to be. I’ll spin up a rough deck in PowerPoint with Copilot drafting from a Word doc I’ve already written, and I’ll show it to someone for feedback the same afternoon instead of next week. The point isn’t that Copilot writes the thing for me. The point is that it removes the excuse to keep polishing before I commit.

Not every bet pays off — and that’s the lesson

I’ve greenlit plenty of projects that didn’t go anywhere. Videos that landed flat. Ideas I was sure would resonate that quietly didn’t. If I’d waited for certainty on any of them, I wouldn’t have learnt what my audience actually responds to. I wouldn’t know which formats earn attention and which ones don’t. I wouldn’t have built the muscle of recovering from a miss and trying again the next week.

What I notice now in clients I work with is the same pattern. The teams that are getting real value from Microsoft 365 and Copilot aren’t the ones who ran a six-month readiness program. They’re the ones who picked a use case, tried it inside Teams or in a SharePoint workspace, watched what happened, and adjusted. They committed first and refined second. The ones still building the business case in a Loop component are usually the ones falling further behind.

The shift is in your thinking

Going all in changes you because it forces you to live with the result. You learn what works because you watched it land. You learn what doesn’t because you felt it. That kind of knowledge doesn’t come from analysis — it comes from being in the arena.

I’d rather ship something imperfect this week and know what to fix next week, than spend a month protecting an idea that never meets the world. Every meaningful jump I’ve made in my business started with that decision. Hit publish. Greenlight it. Find out.

The Audit You Keep Avoiding

You go through your numbers each month. You sit down with your team and review what’s working. You poke at your processes when something breaks. That’s normal business hygiene.

But there’s one thing on the books almost no one runs a proper audit on — and it’s the one most likely to be quietly costing you money.

It’s you. Specifically, your energy.

The hidden line item in your P&L

I’ve been in business long enough to notice a pattern. The weeks I sleep badly, eat rubbish, and skip my walk are the same weeks I send the email that lands the wrong way. Or I sit on a quote for three days when it should have gone out in three hours. Or I miss something obvious in a client conversation that I’d have caught when I was sharper.

None of that shows up on a balance sheet. But the cost is real. A deal that drifts. A client who feels half-listened-to. A reply that creates a problem instead of closing one.

You can’t see it in your numbers, but it’s in there. Every time.

No tactic survives a flat battery

Here’s the part people don’t want to hear: there’s no strategy, framework, or new hire that fixes a depleted owner. I see business owners trying to out-work, out-tool, or out-source their way around tiredness. It doesn’t work. The decisions still have to come through you, and the quality of those decisions tracks the quality of your sleep, your food, and your movement more closely than most of us care to admit.

And ironically, the tools we now have should make this easier, not harder. I use Copilot in Outlook to do the first pass on long replies, and Copilot in Teams to recap a meeting I half-listened to because the day got away from me. That’s not laziness — that’s protecting the limited number of sharp hours I actually have. Letting the machine do the rummaging means I get to spend my energy on the call that matters, not the inbox triage.

The same goes for the weekly running of the business. A clean Planner board, a proper SharePoint home for your documents, a few Power Automate flows handling the boring approvals — these aren’t productivity bling. They’re how you stop bleeding decision-making capacity on things that don’t deserve it.

Treat yourself like the asset you are

Run the audit on yourself the same way you’d run it on the business.

How did you sleep this week? When did you last move? What does the food in your kitchen actually look like? When was the last full day you took off — not “worked from home in a t-shirt”, but actually off?

I’m not pretending I get this right every week. I don’t. But when I notice the slide, I treat it the way I’d treat a leaking margin: stop, look at the inputs, fix what’s fixable. Block the walk in the calendar. Push the late meeting. Let Copilot draft the thing tonight so I can be in bed at a reasonable hour.

The business sits on top of you. If the foundation is shaky, nothing built on it is going to hold.

Audit the owner first.

The next wave of millionaires won’t be coders. They’ll be the people who know how to ask.

I sat across from a small business owner last week who was running a five-person company out of a single browser window. No engineering team. No marketing department. No sales operations. Just her, an Outlook tab, an Excel sheet, a Teams chat with her bookkeeper, and Copilot stitching the whole lot together. She wasn’t writing code. She wasn’t filming videos. She wasn’t cold-calling anyone. She was directing — asking the right thing, of the right tool, at the right moment. And quietly, almost without realising it, she was out-earning people I know with three times her headcount.

That image has stayed with me. For most of my career, the people who built real wealth in small business fell into three buckets — they could build the thing, sell the thing, or reach an audience. The bottleneck was always one of those three. AI has just removed two and a half of them.

The compounding point has moved

Software used to be the hard part. Then writing was. Then distribution. Each wave produced its own millionaires — the engineer-founders, the creators, the inside-sales operators with a phone and a CRM. The pattern was the same every time: somebody figured out how to compound their output past what a single human could reasonably produce, and the market paid them for it.

Copilot has quietly opened that same door for an entirely different kind of person. The new compounding skill isn’t writing code or shooting reels. It’s knowing what to ask, what to push back on, and what “good” looks like when something comes back at you. The advantage has moved from making to directing.

The unglamorous skill nobody talks about

The owners I see pulling ahead this year aren’t the ones using the most apps. They’re the ones who’ve learned to live inside Copilot in the surfaces they already use. They draft a difficult client email in Outlook, then ask Copilot to soften the tone before they send. They drop a messy supplier statement into Excel and ask Copilot to find the months that don’t reconcile. They walk out of a Teams meeting and ask Copilot for the three things they actually committed to. None of this looks heroic. It just adds up.

What separates the power users from everyone else is taste. They know when the first draft is wrong and they keep asking. They know which spreadsheet question will surface the real answer. They’ve built a private library of prompts the way previous generations built rolodexes. That instinct — the one that decides whether to trust a draft or rewrite it — is the new scarce skill, and almost nobody is teaching it.

The quiet wealth shift

I don’t think this is a story about technology displacing people. I think it’s a story about advantage shifting toward whoever can direct an intelligent tool well — and that’s not always the most technical person in the room. Often it’s the operator, the bookkeeper, the franchise owner, the practice manager. People who were already good at making decisions, now equipped with an assistant that turns a good decision into ten finished pieces of work. The wealth doesn’t show up as a single big windfall. It shows up as a quietly higher margin, a smaller payroll, a calendar with more white space than their competitors’.

Watch the small operators in your own network over the next twelve months. The ones quietly buying back time, taking on more clients without hiring, and looking suspiciously relaxed on a Friday afternoon — they aren’t working harder. They’re just better at asking.

Copilot Agents Are the Next Real MSP Conversation

I’ve been having a lot of conversations lately with MSP owners who are still treating Copilot as a licence SKU to resell. They tick the box, push the price up, and wait on the renewal. Meanwhile a small group of their clients are quietly building agents in Copilot Studio and starting to ask sharper questions — questions about data, permissions, governance, and ownership. If your MSP isn’t in those conversations, somebody else is.

Agents are not “Copilot, but more.” They are a different shape of work. And they are the first part of the Copilot story where technical depth genuinely matters again.

Agents change what your clients ask you for

For two years the Copilot pitch has been “draft my email, summarise my meeting, polish my deck.” That is a user training problem dressed up as a technology problem. Agents are different. An agent is a piece of configured behaviour — a declarative agent in Microsoft 365, an agent built in Copilot Studio with actions, or a SharePoint agent grounded in a specific library — that does a specific job, with specific knowledge, for a specific group of people.

The moment a client builds one, the questions change. Which SharePoint sites is it allowed to read? What happens when somebody who shouldn’t see a document asks the agent about it? Who owns it when the person who built it leaves? These are not user questions. These are MSP questions. Nobody else in the client’s world is set up to answer them, and frankly, nobody else should be.

The technical groundwork is the billable work

Here is the part I keep flagging in peer groups. Before an agent is useful, the tenant has to be in shape. SharePoint permissions need to actually reflect reality, not the historical sediment of five years of “just give them access.” Sensitivity labels need to exist and be applied. Purview DLP policies need tuning for the way Copilot grounds answers. Entra ID app governance needs to be switched on, so a rogue agent in Copilot Studio can’t quietly start calling external connectors against a client’s data.

None of that is glamorous. All of it is billable, repeatable, and exactly the kind of work an MSP should be packaging right now. I’d rather sell a tenant readiness engagement than another round of “Copilot adoption training” that doesn’t survive contact with a real inbox.

Agents are how MSPs stop being interchangeable

The MSPs I see pulling ahead aren’t the ones with the slickest Copilot demo. They are the ones building reusable agents for their own clients — a client onboarding agent grounded in a policy library in SharePoint, a compliance Q&A agent pinned in Teams, a quoting assistant that reads the price book and drafts the response in Outlook. Each one is small. Each one is specific. Each one is harder for the next MSP down the road to replicate, because it sits inside the client’s data and inside the client’s workflow.

That is a moat. Not a big one, but a real one — and it compounds.

The watch-this-space part

I think the next twelve months are when the gap between MSPs who treat Copilot as a licence and MSPs who treat it as a platform starts to show up in client retention. Agents are the lever. The technical work to make them safe and useful is squarely in our lane. The MSPs who pick that work up early get to keep having the interesting conversations. The ones who don’t will find their clients having those conversations with somebody else.

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.