Enterprise · Enablement

Make your own teams good at this.

Tools are the cheap part. The return comes when engineers, product managers and leaders know how to use AI well and when not to. We run practical, role-based training using your tools, your policies and examples from your own work.

Format
Live workshops, remote by default
Tracks
Engineering · Product · Leadership
Group size
Small cohorts, hands-on
Material
Built on your stack and use cases

Is this you?

Training is the right move when…

  • Licences for AI assistants have been bought and usage is uneven.
  • Engineers use AI coding tools but review standards have not caught up.
  • Product teams propose AI features without a way to judge feasibility or cost.
  • Leaders are asked to approve AI spend and want a working understanding, not a keynote.
  • There is an AI-use policy on paper that few people could describe.

What you get

Three tracks, one shared vocabulary

Engineering

Working with AI coding assistants safely, building with LLM APIs, retrieval and grounding, writing evaluations, and reviewing AI-written code. Exercises run in your own repositories.

Product and design

Spotting where AI fits a workflow, scoping a feature with its failure modes, estimating running cost, and writing acceptance criteria for something probabilistic.

Leadership

What current AI can and cannot do, how to read a business case, the questions to ask about risk and data, and how to set policy people will follow.

Playbooks you keep

Each track leaves written guidance tailored to your tools and policies, so new joiners can be brought up to the same standard.

How it works

How a track comes together

  1. Week 1

    Short discovery

    We look at the tools you have, your AI-use policy, and two or three real tasks from each group. We build the training around those.

  2. Week 2

    Tailor the material

    We rewrite the exercises for your stack and examples. You review the outline before anything is scheduled.

  3. Weeks 3–4

    Deliver in cohorts

    Live, hands-on sessions. People leave each one having done the thing, not watched it.

  4. After

    Follow-up clinic

    A session a few weeks later to work through what people hit in practice and adjust the playbooks.

Clear boundaries

What is and isn’t included

Included

  • Discovery of your tools, policies and real tasks
  • Tailored material for each track
  • Live delivery in small cohorts, in English, French or Portuguese
  • Written playbooks for each role
  • A follow-up clinic

Not included

  • Vendor certifications or exam preparation
  • Recorded generic courseware
  • Software licences for AI tools

Questions

What people ask us first

Is this generic AI literacy training?

No. A leadership session uses your business cases, and an engineering session runs in your codebase with your tools. That is the reason for the discovery week.

Which tools do you teach?

The ones you have chosen or are evaluating. We are not tied to a vendor and take no commission on tools.

Can training be delivered in French or Portuguese?

Yes. We work in English, French and Portuguese.

How does training connect to the rest of your work?

It stands alone, and it also makes everything else cheaper: trained teams take over systems faster after a Sprint. Some organizations start here because it is the lowest-risk first step.

We use these details only to reply to this request. No newsletters, no list. We aim to reply within one business day. See our Privacy Policy.

Book a callScope an assessment