Your team is the one who will run it, so your team is who learns

A closed cohort, only people from your company, built on the routine it already has. One day of in-person lab building together, and mentoring afterwards while the new way becomes habit.

  • closed cohortonly your team in the room
  • one day in personthe team builds, nobody sits through a lecture
  • your own routinethe exercises come from the work of the people in the room

What the team gets

  • Training on the real tool

    Sessions run inside the system your company actually uses, on the cases your team actually handles. Training in a demo environment teaches the demo.

  • The in-person AI lab

    One day, in the room, where the team brings the work it does today and leaves with part of it automated. Whatever gets built that day stays with the company.

  • A written playbook and prompts

    The steps of what was taught, with the prompts for your own operation. This is what saves the person who joins the team six months later.

  • Mentoring once the novelty wears off

    Recurring sessions with the people running it, to unblock what only shows up in real use. It is what stops the team reverting at the first snag.

How the cohort runs

Here FM does not stay on and run things for your team. The job is the opposite: step out and leave the knowing behind.

  1. What the team does today

    A survey of the tasks each role wants to tackle, before any date is booked. Without that list, training turns into theory.

  2. A track per role

    Support, sales and the person who closes the month do not need the same material. Same cohort, different paths through it.

  3. Lab day

    Hands on, with the team building. The day ends with what was built, documented, and a list of what they can carry on alone and what still needs support.

  4. Mentoring while it becomes habit

    Recurring sessions to adjust prompt, flow and process as the operation changes, with every decision written down.

What the team walks away with

  • The usage playbook and the prompts for your operation, in writing
  • Whatever was built in the lab, documented and in the company’s name
  • An honest list of what the team carries alone and what still needs support
  • The record of the decisions, for whoever joins the team later

True for every service

  • Scope closes before we start

    What is in and what is out comes out of the assessment, in writing, with a price. Anything you ask for later becomes a new scope you approve, never an invoice that shows up at the end.

  • What we deliver stays yours

    Code, documents, domain and accounts sit in your company’s name. If you stop working with FM one day, nothing that is already live goes down with it.

See every solution

Five questions, and we already start looking at your case

This is not a contact form. Each answer changes the next question, and at the end you get a read of your case on screen.

Start my assessment

Takes about two minutes. Nothing to book and nobody to talk to first.

What lands on your screen

  1. The read of your caseIt shows up right here when you finish answering, with nobody to wait for.
  2. What we would switch on firstIn the order that fits your operation, with the reason behind each choice.
  3. A copy in your inboxTo read again later, with a link back whenever you want it.