Creating a Digital Twin of Your Business

When most people hear “digital twin”, they picture an engineer running a virtual copy of a jet engine, or watching a simulated factory floor hum along on a screen. It sounds like something built for heavy industry, a long way from a business that runs on email, spreadsheets and the occasional frantic search through old files. I’ve come to think the idea fits an ordinary organisation just as well — and that most of us are far closer to having one than we’d assume. The raw material is already sitting there. We’ve just never thought of it in those terms.

A digital twin of a business isn’t a 3D model. It’s a living representation of how your organisation actually thinks: the decisions it has made, the reasons behind them, the way a job quietly moves from one person to the next. That knowledge already exists. The problem is that it’s scattered. Some of it sits in SharePoint, some in a Teams thread nobody has opened in a year, some buried in a colleague’s sent items — and an uncomfortable amount lives only inside one person’s head.

You already own the knowledge

A while back I watched someone spend half a morning answering a question their business had already answered twice. The work existed. It simply couldn’t be found quickly enough, so they built it again from nothing. That’s the everyday cost of not having a twin you can talk to. You’re not short of information. You’re short of a way to ask your own business what it already knows.

This is where Copilot starts to shift things. Connected across your Microsoft 365 tenant, it lets you put a question in plain language and pulls the thread together for you. Ask why a particular client moved onto a different plan, and Copilot can surface the Outlook email where it was decided, the meeting where it was thrashed out, and the document that recorded the outcome. A new staff member can ask it how something is normally done and get an answer drawn from real history, not folklore. You stop hunting for a file and start interrogating your own past.

The twin is only as good as what you feed it

This is where most businesses come undone. If a decision gets made on a phone call and never written down, the twin can’t see it. If the reasoning lives only in someone’s memory, it isn’t in the model. So the habit worth building is unglamorous but powerful: put decisions somewhere Copilot can reach. Keep the Teams meeting recap instead of letting it disappear. Write the why into the document, not just the what. Treat a SharePoint page or a Loop component as the place your thinking genuinely lives, rather than a tidy-up job for later.

None of that is technical work. It’s a discipline — choosing to treat your own knowledge as something worth keeping, instead of something you’ll cobble back together under pressure when you next need it.

What it actually buys you

I don’t think the goal is a perfect replica. No model captures everything, and you wouldn’t want one that tried. But a business that can answer its own questions — one that remembers why it did things — moves faster and argues less. It brings new people up to speed sooner. It stops relitigating decisions that were settled months ago.

The pieces are already sitting in your tenant, waiting to be connected. What I’m watching now is which businesses bother to feed the twin, and which keep solving the same problem every Tuesday morning, none the wiser for having solved it before.

CIAOPS AI Dojo 14

What’s the session about?

This month we will be focusing on new Copilot Cowork features and updates as well as optimising AI for Small Business.

Who should attend?

This session is perfect for:

IT administrators and support staff
Business owners
People looking to get more done with Microsoft 365
Anyone looking to automate their daily grind

Save the Date

Date: Friday the 31st of July 2026

Time: 9:30 AM Sydney AU time

Location: Online (link will be provided upon registration)

Cost: $80 per attendee (free for Dojo subscribers)

The AI Toolkit Monetization Strategy: Building Enterprise Value with Microsoft Technologies

I’ll start with something that won’t win me any friends at the next AI meetup: owning the cleverest AI tool in the room won’t make you a cent. Not the model, not the agent, not the prompt you spent a weekend perfecting. I’ve watched a lot of people fall in love with the technology and then wonder why the invoices aren’t getting any bigger. The uncomfortable truth is that nobody pays for tools. They pay for problems disappearing.

Think about a carpenter for a moment. A carpenter doesn’t get wealthy selling you a single hammer off the back of the ute. They get paid because they walk onto a site, look at a house that needs building or a roof that’s letting the rain in, and they know exactly which tool to reach for and when. The hammer matters, but only because of the hand holding it and the job it’s pointed at. That’s the mindset I think anyone serious about AI needs to adopt — and if your organisation already lives inside the Microsoft cloud, you’ve quietly been handed a very good toolkit. Most people just haven’t worked out how to pick it up.

