Skip to main contentSkip to navigation

Team workshops

A Claude workshop your finance team will actually use

Built for CFOs, Controllers, FP&A teams and the finance side of VC firms. Your team brings real files from the close, the forecast and the reconciliations, and we build Claude workflows on them, in the room.

Finance is where we start, not where it ends. The same day works for operations, legal, HR, sales and management, with every exercise rebuilt around that team's own documents.

  • About 4 hours per session
  • On your own files
  • Hebrew or English

Who it is for

Finance teams first, then anyone who works with documents

The content is tailored to the roles in the room. People who have never opened Claude and people who already use it both find their place.

  • CFOs and finance leaders

    See what Claude does well and what it does not, before deciding how it enters your team. And leave with a few workflows you can run this week.

  • Controllers and accounting

    Month-end close, reconciliations, exception checks and documentation. Repetitive work that can move into a structured process, with the review still in your hands.

  • FP&A

    Forecasts, variance analysis and management decks. You work on your actual spreadsheets, not a prepared sample.

  • VC and investment teams

    Reading company materials, screening inbound deals and drafting investment memos. A workshop that fits the pace of a fund.

  • The rest of the organization

    Operations, legal, HR, sales and management. Each group gets its own exercises, because a finance manager and a designer do not need the same day.

Formats

How the workshop runs

The flagship is two independent sessions. You can book either one alone, and the second is built to pick up where the first stops.

  • Foundations

    About 4 hours

    The first session, paced for everyone. Participants practice on files from their own work and leave with something that already runs.

  • Advanced

    About 4 hours

    For people already working with AI. We build repeatable workflows the team can keep using after the day ends.

  • At your offices or remote

    One day or two half-days

    On-site is the format we recommend, because a group sitting in one room feeds off it. Remote works well too, it is just not the same experience.

From the field

From people who sat in the room

Participants and clients who ran a workshop with us, as they wrote to us. No stars and no scores.

  • TLV Partners
  • IGP
  • ScyllaDB
  • Rakia Capital
  • It was excellent today. Shahar is really great. No comparison to workshops I did before.
    Gilat Bar-GutmanCFO, Toka
  • Thank you, Shahar. It was very enriching. It put things in order for me.
    Itay WeinbergerCEO, Datamint
  • It was wonderful, it really opened my appetite. I left with tools for day-to-day use, and that matters to me.
    Shai AngelCFO
  • It was really great. For someone like me who had only tried the basics, it gave a real sense of what can be done to work more efficiently, and how.
    Dana Yaacov-GarbeliCFO, A2Z

Pricing

Why there is no price list, and what sets the price

A workshop for eight people on their own documents and a rollout across several departments are not the same product. These are the things that move the number.

  • Group size

    In a small group we can open every participant's real file. In a larger one there is more independent practice, and the day takes a different shape.

  • On-site or remote

    On-site means travel, setup and sometimes a full day. Online removes that, and loses some of the energy of one room.

  • How much is built around your documents

    Exercises that run on your real spreadsheet and email thread need a discovery call first, and sometimes examples scrubbed of sensitive data. That work happens before the day itself.

  • Follow-up after the day

    A follow-up session, an open question channel or a check-in a month later. Each one changes what is left of the workshop, and the price.

  • Hebrew or English

    Materials in both languages take more than a literal translation. Professional terms have to carry over properly, and that adds preparation.

The full breakdown: what shapes workshop cost

Before you book

Questions about the workshop

What does the workshop day look like?

A session of about four hours, mostly work at the keyboard. A short explanation of what Claude does, then straight into exercises on files from your own work.

How many people can join?

There is no fixed cap. The smaller the group, the more one-on-one time each person gets. For larger teams we suggest several role-based groups rather than one giant session.

Do participants need Claude accounts beforehand?

Strongly recommended. If only part of the room can use the tool, the workshop turns into a demo. On the first call we check who already has access and what is missing, so everyone leaves with something they can use the next day.

Are the exercises tailored to our files and data?

Yes, and that is the main difference from a generic workshop. Before the day we ask about your processes, and sometimes ask for examples cleaned of sensitive details.

What does the team keep afterwards?

The things built in the room, ready to keep using, plus summary materials. Follow-up can be added: a check-in session, a question channel or a review a month later.

Can it run in Hebrew or English?

Both. You pick whichever fits the team, and the materials exist in both languages.

Let us scope the workshop for your team

Tell us what your team does today that takes too long, how many people, and which tools you already hold licenses for. We will come back with a proposal built around that.