Thanks for writing · Team training
Here is what happens next.
Training runs over several sessions, never a single day. It is scoped on the call and quoted in the proposal.
Step by step
In order.
- 01We read your answers and reply by email
A person reads every inquiry. The reply says whether this is a fit, and if it is, when we could start.
- 02A short call
With you and whoever decides. We ask about the problem in your words, what you'd want to celebrate in a year, and what's in the way.
- 03A one-page proposal, in writing
Your problem, how we'd solve it, what's included, what it costs, and the first two weeks. One page, no deck.
- 04A one-page agreement books the start date
It says what's included, how payment works, how changes are handled, and that you own every account, file and output. The first payment holds your start date.
- 05Kickoff: the roles and the real tasks
Who does what, which tasks eat their days, and which tools they use. The sessions are built from that, not from generic tips.
- 06Sessions and written guides
Each session practises AI on that role's daily work. What's agreed gets written down in a short guide the team keeps.
- 07Check-ins
We come back to see what's actually used and fix what isn't.
What we’ll ask
Nothing to prepare for the call.
These come up on the call and in the kickoff. Read them so nothing surprises you.
- The roles on the team, and how many people in each
- The tasks that eat the most time in each role
- Which AI tools people use today, and what they distrust about them
- What 'the team uses it without me' would look like to you
Worth having ready
For when we start.
- 01A list of roles and the people in them
- 02Two or three real tasks per role, with an example
- 03The tools the team already pays for
In writing
What you can hold us to.
- The guides are written for your work and stay with you.
- Sessions run in your own accounts, on your own work.
- You own every account, file and output. Passwords never travel by email.
- Anything outside the agreed scope is priced in writing before it starts.