Corporate training programme

In 2 or 4 months your teams learn to produce with AI.

The programme is hands-on: little lecturing, a lot of practice. Participants work on their own tasks from the first week, every week closes with a concrete output, and those outputs are opened to the whole team on the LeftFlow training platform.

Programme scope

What the programme includes

The programme has three layers: training, platform and ongoing support. Everything each layer produces stays with your organisation.

01 · Training

A curriculum-based programme

Every participant learns by working on their own real tasks.

  • A curriculum for your organisation

    Written after the company analysis: where each department starts and which task is automated first.

  • 36 core lessons

    Three core parts are the same in every company; the fourth part is written from your organisation's real work.

  • Weekly live session

    An online session on the team's real work of that week; recordings stay on the platform.

  • Lesson library

    Short, written, hands-on lessons followed at each participant's own pace.

  • One-to-one technical support

    Direct support for any participant who needs help during setup or in a workflow.

  • Output of the week

    Every week closes with a concrete output; it is uploaded to the platform and opened to the team.

02 · Platform

The LeftFlow training platform

Throughout the programme the whole team moves forward on the same screen.

  • Board

    Where the participant stands this week, their next lesson and the live session time, on one screen.

  • Curriculum

    The 2 or 4 month roadmap opens month by month; completed weeks are marked.

  • Lessons

    The lesson library and live session recordings; each lesson shows as done, in progress or next.

  • Outputs

    Weekly outputs are uploaded; teams see each other's workflows and adapt them to their own work.

  • Team

    Progress department by department: where each team stands and who is in which week.

  • Documents

    How-to documents for the workflows build up on the platform and stay open after the programme.

03 · Support

Support during and after the programme

The team is not left on its own once the programme ends.

  • One-to-one technical support

    Direct support for any participant who needs help during setup or in a workflow.

  • Progress tracking

    Each participant's weekly outputs are followed on the platform; one-to-one follow-up is included in the 4-month programme.

  • Support after the programme

    One-to-one support and training continue once the programme ends.

  • Employees who join later

    New employees are brought in through the same curriculum and the same platform.

The lessons, recordings, documents and the workflows your teams build belong to your organisation.

Who it is for

Who benefits from this programme?

  1. 01

    Teams doing the work by hand

    When reports, lists, proposals and follow-ups depend on human memory.

  2. 02

    Companies that want to grow

    Those who want more output from the same team and the capability kept in-house.

  3. 03

    Non-technical teams

    You do not need to be a developer. The programme starts from zero.

Curriculum

Not a one-off training, a curriculum.

One topic a week, and at the end of each week a concrete output your team produced in its own work.

  1. Start

    Company analysis

    Which work runs by hand, which department should start where. The curriculum is written for your company.

    A curriculum written for you

  2. Month 1

    Setup and first output

    Claude Code is learned from scratch. Everyone works on their own job from the first week.

    A working workstation for everyone

  3. Month 2

    Deepening in production

    Each department builds its own flows and starts using them regularly.

    Working flows per department

  4. Month 3

    Data and automation

    Company data gets connected. Reports and alerts start running on their own.

    Reports that arrive on their own

  5. Month 4

    Measurement and continuity

    Dashboards are completed. Every flow is written down and spread across the whole team.

    Dashboards and a written operating guide

    The 4-month programme ends here

Lesson library

Three core sections are the same for every company. The fourth is written for yours.

  1. 01AI and Claude: what changes in your work
  2. 02What is Claude Code
  3. 03Setup: account, app, terminal
  4. 04Using the terminal: commands and terms
  5. 05Writing a good prompt
  6. 06Working with files: CSV, Excel, PDF
  7. 07CLAUDE.md: what it is and how to write it
  8. 08Plan mode and permissions: safe use
  9. 09Skills: automating repeated work
  10. 10MCP: connecting to outside systems
  11. 11Subagents: running work in parallel
  12. 12Scheduled tasks: every morning, on its own

  1. 13Getting data without an API: four methods
  2. 14Copy and extract quickly with Claude
  3. 15Instant Data Scraper: setup and basics
  4. 16Instant Data Scraper: pagination and multiple pages
  5. 17Instant Data Scraper: dynamic pages
  6. 18Pulling data from the browser with Claude
  7. 19Claude in the browser: multi-step flows behind a login
  8. 20Puppeteer: preparation and first script
  9. 21Puppeteer: pagination, login, waiting
  10. 22Puppeteer: hardening and error handling
  11. 23Competitor and sector data
  12. 24Social media and competitor data

  1. 25Cleaning raw data
  2. 26Splitting columns, fixing units and dates
  3. 27Combining several sources
  4. 28Analysis with Claude: asking the right questions
  5. 29Finding trends and comparisons
  6. 30Summary: what is happening at a glance
  7. 31Table and pivot views
  8. 32Showing the whole picture with a chart
  9. 33Building a simple dashboard
  10. 34Having reports written automatically
  11. 35Alerts: tell me when it changes
  12. 36An automatic report every morning