The hammer: Copilot and Azure OpenAI

The language model is your hammer. It’s the tool you swing by hand, and it’s genuinely powerful — but it does what you tell it, no more. In the Microsoft world that’s Microsoft Copilot sitting across your Outlook, Word and Teams, with Azure OpenAI underneath when you need to build something bespoke.

Here’s where most people get it wrong: they treat Copilot like a fancier search box. They type a vague half-question, get a vague half-answer, and conclude the whole thing is overhyped. The people getting real value approach it with a bit of discipline. The way I think about it is four steps — mission, ask, parameters, shape.

Start with the mission: the business outcome, not the chore. Don’t ask Copilot to “find me some leads.” Tell it you need thirty new enterprise clients this quarter to hit a revenue target. Then comes the ask — one sharp, specific request, like pulling together forty qualified IT directors in healthcare with their contact details. Then parameters — the context and the guardrails. This is where Copilot in Microsoft 365 earns its keep, because you can point it straight at the files in your SharePoint or OneDrive so it’s reasoning over your data, not a guess about the world. A tip I lean on constantly: dictate your context rather than typing it. The voice option in Copilot lets you talk through the background in thirty seconds, and you talk far faster than you type. Finally, shape — tell it the format you want. A clean table, a CSV you can drop into Excel, a tight bulleted summary. Stop reformatting things by hand like it’s 2015.

The screwdriver: Power Automate

A hammer needs a fresh swing every single time. The moment you find yourself doing the same AI-assisted task over and over, you’ve outgrown it. That’s when you reach for the screwdriver — automation — and in the Microsoft stack that’s Power Automate with AI Builder doing the heavy lifting.

The shift here is subtle but enormous. Instead of opening Copilot every morning to run the same prompt, you build a flow once and let it run on a schedule or off a trigger, quietly, in the cloud, forever.

Not everything deserves a flow, though, and this is where people burn weeks they’ll never get back. I run three quick tests before building anything. Is it repetitive — happening at least weekly, ideally daily? Is it rule-based, with predictable inputs and a predictable result? And does it actually pay back — does the time saved over a year dwarf the time spent building it? Don’t spend sixty hours constructing a flow that rescues someone two minutes a week. That’s not automation, that’s a hobby.

A example I like: a sales call recording lands in a Teams channel. Power Automate sees it, AI Builder pulls the transcript, reads the sentiment, drops the action items straight into Dynamics 365, and posts a tidy weekly summary back into the leadership channel in Teams. Nobody touched it. That’s the screwdriver doing its job.

The power drill: Copilot Studio

Then there are the jobs where you don’t want to define the steps at all — you just want the outcome. That’s the power drill, and Microsoft’s answer is Copilot Studio, where you build agents that handle whole processes on their own.

With the hammer and the screwdriver, you’re still drawing the map. With an agent, you describe the destination and let it find its own way through the subsystems. The trick to doing this without disaster is what I’d call staying on the loop rather than in it. Pick a genuinely meaty workflow — vendor onboarding end to end, say, from reading the invoice email, to cross-checking your Dataverse tables, to running compliance, to setting up billing. Then, and this is the hard part, don’t keep grabbing the wheel. Let it run.

Two habits make this safe. First, have agents check each other — a builder agent in Copilot Studio writes a script, and a separate reviewing agent picks it apart for security gaps before anything reaches a human. Second, watch for drift. An agent grinding away over hours or days can slowly lose the plot, so your role becomes the manager who inspects, resets the context when it wanders, and keeps it pointed at the goal.

The orchestrator gets paid

Here’s the part that actually moves the money. Owning these three tools doesn’t make you rich. Conducting them does. The orchestrator is the one who looks at a bleaking supply chain or a drowning support desk and reaches across the whole Microsoft AI toolkit — Copilot, Power Automate, Copilot Studio — to make the pain stop.

