AI Solutions · AI Enablement
Get your whole team using AI the same way, safely.
Most businesses do not need a custom AI system. They need Claude or Copilot rolled out properly, with governance done well and every staff member working from the same playbook. This is that rollout.
Most businesses adopt AI tool by tool, with no shared rules, no record of what is connected, and no plan for what happens when someone leaves. AI Enablement builds that operating model, with a usage policy, practical guides and registers. Then we configure the chosen tool around how your team actually works.
When this is the right answer
When AI use has outgrown one person.
- You have 10 or more staff.
- Staff are already using AI independently.
- The rules about what goes into AI tools are unwritten.
- An owner wants consistency, not ten different habits.
The choice between Claude and Copilot depends on your business, mainly the systems your team already works in. The two products do not offer identical features, so we confirm what each can do for you before recommending one.
The method
Set up. Govern. Adopt.
Set up
Licences, workspace structure and security settings.
- Licences matched to roles
- Internal and client workspaces kept apart
- Security settings reviewed
More detail
We confirm who needs a licence and who does not. Shared instructions set how the tool works across the business, with personal instructions for each role. Where Claude is chosen, we also build custom skills for tasks your team repeats every week. Projects separate internal work from client work so nothing bleeds between them. Suitable connectors, such as SharePoint and Outlook, are added where the product supports them.
Govern
Usage policy, risk register and what data goes where.
- Plain-English usage policy
- Register of tools, owners and access
- Clear rules on data
More detail
The policy says what staff can put into AI tools, where a person still signs off, and how the business uses AI to support the team. The register records subscriptions, owners, access and what happens when someone leaves. We document onboarding and offboarding responsibilities, including who removes access. The risk register records each concern, the agreed control and who reviews it. Staff get a plain-language reference on which data belongs in which tool, including client information and material that needs approval before use.
Adopt
Role-based skills and prompts, training and a 30-day check-in.
- Skills and prompts for each role
- Team training
- 30-day check-in
More detail
Practical guides are written around your workflows. Training is by role, so people start with the tasks they repeat each week. Each person leaves with prompts and skills they can use the same day, kept in a shared library so good habits spread across the team instead of staying with one person. The workshop part of this is described on our training page. After 30 days we check what is being used and adjust.
What you get
Written down and set up.
- Licence setup and structure
- AI usage policy
- Risk and governance register
- Role-based skills and prompts
- Team training
- 30-day check-in
Scope
Scope follows your business.
The work is sized to your team, the systems it uses and how many roles need their own skills. A ten-person office and a fifty-person firm with several departments need different amounts of setup. We agree the scope with you, including the tools, connections, training and responsibilities. At the 30-day check-in, we review what staff are using, where they are getting stuck and which instructions need adjusting.
Experience
Rolled out before, at scale.
Ethan ran a Microsoft Copilot rollout across a 200-person agency while leading digital transformation in South Australian government. The same discipline of licences, rules and training applies at your size.
Related
Training and larger rollouts.
Hands-on workshops give staff time to practise with their own tasks, ask questions and check the results. Explore the workshop component on our training page.
For larger rollouts spanning several systems or teams, with broader coordination and change support, see Implementation and Change.
Questions about AI Enablement
Do we need this if we already have an AI policy?
A policy is one piece. We review the guidance you already have, set up the tool to match it, keep a register of who has access and train people to follow it. Existing material can be adapted to the agreed rollout rather than starting again.
Should we choose Claude or Copilot?
It depends on your business, mainly the software your team already uses. We compare what each can do for you before recommending one.
Does this replace our IT provider?
We work alongside your IT provider or internal IT team. They remain involved in access, security settings and connections to existing systems. Our work covers AI-specific governance, setup and adoption, with responsibilities agreed together before changes are made.
Do we need a Targeted Discovery first?
We confirm the starting point in a chat with Ethan. Clear requirements may be ready for implementation. Where a specific rollout problem needs investigation, Targeted Discovery can establish the requirements and a Solution Proposal before delivery is agreed.
How long does it take?
It depends on team size, the systems involved and the amount of role-specific preparation. We confirm a timeline once the scope is agreed, including training and the 30-day check-in. Staff availability and access to existing systems are part of that planning.