What is AI enablement, and how is it different from tool training?

It is not tool training and it is not adoption psychology. It is a structured program that starts by showing your leadership team what AI-native work actually looks like, then builds real capability into your business, desk by desk. Most organisations that skip straight to training end up asking AI to do incremental versions of what they already do. Enablement starts with the mindset shift so the ideas that follow are the right size.

What is the Art of the Possible session?

A two-hour session for your leadership team, run in person or online. It has three parts: a plain-English grounding in where AI actually is today and where it is heading over the next few years; live demonstrations built on your own business problems, not generic examples, so the room sees something working on their data; and a facilitated discussion of what this means specifically for your organisation, including where the value sits, what changes for leaders, and the common mistakes to avoid. Ben Ross, Propel's founder, delivers this session personally. Groups typically run from a handful of executives up to larger cohorts split by function.

What happens during the enablement week?

A Propel consultant sits alongside your team, typically for a week, working on real tasks and documents rather than hypothetical exercises. The week builds as much of your priority list as can be built in that time, leaves you with a working skills library your team owns, and surfaces the shortlist of bigger opportunities as a natural by-product of trying to build each item.

Do we need a separate strategy or discovery phase first?

Not necessarily. For a smaller team with a clear priority list, we go straight to the enablement week and let the build surface what matters most; a workshop rarely tells you more than the attempt itself does. For larger, multi-function transformations, a structured discovery phase earns its place: executive interviews, opportunity assessment against feasibility and impact, and a strategy and roadmap the board can act on. We size this to the problem rather than defaulting to the heavier version.

What can actually be built in a week, versus what needs a longer build afterwards?

Anything that is document in, document out is available immediately. Anything that needs live data moving between your systems on a schedule needs proper engineering. We are explicit up front about which of your priorities fall into each category.

What happens after the enablement week - are we locked into a bigger build with Propel?

No. Any roadmap or recommendations become your property once paid for. You are free to build it yourselves, bring in another partner, or continue with Propel. We deliberately do not price or scope a build phase until the discovery work has identified what is actually worth building - you only commission what has earned its place.

Can this run alongside Copilot or another tool we already use?

Yes. Your existing tool typically stays as the baseline for everyone, while a small group of super users moves onto Claude, because that is where the deeper skills and automation work happens. Which model or platform to standardise on is a decision for your leadership team, not something that should be settled by whoever opened the first account.

Engagements are scoped to your priorities and quoted as a fixed price, built up from the time we expect it to take. There is no standard package price because a six-person firm and a multi-site enterprise need different amounts of work. Get in touch and we will size it against your actual list.

What do we need to prepare before you arrive?

A prioritised list of the tasks or problems you want help with, confirmation of which systems are actually in use day to day, and a decision on who our consultant sits with on day one. If we are building demonstrations ahead of a session, real documents to work from (a contract, a model, a report) make the difference between a generic demo and one that lands.

What does our IT team need to set up in advance?