Your clients don’t lie awake wondering whether you used GPT-4o through Azure or a Copilot Studio agent. They lie awake about their costs. Solve that, and the technology underneath becomes a footnote. Problems are where the value lives.

So the real shift isn’t learning another tool. It’s moving from doing the work to directing it. Step back, find the problem worth solving, and orchestrate the kit you already own.

Outlook Draft Instructions vs Microsoft 365 Copilot Personalization — what’s the difference and which takes priority?

I see a lot of people trying out Microsoft 365 Copilot for Outlook, then asking why the emails it drafts don’t sound like them. Many end up manually tweaking every email Copilot writes, thinking it’s unavoidable.

“Why does Copilot always add ‘I hope you’re well’? I’m spending more time editing than drafting!”

Sound familiar? That’s not a failure of Copilot. That’s a missed opportunity. If you keep re-teaching Copilot your style every time you use it, you’re doing it wrong. The solution: set up the right instructions once, so Copilot learns how you want your emails written from the start.

What are Outlook Draft Instructions and Copilot Personalization, really?

Think of them as layers of guidance for Copilot. Outlook Draft Instructions are your email-specific preferences stored in Outlook. They’re all about how your email drafts should look: friendly vs formal tone, how long or detailed to make messages, whether to use bullet points, how to greet people, the sign-off you prefer—basically, how to sound like you in email (https://support.microsoft.com/outlook/copilot-outlook/ask-copilot-to-make-email-drafts-sound-like-you).

By contrast, Microsoft 365 Copilot Personalization is your global Copilot profile—the custom instructions and memory that apply across all Copilot experiences in Microsoft 365 (Word, Outlook, Teams, etc.), not just email. These personalization settings let Copilot know your role, typical audience, and general communication style so it can tailor any response, in any app, closer to what you need (Customize how Microsoft 365 Copilot responds to you).

Put simply: Draft Instructions tell Copilot how to handle your emails, while Copilot Personalization defines how Copilot behaves everywhere. And there’s no mystery about which one takes priority. When you click Draft with Copilot in Outlook, here’s the order in which Copilot follows your instructions:

Your prompt (highest priority): Anything you explicitly ask for (tone, style, language, etc.) in the prompt overrides everything else.
Outlook Draft Instructions: Your app-specific email defaults; used whenever your prompt doesn’t override them.
Global Copilot Personalization: Your general preferences fill any gaps not covered by your prompt or Outlook’s instructions.
Organizational policies: These always apply for compliance and safety (e.g. Data Loss Prevention (DLP) blocking sensitive info) but they don’t affect writing style.

Step-by-Step: Fine-tune Copilot for your email style

Open Outlook’s Copilot Draft Instructions

To set this up, you’ll need the new Outlook (or Outlook on the web) since the feature isn’t in classic Outlook’s UI. In the new Outlook on Windows or web, click the Copilot icon in the compose window. From the dropdown, select Settings, then click Draft Instructions.

Add your email style preferences

Turn on Use custom instructions when drafting email. Now type a short description of how you want Copilot to draft your emails. Be specific about tone, structure, greetings, and sign-offs. Do you prefer concise messages or detailed ones? Formal language or a friendly vibe? For example, you might write:

Use a friendly tone.
Start each email with "Hi [Name],".
Avoid corporate jargon and fluff.
Sign off with "Thanks, [Your Name]".

Notice what’s missing? We didn’t mention anything about length or level of detail in those instructions. That’s on purpose – if you leave something out here, Copilot will fall back to your global Personalization settings to fill in the blanks.

Set global Copilot Personalization

Next, open your Microsoft 365 Copilot settings (for example, in the Copilot Chat app or via the Copilot sidebar in any Office app). Go to Settings and select Personalization. Under Custom instructions, add broad guidance about yourself and your style that should apply everywhere. Tell it who you are and how you like your output across Microsoft 365. For instance, “I’m a small business owner writing for busy clients, so keep everything concise and professional.” Save your instructions.

Why this changes how you email

Once you’ve set up these preferences, you’ll stop fighting with Copilot’s tone and phrasing. Instead of manually fixing greetings or trimming fluff each time, you get drafts that fit your style on the first try. It’s like hiring an assistant who already knows your voice—from day one.

Better yet, showing your clients how to configure these settings is an easy win. It reduces their frustration with generic AI output, boosts their trust in Copilot, and makes you look like a trusted advisor. If you’re not helping them set their Copilot’s style, you’re leaving a lot of value on the table.

Copilot’s drafting preferences aren’t about adding complexity – they’re there to remove it.

Set them up once, and you can stop rewriting Copilot’s emails and start reaping the benefits of an AI that truly sounds like you.

The Most Important Part of Productivity Is the Product

I had a conversation last week that’s stuck with me. Someone was describing their week — back-to-back meetings, an inbox wrestled down to zero, a colour-coded calendar that would make a project manager weep with joy. They were exhausted and, oddly, proud of it. So I asked a simple question: what did you actually make? Long pause. The honest answer was “not much.” A full week of motion, and almost nothing to show for it.

We’ve quietly redefined productivity to mean busyness. How fast you reply. How many minutes you squeeze from a day. How efficiently you move between tasks. But strip the word back and the heart of it isn’t the activity — it’s the product. The thing that exists now that didn’t exist on Monday morning. The proposal that’s written. The decision that’s made. The client problem that’s solved. Everything else is just noise around the signal. We measure the noise because it’s loud and easy to count. The signal is quieter, and it’s the only part that actually matters.

Motion is easy to measure. Output is the hard part.

The reason we drift toward efficiency is that it’s comfortable. You can count emails sent and meetings attended. You feel the satisfaction of a tidy inbox. But none of those are products — they’re scaffolding. I’ve watched people spend an entire afternoon “getting organised” and call it a good day’s work, when really they just rearranged the furniture. The week looked productive. Nothing was produced.

This is where I think Copilot changes the conversation, and not in the way the marketing suggests. The point isn’t that it makes you faster at the busywork. It’s that it takes the busywork off the table, so what’s left is the actual product. When I ask Copilot in Outlook to summarise a long thread and draft the reply, I haven’t saved twenty minutes — I’ve removed a task that was never the point. The reply was never my product. The thinking behind it was.

Spend the time you save on something worth showing.

That’s the part people miss. The danger isn’t that Copilot does the low-value work — it’s what you do with the gap it opens up. If Copilot pulls your meeting notes and action items together in Teams, and you spend that reclaimed hour clearing three more emails, you’ve efficiency-ed yourself in a circle. But if you use it to write the strategy document you’ve been avoiding, or to think properly about a client’s problem in Word with Copilot helping shape the argument, the tool has earned its place. Or you point Copilot at a messy spreadsheet in Excel, ask it what the numbers are really saying, and walk into the meeting with an answer instead of a pile of data. The output, not the speed, is the scorecard.

I’ve started asking myself a blunt question at the end of each day, and I’d suggest you try it. Not “was I busy?” — I’m always busy. The question is: what can I point to? What did I produce that someone else could pick up, use, or judge? Some days the answer is a single solid thing, and that beats a day filled with forty small tasks that vanish the moment they’re done.

Copilot has made me more honest about this, because once the friction is gone, you can’t hide behind it. The empty afternoon is exposed for what it is. That’s the real shift worth watching — not doing things faster, but finally being able to ask whether the thing was worth doing at all.

Where Do Your Uploaded Documents Actually Go in Copilot Notebooks?

One of the questions I get asked most often about Microsoft 365 Copilot Notebooks is deceptively simple: when I upload a document into a notebook, where does it actually live? It’s a fair question. If you’re an MSP, an administrator, or anyone responsible for governance, “it’s in the cloud somewhere” isn’t a good enough answer. You need to know exactly where that data sits, who can reach it, and what compliance controls apply. The answer turns out to be more interesting than most people expect, and it hinges on a relatively new piece of the Microsoft 365 storage platform called SharePoint Embedded.

The short answer: SharePoint Embedded

When you upload a document into a Copilot Notebook, it does not land in your OneDrive, and it doesn’t go into a regular SharePoint site or document library that you can browse to. Instead, it’s stored in SharePoint Embedded — specifically inside a user-owned container.

Here’s the part that surprises people. Copilot Notebooks, Copilot Pages, and Loop’s “My workspace” all share the same single user-owned container per user. You don’t get a separate container for each. The first time you need any one of those experiences, Microsoft provisions one container and reuses it for all three. Even the container’s name depends on which app you opened first: it’s called “Pages” if you visited the Microsoft 365 Copilot app first, or “My workspace” (localised to your Loop language) if you opened Loop first.

There’s a governance wrinkle worth committing to memory: in the SharePoint admin center, in PowerShell, and in Purview audit data, this container’s application name always shows as “Loop” — even when it only holds Copilot Notebooks. There is no separate “Copilot Notebooks” application filter. So if you go hunting for Copilot content in your audit logs and only search for “Copilot”, you’ll come up empty. Look for Loop.

So what is SharePoint Embedded?

SharePoint Embedded is an API-only file and document management system built on the same proven Microsoft 365 storage platform that powers SharePoint and OneDrive. The key word is API-only. Unlike a normal SharePoint site, there’s no friendly web UI you can navigate to. When an application uses SharePoint Embedded, it creates a separate storage partition inside your Microsoft 365 tenant, and the documents in that partition are only accessible through Microsoft Graph APIs — and only to the owning application.

Within that partition, the application stores content in entities called File Storage Containers. Think of a container as an API-only document library: it can hold any file type, supports folders, versioning, search, and co-authoring, but it’s dedicated to and reachable by just the one app that owns it. That isolation is the whole point. The files your Copilot Notebook depends on are walled off from other applications, yet they still benefit from the full richness of the Office stack — you can open an uploaded Word or Excel file in Office for the web straight from the experience.

This is the same architecture Microsoft uses under the hood for Loop and Designer. Copilot Notebooks is simply another first-party consumer of the platform.

The detail that matters most: your data stays in your tenant

This is the line I always emphasise with clients. The storage partition that SharePoint Embedded creates lives inside your own Microsoft 365 tenant. Your uploaded documents do not leave your tenant boundary. That means everything your existing Microsoft Purview controls already do, they continue to do here:

eDiscovery — content is discoverable
Auditing — actions are logged (remember: under the “Loop” application name)
Data Loss Prevention (DLP)
Retention policies and sensitivity labels
Conditional access

So while the storage mechanism is new, the compliance posture is reassuringly familiar. The data is yours, it’s in your tenant, and your governance tooling applies.

Quotas, limits, and a billing nuance

Here’s a distinction that trips people up. The general, developer-facing SharePoint Embedded model bills storage separately through an Azure pay-as-you-go subscription, and that storage does not count against your SharePoint quota. But Microsoft’s first-party use of it for Copilot Pages and Copilot Notebooks works differently. Copilot Pages and Copilot Notebooks content counts against your organisation’s existing SharePoint storage quota — there’s no separate Azure bill for it. The user-owned container has a hard ceiling of 25 TB, which can’t be raised or lowered.

Lifecycle: tied to the user, with sharp edges

The container’s lifecycle is bound to its owner. Content is private by default, much like OneDrive — there’s no forced sharing. When the owning user’s account is deleted, the container is scheduled for deletion and follows the same lifecycle as OneDrive, including a manual handoff step at departure and the option to permanently reassign the container to a new owner.

One critical warning for anyone planning their data protection strategy: there is no end-user recycle bin for Copilot Notebooks. If a notebook is deleted, neither the user nor an administrator can recover it. That’s a meaningful gap compared to the recycle-bin safety net we take for granted in SharePoint and OneDrive, and it’s worth flagging to end users before they start relying on Notebooks for anything important.

Why this matters

Copilot Notebooks feel lightweight and personal, but underneath sits real enterprise-grade storage that you already know how to govern — just wearing a new name. Knowing it’s SharePoint Embedded, that it surfaces as “Loop” in your admin tools, that it counts against SharePoint quota, and that it has no recycle bin turns “somewhere in the cloud” into something you can actually manage.

Copilot Notebooks storage & governance

Overview of Copilot Pages and Copilot Notebooks storage — the user-owned container, “Pages”/”My workspace” naming, the “Loop” application name in admin tools, 25 TB limit, quota, lifecycle, and the no-recycle-bin warning: https://learn.microsoft.com/en-us/microsoft-365/loop/cpcn-storage
Summary of governance, lifecycle, and compliance capabilities for Copilot Pages and Copilot Notebooks — what Purview/compliance features are supported (eDiscovery, Legal Hold, retention, Customer Lockbox, Conditional Access, etc.): https://learn.microsoft.com/en-us/microsoft-365/loop/cpcn-compliance-summary

SharePoint Embedded platform

SharePoint Embedded overview — API-only model, tenant partition, File Storage Containers, data residency, Purview controls: https://learn.microsoft.com/en-us/sharepoint/dev/embedded/overview
Limits and calling patterns — the 25 TB per container, 250 GB file size, and other hard limits: https://learn.microsoft.com/en-us/sharepoint/dev/embedded/development/limits-calling
Container types — how a container type couples 1:1 with an owning app, plus billing classifications: https://learn.microsoft.com/en-us/sharepoint/dev/embedded/getting-started/containertypes
What’s new in SharePoint Embedded — handy for keeping the post current as the platform evolves: https://learn.microsoft.com/en-us/sharepoint/dev/embedded/whats-new

The MSP Skills Gap Nobody Is Talking About Yet

I had a conversation with an MSP owner last week that has been rattling around in my head ever since. He was telling me, proudly, about how his team had just finished a big project hardening a client’s endpoint stack. Patching, EDR, conditional access, the lot. Then almost as an afterthought he mentioned the same client had quietly turned on Copilot for sixty users and was already building their first agent in Copilot Studio. He had no plan for any of it. No policy, no review process, no clear idea who in his team would actually own it. And here is the uncomfortable part. He is not unusual. He is the rule.

The growth in AI agents inside SMB environments is going to be the steepest curve we have seen in years, and most MSPs are walking into it carrying the wrong toolkit. The skills that built a successful managed services business over the last decade are not the skills that will keep customers safe and productive over the next one. That gap is widening every week, and very few MSP owners I speak to have noticed.

Agents are not endpoints

For twenty years MSPs have been organised around things. Devices, servers, mailboxes, firewalls. You patch them, monitor them, back them up, replace them. The whole MSP operating model — RMM, PSA, ticketing, SLAs — assumes a world of static assets that misbehave in fairly predictable ways.

An AI agent is none of those things. It is not an endpoint. It does not sit still. It reads documents in SharePoint, drafts replies in Outlook, pulls data from line-of-business systems, and acts on behalf of a user across surfaces the MSP has never had to think about as a single connected thing. When a Copilot agent fetches the wrong document and pastes confidential numbers into an external chat, no RMM alert is going to fire. The questions are different too. Not “is it patched?” but “what did it do today, and why?” That is a governance and behaviour problem, not an infrastructure one.

The new skill set is governance, data and prompts

Managing agents well leans on a set of muscles most MSPs have never had to build. Understanding identity scope in Entra so an agent cannot reach data it has no business touching. Configuring sensitivity labels and DLP in Purview so a chatty agent does not quietly become a leak. Reviewing prompt design and grounding sources in Copilot Studio before an agent is let near real users. Watching audit logs in the Microsoft 365 admin centre for patterns of agent behaviour that look off.

This is closer to the work of a data steward or a security analyst than a traditional systems engineer. It is slower, more interpretive, and more about judgement than ticket throughput. It rewards curiosity and writing skills as much as PowerShell. The MSP business model has not been built for that kind of work, and the hiring pipeline certainly has not.

The retraining window is now

Here is the bit that worries me. Customers are going to assume their MSP has this covered. They will turn on Copilot, build agents in Copilot Studio, plug them into their CRM, and look across the table expecting the same calm competence they get for backups. When something goes wrong — a leaked document, an agent that quietly emails the wrong list, a workflow that has drifted off purpose — they will ring their MSP. And most will not be able to help.

The MSPs that get ahead of this will start small and start now. Pick one client, one agent, and learn it end to end. Read the audit logs. Write the policy. Build the review cadence. The technical hardening skills will still matter. They are just no longer enough on their own.

The Invisible Business

I had a conversation recently with a business owner who told me they were “flat out.” Every week was packed. The team was busy. Revenue was coming in. But when I asked a simple question — what’s actually driving your growth right now? — the room went quiet.

Not because they didn’t care. Because they genuinely didn’t know.

This is more common than most people want to admit. You can run a business for years, keep the lights on, even grow a bit, all without really understanding which activities are pulling their weight and which ones are just filling the calendar. And the longer you go without that clarity, the harder it gets to make good decisions about where to invest next.

Busy Is Not the Same as Productive

There’s a comfortable illusion in being busy. If the inbox is full and the meetings are back-to-back, it feels like progress. But activity isn’t the same as impact. I’ve seen businesses pour hours into client work that barely breaks even while ignoring a service line that customers are quietly asking for. The information was there — buried in emails, mentioned in meeting notes, sitting in a spreadsheet nobody opened twice.

The problem isn’t a lack of data. Most businesses running Microsoft 365 are swimming in it. Every email thread, every Teams conversation, every shared document carries a signal about what matters and what doesn’t. The problem is that nobody’s stepping back to read the pattern.

Your Business Already Knows — You Just Haven’t Asked

This is where I think Copilot changes the equation in a way that actually matters. Not because it does the work for you, but because it helps you see what’s already happening inside your own organisation.

Think about it practically. You can open Excel, point Copilot at your last twelve months of client revenue, and ask it to show you which accounts grew, which ones shrank, and where the margin actually sits. That’s a conversation you can have in five minutes that most business owners never get around to having at all.

Or take something even simpler. Ask Copilot in Outlook to summarise what a particular client has been emailing about over the past quarter. Patterns emerge quickly — repeated questions, unmet needs, opportunities you’ve been walking past every day without noticing them.

In Teams, after a string of internal meetings, you can ask Copilot what decisions were made and what follow-ups were assigned. Not because you weren’t paying attention, but because the sheer volume of conversations makes it nearly impossible to hold the full picture in your head. Most of us don’t have a visibility problem. We have an attention bandwidth problem. The data is there. We just need a better way to surface it.

Clarity Before Growth

I’ve come to believe that the single biggest barrier to scaling a small business isn’t capital, or people, or even time. It’s visibility. If you can’t see where value is being created — and where it’s leaking — you end up scaling the wrong things. More staff on a service that doesn’t pay. More marketing for an offer nobody’s responding to. More meetings about problems that aren’t the real problem.

The businesses I see growing well right now aren’t necessarily working harder. They’re just clearer on what deserves their attention. And increasingly, that clarity comes from asking better questions of the tools they already have open on their screen every morning.

You don’t need a business intelligence platform or a consulting engagement to start. You need the habit of asking — regularly, specifically — what’s working and what isn’t. Copilot won’t run your business for you. But it will hold up a mirror. And sometimes, that’s exactly the thing you’ve been missing.