Full Engagement · Online · 4-6 weeks
By the end, AI is part of how your organisation actually works.
A 4-6 week engagement where I map your workflows, build Copilot and Claude into your real processes, train each role group on their own tasks, and hand over full documentation. Everything is set up around how your organisation actually operates, not a generic implementation dropped into your environment.
Why this works
Switching Copilot on is not the same as using it
Most organisations go through the same cycle. Licenses are purchased, IT switches everything on, a vendor runs a demonstration, and then very little changes. The tools are there. The habits are not.
The reason is not that people are resistant to change. It is that nobody mapped how the work actually happens before setting anything up. Copilot configured around generic workflows does not survive contact with a real organisation. It gets ignored, then forgotten, then written off as something that did not work out.
The AI Enabled Workplace starts from the opposite direction. Before anything is built, I spend time understanding exactly how your organisation operates: where the hours go, how information moves, which tasks repeat, where decisions get made. The setup comes after that, not before.
What is included
Four phases, one engagement
Before touching any settings, I document how work actually happens.
I meet with the people who do the work: not just leadership, but the team members who process the documents, run the meetings, chase the approvals, and produce the reports. I ask where the hours go, where things get stuck, and what would change if those tasks took half the time.
By the end of Week 1 I have a documented picture of your workflows, your role groups, and the specific places where AI would make the biggest difference. This becomes the blueprint for everything that follows.
With the map complete, I set up Copilot and Claude inside your environment, configured around the workflows we identified.
- Copilot configured across Microsoft 365 apps relevant to each role group: Teams, Outlook, Word, Excel, SharePoint.
- Claude integrated for the heavier thinking work: longer documents, multi-step analysis, structured outputs that Copilot does not handle well.
- Workflows built and tested on real tasks, not sample data.
- Every setup decision documented and explained. Your team will know what was built and why.
Role-based Working Sessions for each group, built around the specific workflows set up in the build phase.
Each group gets sessions designed for their work: admin teams work on the tasks admin teams do, managers work on reporting and communication, frontline staff work on their daily processes. Nobody sits through a session built for a different role.
Each session includes a pre-session video so participants arrive ready, and a recap video afterwards so the learning does not disappear when people get back to their desks.
Responsible use is part of every session: data governance, what Copilot does and does not store, and how to use AI in a way that holds up to scrutiny. Covered at the start, not as an afterthought.
The engagement does not end at delivery.
Weeks 5 and 6 cover handover: full documentation of what was built and why, a governance basics guide, and a practical "what to do when things change" document, because Copilot updates regularly and your team needs to know how to adapt without calling me every time.
A 30-day check-in is scheduled before I leave. It is not an upsell, it is part of the engagement. After 30 days of using the setup in real conditions, questions come up that did not exist on delivery day. The check-in is there to answer them.
Who it is for
This is for you if
- Your organisation has been using Copilot for a while but nothing has really changed.
- You have done a training day before and the habits did not stick.
- You want AI embedded in how the work actually happens, not just used occasionally by a few people.
- You have 20 or more staff on Microsoft 365.
- You have someone responsible for IT or operations who can be the point of contact through the engagement.
- You are ready to commit to a 4-6 week engagement and you want it done properly.
This is not for you if
You have not tried AI with your team yet and want to start smaller. The Working Session is a better fit: one fixed-price session, your team, your real work.
You are not sure whether this is the right step. Start with an AI Readiness Review. It will give you a written picture of where AI can help most, and whether a full implementation is the right move.
Not sure yet?
Start with the free 7-minute assessment. It looks at where your organisation is right now and helps you understand which engagement makes the most sense.
Take the Free AssessmentPricing
Scoped to your organisation
The AI Enabled Workplace is scoped per engagement. A short discovery call of 20-30 minutes is all I need to give you a clear number. Get in touch and I will come back to you with an exact figure.
If you completed the AI Readiness Review
The cost of your Readiness Review is credited in full. The scoping call is shorter because we already have the map.
Delivered online
All sessions, workshops, and check-ins are delivered via video call. Everything is built inside your own Microsoft 365 environment.
How to think about the value
A 50-person team saving one hour per person per week is 200 hours a month returned to the organisation. At an average fully-loaded cost of £25 per hour, that is £5,000 a month. This engagement pays for itself in the first few weeks.
The full picture
Where this fits
Free Assessment
A general picture of where your organisation stands. Good for getting a sense of the landscape.
Take it nowAI Readiness Review
A specific, in-depth picture of your organisation: what you have, what you are missing, and what to do first. Maps into Week 1 of this engagement.
Learn moreThe Working Session
Half a day inside your own environment, training your team on their real tasks. The right entry point for one team before going all in.
Learn moreThe AI Enabled Workplace
The full engagement: map, build, train, embed. Every role group, every workflow, everything documented and embedded.
You are hereRefreshers and ongoing support
After the 30-day check-in, some organisations want refresher sessions as the team grows or as tools change. These are priced as Working Sessions and can be booked as needed.
What participants say
"Just brilliant once you know how."
Staff training participant · UK university
"I know I will start using this on a daily basis."
Staff training participant · UK university
"The whole session was very clear, focused and effective."
Staff training participant · UK university
"How quick and how polished the results were."
Staff training participant · UK university
Clients include
UK universities & professional organisations
Questions
Questions people ask before booking
How is this different from hiring an IT consultant to set up Copilot?
An IT consultant will configure the technical settings. That is not what this is. The AI Enabled Workplace maps how your organisation works first, then builds around that. It also includes training your team by role group and embedding the habits, which is where most implementations fail. The setup is only one part of it.
Do we need to have Copilot licenses already?
Not before the scoping call. Some organisations get licenses as part of the engagement. We talk through what you have and what you need during the discovery call.
What if our team is resistant to change?
This comes up often. The answer is usually that resistance comes from bad past experiences with technology that was imposed without explanation. The way this engagement runs, working with each role group on their own tasks, explaining every decision, building in responsible use from the start, tends to shift that. People are less resistant when the training is about their actual work and not someone else's demo.
What happens if Copilot changes after we finish?
It will. Microsoft updates Copilot regularly. The "what to do when things change" guide is part of the handover documentation specifically because of this. The 30-day check-in also catches anything that has shifted in the first month. For bigger changes, refresher sessions are available.
Can we start with one department and expand later?
Yes. Some organisations start with one team or one department. The Working Session is the right entry point for that. Once you have seen what it looks like in practice, the full engagement scales to the rest of the organisation.
How involved does our team need to be during the engagement?
The map phase requires time from the people who actually do the work, usually an hour each across a few sessions in Week 1. The build phase is mostly me. The training phase requires the team to show up for their sessions. The embed phase is light, mainly reviewing documentation and the check-in call. I try to keep the demand on your team's time as low as possible given what we are building together.
Ready to make AI part of how your organisation actually works?
A scoping call takes 20-30 minutes. By the end of it, you will have a clear picture of what the engagement looks like for your organisation and an exact price.