A short list, and none of it is exotic, but it is worth starting the conversation early because managed service provider turnaround can run to days or weeks: confirm staff can install the current Claude desktop app; confirm Cowork is switched on for each user, since the skills and automation work depends on it; have a Microsoft 365 admin approve the connector (access follows each person's existing permissions, so nobody sees anything they cannot already see); check whether your Teams tenant allows meeting transcription, which AI needs to summarise a meeting; and decide whether you want single sign-on set up for the Claude account.

Can training be delivered online, and how many people can attend?

Yes, either in person or online, and we will co-design the format with you. Executive sessions typically run from around six people up to fifteen; larger cohorts run well over video conferencing split into workshops by function.

How quickly can we start?

Once we have agreed the shape of the engagement, we hold consultant availability for a nominated week and ask for a quick decision to lock it in. For a straightforward enablement week this can happen within a matter of weeks. For a larger transformation program, allow one to two months for a considered start, though we can begin preparatory work ahead of signature.

What do we walk away with at the end?

Everything is handed to you and owned by you: training materials your team can reuse, a working skills library with named owners, configuration guides for your IT team, and - where relevant - an acceptable use policy with examples drawn from your own week. Nothing depends on Propel remaining involved.

Is our data used to train the models?

No. Data on Claude Team and Enterprise plans is not used to train Anthropic's models, on the same basis as Microsoft 365. Where the data actually sits differs by product: Claude's standard plans currently process and store data in the United States by default; Australian-region processing is available through the API via AWS Bedrock in Sydney, though that generally applies to software we build for you rather than everyday chat use. Anthropic has been expanding local infrastructure, so this is worth checking against their current position at the time you engage - we will always give you the accurate answer for your specific setup rather than a generic one.

Who owns what we build together?

You do. Roadmaps, use-case registers, prompts, skills and any code built for you become your intellectual property once the engagement is paid for. The only thing we retain is our own background IP - the frameworks, methods and general-purpose tooling we bring to every client, which no consultancy can sign away to a single one.

How do you approach governance for a regulated business?

We deliberately keep policy-writing separate from the enablement week itself, because a policy is far better informed by a week of real usage than one drafted cold. The Art of the Possible session covers what a board or regulator will ask and how to think about acceptable use in your context; once the enablement week has surfaced the real use cases and risks, we can help your compliance team turn that into a proper acceptable use policy and controls as a short, separately scoped piece of work.

Are you ISO 27001 certified?

Yes. Propel is ISO 27001 certified and a registered Anthropic partner with Claude-certified consultants, as well as a Microsoft partner.

What kind of results have other clients seen?

Enablement work is deliberately measured, not just delivered. Examples from recent engagements include an agentic merchant processing system that doubled output while cutting costs by around a third, an AI-assisted design workflow that cut sampling time by 60 per cent, and a financial analysis agent that took research turnaround from weeks to minutes. At one large-scale rollout, daily AI usage quadrupled within four weeks and low adopters fell by 70 per cent. Every engagement is built to leave capability behind, not a dependency on us.

// Corporate AI Training

AI Enablement. Skills, not slide decks.

Skip the frameworks and the six-month roadmaps. We put your team hands-on with AI from the first session — building real automations and agents inside your business, with the same tools we use every week.

Book a discovery call

Whole team enablementMicrosoft CopilotClaudeChatGPTGrok

// the propel claim

4× the AI usage in four weeks doesn’t come from buying more licences.

The firms pulling ahead aren’t the ones with the most seats — they’re the ones whose people actually build with AI every day. That doesn’t happen in a demo or a slide deck. It happens with hands on the keyboard, on real work, from session one — which is exactly the work we do, in the room, alongside your team.

// the gap we close

Your team knows AI could change how they work. They just need to build with it.

Most teams run on spreadsheets, specs and compliance docs — and most AI training stops at the demo. We do the opposite: every session ends with something working, applied to the work your team actually does.

// Services

Hands-on workshops — your team builds in the first session
Innovation days that produce working prototypes, not backlogs
Embedded implementation of automations and AI agents
Coaching for leaders and internal AI champions
Prompting, tooling and workflow design for ChatGPT, Claude and agents
No tech background required — we meet your people where they are

// TRAINING PACKAGES

Three packages, one approach

All hands-on from session one, all tool agnostic, none requiring a tech background. Pick the depth that matches the club's ambition.

Foundations

Your team can use AI, in one day.

One high-energy day on site — foundations session in the morning, hands-on prompting workshop in the afternoon. Everyone builds with AI on their own real work before the day is out.

Includes

Session tuned to the club's tool stack
Prompt cheat-sheet by role
Recording for staff who miss it

For: teams starting out, or leaders who want appetite and use cases surfaced fast.

Momentum

Your team uses AI daily — 4× the usage in four weeks.

A four-week program: repeated foundations sessions for full coverage, a brown-bag deep-dive series, role-specific workshops, and desk-side support days working shoulder-to-shoulder on live work.

Includes

Prompt guids and internal reference page
Executive briefing
Before/after adoption pulse

For: organisations that want AI as a daily habit, not a memory of a good workshop. The package we recommend most often.

Embedded

AI capability that outlasts us.

Six to eight weeks, whole of organisation — everything in Momentum at full scale, plus build-your-own-agent workshops per team and 1:1s producing a validated use-case backlog.

Includes

Internal champions identified and coached
Adoption dashboard
Steering-committee reporting

For: businesses treating AI capability as a strategic program — finish with trained people, named champions, hard adoption data and a costed backlog of automation opportunities.

Package	Foundations	Momentum	Embedded
Duration	1 day	4 weeks	6–8 weeks
Hands-on from session one	✓	✓	✓
Tool agnostic — your stack	✓	✓	✓
Role-specific workshops	–	✓	✓
Deep-dive series + desk-side support	–	✓	✓
Prompt guides + internal reference page	–	✓	✓
Executive briefing	–	✓	✓
Adoption measurement	–	Pulse survey	Live dashboard
Build-your-own-agent workshops	–	–	✓
Validated use-case backlog	–	–	✓
Internal champions coached	–	–	✓

Any package can be extended with ongoing coaching and champion support (04 · Coach).

// why this works

The tools we use are the tools we teach.

We're practitioners, not lecturers. Everyone who works with your team has built with AI this week — inside real businesses, on real problems. We teach from this week's tools, not last year's playbook.

Microsoft CoPilot

Google Gemini

Anthropic Claude

OpenAI ChatGPT

X.ai Grok

// proof · canaccord genuity

We quadrupled AI usage at a global investment bank in four weeks.

At Canaccord Genuity, we ran hands-on training, 213 one-to-one sessions and embedded build across Sydney, Melbourne, Perth and Brisbane — turning a firm that was barely using AI into one where nine in ten staff use it daily.

AI usage in four weeks
19,464 → 76,799 interactions

92%

of staff now use Copilot
low adopters down 70%

213

1:1 enablement sessions
173 unique staff supported

4.64

avg session rating (of 5)
no rating below 4 stars

I now have a clearer understanding of how it functions, and how to apply it effectively in my daily tasks.
Canaccord Genuity staff, post-engagement

// let's talk

Ready to enable your team?

Tell us where your team is with AI today. We'll come back within a day with a view on whether we're the right fit and what a first workshop could look like.

Book a discovery call Or see AI Consulting

// frequently asked

How it works

What is AI enablement, and how is it different from tool training?: It is not tool training and it is not adoption psychology. It is a structured program that starts by showing your leadership team what AI-native work actually looks like, then builds real capability into your business, desk by desk. Most organisations that skip straight to training end up asking AI to do incremental versions of what they already do. Enablement starts with the mindset shift so the ideas that follow are the right size.
What is the Art of the Possible session?: A two-hour session for your leadership team, run in person or online. It has three parts: a plain-English grounding in where AI actually is today and where it is heading over the next few years; live demonstrations built on your own business problems, not generic examples, so the room sees something working on their data; and a facilitated discussion of what this means specifically for your organisation, including where the value sits, what changes for leaders, and the common mistakes to avoid. Ben Ross, Propel's founder, delivers this session personally. Groups typically run from a handful of executives up to larger cohorts split by function.
What happens during the enablement week?: A Propel consultant sits alongside your team, typically for a week, working on real tasks and documents rather than hypothetical exercises. The week builds as much of your priority list as can be built in that time, leaves you with a working skills library your team owns, and surfaces the shortlist of bigger opportunities as a natural by-product of trying to build each item.
Do we need a separate strategy or discovery phase first?: Not necessarily. For a smaller team with a clear priority list, we go straight to the enablement week and let the build surface what matters most; a workshop rarely tells you more than the attempt itself does. For larger, multi-function transformations, a structured discovery phase earns its place: executive interviews, opportunity assessment against feasibility and impact, and a strategy and roadmap the board can act on. We size this to the problem rather than defaulting to the heavier version.
What can actually be built in a week, versus what needs a longer build afterwards?: Anything that is document in, document out is available immediately. Anything that needs live data moving between your systems on a schedule needs proper engineering. We are explicit up front about which of your priorities fall into each category.
What happens after the enablement week - are we locked into a bigger build with Propel?: No. Any roadmap or recommendations become your property once paid for. You are free to build it yourselves, bring in another partner, or continue with Propel. We deliberately do not price or scope a build phase until the discovery work has identified what is actually worth building - you only commission what has earned its place.
Can this run alongside Copilot or another tool we already use?: Yes. Your existing tool typically stays as the baseline for everyone, while a small group of super users moves onto Claude, because that is where the deeper skills and automation work happens. Which model or platform to standardise on is a decision for your leadership team, not something that should be settled by whoever opened the first account.

Practicalities

How is this priced?: Engagements are scoped to your priorities and quoted as a fixed price, built up from the time we expect it to take. There is no standard package price because a six-person firm and a multi-site enterprise need different amounts of work. Get in touch and we will size it against your actual list.
What do we need to prepare before you arrive?: A prioritised list of the tasks or problems you want help with, confirmation of which systems are actually in use day to day, and a decision on who our consultant sits with on day one. If we are building demonstrations ahead of a session, real documents to work from (a contract, a model, a report) make the difference between a generic demo and one that lands.
What does our IT team need to set up in advance?: A short list, and none of it is exotic, but it is worth starting the conversation early because managed service provider turnaround can run to days or weeks: confirm staff can install the current Claude desktop app; confirm Cowork is switched on for each user, since the skills and automation work depends on it; have a Microsoft 365 admin approve the connector (access follows each person's existing permissions, so nobody sees anything they cannot already see); check whether your Teams tenant allows meeting transcription, which AI needs to summarise a meeting; and decide whether you want single sign-on set up for the Claude account.
Can training be delivered online, and how many people can attend?: Yes, either in person or online, and we will co-design the format with you. Executive sessions typically run from around six people up to fifteen; larger cohorts run well over video conferencing split into workshops by function.
How quickly can we start?: Once we have agreed the shape of the engagement, we hold consultant availability for a nominated week and ask for a quick decision to lock it in. For a straightforward enablement week this can happen within a matter of weeks. For a larger transformation program, allow one to two months for a considered start, though we can begin preparatory work ahead of signature.
What do we walk away with at the end?: Everything is handed to you and owned by you: training materials your team can reuse, a working skills library with named owners, configuration guides for your IT team, and - where relevant - an acceptable use policy with examples drawn from your own week. Nothing depends on Propel remaining involved.

Security, IP and governance

Is our data used to train the models?: No. Data on Claude Team and Enterprise plans is not used to train Anthropic's models, on the same basis as Microsoft 365. Where the data actually sits differs by product: Claude's standard plans currently process and store data in the United States by default; Australian-region processing is available through the API via AWS Bedrock in Sydney, though that generally applies to software we build for you rather than everyday chat use. Anthropic has been expanding local infrastructure, so this is worth checking against their current position at the time you engage - we will always give you the accurate answer for your specific setup rather than a generic one.
Who owns what we build together?: You do. Roadmaps, use-case registers, prompts, skills and any code built for you become your intellectual property once the engagement is paid for. The only thing we retain is our own background IP - the frameworks, methods and general-purpose tooling we bring to every client, which no consultancy can sign away to a single one.
How do you approach governance for a regulated business?: We deliberately keep policy-writing separate from the enablement week itself, because a policy is far better informed by a week of real usage than one drafted cold. The Art of the Possible session covers what a board or regulator will ask and how to think about acceptable use in your context; once the enablement week has surfaced the real use cases and risks, we can help your compliance team turn that into a proper acceptable use policy and controls as a short, separately scoped piece of work.
Are you ISO 27001 certified?: Yes. Propel is ISO 27001 certified and a registered Anthropic partner with Claude-certified consultants, as well as a Microsoft partner.

Results

What kind of results have other clients seen?: Enablement work is deliberately measured, not just delivered. Examples from recent engagements include an agentic merchant processing system that doubled output while cutting costs by around a third, an AI-assisted design workflow that cut sampling time by 60 per cent, and a financial analysis agent that took research turnaround from weeks to minutes. At one large-scale rollout, daily AI usage quadrupled within four weeks and low adopters fell by 70 per cent. Every engagement is built to leave capability behind, not a dependency on us.