Role-specific playbooks
Written AI workflows for each role, with the prompts and steps that fit their tasks.
01 Service / Enablement
AI Enablement & Training
Your team, using AI well. Guardrails, prompts, and workflows built for their day-to-day, plus the change management that makes adoption stick.
02 What it is
Adoption is the product.
Most AI training is generic prompt tips that evaporate by the next Monday. We do it differently: we take the workflows your team already runs, build AI into them, and train each role on their own work. People adopt what saves them time on the tasks they already have.
The engagement also settles the questions that quietly block adoption: what data is safe to put where, which tools are approved, and what the rules are. Clear guardrails do more for usage than any amount of enthusiasm.
03 Who it's for
The problems this fixes.
Enablement is the right engagement when the tools exist but the usage does not.
- You bought AI tools and usage flatlined after week two.
- Every team uses AI differently, and nobody knows what is allowed.
- A few power users are far ahead, and nothing they know transfers.
- You need a usage policy people will actually follow.
04 How it works
Five steps to adoption that lasts.
We measure usage before and after, so you know whether it worked instead of hoping.
- 01
Baseline the team
Measure current usage and find where hours actually go, role by role.
- 02
Build role playbooks
AI workflows for each role, built on their real tasks, not examples.
- 03
Set the guardrails
A plain-language policy: which tools, which data, which use cases.
- 04
Train on real work
Hands-on sessions where people do their own tasks, not exercises.
- 05
Embed and follow up
Office hours and check-ins until the new workflows are the default.
05 What you get
What you get.
A usage policy
What is allowed, with which data, in which tools. Plain language, one page people read.
Training sessions
Live, hands-on, recorded, and run on your workflows. In English or Mandarin.
An adoption report
Usage measured before and after, with where it stuck and where it needs another pass.
06 Timeline & investment
What it costs, and how long.
Scope scales with team size and how many roles need their own playbook.
| Phase | Timeline | Pricing | What it covers |
|---|---|---|---|
| Baseline | 1 week | Fixed fee | Usage measurement, role interviews, and the adoption targets. |
| Playbooks & training | 1–3 weeks | Scoped by team size | Role playbooks, the usage policy, and the live sessions. |
| Embed & follow up | 2–4 weeks | Included | Office hours, check-ins, and the before-and-after adoption report. |
Figures are illustrative. Actual pricing is quoted after a short scoping call.
07 Questions
About this service.
Is this generic prompt training?
No. Every session runs on your workflows and your documents, and every role leaves with a playbook for their own tasks. Generic tips are what usually fail, and the reason this engagement exists.
How do you measure whether it worked?
We baseline usage and time-on-task before training and measure again after. The adoption report shows what changed, by role, with numbers instead of vibes.
Can you train in Mandarin?
Yes. Sessions, playbooks, and office hours are available in English and Mandarin, for teams working in either or both.
08 Related
Where to go next.
Other services
Make the AI spend actually get used.
Book a call and tell us where adoption stalled. We will tell you what it takes to get your team using AI well.