AI & Copilot
Copilot is not one thing. It is a dozen features with very different value, and most of the disappointment comes from turning all of them on at once. We start by finding the tasks worth automating.
What we do
Task selection first. We rank candidates by time saved and risk, then start with one.
Measured, not assumed. We record how long the task took before, so the effect is a number rather than a feeling.
Ownership internally. Someone at your end owns the agent. Without that it decays within months.
Honest about the limits. Where Copilot does not help, we say so instead of billing for it.
How we work
We rank the candidates by time saved and risk.
One agent, live, with a measurement against the baseline.
The owner internally can change it without calling us.
What a delivery contains
Finding where the time actually goes, before anything is rolled out
Copilot Studio agents for the questions that get asked over and over
Connections to your own sources, so answers are about you and not the internet
Permissions, so an agent never shows more than the user could see themselves
Rollout to one department first, measured before it widens
Training about tasks, not about buttons
A follow-up a few weeks in, once the first habits have formed
What it costs
The Copilot licence is the easy part: a fixed monthly price per user, set by Microsoft. What decides whether it pays for itself is something else, whether you give it to the right people, and whether the sources it reads are tidy enough for the answers to be worth trusting. We more often see money lost on licences handed to everyone than on too little work on adoption.
Start with the department where the tasks repeat most, measure for a few weeks, and widen from there. Ask for an estimate.
How long it takes
| Scope | Time |
|---|---|
| Finding where the time goes | half a day |
| First Copilot Studio agent in use | 2-4 weeks |
| Rollout to one department with measurement | 4-8 weeks |
| Wider rollout with governance | 2-3 months |
What takes time is not the technology but the tidying: documents that live in five places, and permissions set loosely because nobody had to think about them before. Copilot makes both visible immediately.
When this fits, and when it does not
Fits when
- You are already on Microsoft 365 and use Teams and SharePoint
- A lot of time goes to looking for something that exists
- The same questions go to the same people every week
- Somebody can own adoption internally
Does not fit when
- Permissions are not tidy, Copilot will surface what sits in the wrong place
- The documents are not digital yet
- The licence is to be given to everyone at once, without measurement
- The need is really an agent that does work, look at AI development
Questions we get
What is the difference between Copilot and Copilot Studio?
Microsoft Copilot is the assistant included with Microsoft 365 that helps an individual in Word, Outlook and Teams. Copilot Studio is the tool we build custom agents in, agents that answer your questions, against your sources, under your rules.
Will Copilot show people things they should not see?
It sees exactly what the user could see themselves, no more. The problem people meet is that permissions have been set loosely for years without anyone noticing. Copilot reveals that, it does not cause it.
Does everyone need a licence?
No, and giving it to everyone at once is usually the wrong move. Start where tasks repeat most, measure for a few weeks, and widen from there.
What if the answers are wrong?
Then it is usually the source, not the model. An agent reading an out-of-date document library gives out-of-date answers. That is why we start with which sources it may read.
Shall we talk this through?
Tell us briefly what you need and you get a concrete answer, and an estimate you can plan around.