Example: six lessons written for a sales team

  1. 37Pulling a target customer list
  2. 38Invitation and follow-up emails
  3. 39Spotting customers from an event
  4. 40Producing content from a recording
  5. 41Podcast editing: from recording to episode
  6. 42From attendee to opportunity list
How it runs

What does a week look like?

Little lecturing, a lot of practice. The team works on its own job.

  1. 01

    Live session

    Once a week, online. We work on the team's real job of that week. Recordings are shared.

  2. 02

    Lessons

    Library lessons are followed at your own pace. Each lesson is short, written and practical.

  3. 03

    Technical support

    Any participant who needs help with a setup or a workflow receives one-to-one technical support.

  4. 04

    Output of the week

    Every week closes with a concrete output. It is uploaded to the board, so progress is visible.

Every participant's progress is followed regularly. One-to-one follow-up is included in the 4-month programme.

Result

What remains in your organisation after the programme?

  1. 01

    Workflows that run

    Reports, dashboards and automations each department built in its own work, documented and usable by the whole team.

  2. 02

    In-house capability

    A team that builds its own answer when a new need comes up, instead of waiting for outside help.

  3. 03

    Written how-to guides

    How every workflow runs is written down, so an employee who joins later can take it over from the same guide.

  4. 04

    Platform access

    The lesson library, live session recordings and weekly outputs stay accessible after the programme.

From the programme

This dashboard was built by a team in the programme.

The team of an e-commerce brand built it with its own data during a live session of the programme. They still run and improve it themselves.

This dashboard was built by a team in the programme.
Live screenshot. The brand name is kept confidential.
people in the team
8
live dashboards
3
lessons in the library
60+
Frequently asked

Questions

One live session a week, a lesson library you follow at your own pace, and one-to-one technical support. Every week closes with a concrete output. Lessons, session recordings, weekly outputs and progress all sit in one place on the LeftFlow training platform.

A board, the curriculum, the lesson library, weekly outputs and a team view. Participants see their next lesson and the live session time on the board, follow which week they are in on the curriculum, and see where each department stands in the team view. The platform stays open during the programme and afterwards.

Every workflow, command and report is added to the outputs section of the platform and documented. A workflow built by one department can be seen by other teams and adapted to their own work, so the same task is never built twice.

Yes. The programme teaches Claude Code from scratch. There is no prerequisite; any department can join, from sales to accounting.

There is no limit. You can start with a single department or with the whole company. Participants follow their own track according to their role.

In the 2-month programme everything is set up and each department builds and starts using its first flows. The 4-month programme adds connecting company data, reports and alerts that run on their own, measurement, and spreading the knowledge across the whole team.

Fully online: a weekly live session, a lesson library followed at your own pace, and one-to-one technical support.

Yes. One-to-one support and training can continue after the programme. Employees who join later are brought in through the same curriculum and the same platform.

Safe use is part of the curriculum: which data may be shared, how permissions are set and which tool is used where are written down at the start of the programme. Company data stays in your own environment.

Article 4 of the EU AI Act requires organisations that use AI systems to ensure a sufficient level of AI literacy among their staff. The programme provides structured, documented training in safe and effective AI use, and participation and progress are recorded. These records support organisations in demonstrating that obligation.

With a company analysis. Manual work, data sources and each department's starting point are mapped together, and the curriculum is written from that analysis.

Request a company analysis

In the analysis session, the work that runs by hand, your data sources and each department's starting point are reviewed together, and the curriculum is written from that session.

Request the analysis

We reply to every request within two business days.