Corporate

For your team, using your own work

Not a generic "AI awareness presentation". The day runs on examples taken from what your team actually does; at the end they hold not a slide deck but a working flow embedded in their own job.

Request a proposal →

Half day

3 hours

Awareness and first contact in a single session. The format where the team picks up the tools and tries something on their own work.

  • What AI tools actually do, and where they get stuck
  • Live practice on examples taken from your team's own work
  • What can be delegated, and what should not be
  • A simple usage guide so it spreads inside the organisation

Full day

6 hours

From awareness to implementation. By the end of the day the team holds a working flow embedded in their own job.

  • Everything in the half day
  • Picking one of the team's repetitive tasks and building it end to end together
  • Auditing the output: what to trust, how to check it
  • Practical limits around data and privacy
  • A short internal guide, written by the team itself, at the end of the day

How it proceeds

  1. Write

    Tell us how many people are on the team, what they do and what you want to solve — through the form or on WhatsApp.

  2. A short call

    We settle the scope together: which team, which format, which examples.

  3. Written proposal

    Content and examples are built around your processes; you receive a written proposal suitable for invoicing, contracts and internal approval.

  4. The session

    Closed group, live online. The day runs on examples taken from your team's own work.

Which subject?

Putting AI to work

The side that needs no coding. Delegating repetitive work, auditing the output, understanding which jobs are not suited to the tool.

Speaking the same language as the technical team

For non-technical teams: what the developers are actually saying, and why some jobs look "simple" and take long.

First contact with software

If you want to give your team code literacy; the group workshop, tailored to the organisation.

A mix of all three is possible too — if the team has both technical and non-technical people, that is usually how we build it.

Said up front

  • We are not a certification programme. At the end of the day your team holds something that works in their own job, not a certificate.
  • We are not turning your team into AI engineers. What we do is put the tools in the right place in their day.
  • We build the content around your organisation, so we cannot send a ready-made curriculum PDF. We need to understand what you do first.
  • If we think we are not a fit, we say so. If your team is already advanced, this workshop will be too basic for them.

Who are you contracting with?

Corporate training and the whole commercial relationship run through Waka Digital Limited; invoices and contracts are issued in that entity's name. Company number 1885497, NZBN 9429033751610.

The people in the room do not change — only the invoicing entity differs, and we say so up front so procurement is not surprised at contract stage.

Waka Digital Limited

Who runs the corporate side?

On corporate days two different needs usually sit side by side: the team picking up the tools, and management's question of "where do we fit this in?". Uğur runs the corporate side end to end: the training day, the organisation and the questions on the management side.

Uğur İnal

Uğur İnal

Partner · technology strategy and AI systems

The one who builds AI systems in production. Co-founder and interim CFO/CIO of Fjordland Group in New Zealand; technical lead at Waka Research. On corporate days he takes the management questions: what can be delegated, what should not be, and what it costs the organisation.

About · LinkedIn