Approach
How an engagement runs.
Every engagement follows the same sequence, whether we are on-site at your offices or working remotely. You decide what we can see, your IT team grants and removes our access, and each stage ends with something written down that you can check.
The sequence
Six stages, in order.
Nothing is changed in your environment until you have read the findings and agreed what comes next.
-
01
Scoping call
We start with a conversation about who is involved, which systems are in scope and what is off-limits. We agree on the questions the engagement has to answer. A confidentiality agreement is signed before we are given any access.
-
02
Access and ground rules
Your IT team or managed service provider creates least-privilege accounts for us. Access is read-only first, and widened only when a specific change has been agreed. Client documents and company data do not leave your environment. All of our access is removed at the end.
-
03
Review, on-site or remote
We interview the people doing the work about how they actually use AI tools day to day. We then look at the systems behind those answers:
- admin consoles and tenant settings
- licences and the accounts assigned to them
- sign-in logs and connected applications
- browser extensions, and meeting and transcription tools
-
04
Findings
You receive a written report in plain language, ranked by risk to client confidentiality. Each finding names what we saw, why it matters, what to change and who owns the fix. We walk leadership and IT through it before anything moves.
-
05
Fix and build
We make the agreed configuration changes with your IT team, under your change process. Where you want AI in the work itself, we build the agreed workflows inside your existing systems and test them with the people who will use them.
-
06
Handover
Runbooks for your IT team, a session for the people who will use what we built, and a draft usage policy for leadership. Our access is revoked, and we confirm in writing that it has been removed.
Ground rules
Ground rules for every engagement.
Each of these is written into the scope before work starts.
- Access
- Granted by your team, removed at the end
- Client documents
- Stay in your environment
- Changes
- Agreed in writing, made with your IT team
- Publicity
- No names or case studies without written permission
- Point of contact
- One named person on each side
- Findings
- Reviewed with you before anything changes
Who is involved
Who should be in the room.
Decisions about AI touch leadership, infrastructure and the way your people find and reuse their work. We ask for three people from the start. In a smaller business one person may hold more than one role, as long as each is covered.
A sponsoring leader
Someone who can set priorities and approve the usage policy.
Your IT lead or service provider
The person who grants access, owns the configuration and makes changes with us.
Someone who knows the work
From operations or practice support: where documents live and how people actually work.
Next step
Book a scoping call.
Tell us who is involved and which systems matter. We will describe what the first stage would look like for you and what we would need from your team.