That is not a tool problem. It is a method problem.
Copilot that does the work is not adoption
Until recently, “Copilot in the company” meant a chat in Word, a suggestion in Outlook, sometimes a meeting summary. Since summer 2026, Microsoft has been selling something else. Copilot Cowork carries out tasks: email, files, calendar, search across what you are already allowed to see. Several models, a finished result, not only a draft.
That is true. It does not write the process.
A licence is not an owner. A seat is not a permission. An agent that “already did the work” is not a team that knows what to accept, what to reread, and what to refuse.
“Copilot training” catalogues orbit the product. Our first call often sounds like this: we bought Copilot, and nobody uses it.
Before it handles a week of mail
Cowork can, according to Microsoft, draft and send, file, prepare a document, and chain several apps. Sensitive actions are supposed to ask for approval. People click anyway. An “approve” button is not a policy.
Before the tool runs on a week of mail, four things, in writing:
- A named owner. Not “everyone has a licence.” Who sponsors, who is the lead, who cuts access.
- What may leave the tenant. Client files, HR, trade secrets: public, internal, confidential, forbidden. Copilot in Microsoft 365 is not free ChatGPT — and it is not a permit to paste everything.
- Who says no. Who rereads before something is sent. Who may stop a task in progress. Who trains the new people.
- A process. Human / Copilot / check, on one real flow: opening a ticket, a first pass on an email, a file summary, the skeleton of a proposal.
Three good cases beat fifteen committee ideas. See Approach.
If you want an AI consultant in Quebec to frame the mandate first, start there. This page is Copilot already (or soon) in the tenant — and the work that does not follow.
An agent is not a custom project
“Agent” became the word of 2026. In Copilot it often means an instruction that chains moves in Outlook, Teams, and Excel. It is not a model trained in your office. It is not a robot factory. It is not Copilot Studio as a deliverable.
We do not sell a fleet of agents. Most SMEs, nonprofits, and firms need a playbook and an internal lead, not an army. When a simple automation becomes obvious during the mandate, we say so — and we help specify it. We do not sell it as a product.
If you were asked to “build an agent” before you had a boring process, the answer is no. Not out of snobbery. Because without an owner and a check, the agent speeds up the mess.
Copilot training: your files, not a catalogue
There are catalogue courses for Microsoft 365 Copilot. Price, length, a room. That is not our work. We are not trying to beat them on “free Copilot training.”
We train on your files. Outlook, Excel, Teams, the templates your people open on Monday. Leadership and the role do not get the same workshop. People type. We correct. They leave with a versioned instruction, not a list of prompts of the moment.
If Monday’s tool is ChatGPT rather than Copilot, the page to read is ChatGPT training for companies. We have no allegiance to a platform. We look at what you already have, how sensitive the data is, and what the team will actually open.
The use frame is worked in the workshop, not six months later. An operational checklist — paste / don’t paste, free ChatGPT vs a workspace, a privacy impact assessment — is on Law 25 and AI. That is not a legal opinion. We are not the privacy officer. We do not write “Law 25 compliant.”
An agent that reads a whole Teams or Slack channel is an information system, not a weekend plugin. The privacy-impact conversation is theirs, with their counsel. We frame the use.
Formats: sprint, program, year-round
We fit the size of the company. We do not ask the company to fit us.
30-day sprint. A short diagnostic, one team workshop on their Copilot files, one process written down. Useful when the tenant is there and one team wants to stop circling.
90-day program. A roadmap, training by cohort, playbooks on two or three processes, coaching the leads. The format we get asked for most when the seats are paid and nobody uses them. This is where Copilot stops being the affair of two curious people.
Year-round support. Several teams, a training calendar, a quarterly review, a policy kept current. New people get a path. The leads keep the wheel. We do not sell it as the first product when there is still no process and no champion.
Lengths we already deliver: a leadership briefing (2 to 3 hours), role workshops (a half-day or a day). Training alone almost never holds — which is why the 30-minute rituals and the handover are described on Services.
Montreal, in the regions when the trip is worth it, or remote. The test: can people actually practice, on their files.
What you receive
- A diagnostic: who has a seat, who uses it, which tasks are worth it
- A workshop (or a path) on your Outlook / Excel / Teams, not a template
- A playbook: when Copilot gets opened, what it is given, what gets checked, what is never sent without a human
- A use frame clear enough to pin next to the screen
- Coaching for the leads, when the 90-day or year-round format includes it
You will not get: a model lab, Copilot Studio as a product, a tour of prompts, or pressure to buy more seats because we are a reseller. We are not. If the mandate has no sponsor and no first process to anchor, we say so before we invoice.
What it costs
It depends on how many teams and how long. A scoping sprint is not a year-long rollout. We give you a range on the first call, before any written proposal. Copilot licences are Microsoft’s. We do not resell them, and we do not pad them.
Page written in August 2026. Cowork and Microsoft’s product names move. The decision does not: an owner, a frame, a playbook — then the tool.